Configuration Guide - Reliability (V100R005C01 02) PDF

Quidway S5300 Series Ethernet Switches
V100R005C01
Configuration Guide - Reliability
Issue 02
Date 2010-12-01
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 written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

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

Copyright © Huawei Technologies Co., Ltd.
Configuration Guide - Reliability About This Document
About This Document
Intended Audience
This document provides the basic concepts, configuration procedures, and configuration
examples in different application scenarios of the reliability supported by the S5300.
This document describes how to configure the reliability.
This document is intended for:
l Data configuration engineers

l Commissioning engineers
l Network monitoring engineers
l System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
time.
NOTE Provides additional information to emphasize or supplement

important points of the main text.
Issue 02 (2010-12-01) Huawei Proprietary and Confidential iii

About This Document Configuration Guide - Reliability
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

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

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

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

vertical bars. Several items or no item can be selected.
&<1-n> The parameter before the & sign can be repeated 1 to n times.
# A line starting with the # sign is comments.
Change History
Updates between document issues are cumulative. Therefore,the latest document issue contains
all updates made in previous issues.
Changes in Issue 02 (2010-12-01)

Based on issue 01 (2010-08-15), the document is Changed as follows:
l 3.6.2 Example for Configuring Crossed RRPP Rings with a Single Instance
Changes in Issue 01 (2010-08-15)

Initial commercial release.
iv Huawei Proprietary and Confidential Issue 02 (2010-12-01)

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

1 DLDP Configuration.................................................................................................................1-1
1.1 Introduction to DLDP......................................................................................................................................1-2
1.2 Configuring DLDP Functions.........................................................................................................................1-3
1.2.1 Establishing the Configuration Task......................................................................................................1-3
1.2.2 Enabling DLDP......................................................................................................................................1-4
1.2.3 (Optional) Setting the Operating Mode of DLDP..................................................................................1-4
1.2.4 (Optional) Setting the Interval for Sending Advertisement Packets......................................................1-5
1.2.5 (Optional) Setting the Delay Down Timer.............................................................................................1-5
1.2.6 (Optional) Setting the Interface Blocking Mode....................................................................................1-6
1.2.7 (Optional) Setting the Authentication Mode of DLDP Packets.............................................................1-7
1.2.8 Checking the Configuration...................................................................................................................1-7
1.3 Resetting the DLDP Status..............................................................................................................................1-8
1.3.2 Resetting the DLDP Status Globally......................................................................................................1-9
1.3.3 Resetting the DLDP Status of an Interface............................................................................................1-9
1.3.4 Checking the Configuration.................................................................................................................1-10
1.4 Maintaining DLDP........................................................................................................................................1-10
1.4.1 Clearing the Statistics of DLDP...........................................................................................................1-10
1.5 Configuration Examples................................................................................................................................1-11
1.5.1 Example for Configuring DLDP..........................................................................................................1-11
2 Smart Link and Monitor Link Configuration.......................................................................2-1

2.1 Smart Link and Monitor Link.........................................................................................................................2-2
2.2 Configuring a Smart Link Group....................................................................................................................2-2
2.2.2 Creating and Enabling a Smart Link Group...........................................................................................2-4
2.2.3 Configuring the Master and Slave Interfaces in a Smart Link Group....................................................2-4
2.2.4 Enabling the Sending of Flush Packets..................................................................................................2-5
2.2.5 (Optional) Configuring Load Balancing in a Smart Link Group...........................................................2-6
2.2.6 (Optional) Enabling Revertive Switching and Setting the WTR Time..................................................2-7
2.2.7 (Optional) Enabling the Receiving of Flush Packets.............................................................................2-8
2.2.8 Enabling the Functions of the Smart Link Group..................................................................................2-9
Issue 02 (2010-12-01) Huawei Proprietary and Confidential v

Contents Configuration Guide - Reliability

2.3 Configuring a Flow Control Policy in a Smart Link Group..........................................................................2-10
2.3.1 Establishing the Configuration Task....................................................................................................2-10
2.3.2 Locking Data Flows on the Master Interface.......................................................................................2-11
2.3.3 Locking Data Flows on the Slave Interface.........................................................................................2-12
2.3.4 Switching Data Flows Manually..........................................................................................................2-12
2.4 Configuring a Monitor Link Group...............................................................................................................2-13
2.4.2 Creating a Monitor Link Group...........................................................................................................2-15
2.4.3 Configuring the Uplink and Downlink Interfaces in a Monitor Link Group.......................................2-16
2.4.4 Setting the Revertive Switching Interval of a Monitor Link group.....................................................2-17
2.5 Maintaining the Smart Link..........................................................................................................................2-18
2.5.1 Debugging the Smart Link...................................................................................................................2-18
2.6.1 Example for Configuring Basic Functions of Smart Link...................................................................2-18
2.6.2 Example for Configuring Load Balancing Between Active and Standby Links of a Smart Link Group
.......................................................................................................................................................................2-22
2.6.3 Example for Applying the Smart Link Functions................................................................................2-26
3 RRPP Configuration..................................................................................................................3-1
3.1 Introduction to RRPP......................................................................................................................................3-2
3.2 RRPP Features Supported by the S5300.........................................................................................................3-2
3.3 Configuring Basic RRPP Functions................................................................................................................3-6
3.3.2 Creating Instances..................................................................................................................................3-8
3.3.3 Configuring Interfaces on the RRPP Ring.............................................................................................3-8
3.3.4 Creating an RRPP Domain.....................................................................................................................3-9
3.3.5 Specifying Protected VLANs...............................................................................................................3-10
3.3.6 Creating a Control VLAN....................................................................................................................3-11
3.3.7 Creating an RRPP Ring........................................................................................................................3-11
3.3.8 Enabling the RRPP Ring......................................................................................................................3-12
3.3.9 Enabling the RRPP Protocol................................................................................................................3-13
3.3.10 (Optional) Setting the Hello Timer and Fail Timer of an RRPP Domain..........................................3-13
3.3.11 Checking the Configuration...............................................................................................................3-14
3.4 Configuring RRPP Multi-Instance................................................................................................................3-15
3.4.2 Creating Instances................................................................................................................................3-18
3.4.3 Configuring Interfaces on the RRPP Ring...........................................................................................3-19
3.4.4 Creating an RRPP Domain...................................................................................................................3-20
3.4.5 Specifying Protected VLANs...............................................................................................................3-20
3.4.6 Creating a Control VLAN....................................................................................................................3-21
vi Huawei Proprietary and Confidential Issue 02 (2010-12-01)

3.4.7 Creating an RRPP Ring........................................................................................................................3-22

3.4.8 Enabling the RRPP Ring......................................................................................................................3-23
3.4.9 Enabling the RRPP Protocol................................................................................................................3-23
3.4.10 (Optional) Creating a Ring Group......................................................................................................3-24
3.4.11 (Optional) Setting the Link-Up-Delay Timer.....................................................................................3-25
3.4.12 (Optional) Setting the Hello Timer and Fail Timer of an RRPP Domain..........................................3-25
3.5 Maintaining RRPP.........................................................................................................................................3-27
3.5.1 Clearing RRPP Statistics......................................................................................................................3-27
3.5.2 Debugging RRPP.................................................................................................................................3-28
3.6.1 Example for Configuring a Single RRPP Ring....................................................................................3-28
3.6.2 Example for Configuring Crossed RRPP Rings with a Single Instance..............................................3-33
3.6.3 Example for Configuring Tangent RRPP Rings..................................................................................3-43
3.6.4 Example for Configuring a Single RRPP Ring with Multiple Instances.............................................3-51
3.6.5 Example for Configuring Crossed RRPP Rings with Multiple Instances(HW version)......................3-64
3.6.6 Example for Configuring Tangent RRPP Rings with Multiple Instances...........................................3-85
4 Ethernet OAM Configuration..................................................................................................4-1

4.1 Introduction to Ethernet OAM........................................................................................................................4-3
4.2 Ethernet OAM Supported by the S5300.........................................................................................................4-3
4.3 Configuring Basic Functions of EFM OAM...................................................................................................4-8
4.3.2 Enabling EFM OAM Globally...............................................................................................................4-9
4.3.3 Setting the Working Mode of EFM OAM on an Interface....................................................................4-9
4.3.4 (Optional) Setting the Maximum Length of an EFM OAMPDU........................................................4-10
4.3.5 Enabling EFM OAM on an Interface...................................................................................................4-10
4.4 Configuring EFM OAM Link Monitoring....................................................................................................4-12
4.4.2 (Optional) Detecting Errored Frames of EFM OAM...........................................................................4-13
4.4.3 (Optional) Detecting Errored Codes of EFM OAM.............................................................................4-13
4.4.4 (Optional) Detecting Errored Frame Seconds of EFM OAM..............................................................4-14
4.4.5 (Optional) Associating a Threshold Crossing Event with an Interface................................................4-15
4.5 Testing the Packet Loss Ratio on a Physical Link........................................................................................4-17
4.5.2 Enabling Remote Loopback of EFM OAM.........................................................................................4-18
4.5.3 Sending Test Packets............................................................................................................................4-19
4.5.4 Checking the Statistics on Returned Test Packets...............................................................................4-19
4.5.5 (Optional) Disabling Remote Loopback of EFM OAM......................................................................4-20
4.6 Configuring Basic Functions of Ethernet CFM............................................................................................4-21
Issue 02 (2010-12-01) Huawei Proprietary and Confidential vii


4.6.2 Switching the IEEE 802.1ag Version...................................................................................................4-23
4.6.3 Enabling Ethernet CFM Globally........................................................................................................4-23
4.6.4 Creating an MD....................................................................................................................................4-24
4.6.5 (Optional) Creating the Default MD....................................................................................................4-24
4.6.6 Creating an MA....................................................................................................................................4-25
4.6.7 Creating a MEP....................................................................................................................................4-26
4.6.8 Creating an RMEP...............................................................................................................................4-27
4.6.9 (Optional) Setting the MIP Creation Rule............................................................................................4-27
4.6.10 Configuring Continuity Check...........................................................................................................4-28
4.6.11 (Optional) Creating a VLAN..............................................................................................................4-30
4.7 Adjusting Parameters of Ethernet CFM........................................................................................................4-32
4.7.2 (Optional) Setting the Activation Time for Receiving CCMs from the RMEP...................................4-34
4.7.3 (Optional) Setting the Anti-Jitter Time During Alarm Restoration.....................................................4-35
4.7.4 (Optional) Setting the Anti-Jitter Time During Alarm Generation......................................................4-35
4.8 Configuring Fault Acknowledgement on the Ethernet.................................................................................4-36
4.8.2 (Optional) Performing 802.1ag MAC Ping..........................................................................................4-37
4.8.3 (Optional) Performing Gmac Ping.......................................................................................................4-38
4.9 Configuring Fault Location on the Ethernet.................................................................................................4-39
4.9.2 (Optional) Performing 802.1ag MAC Trace........................................................................................4-40
4.9.3 (Optional) Performing Gmac Trace.....................................................................................................4-40
4.10 Associating EFM OAM with an Interface..................................................................................................4-41
4.10.1 Establishing the Configuration Task..................................................................................................4-42
4.10.2 Configuring Association Between an EFM OAM Module and an Interface.....................................4-42
4.10.3 (Optional) Setting the Faulty-State Hold Timer.................................................................................4-43
4.11 Configuring Association Between an EFM OAM Module and an Interface..............................................4-45
4.11.2 Configuring Association Between an EFM OAM Module and an Interface.....................................4-46
4.12 Configuring Association Between EFM OAM Modules............................................................................4-48
4.12.2 Configuring Association Between EFM OAM Modules...................................................................4-49
4.13 Associating Ethernet CFM with an Interface..............................................................................................4-50
4.13.2 Configuring Association Between an Ethernet CFM Module and an Interface.................................4-53
viii Huawei Proprietary and Confidential Issue 02 (2010-12-01)

4.14 Configuring Association Between an Ethernet CFM Module and an Interface..........................................4-54

4.14.2 Configuring Association Between an Ethernet CFM Module and an Interface.................................4-56
4.15 Associating EFM OAM with Ethernet CFM..............................................................................................4-57
4.15.2 Associating EFM OAM with Ethernet CFM.....................................................................................4-58
4.16 Configuring Association Between Ethernet CFM and Ethernet CFM........................................................4-60
4.16.2 Configuring Association Between Ethernet CFM and Ethernet CFM...............................................4-61
4.17 Configuring Association Between Ethernet CFM and SEP........................................................................4-62
4.17.2 Configuring Association Between Ethernet CFM and SEP...............................................................4-63
4.18 Configuring the One-way Frame Delay Measurement in a VLAN............................................................4-64
4.18.2 Binding an MA to a VLAN................................................................................................................4-65
4.18.3 (Optional) Setting an Alarm Threshold for the One-way Frame Delay Measurement......................4-66
4.18.4 Configuring DM Frame Reception on a Remote MEP......................................................................4-66
4.18.5 Enabling the One-way Frame Delay Measurement in a VLAN........................................................4-67
4.19 Configuring the Two-way Frame Delay Measurement in a VLAN............................................................4-68
4.19.2 Binding an MA to a VLAN................................................................................................................4-70
4.19.3 (Optional) Setting an Alarm Threshold for the Two-way Frame Delay Measurement.....................4-70
4.19.4 Configuring DMM Frame Reception on a Remote MEP..................................................................4-71
4.19.5 Enabling the Two-way Frame Delay Measurement in a VLAN........................................................4-72
4.20 Maintaining Ethernet OAM........................................................................................................................4-73
4.20.1 Debugging EFM OAM.......................................................................................................................4-73
4.21 Configuration Examples..............................................................................................................................4-74
4.21.1 Example for Configuring EFM OAM................................................................................................4-75
4.21.2 Example for Testing the Packet Loss Ratio on a Link.......................................................................4-78
4.21.3 Example for Configuring Basic Functions of Ethernet CFM............................................................4-81
4.21.4 Example for Configuring the Default MD for Ethernet CFM............................................................4-89
4.21.5 Example for Configuring Association Between an EFM OAM Module and an Interface................4-96
4.21.6 Example for Configuring Association Between EFM OAM Modules..............................................4-98
4.21.7 Example for Configuring Association Between an Ethernet CFM Module and an Interface..........4-101
4.21.8 Example for Configuring Association Between an EFM OAM Module and an Ethernet CFM Module
.....................................................................................................................................................................4-105
4.21.9 Example for Configuring Association Between Ethernet CFM with Ethernet CFM.......................4-109
Issue 02 (2010-12-01) Huawei Proprietary and Confidential ix

4.21.10 Example for Associating Ethernet CFM with Smart Link.............................................................4-112

4.21.11 Example for Associating Ethernet CFM with RRPP.....................................................................4-119
4.21.12 Example for Associating SEP with Ethernet CFM........................................................................4-131
4.21.13 Example for Configuring the One-way Frame Delay Measurement in a VLAN..........................4-144
4.21.14 Example for Configuring the Two-way Frame Delay Measurement in a VLAN..........................4-148
5 BFD Configuration.....................................................................................................................5-1
5.1 Introduction to BFD........................................................................................................................................5-2
5.2 BFD Features Supported by the S5300...........................................................................................................5-2
5.3 Configuring Single-Hop BFD.........................................................................................................................5-4
5.3.2 Enabling BFD Globally..........................................................................................................................5-5
5.3.3 (Optional) Setting the Multicast IP Address of BFD.............................................................................5-5
5.3.4 Creating a BFD Session.........................................................................................................................5-6
5.3.5 (Optional) Configuring the Description of a BFD Session....................................................................5-7
5.4 Configuring the BFD Passive Echo Function.................................................................................................5-9
5.4.2 Configuring the BFD Passive Echo Function......................................................................................5-10
5.5 Configuring Multi-Hop BFD........................................................................................................................5-11
5.5.2 Enabling BFD Globally........................................................................................................................5-12
5.5.3 Creating a BFD Session.......................................................................................................................5-13
5.5.4 (Optional) Configuring the Description of a BFD Session..................................................................5-14
5.6 Configuring a Static BFD Session with Automatically Negotiated Discriminators.....................................5-16
5.6.2 Enabling Global BFD...........................................................................................................................5-16
5.6.3 Configuring a Static BFD Session with Automatically Negotiated Discriminators............................5-17
5.7 Adjusting the BFD Detection Parameters.....................................................................................................5-18
5.7.2 Adjusting the BFD Detection Time.....................................................................................................5-19
5.7.3 Setting the WTR Time of a BFD Session............................................................................................5-20
5.7.4 Setting the Priority of BFD Packets.....................................................................................................5-21
5.8 Setting the Interval for Sending Trap Messages...........................................................................................5-23
5.8.2 Setting the Interval for Sending Trap Messages..................................................................................5-24
5.9 Maintaining BFD...........................................................................................................................................5-24
5.9.1 Clearing the Statistics of BFD..............................................................................................................5-25
x Huawei Proprietary and Confidential Issue 02 (2010-12-01)

5.9.2 Debugging BFD...................................................................................................................................5-25

5.10.1 Example for Configuring Single-Hop BFD on a Layer 2 Interface...................................................5-26
5.10.2 Example for Configuring Single-Hop BFD on a VLANIF Interface.................................................5-28
5.10.3 Example for Configuring Multi-Hop BFD.........................................................................................5-31
6 VRRP Configuration.................................................................................................................6-1
6.1 Introduction to VRRP......................................................................................................................................6-3
6.2 VRRP Features Supported by the S5300........................................................................................................ 6-3
6.3 Configuring a VRRP Backup Group...............................................................................................................6-4
6.3.2 Creating a VRRP Group and Configuring the Virtual IP Address........................................................ 6-6
6.3.3 Setting the Priority of an Interface in a Backup Group..........................................................................6-7
6.3.4 (Optional) Configuring the Sending Mode of VRRP Packets in Super-VLAN.................................... 6-7
6.4 Configuring VRRP to Track the Interface Status............................................................................................6-9
6.4.2 Tracking the Status of an Interface.........................................................................................................6-9
6.5 Configuring VRRP to Tracking the BFD Session Status..............................................................................6-11
6.5.2 Tracking the Status of a BFD Session..................................................................................................6-12
6.6 Configuring VRRP Authentication...............................................................................................................6-13
6.6.2 Setting the Authentication Mode of VRRP Packets.............................................................................6-14
6.7 Optimizing the VRRP Performance..............................................................................................................6-16
6.7.2 Setting the Interval for Sending VRRP Advertisement Packets..........................................................6-17
6.7.3 Setting the Preemption Delay of Switches in a Backup Group............................................................6-18
6.7.4 Disabling a router from Checking Number of Hops in VRRP Packets...............................................6-19
6.7.5 Enabling the Ping to Virtual IP Addresses...........................................................................................6-19
6.7.6 Setting the Interval for Sending Gratuitous ARP Packets....................................................................6-20
6.8 Configuring mVRRP Backup Groups...........................................................................................................6-21
6.8.2 Configuring mVRRP Backup Group...................................................................................................6-23
6.8.3 (Optional) Configuring Member VRRP Backup Groups and Binding them to the mVRRP Backup Group
.......................................................................................................................................................................6-23
6.9 Configuring VRRP Version Upgrade...........................................................................................................6-25
Issue 02 (2010-12-01) Huawei Proprietary and Confidential xi

6.9.2 Configuring VRRPv3...........................................................................................................................6-26

6.10 Maintaining VRRP......................................................................................................................................6-27
6.10.1 Debugging VRRP...............................................................................................................................6-27
6.11.1 Example for Configuring VRRP in Master/Backup Mode................................................................6-28
6.11.2 Example for Configuring VRRP in Master/Backup Mode................................................................6-34
6.11.3 Example for Configuring VRRP Fast Switchover.............................................................................6-39
7 VRRP6 Configuration...............................................................................................................7-1
7.1 Introduction to VRRP6....................................................................................................................................7-2
7.2 VRRP6 Features Supported by the S5300......................................................................................................7-2
7.3 Configuring a VRRP6 Backup Group.............................................................................................................7-3
7.3.2 Creating a Backup Group and Configuring a Virtual IPv6 Address......................................................7-3
7.3.3 Configuring the Priority of the S5300 in a VRRP6 Group....................................................................7-4
7.4 Configuring VRRP6 to Track the Status of an Interface.................................................................................7-5
7.4.2 Configuring VRRP6 to Track the Status of an Interface........................................................................7-6
7.5 Configuring VRRP6 to Tracking the BFD Session Status..............................................................................7-8
7.5.2 Configuring VRRP6 to Tracking the BFD Session Status.....................................................................7-9
7.6 Adjusting and Optimizing VRRP6................................................................................................................7-10
7.6.2 Setting the Interval for Sending VRRP6 Advertisement Messages.....................................................7-11
7.6.3 Setting the Preemption Delay on the S5300.........................................................................................7-12
7.6.4 Disabling Checking of the Hop Limit of VRRP6 Packets...................................................................7-12
7.6.5 Disabling Preemption Mode on an Interface........................................................................................7-13
7.7 Configuring mVRRP6 Backup Groups.........................................................................................................7-15
7.7.2 Configuring mVRRP6 Backup Group.................................................................................................7-17
7.7.3 (Optional) Configuring Member VRRP6 Backup Groups and Binding them to the mVRRP6 Backup
Group.............................................................................................................................................................7-17
7.8 Maintaining VRRP6......................................................................................................................................7-18
7.8.1 Resetting VRRP6 Statistics..................................................................................................................7-18
7.9.1 Example for Configuring VRRP6 on an Interface...............................................................................7-19
7.9.2 Example for Configuring VRRP6 in Load Balancing Mode...............................................................7-22
xii Huawei Proprietary and Confidential Issue 02 (2010-12-01)

Configuration Guide - Reliability Figures
Figures
Figure 1-1 Crossed connection of fibers..............................................................................................................1-2

Figure 1-2 Disconnection of one fiber.................................................................................................................1-2
Figure 1-3 Disconnection of one fiber...............................................................................................................1-11
Figure 2-1 Application scenario of the Smart Link..............................................................................................2-3
Figure 2-2 Data flow control policy...................................................................................................................2-11
Figure 2-3 Application scenario of the Monitor Link........................................................................................2-14
Figure 2-4 Networking for configuring basic functions of Smart Link.............................................................2-19
Figure 2-5 Networking diagram for configuring load balancing between active and standby links of a Smart Link
group....................................................................................................................................................................2-23
Figure 2-6 Networking of Smart Link application.............................................................................................2-27
Figure 3-1 Application of crossed RRPP rings on the MAN...............................................................................3-3
Figure 3-2 Networking diagram of RRPP multi-instance....................................................................................3-5
Figure 3-3 Ring group in RRPP multi-instance application.................................................................................3-6
Figure 3-4 Application scenario of RRPP multi-instance..................................................................................3-17
Figure 3-5 Networking diagram of a single RRPP ring.....................................................................................3-29
Figure 3-6 Networking diagram of crossed RRPP rings with a single instance (Huawei version)....................3-34
Figure 3-7 Networking diagram of tangent RRPP rings....................................................................................3-43
Figure 3-8 Networking diagram of single RRPP ring with multiple instances..................................................3-53
Figure 3-9 Networking diagram of crossed RRPP rings with multiple instances..............................................3-66
Figure 3-10 Networking diagram of tangent RRPP rings with multiple instances............................................3-87
Figure 4-1 Networking diagram for configuring basic functions of EFM OAM.................................................4-8
Figure 4-2 Networking diagram for testing the packet loss ratio on the link.....................................................4-17
Figure 4-3 Diagram of associating EFM OAM with an interface......................................................................4-42
Figure 4-4 Networking diagram for configuring association between an EFM OAM module and an interface
.............................................................................................................................................................................4-45
Figure 4-5 Networking diagram for configuring association between EFM OAM modules.............................4-48
Figure 4-6 Application scenario of association between an Ethernet CFM module and an interface (1)..........4-50
Figure 4-10 Networking for configuring association between an Ethernet CFM module and an interface......4-55
Figure 4-11 Association between EFM OAM and Ethernet CFM.....................................................................4-58
Figure 4-12 Networking diagram for configuring association between Ethernet CFM and Ethernet CFM......4-60
Figure 4-13 Networking diagram for configuring EFM OAM..........................................................................4-75
Issue 02 (2010-12-01) Huawei Proprietary and Confidential xiii

Figures Configuration Guide - Reliability
Figure 4-14 Networking diagram for testing the packet loss ratio on the link...................................................4-78
Figure 4-15 Networking diagram for configuring basic functions of Ethernet CFM........................................ 4-81
Figure 4-16 Networking diagram for configuring the default MD for Ethernet CFM.......................................4-89
Figure 4-17 Networking diagram for configuring association between an EFM OAM module and an interface
.............................................................................................................................................................................4-96
Figure 4-18 Networking diagram for configuring association between EFM OAM modules...........................4-98
Figure 4-19 Networking diagram for associating an Ethernet CFM module with an interface.......................4-101
Figure 4-20 Networking diagram for configuring association between an EFM OAM module and an Ethernet CFM
module...............................................................................................................................................................4-105
Figure 4-21 Networking diagram for configuring association between Ethernet CFM and Ethernet CFM....4-109
Figure 4-22 Networking diagram for associating Ethernet CFM with Smart Link.........................................4-113
Figure 4-23 Networking diagram for associating Ethernet CFM and RRPP multi-instance...........................4-119
Figure 4-24 Networking diagram of association between SEP and CFM........................................................4-132
Figure 4-25 Networking diagram of configuring the one-way frame delay measurement in a VLAN...........4-144
Figure 4-26 Networking diagram of configuring the two-way frame delay measurement in a VLAN...........4-149
Figure 5-1 Application scenario of the BFD passive Echo function....................................................................5-9
Figure 5-2 Networking diagram of single-hop BFD (for Layer 2 forwarding link).......................................... 5-26
Figure 5-3 Networking diagram for configuring single-hop BFD on a VLANIF interface...............................5-28
Figure 5-4 Networking diagram of multi-hop BFD...........................................................................................5-32
Figure 6-1 Default gateway of a LAN..................................................................................................................6-3
Figure 6-2 mVRRP determines the dual-homing of the master and slave switchs............................................6-22
Figure 6-3 Networking of a VRRP group in master/backup mode....................................................................6-28
Figure 6-4 Networking of a VRRP group in master/backup mode....................................................................6-34
Figure 6-5 Networking of VRRP fast switchover..............................................................................................6-40
Figure 7-1 mVRRP6 determines the dual-homing of the master and slave routers...........................................7-16
Figure 7-2 Networking of VRRP6..................................................................................................................... 7-20
Figure 7-3 Networking of VRRP in load balancing mode.................................................................................7-23
xiv Huawei Proprietary and Confidential Issue 02 (2010-12-01)

Configuration Guide - Reliability Tables
Tables
Table 3-1 Mapping between protected VLANs and instances...........................................................................3-52

Table 3-2 Master nodes, and primary and secondary ports on the master nodes...............................................3-52
Table 3-5 Edge nodes, assistant edge nodes, public port, and edge port of the subrings...................................3-65
Table 4-1 Differences between IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007..................................4-5
Table 4-2 Mapping between instances and protected VLANs.........................................................................4-119
Table 4-3 Master node, and primary and secondary interfaces on the master node.........................................4-120
Issue 02 (2010-12-01) Huawei Proprietary and Confidential xv

Configuration Guide - Reliability 1 DLDP Configuration
1 DLDP Configuration
About This Chapter
This chapter describes the principle, configuration procedure, and configuration example of the
Device Link Detection Protocol (DLDP).
1.1 Introduction to DLDP

This section describes the concept of DLDP.
1.2 Configuring DLDP Functions
This section describes how to configure DLDP functions.
1.3 Resetting the DLDP Status
This section describes how to reset the DLDP status.
1.4 Maintaining DLDP
This section describes how to maintain DLDP.
1.5 Configuration Examples
This section provides a configuration example of DLDP.
Issue 02 (2010-12-01) Huawei Proprietary and Confidential 1-1

1 DLDP Configuration Configuration Guide - Reliability
1.1 Introduction to DLDP

This section describes the concept of DLDP.
On a network, the unidirectional link fault often occurs. That is, the local device can receive
packets from the remote device through the link layer, but the remote device cannot receive
packets from the local device.
Take the fiber as an example. The fault of unidirectional link may be caused by crossed
connection of fibers or disconnection of one fiber.
Figure 1-1 Crossed connection of fibers

SwitchA
GE0/0/1 GE0/0/2
GE0/0/1 GE0/0/2
SwitchB
Figure 1-2 Disconnection of one fiber

SwitchA
TX RX
GE0/0/1
GE0/0/1
RX TX
SwitchB
DLDP can detect the link status of fibers or copper twisted pairs. If a unidirectional link exists,
DLDP automatically disables the interface or prompts the user to manually disable the interface.
This prevents network faults. Currently, the S5300 supports DLDP detection for up to 256
neighbors.
As a link layer protocol, DLDP works with the physical layer protocol to detect the link status.
The auto negotiation mechanism on the physical link detects physical signals and faults on the
1-2 Huawei Proprietary and Confidential Issue 02 (2010-12-01)

physical link, and DLDP identifies the remote device and unidirectional link and disables
unreachable interfaces. The auto negotiation mechanism and DLDP work together to detect and
close unidirectional links on the physical and logical interfaces. If the interfaces on both ends
of the link work normally on the physical layer, DLDP checks the connection and packet
exchange between the two interfaces on the link layer. This process cannot be implemented
through the auto negotiation mechanism.
1.2 Configuring DLDP Functions

This section describes how to configure DLDP functions.
1.2.1 Establishing the Configuration Task

1.2.2 Enabling DLDP
1.2.3 (Optional) Setting the Operating Mode of DLDP
1.2.4 (Optional) Setting the Interval for Sending Advertisement Packets
1.2.5 (Optional) Setting the Delay Down Timer
1.2.6 (Optional) Setting the Interface Blocking Mode
1.2.7 (Optional) Setting the Authentication Mode of DLDP Packets
1.2.8 Checking the Configuration
Applicable Environment
On a network, a unidirectional link fault often occurs. To prevent network faults caused by
unidirectional links, you can enable DLDP on interfaces at two ends of a pair of fibers or a copper
twisted pair to monitor the link status. If a unidirectional link exists, DLDP automatically
disables the interface connected to the link or prompts you to manually disable the interface.
Unidirectional links can be tested only when the devices on both ends of the fibers and copper
twisted pairs support DLDP functions.
Pre-configuration Tasks
Before configuring DLDP, complete the following task:
l Configuring the interfaces at both ends to work in non-auto-negotiation mode
Data Preparation
To configure DLDP, you need the following data.
No. Data
1 Type and number of each interface
2 (Optional)Name of the interface group

No. Data
3 (Optional) Interval for sending Advertisement packets
4 (Optional) Value of the Delay Down timer
1.2.2 Enabling DLDP
Procedure
Step 1 Run:
system-view
The system view is displayed.
Step 2 Run:
dldp enable
DLDP is enabled globally.
Step 3 Run:
interface interface-type interface-number
The Ethernet interface view is displayed.
Or run:
port-group port-group-name
The interface group view is displayed.
Step 4 Run:
dldp enable
DLDP is enabled on the interface.
By default, DLDP is disabled globally and on each interface.
----End
1.2.3 (Optional) Setting the Operating Mode of DLDP
Context
If DLDP works in normal mode, the system can identify only one type of unidirectional link,
that is, the crossed connection of fibers. In this mode, the system does not use any timer, so it
cannot detect that a bidirectional link changes to a unidirectional link.
If DLDP works in enhanced mode, the system can identify two types of unidirectional links,
that is, the crossed connection of fibers and the connection where one fiber is disconnected. To
detect the unidirectional link caused by disconnection of one fiber, you need to manually set the
rate and full-duplex mode of the interconnected ports; otherwise, DLDP does not take effect
even if it is enabled. When a bidirectional link changes to a unidirectional link, the port where

the Tx fiber receives optical signals is in Disable state, and the port where the Tx fiber receives
no optical signals is in Inactive state.
Procedure
Step 1 Run:
system-view
Step 2 Run:
dldp work-mode { enhance | normal }
The operation mode of DLDP is set.
By default, the operation mode of DLDP is enhance mode.
----End
1.2.4 (Optional) Setting the Interval for Sending Advertisement

Packets
Context
Do as follows on the S5300 that needs to run DLDP.
Procedure
Step 1 Run:
system-view
Step 2 Run:
dldp interval time
The interval for sending Advertisement packets is set.
By default, the interval for sending Advertisement packets is 5 seconds.
The interval for sending Advertisement packets must be smaller than one third of the STP
convergence time. If the interval is too long, STP loops occur before a unidirectional link is shut
down on a DLDP interface. If the interval is too short, traffic on the network increases.
NOTE
Ensure that the interval for sending Advertisement packets is the same on the local and remote devices that
are connected through fibers or copper twisted pairs.
----End
1.2.5 (Optional) Setting the Delay Down Timer

Procedure
Step 1 Run:
system-view
Step 2 Run:
dldp delaydown-timer time
The Delay Down timer is set.
By default, the Delay Down timer is 1 second.
If DLDP receives a Port-Down event when it is in Active, Advertisement, or Probe state, DLDP
will enter Inactive state and clear the neighbor information. In certain cases, the port is Down
for a very short time. For example, failure of the Tx fiber on a port may cause jitter of optical
signals on the Rx fiber, that is, the port becomes Down and then becomes Up again. To prevent
the neighbor information from being deleted immediately in this case, DLDP first enters the
DelayDown state and starts the DelayDown timer. Before the DelayDown timer times out, DLDP
retains the neighbor information and responds to only Port-Up events.
l If DLDP does not receive any Port-Up event when the DelayDown timer times out, it deletes
the neighbor information and enters the Inactive state.
l If DLDP receives the Port-Up event before the DelayDown timer times out, it returns to the
previous state.
The Delay Down timer applies to all DLDP interfaces.
----End
1.2.6 (Optional) Setting the Interface Blocking Mode
Context
When a unidirectional link is detected, DLDP blocks the corresponding interface in either of the
following ways:
l Manual mode: This mode can prevent DLDP from blocking the interface immediately to
affect packet forwarding when the network performance is poor. It is a compromise mode
used to prevent an interface from being blocked because of incorrect judgement of the
system. In this mode, DLDP detects the unidirectional link, and the network administrator
blocks the interface manually. When the DLDP state machine detects a unidirectional link,
the system records the log and sends trap messages to prompt you the network administrator
to block the interface manually. Then the DLDP state machine changes to the Disable state.
l Automatic mode: It is the default mode. When a unidirectional link is detected, the DLDP
state machine changes to the Disable state, and the system records the log, sends trap
messages, and sets the interface state to Blocking.
Procedure
Step 1 Run:
system-view

Step 2 Run:
dldp unidirectional-shutdown { auto | manual }
The mode of blocking interfaces when a unidirectional link fault is detected is set.
By default, DLDP automatically blocks the interface when a unidirectional link fault is detected.
An interface in DLDP Down state still sends RecoverProbe packets periodically. If correct
RecoverEcho packets are received, it indicates that the unidirectional link changes to the
bidirectional link and the DLDP status becomes Up.
----End
1.2.7 (Optional) Setting the Authentication Mode of DLDP Packets
Procedure
Step 1 Run:
system-view

Step 2 Run:
dldp authentication-mode { md5 md5-password | none | simple simple-password }
The DLDP authentication mode used between the interfaces of the S5300 and the remote device
is set.
By default, the DLDP authentication mode used between the interfaces of the S5300 and the
remote device is none. That is, DLDP packets are not authenticated.
NOTE
Ensure that the local and remote devices use the same authentication mode and same authentication
password; otherwise, the DLDP authentication fails. DLDP works normally only after the DLDP
authentication succeeds.
----End
Procedure
Step 1 Run the display dldp [ interface-type interface-number ] command to check the DLDP
configuration and neighbor entries.
----End
Example
Run the display dldp command, and you can view the operation mode of DLDP, interval for
sending Advertisement packets, value of the Delay Down timer, interface disabling mode, and
authentication mode of DLDP packets.
<Quidway> display dldp
DLDP global status : enable
DLDP interval : 5s

DLDP work-mode : enhance

DLDP authentication-mode : simple, password is 123
DLDP unidirectional-shutdown : auto
DLDP delaydown-timer : 2s
The number of enabled ports is 2.
The number of global neighbors is: 2.
Interface GigabitEthernet0/0/1
DLDP port state : advertisement
DLDP link state : up
The neighbor number of the port is 1.
Neighbor mac address : 0000-0000-0100
Neighbor port index : 21
Neighbor state : two way
Neighbor aged time : 13
1.3 Resetting the DLDP Status

This section describes how to reset the DLDP status.

1.3.2 Resetting the DLDP Status Globally
1.3.3 Resetting the DLDP Status of an Interface
When a unidirectional link is detected, the corresponding interface enters the Disable state. The
system prompts you to disable the interface or sets the interface state to DLDP Down
automatically according to the configuration. To enable the interface to detect unidirectional
links again, you can reset the DLDP state of the interface. The DLDP status of the interface after
recovery depends on the physical status of the interface. If the physical status is Down, the DLDP
status of the interface changes to Inactive. If the physical status is Up, the DLDP status changes
to Active.
None.
Data Preparation
To reset the DLDP status, you need the following data.

No. Data
1 Type and number of each interface
2 Name of the interface group
1.3.2 Resetting the DLDP Status Globally
Context
The dldp reset command takes effect only when DLDP is enabled globally and on interfaces.
When you reset the DLDP status globally, the DLDP status is reset for all the disabled interfaces
on the S5300.
Procedure
Step 1 Run:
system-view

Step 2 Run:
dldp reset
The DLDP status is reset globally.
----End
1.3.3 Resetting the DLDP Status of an Interface
Context
If you reset the DLDP status on an interface or interface group, the DLDP status is reset for the
interface or all the disabled interfaces in the interface group.
The dldp reset command takes effect only when DLDP is enabled globally and on interfaces.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The Ethernet interface view is displayed.

Or run:
port-group port-group-name

The interface group view is displayed.

Step 3 Run:
dldp reset
The DLDP status is reset on the interface or interface group.
----End
Procedure
Step 1 Run the display dldp [ interface-type interface-number ] command to check the DLDP
configuration and neighbor entries.
----End
Example
Run the display dldp command, and you can view the status of an interface after the DLDP
status is reset.
<Quidway> display dldp
DLDP global status : enable
DLDP interval : 5s
DLDP work-mode : enhance
DLDP authentication-mode : simple, password is 123
DLDP unidirectional-shutdown : auto
DLDP delaydown-timer : 2s
The number of enabled ports is 2.
The number of global neighbors is: 2.
1.4 Maintaining DLDP

This section describes how to maintain DLDP.
1.4.1 Clearing the Statistics of DLDP
1.4.1 Clearing the Statistics of DLDP

Context
CAUTION
Statistics of DLDP cannot be restored after you clear them. So, confirm the action before you
use the command.
Procedure
Step 1 Run the reset dldp statistics [ interface-type interface-number ] command in the user view to
clear the statistics of DLDP packets on an interface.
----End

This section provides a configuration example of DLDP.
1.5.1 Example for Configuring DLDP
1.5.1 Example for Configuring DLDP
Networking Requirements
As shown in Figure 1-3, two S5300s are connected through a pair of optical fibers. On a fiber,
RX indicate the receive end, and TX indicates the transmit end. DLDP is enabled on the
interconnected interfaces. If the Rx fiber on SwitchA fails, SwitchA cannot receive optical
signals. In this case, GigabitEthernet0/0/1 of SwitchA becomes Down and cannot send or receive
any packets. However, the Tx fiber on SwitchB still sends optical signals, and SwitchB can
receive optical signals because the Tx fiber on SwitchA is working normally. Therefore, the link
status on SwitchB is still Up. If SwitchB does not receive any DLDP packet from SwitchA within
the neighbor aging time, GigabitEthernet0/0/1 of SwitchB changes to unidirectional state. To
prevent network fauls, DLDP disables GigabitEthernet0/0/1 of SwitchB.
Figure 1-3 Disconnection of one fiber

SwitchA
TX RX
GE0/0/1
GE0/0/1
RX TX
SwitchB

Configuration Roadmap
The configuration roadmap is as follows:
1. Configure the interfaces at both ends to work in non-auto-negotiation mode.
2. Enable DLDP.
3. Set the operation mode of DLDP.
4. Set the interval for sending Advertisement packets.
5. Set the Delay Down timer.
6. Set the mode of disabling the interface when a unidirectional link is detected.
7. Set the authentication mode of DLDP packets.
Data Preparation
To complete the configuration, you need the following data:
l Type and number of each interface
l Interval for sending Advertisement packets
l Value of the Delay Down timer
Procedure
Step 1 Configure the interface on Switch A to work in non-auto negotiation mode.
<Quidway> system-view
[Quidway] sysname SwitchA
[SwitchA] interface gigabitethernet 0/0/1
[SwitchA-GigabitEthernet0/0/1] undo negotiation auto
[SwitchA-GigabitEthernet0/0/1] quit
Step 2 Enable DLDP globally

[SwitchA] dldp enable
Step 3 Enable DLDP on the interface.

[SwitchA-GigabitEthernet2/0/1] dldp enable
Step 4 Configure DLDP to work in enhanced mode.

[SwitchA] dldp work-mode enhance
Step 5 Set the interval for sending Advertisement packets to 80 seconds.

[SwitchA] dldp interval 80
Step 6 Set the timeout interval of the DelayDown timer to 4 seconds.

[SwitchA] dldp delaydown-timer 4
Step 7 Configure DLDP to automatically shut down the interface where a unidirectional link is detected.
[SwitchA] dldp unidirectional-shutdown auto
Step 8 Set the authentication mode of DLDP packets to simple password authentication and set the
password to 123456.
[SwitchA] dldp authentication-mode simple 12345
Repeat the preceding steps on Switch B.

Step 9 Verify the configuration.

After the configuration, run the display dldp command in the interface view, and you can find
that the DLDP status of the interface is advertisement.
<SwitchA> display dldp gigabitethernet 0/0/1
DLDP port state: advertisement
DLDP link state: up
The neighbor number of the port is: 1.
Neighbor mac address:0018-2000-0083
Neighbor port index:27
Neighbor state:two way
Neighbor aged time:185
Remove the Rx fiber from Switch A to simulate a unidirectional link between GE 0/0/1 of Switch
A and GE 0/0/1 of Switch B, as shown in Figure 1-3. You find that DLDP blocks the GE
0/0/1 interface of Switch B.
# Run the display dldp on Switch A, and you can find that the DLDP status of GE 0/0/1 is
inactive. Run the display dldp on Switch B, and you can find that the DLDP status of GE
0/0/1 is disable.
<SwitchA> display dldp gigabitethernet 0/0/1
DLDP port state: inactive
DLDP link state: down
The neighbor number of the port is: 0
<SwitchB> display dldp gigabitethernet 0/0/1
DLDP port state: disable
DLDP link state: up
The neighbor number of the port is: 0
----End
Configuration Files
Configuration file of Switch A
#
sysname SwitchA
#
dldp enable
dldp interval 80
dldp delaydown-timer 4
dldp authentication-mode simple 12345
#
interface GigabitEthernet0/0/1
dldp enable
#
return

Configuration Guide - Reliability 2 Smart Link and Monitor Link Configuration
2 Smart Link and Monitor Link Configuration
About This Chapter
This chapter describes the principle, configuration procedure, and configuration example of the
Smart Link and and Monitor Link.
2.1 Smart Link and Monitor Link

This section describes the concepts of Smart Link and Monitor Link.
2.2 Configuring a Smart Link Group
This section describes how to create a Smart Link group, enable the Smart Link group, configure
the master and slave interfaces, enable the revertive switching, and configure functions related
to Flush packets.
2.3 Configuring a Flow Control Policy in a Smart Link Group
This section describes how to configure the advanced functions of the Smart Link group, such
as lock of data flows and manual switchover between links.
2.4 Configuring a Monitor Link Group
This section describes how to create a Monitor Link group, configure the uplink and downlink
interfaces, and enable the revertive switching.
2.5 Maintaining the Smart Link
This section describes how to debug the Smart Link.
This section provides several configuration examples of the Smart Link.

2 Smart Link and Monitor Link Configuration Configuration Guide - Reliability
2.1 Smart Link and Monitor Link

This section describes the concepts of Smart Link and Monitor Link.
The dual-homing networking is often used. In this networking, STP blocks redundant links,
providing redundancy. When the active link fails, the traffic is switched to the standby link.
Although this scheme can implement redundancy, the performance cannot meet the requirements
of users. Route convergence is performed within several seconds even if the Rapid Spanning
Tree Protocol (RSTP) is used. The convergence speed is unfavorable for the high-end Ethernet
switch used on the core of the carrier-class network.
To address the preceding problem, Huawei introduces Smart Link in dual-homing networking
to implement redundancy of active and standby links and fast transition. In this manner, the high
performance is ensured and the configuration is simplified. In addition, cooperation of interfaces
is used.
The Monitor Link is introduced as a supplement to the Smart Link. This technology supports
the association of interfaces. A Monitor Link group consists of an uplink interface and several
downlink interfaces. If the uplink interface fails, the Monitor Link group automatically disables
the downlink interfaces. When the uplink interface recovers, the downlink interfaces also
recover.
2.2 Configuring a Smart Link Group

This section describes how to create a Smart Link group, enable the Smart Link group, configure
the master and slave interfaces, enable the revertive switching, and configure functions related
to Flush packets.

2.2.2 Creating and Enabling a Smart Link Group
2.2.3 Configuring the Master and Slave Interfaces in a Smart Link Group
2.2.4 Enabling the Sending of Flush Packets
2.2.5 (Optional) Configuring Load Balancing in a Smart Link Group
2.2.6 (Optional) Enabling Revertive Switching and Setting the WTR Time
2.2.7 (Optional) Enabling the Receiving of Flush Packets
2.2.8 Enabling the Functions of the Smart Link Group
As shown in Figure 2-1, each device at the access and convergence layer is connected to two
uplink devices. This networking mode provides higher security and reduces the duration of
service interruption caused by the link failure.

Figure 2-1 Application scenario of the Smart Link
IP/MPLS
core
network
SwitchA
SwitchB SwitchC
Smart Link group Smart Link group

SwitchD SwitchE
User1 User 2 User 3
Active link
Inactive link
As shown in Figure 2-1, Switch D and Switch E are connected to user devices, and both are
connected to Switch B and Switch C. Configure the Smart Link on Switch D and Switch E and
add the two uplink interfaces to the respective Smart Link group to avoid loops. In this manner,
interrupted services can be restored in milliseconds.
Before configuring the basic functions of a Smart Link group, complete the following task:
l Ensuring that the Multiple Spanning Tree Protocol (MSTP) Rapid Ring Protection Protocol
(RRPP) and Smart Ethernet Protection (SEP) are not enabled on the master and slave
interfaces of the Smart Link group
Data Preparation
To configure basic functions of the Smart Link group, you need the following data.
No. Data
1 Number of the interface added to the Smart Link group

No. Data
2 ID of the Smart Link group
3 IDs of VLANs bound to the instance
4 Control VLAN ID contained in the Flush packet
5 (Optional)Password contained in the Flush packet
2.2.2 Creating and Enabling a Smart Link Group

Context
Do as follows on the S5300.
Procedure
Step 1 Run:
system-view

Step 2 Run:
smart-link group group-id
A Smart Link group is created and the Smart Link group view is displayed.
The S5300 supports a maximum of 16 Smart Link groups.
Step 3 Run:
protected-vlan reference-instance instance-id [ to instance-id2 ]
An instance is bound to the Smart Link group as the protected instance. The functions of the
Smart link group takes effect only on the VLANs bound to the protected instance.
NOTE
By default, a Smart Link group protects all VLANs and the protected-vlan reference-instance command
is applicable only to multicast services.
----End
2.2.3 Configuring the Master and Slave Interfaces in a Smart Link

Group
Context
The slave interface of a Smart Link group is blocked when the group is started.
An interface cannot be added to a Smart Link group in the following situations:
l The interface is a Rapid Ring Protection Protocol (RRPP) interface.

l Spanning Tree Protocol (STP) is enabled on the interface.

l The interface has been added to an Eth-Trunk.

l The interface has been added to a Monitor Link group.
l The interface has been added to another Smart Link group.
l STP is configured on the interface.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
stp disable
STP is disabled on the interface.
Step 4 Run:
quit
Return to the interface view.
Step 5 Run:
The Smart Link group view is displayed.
Step 6 Run:
port interface-type interface-number master
An interface is added to the Smart Link group and is specified as the master interface.
Step 7 Run:
port interface-type interface-number slave
Another interface is added to the Smart Link group and is specified as the slave interface.
A Smart Link group consists of a master interface and a slave interface. By default, a Smart Link
group does not have interfaces.
----End
2.2.4 Enabling the Sending of Flush Packets
Context
When the active and standby links of the Smart Link group switch, the existing forwarding
entries no longer apply to the new topology. All the MAC address entries and ARP entries on
the network need to be updated. Then the Smart Link group sends Flush packets to ask other
devices to update the MAC address table and ARP entries.

Because manufacturers define the format of Flush packets differently, the Flush packets
described here are used only for the intercommunication between Huawei S-series switches. In
addition, the function of receiving Flush packets must be enabled on the remote switch.
If you run flush send control-vlan vlan-id [ password simple password ] command in the Smart
Link group view, the Smart Link group is enabled to send Flush packets that contain the specified
control VLAN ID and password. The VLAN ID specified by vlan-id must already exist on the
S5300. If the specified VLAN ID does not exist on the S5300, Flush packets cannot be sent.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
flush send control-vlan vlan-id [ password simple password ]
The S5300 is enabled to send Flush packets, and the control VLAN ID and password contained
in Flush packets are set.
A control VLAN cannot be a VLAN mapping a load-balancing instance.
The control VLAN ID and password contained in Flush packets on both devices must be the
same. That is, the control VLAN ID and password in Flush packets sent by the device must be
the same as the control VLAN ID and password in Flush packets received by the device.
NOTE
After the flush send control-vlan command is run, the interface cannot be added to the control VLAN. You need
to configure the interface to allow the packets of the control VLAN to pass through.
----End
2.2.5 (Optional) Configuring Load Balancing in a Smart Link Group
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
stp region-configuration

The Multiple Spanning Tree (MST) region view is displayed.
Step 3 Run:
instance instance-id vlan { vlan-id1 [ to vlan-id2 ] }&<1-10>
The mapping between an instance and VLANs is set.
A domain supports up to 49 instances, among which Instance 0 is the default instance and does
not need to be created.
By default, all VLANs are mapped to Instance 0.
Step 4 Run:
active region-configuration
The configuration of the MST region is activated.
After configuring the domain name, VLAN mapping table, or MSTP revision level, you must
run the active region-configuration command for the configuration to take effect.
Step 5 Run:
quit
Return to the system view.
Step 6 Run:
Step 7 Run:
load-balance instance { instance-id1 [ to instance-id2 ] } &<1-10> slave
Packets of the VLANs bound to the specified instance are sent from the slave interface to
implement load balancing.
----End
2.2.6 (Optional) Enabling Revertive Switching and Setting the WTR

Time
Context
When the active link in a Smart Link group fails, the traffic is automatically switched to the
standby link. The original active link does not preempt the traffic but remains blocked after
recovering from the fault. To switch the traffic back to the active link, you can adopt either of
the following methods:
l Enable the revertive switching of a Smart Link group. The switching is automatically
performed after the revertive switching timer times out.
l Run the smart-link manual switch command to perform the link switching forcibly.
NOTE
The link switching is performed only when the two member interfaces in a group are both Up.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
restore enable
Revertive switching is enabled for the Smart Link group.
Be default, the revertive switching of the Smart Link group is disabled.
Step 4 (Optional) Run:

timer wtr wtr-time
The wait to recover (WTR) time of the Smart Link group is set.
By default, the WTR time of a Smart Link group is 60 seconds.
----End
2.2.7 (Optional) Enabling the Receiving of Flush Packets
Context
An interface receives Flush packets only when it is configured with the control VLAN ID and
added to this VLAN.
Do as follows on SwitchA, SwitchB, and SwitchC shown in Figure 2-1.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface { gigabitethernet | eth-trunk| xgigabitethernet } interface-number
The view of the downlink interface of the SwitchA, SwitchB, or SwitchC is displayed.
Step 3 Run:
smart-link flush receive control-vlan vlan-id [ password simple password ]
The interface is enabled to receive Flush packets, and the control VLAN ID and password
contained in Flush packets are set.
The password is optional. If no password is specified, no password is used for authentication.

When the control VLAN ID is changed, the password must also be changed.

The control VLAN ID and password contained in Flush packets on both devices must be the
same. That is, the control VLAN ID and password in Flush packets sent by the device must be
the same as the control VLAN ID and password in Flush packets received by the device.
----End
2.2.8 Enabling the Functions of the Smart Link Group
Context
After the functions of the Smart Link group are enabled, the standby interface in the group is
blocked. After the functions of the Smart Link group are disabled, the blocked standby interface
is recovered.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
smart-link enable
The functions of the Smart Link group are enabled.
----End
Procedure
l Run the display smart-link group { all | group-id } command to check information about
a Smart Link group.
l Run the display smart-link flush command to check information about the received Flush
packets.
----End
Example
Run the display smart-link group { all | group-id } command to check information about a
Smart Link group. The following information is displayed:
<Quidway> display smart-link group 1
Smart Link group 1 information :
Smart Link group was enabled
Wtr-time is: 30 sec.
Load-Balance Instance: 1 to 2
There is no protected-vlan reference-instance
DeviceID: 0018-2000-0083 Control-vlan ID: 20

Member Role State Flush Count Last-Flush-Time

------------------------------------------------------------------------
GigabitEthernet0/0/1 Master Active 1 2008/11/21 16:37:20 UTC
+05:00
GigabitEthernet0/0/2 Slave Inactive 2 2008/11/21 17:45:20 UTC
+05:00
If the configuration is correct, the following information is displayed:
l The functions of the Smart Link group are enabled. Therefore, "Smart link group was
enabled" is displayed.
l The status of the interfaces in the Smart Link group is displayed, including the role of each
interface in the group, number of sent Flush packets, and time when the last Flush packets
are sent. As shown in the preceding information, GigabitEthernet0/0/1 is the master
interface in the Smart Link group; this interface is in the Forwarding state; it sent a Flush
packet at 16:37 on 2008-11-21.
l The control VLAN ID contained in the sent Flush packets is 20.
Run the display smart-link flush command, and you can view information about received Flush
packets.
<Quidway> display smart-link flush
Receive flush packets count: 1191
Receive last flush interface: GigabitEthernet0/0/1
Receive last flush packet time: 16:48:53 UTC+05:00 2009/02/23
Receive last flush packet source mac: 0018-0202-0088
Receive last flush packet control vlan ID: 20
2.3 Configuring a Flow Control Policy in a Smart Link

Group
This section describes how to configure the advanced functions of the Smart Link group, such
as lock of data flows and manual switchover between links.

2.3.2 Locking Data Flows on the Master Interface
2.3.3 Locking Data Flows on the Slave Interface
2.3.4 Switching Data Flows Manually
As shown in Figure 2-2, the basic functions and revertive switching of the Smart Link group
are enabled on Switch D. During maintenance, the active link in the Smart Link group needs to
be inspected. To prevent the inspection from affecting normal services, you need to configure
a flow control policy for the Smart Link group. Through the configuration, you can forcibly lock
the data flows to the standby link and switch them back to the active link after the inspection is
complete.

Figure 2-2 Data flow control policy
SwitchA
SwitchB SwitchC
Smart Link
group
Active link
SwitchD SwitchE
Inactive link
Before configuring a flow control policy for the Smart Link group, complete the following task:
l 2.2 Configuring a Smart Link Group
Data Preparation
None.
2.3.2 Locking Data Flows on the Master Interface

Context
CAUTION
If data flows are locked on the master interface, they cannot be switched to the slave interface
automatically when the master interface fails. Thus, traffic is interrupted.
Do as follows on SwitchD shown in Figure 2-2.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
smart-link lock
Data flows are locked on the master interface.
----End
2.3.3 Locking Data Flows on the Slave Interface
Context
CAUTION
If data flows are locked on the slave interface, they cannot be switched to the master interface
automatically when the slave interface fails. Thus, traffic is interrupted.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
smart-link force
Data flows are locked on the slave interface.
----End
2.3.4 Switching Data Flows Manually
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:


Step 3 Run:
smart-link manual switch
Data flows are switched to the other link.

To implement active/standby switchover between links, ensure that:
l The master interface and slave interface exist and are both in Up state.
l The smart-link command is not run to lock data streams.
The smart-link manual switch command can be repeatedly used in the Smart Link group view.
Each time you run the command, the active/standby switchover is performed between links.
Packet loss occurs during the switchover. The duration is measured in milliseconds.
----End
Procedure
Step 1 Run the display smart-link group { all | group-id } command to check information about a
Smart Link group.
----End
Example
Run the display smart-link group { all | group-id } command. If lock is displayed, it indicates
that data flows are locked on the master interface. If force is displayed, it means that data flows
are locked on the slave interface.
<Quidway> display smart-link group 1
Link status:lock
Wtr-time is: 30 sec.
Load-Balance Instance: 1 to 2
DeviceID: 0018-2000-0083 Control-vlan ID: 20
------------------------------------------------------------------------
GigabitEthernet0/0/1 Master Active 1 2008/11/21 16:37:20 UTC
+05:00
GigabitEthernet0/0/2 Slave Inactive 2 2008/11/21 17:45:20 UTC
+05:00
2.4 Configuring a Monitor Link Group

This section describes how to create a Monitor Link group, configure the uplink and downlink
interfaces, and enable the revertive switching.

2.4.2 Creating a Monitor Link Group
2.4.3 Configuring the Uplink and Downlink Interfaces in a Monitor Link Group

2.4.4 Setting the Revertive Switching Interval of a Monitor Link group


As shown in Figure 2-3, the uplink of Switch A is faulty. Although Smart Link is enabled on
Switch C, link switching is not performed because the active link is not faulty. In this case,
services are interrupted. To enable the Smart Link group to respond more quickly to the faults
of the uplink, you need to configure the Monitor Link function on the device connected to the
active link to monitor the status of the uplink. When a fault occurs on an uplink, the active link
of the Smart Link group is rapidly blocked. Thus, the Smart Link group can detect the fault and
switch the traffic to the standby link to reduce the service interruption duration.
When the uplink interface belongs to a Smart Link group, the uplink interface is considered as
faulty only if the maser and slave interfaces of the Smart Link group are in standby sate (including
the Down state).
Figure 2-3 Application scenario of the Monitor Link
IP/MPLS
core
network
Smart Link group

GE0/0/1 GE0/0/1
GE0/0/2
Monitor Link group Monitor Link group
GE0/0/2
SwitchA GE0/0/2 SwitchB
Smart Link group GE0/0/1 GE0/0/2
SwitchC
Active link
User1 User2 Inactive link

As shown in Figure 2-3, the link between Switch A and Router breaks. Although Smart Link
is enabled on Switch C and Switch D, link switching is not performed because the active link
does not fail. In this case, services are interrupted. To enable the Smart Link group to respond
more quickly to the faults of the uplink, you need to configure the Monitor Link function on the
device connected to the active link Monitor Link to monitor the status of the uplink. When a
fault occurs, the active link of the Smart Link group is blocked quickly. The Smart Link group
can then detect the fault and switch the traffic to the standby link. Thus, the duration of service
interruption is shortened.
Before configuring the basic functions of the Monitor Link group, complete the following tasks:
l 2.2 Configuring a Smart Link Group

l Ensuring that no interface in the Monitor Link group is added to a Eth-Trunk, Smark Link
group and other Monitor Link group.
Data Preparation
To configure the basic functions of the Monitor Link group, you need the following data.
No. Data
1 ID of the Monitor Link group
2 Number of each interface added to the Monitor Link group
3 Revertive switching interval of the Monitor Link group
4 ID of the Smart Link group
2.4.2 Creating a Monitor Link Group
Context
Do as follows on SwitchA and SwitchB.
Procedure
Step 1 Run:
system-view
Step 2 Run:
monitor-link group group-id
A Monitor Link group is created and the Monitor Link group view is displayed.
----End

2.4.3 Configuring the Uplink and Downlink Interfaces in a Monitor

Link Group
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The Monitor Link group view is displayed. The S5300 supports a maximum of 16 Monitor Link
groups.
Step 3 Run:
port interface-type interface-number { downlink [ downlink-id ] | uplink }
An interface is configured as the uplink interface or downlink interface of the Monitor Link
group.
Or run:
smart-link group group-id uplink
An interface cannot be added to a Monitor Link group in the following situations:
l The interface is added to an Eth-Trunk.

l The interface is added to a Smart Link group.
l The interface is added to another Monitor Link group.
A Smart Link group is configured as the uplink interface of the Monitor Link group.
NOTE
The status of the uplink interface determines the status of the Monitor Link group. Therefore, after the
downlink interface is added to the Monitor Link group, the result of the shutdown or undo shutdown
command can be retained before the status of the uplink interface changes. When the status of the uplink
interface changes, the status of the downlink interfaces changes as follows:
l When an uplink interface in Up state is added to the Monitor Link group or when an uplink interface
in Down state becomes Up, all the downlink interfaces in the Monitor Link group become Up.
l When an uplink interface is deleted from the Monitor Link group or when an uplink interface in Up
state becomes Down, all the downlink interfaces in the Monitor Link group become Down.
To add a Smart Link group to a Monitor Link group, you need to delete the existing uplink interface of the
Monitor Link group. The Smart Link group and common interfaces are incompatible when serving as the
uplink interface for a Monitor Link group.
----End

2.4.4 Setting the Revertive Switching Interval of a Monitor Link

group
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
The Monitor Link group view is displayed.
Step 3 Run:
timer recover-time recover-time
The interval of revertive switching is set.
By default, the revertive switching of a Monitor Link group is enabled and the interval of
revertive switching is 3 seconds.
----End
Procedure
Step 1 Run the display monitor-link group { all | group-id } command to check information about a
Monitor Link group.
----End
Example
Run the display monitor-link group { all | group-id } [ | count ] [ | { begin | include |
exclude } regular-expression ], and you can view basic information about the interfaces in the
Monitor Link group, including the role and status of the interfaces and the time when the
interfaces become Up or Down for the last time.
<Quidway> display monitor-link group 1
Monitor Link group 1 information :
Recover-timer is 5 sec.
Member Role State Last-up-time Last-down-time
GigabitEthernet0/0/1 UpLk UP 0000/00/00 00:00:00 UTC+00:00 0000/00/00
00:00:00 UTC+00:00
GigabitEthernet0/0/2 DwLk[1] DOWN 0000/00/00 00:00:00 UTC+00:00 0000/00/00
00:00:00 UTC+00:00

2.5 Maintaining the Smart Link

This section describes how to debug the Smart Link.
2.5.1 Debugging the Smart Link
2.5.1 Debugging the Smart Link
Context
NOTE
Debugging affects the performance of the system. So, after debugging, run the undo debugging all
command to disable it immediately.
Procedure
l Run the debugging smart-link { all | error | event | fsm-machine } [ group group-id ] to
enable debugging of the Smart Link.
l Run the debugging smart-link flush { all | receive | send } command to enable debugging
of Flush packets.
----End

This section provides several configuration examples of the Smart Link.
2.6.1 Example for Configuring Basic Functions of Smart Link

2.6.2 Example for Configuring Load Balancing Between Active and Standby Links of a Smart
Link Group
2.6.3 Example for Applying the Smart Link Functions
2.6.1 Example for Configuring Basic Functions of Smart Link

As shown in Figure 2-4, the user-side network is connected to the metropolitan area network
(MAN) in dual-homing mode to guarantee the reliability of the network. In addition, ensure
rapid switching of traffic over the standby link when the active link fails so that the duration of
service interruption is limited to several milliseconds.

Figure 2-4 Networking for configuring basic functions of Smart Link
MAN
SwitchB
SwitchC
GE0/0/1 GE0/0/1
Smart Link group

GE0/0/1 GE0/0/2
SwitchA
Active link
Inactive link
1. Configure the Smart Link group on SwitchA and add the uplink interfaces to the Smart
Link group.
2. Enable revertive switching on SwitchA.
3. Enable SwitchA to send Flush packets.
4. Enable SwitchB and SwitchC to receive Flush packets.
5. Enable the Smart Link group on SwitchA.
Data Preparation
l Smart Link group ID
l Number of the uplink interface of SwitchA
l Control VLAN ID and password contained in Flush packets
Procedure
Step 1 On SwitchA, configure the control VLAN and add interfaces to the control VLAN.
<SwitchA> system-view
[SwitchA] vlan batch 10
[SwitchA-GigabitEthernet0/0/1] port link-type trunk
[SwitchA-GigabitEthernet0/0/1] port trunk allow-pass vlan 10

The configurations of SwitchB and SwitchC are similar to the configuration of SwitchA, and
are not mentioned here.
Step 2 Add the STP-disabled uplink interface to the Smart Link group and specify it as the master or
slave interface.
# Configure SwitchA.
[SwitchA-GGigabitEthernet0/0/1] stp disable
[SwitchA-GigabitEthernet0/0/2] stp disable
[SwitchA] smart-link group 1
[SwitchA-smlk-group1] port gigabitethernet 0/0/1 master
[SwitchA-smlk-group1] port gigabitethernet 0/0/2 slave
Step 3 Enable revertive switching and set the WTR time.

[SwitchA-smlk-group1] restore enable
[SwitchA-smlk-group1] timer wtr 30
Step 4 Enable the function of sending Flush packets.

[SwitchA-smlk-group1] flush send control-vlan 10 password simple 123
Step 5 Enable the Smart Link group on SwitchA.

[SwitchA-smlk-group1] smart-link enable
Step 6 Enable the function of receiving Flush packets.

# Configure SwitchB.
[SwitchB] interface gigabitethernet 0/0/1
[SwitchB-GigabitEthernet0/0/1] smart-link flush receive control-vlan 10 password
simple 123
[SwitchB-GigabitEthernet0/0/1] quit
# Configure SwitchC.
[SwitchC] interface gigabitethernet 0/0/1
[SwitchC-GigabitEthernet0/0/1] smart-link flush receive control-vlan 10 password
simple 123
[SwitchC-GigabitEthernet0/0/1] quit

# Run the display smart-link group command to view information about the Smart Link group
on SwitchA. If the following information is displayed, it indicates that the configuration is
successful:
l The Smart Link group is enabled.
l The control VLAN ID is 10.
l GigabitEthernet 0/0/1 is the master interface and is in Active state, and GigabitEthernet 0/0/2
is the slave interface and is in Inactive state.
<SwitchA> display smart-link group 1
There is no Load-Balance

DeviceID: 0025-9e80-2494 Control-vlan ID:

10
----------------------------------------------------------------------
GigabitEthernet0/0/1 Master Active 1 0000/00/00 00:00:00 UTC+00

:00
GigabitEthernet0/0/2 Slave Inactive 0 0000/00/00 00:00:00 UTC+00
:00
# Run the shutdown command to shut down GigabitEthernet 0/0/1, and you can find that
GigabitEthernet 0/0/1 is in Inactive state and GigabitEthernet 0/0/2 is in Active state.
[SwitchA-GigabitEthernet0/0/1] undo shutdown
[SwitchA-GigabitEthernet0/0/1]display smart-link group 1
10
----------------------------------------------------------------------
GigabitEthernet0/0/1 Master Inactive 1 0000/00/00 00:00:00 UTC+00

:00
GigabitEthernet0/0/2 Slave Active 1 0000/00/00 00:00:00 UTC+00
:00
# Run the undo shutdown command to shut down GigabitEthernet 0/0/1, and you can find that
GigabitEthernet 0/0/1 is in Active state and GigabitEthernet 0/0/2 is in Inactive state.
SwitchA-GigabitEthernet0/0/1] undo shutdown
[SwitchAGigabitEthernet0/0/1] display smart-link group 1
10
----------------------------------------------------------------------

:00
:00
----End
Configuration Files
l Configuration file of SwitchA
#
sysname SwitchA
#
vlan batch 10
#
port link-type trunk
port trunk allow-pass vlan 10
stp disable
#
stp disable
#

smart-link group 1
restore enable
smart-link enable
port GigabitEthernet0/0/1 master
port GigabitEthernet0/0/2 slave
timer wtr 30
flush send control-vlan 10 password simple 123
#
return
l Configuration file of SwitchB

#
sysname SwitchB
#
vlan batch 10
#
smart-link flush receive control-vlan 10 password simple 123
#
return
l Configuration file of SwitchC

#
sysname SwitchC
#
vlan batch 10
#
#
return
2.6.2 Example for Configuring Load Balancing Between Active and

Standby Links of a Smart Link Group
As shown in Figure 2-5, packets of VLAN 100 and VLAN 500 are transmitted through the
standby link, and packets of other VLANs are transmitted through the active link. To ensure
network reliability, the customer network is dual-homed to the MAN. Packets of VLAN 100
and VLAN 500 are transmitted through the standby link, and packets of other VLANs are
transmitted through the active link. When the active link fails, packets on the active link can be
switched to the standby link quickly. When the standby link fails, packets of VLAN 100 and
VLAN 500 can be switched to the active link quickly. The service interruption duration is
restricted to millisecond level.

Figure 2-5 Networking diagram for configuring load balancing between active and standby links
of a Smart Link group
MAN
SwitchB
SwitchC
GE0/0/1 GE0/0/1
Smart Link group

GE0/0/1 GE0/0/2
SwitchA Active link
Inactive link
VLAN
100 500
1. On SwitchA, configure Smart Link multi-instance and add the uplink interfaces to the Smart
Link group.
2. Configure load balancing on SwitchA.
3. Enable revertive switching on SwitchA.
4. Enable SwitchA to send Flush packets.
5. Enable SwitchB and SwitchC to receive Flush packets.
6. Enable Smart Link on SwitchA.
Data Preparation
l IDs of instances and IDs of the VLANs bound to the instances on SwitchA
l ID of a Smart Link group
l Numbers of the uplink interfaces on SwitchA
Procedure
Step 1 On SwitchA, configure the control VLAN and add the uplink interfaces to the control VLAN.
[SwitchA] vlan batch 10 100 500


[SwitchA-GigabitEthernet0/0/1] port trunk allow-pass vlan 10 100 500
[SwitchA-GigabitEthernet0/0/2] port trunk allow-pass vlan 10 100 500
Step 2 Configure VLAN mapping on SwitchA.

[SwitchA] stp region-configuration
[SwitchA-mst-region] instance 10 vlan 100 500
[SwitchA-mst-region] active region-configuration
[SwitchA-mst-region] quit
Step 3 Add the uplink interfaces to the Smart Link group and specify the master and slave interfaces.
Ensure that STP is disabled on the uplink interfaces.
Step 4 Configure load balancing on SwitchA.

[SwitchA-smlk-group1] load-balance instance 10 slave
Step 5 Enable the revertive switching and set the wait-to-restore (WTR) time.
Step 6 Enable the sending of Flush packets.
Step 7 Enable Smart Link on SwitchA.

Step 8 Enable the receiving of Flush packets.
simple 123
simple 123

# Run the display smart-link group command to view information about the Smart Link group
on SwitchA. If the following information is displayed, it indicates that the configuration is
successful.
l The Smart Link function is enabled.

l The control VLAN ID is 10.
l GigabitEthernet0/0/1 is the master interface and is in Active state, and GigabitEthernet0/0/2
is the slave interface and is in Inactive state. The load balancing function is configured.
Load-Balance Instance: 10
10
----------------------------------------------------------------------

:00
:00
# Run the shutdown command to shut down GigabitEthernet0/0/1, and you can find that
GigabitEthernet0/0/1 is in Inactive state and GigabitEthernet0/0/2 is in Active state.
[SwitchA-GigabitEthernet0/0/1] display smart-link group 1
10
----------------------------------------------------------------------
GigabitEthernet0/0/1 Master Inactive 1 0000/00/00 00:00:00 UTC+00

:00
GigabitEthernet0/0/2 Slave Active 1 0000/00/00 00:00:00 UTC+00
:00
# Run the undo shutdown command to enable GE 1/0/1 and wait for 30 seconds. Then you can
find that GigabitEthernet0/0/1 is in Active state and GigabitEthernet0/0/2 is in Inactive state.
[SwitchA-GigabitEthernet0/0/1] display smart-link group 1
10
----------------------------------------------------------------------

:00
:00
----End

Configuration Files
#
sysname SwitchA
#
vlan batch 10 100 500
#
instance 10 vlan 10 100 500
#
port trunk allow-pass vlan 10 100 500
stp disable
#
stp disable
#
smart-link group 1
load-balance instance 10 slave
restore enable
smart-link enable
timer wtr 30
#
return

#
sysname SwitchB
#
#
#
return

#
sysname SwitchC
#
#
#
return
2.6.3 Example for Applying the Smart Link Functions
As shown in Figure 2-6, Switch C on the MAN is connected to user networks. It accesses the
backbone network through uplink devices Switch A and Switch B in dual-homed mode.

Switch A and Switch C are connected to uplink devices in dual-homed mode. One out of each
link pair needs to be blocked to prevent loops. When the active link fails, the data flows can be
rapidly switched to the standby link to ensure normal services.
In addition, a monitoring mechanism is required to prevent service interruption caused by faults

of the uplink. This monitoring mechanism enables the downlink to quickly detect the fault of
the uplink. When the uplink fails, link switching can be performed immediately to shorten the
duration of service interruption.
Figure 2-6 Networking of Smart Link application
IP/MPLS
core
network
Smart Link group

GE0/0/1 GE0/0/1
GE0/0/2
Monitor Link group Monitor Link group
GE0/0/3
SwitchA GE0/0/3 SwitchB
Smart Link group GE0/0/1 GE0/0/2
SwitchC
Active link
User1 User2 Inactive link
1. Configure Smart Link groups on Switch A and Switch C, and add uplink interfaces to the
groups.
2. Configure Monitor Link groups on Switch Switch A and Switch B.
3. Enable Switch A and Switch C to send Flush packets.
4. Enable Switch A and Switch C to receive Flush packets.

Data Preparation
l Numbers of interfaces on Switch A, Switch B, and Switch C
l IDs of the Smart Link groups
l IDs of the Monitor Link groups and the numbers of the downlinks
Procedure
Step 1 Configure the same control VLAN on Switch A, Switch B, and Switch C. Add the interfaces of
the Smart Link group or Monitor Link group to this VLAN.
The configuration procedures are not mentioned here. For details, see "VLAN Configuration"
in the Quidway S5300 Series Ethernet Switches Configuration Guide - Ethernet.
Step 2 Create Smart Link groups and enable the functions of the groups.
# Configure Switch A.
[SwitchA-smlk-group1] quit
# Configure Switch C.
<SwitchC> system-view
[SwitchC] smart-link group 2
[SwitchC-smlk-group2] quit
Step 3 Add interfaces to Smart Link groups and specify the master and slave interfaces of each Smart
Link group
[SwitchA]smart-link group 1
[SwitchC-GigabitEthernet0/0/1] stp disable
[SwitchC-smlk-group2] port gigabitethernet 0/0/1 master
[SwitchC-smlk-group2] port gigabitethernet 0/0/2 slave
Step 4 Enable revertive switching and set the interval of revertive switching.

[SwitchC-smlk-group2] restore enable
[SwitchC-smlk-group2] timer wtr 30
Step 5 Enable the sending and receiving of Flush packets.

[SwitchA-GigabitEthernet0/0/3] smart-link flush receive control-vlan 10 password
simple 123
# Configure Switch B.
<SwitchB> system-view
simple 123
[SwitchC-smlk-group2] flush send control-vlan 10 password simple 123
Step 6 Enabling the Functions of the Smart Link Group

[SwitchC-smlk-group2] smart-link enable
[SwitchC-smlk-group2] quit
Step 7 Create Monitor Link groups and add the uplink and downlink interfaces to the Monitor Link
groups.
[SwitchA] monitor-link group 1
[SwitchA-mtlk-group1] smart-link group 1 uplink
[SwitchA-mtlk-group1] port gigabitethernet 0/0/3 downlink 1
[SwitchB] monitor-link group 2
[SwitchB-mtlk-group2] port gigabitethernet 0/0/1 uplink
[SwitchB-mtlk-group2] port gigabitethernet 0/0/3 downlink 1
Step 8 Set the revertive switching interval of the Monitor Link groups.
[SwitchA-mtlk-group1] timer recover-time 10
[SwitchB-mtlk-group2] timer recover-time 10


DeviceID: 0025-9e80-2494 Control-vlan ID: 10

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

:00
:00
<SwitchA> display monitor-link group 1
Monitor Link group 1 information :
Recover-timer is 10 sec.
Member Role State Last-up-time Last-down-tim
e
Smart-link1 UpLk DOWN 0000/00/00 00:00:00 UTC+00:00 0000/0
0/00 00:00:00 UTC+00:00
GigabitEthernet0/0/3 DwLk[1] DOWN 0000/00/00 00:00:00 UTC+00:00 0000/0
0/00 00:00:00 UTC+00:00
----End
Configuration Files
l Configuration file of Switch A
#
sysname SwitchA
#
vlan batch 10
#
stp disable
#
stp disable
#
#
smart-link group 1
smart-link enable
timer wtr 30
restore enable
#
monitor-link group 1
smart-link group 1 uplink
port GigabitEthernet0/0/3 downlink 1
timer recover-time 10
#
return
l Configuration file of Switch B

#
sysname SwitchB
#
vlan batch 10
#
#

#
monitor-link group 2
port GigabitEthernet0/0/1 uplink
port GigabitEthernet0/0/3 downlink 1
timer recover-time 10
#
return
l Configuration file of Switch C

#
sysname SwitchC
#
vlan batch 10
#
stp disable
#
stp disable
#
smart-link group 2
smart-link enable
timer wtr 30
restore enable
#
return

Configuration Guide - Reliability 3 RRPP Configuration
3 RRPP Configuration
About This Chapter
This chapter describes the basic knowledge, methods, and examples for configuring the Rapid
Ring Protection Protocol (RRPP).
3.1 Introduction to RRPP

This section describes the concept of RRPP.
3.2 RRPP Features Supported by the S5300
This section describes the RRPP features supported by the S5300.
3.3 Configuring Basic RRPP Functions
This section describes how to configure the basic RRPP functions.
3.4 Configuring RRPP Multi-Instance
This section describes how to configure the RRPP multi-instance feature.
3.5 Maintaining RRPP
Describes how to clear the RRPP statistics and debug RRPP.
This section provides several configuration examples of RRPP.

3 RRPP Configuration Configuration Guide - Reliability
3.1 Introduction to RRPP

This section describes the concept of RRPP.
Most metropolitan area networks (MANs) and LANs adopt the ring networking to ensure high
reliability. The services, however, are affected if any node on the ring fails. Generally, a ring
network adopts the Resilient Packet Ring (RPR) or Ethernet ring technology. The costs of the
RPR technology are high because it requires the dedicated hardware. As the Ethernet ring is
improved and its costs are low, increasing MANs and LANs adopt the Ethernet ring.
Currently, RSTP, MSTP, and RRPP are adopted to prevent loops on a Layer 2 network. RSTP
and MSTP are well developed, but the network converges in seconds.
RRPP is a link layer protocol used for Ethernet rings. RRPP can prevent broadcast storms caused
by data loops on a complete Ethernet ring. When a link on the Ethernet ring fails, nodes on the
ring can restore communication immediately through the backup link.
Compared with other Ethernet ring technologies, RRPP has the following advantages:
l Network convergence is fast, which can be complete within 50 ms.
l The number of nodes on the ring does not affect the convergence time. Therefore, RRPP
can be used on large-scaled networks.
l RRPP can prevent broadcast storms caused by data loops when an Ethernet ring network
is complete.
l When a link on the Ethernet ring fails, nodes on the ring can restore communication
immediately through the backup link.
l The cost is low.
3.2 RRPP Features Supported by the S5300

This section describes the RRPP features supported by the S5300.
Basic RRPP Functions

The concepts of RRPP are described based on Figure 3-1.

Figure 3-1 Application of crossed RRPP rings on the MAN
RRPP Domain
Master SwitchB
Node Edge Transit
SwitchD Node Transit Node
RRPP Sub-Ring 1
SwitchA
RRPP Major-Ring
SwitchC Master Node

Edge Transit
Master Node Transit Node
Node
RRPP Sub-Ring 2
SwitchE
l RRPP domain
An RRPP domain consists of a group of interconnected switches with the same domain ID
and control VLAN ID. An RRPP domain consists of the elements such as the RRPP major
ring and subring, control VLAN, master node, transit node, and primary port and secondary
port.
An RRPP domain is identified by its ID, which is an integer.
l RRPP ring
Physically, an RRPP ring corresponds to an Ethernet ring. An RRPP ring is a part of its
RRPP domain. An RRPP domain consists of one RRPP ring or multiple crossed RRPP
rings.
l RRPP major ring and subring
If an RRPP domain consists of multiple crossed RRPP rings, you can configure one ring
as the major ring and other rings as subrings by setting their levels.
An RRPP domain has only one major ring.
Protocol packets of subrings are transmitted in the major ring as data packets, and protocol
packets of the major ring are transmitted only in the major ring.
l Control VLAN
A VLAN that transmits RRPP protocol packets in an RRPP domain is called a control
VLAN. A control VLAN can contain only RRPP ports.
An RRPP domain is configured with two control VLANs: the primary control VLAN and
the sub control VLAN. You need to specify only the primary control VLAN. The VLAN
whose ID is one more than the ID of the primary control VLAN becomes the sub control
VLAN.

Different from a control VLAN, a data VLAN is used to transmit data packets. The data
VLAN can contain both the RRPP ports and non-RRPP ports.
l Master node
On an Ethernet ring, each switch is called a node. Each RRPP ring must have only one
master node.
l Transit node
On an RRPP ring, all nodes except the master node are transit nodes.
A transit node monitors the status of its directly connected RRPP links. When the link status
changes, the transit node informs the master node. The master node then determines the
policy for reacting to the change of the link status.
l Edge transit node
Edge transit node is a role of a switch on a subring. On the major ring, the switch functions
as a transit node or the master node. A switch can be configured as the master node on the
major ring and the edge transit node simultaneously.
The two edge transit nodes on two crossed rings are of the same level.
l Primary interface and secondary interface
On the master node and transit nodes, you can configure one of the two interfaces connected
to the Ethernet ring as the primary interface and the other as the secondary interface.
Hello Timer and Fail Timer

When RRPP detects the link status on the Ethernet ring, the master node sends Hello packets
according to the Hello timer and determines whether the secondary interface receives the Hello
packets according to the Fail timer.
l The value of the Hello timer specifies the interval at which the master node sends Hello
packets from the primary interface.
l The Fail timer specifies the maximum interval between two Hello packets received on the
secondary interface.
RRPP Multi-Instance
l Multi-instance
In the RRPP networking, one RRPP ring contains only one master node. When the master
node is in Complete state, the blocked secondary interface rejects all the data packets. In
this manner, all the data packets are transmitted through the same path on the RRPP ring.
The link of the secondary interface on the master node is idle, which wastes bandwidth.
The RRPP multi-instance feature is implemented based on domains. In the RRPP domain,
all the interfaces, nodes, and topologies conform to the RRPP principle. In the RRPP multi-
instance networking, multiple domains can be configured on an RRPP ring.
Each domain contains one or more instances, and each instance represents a VLAN range.
The VLANs in a domain are protected VLANs in the RRPP domain. A protected VLAN
can be a data VLAN, the control VLAN on the major ring, or the control VLAN on a subring
in the RRPP domain.
In the RRPP multi-instance networking, a ring can contain multiple master nodes. Load
balancing and link backup can be implemented based on the blocking state of the secondary
interface on the master node.
As shown in Figure 3-2, Switch A, Switch B, Switch C, Switch D, and Switch E form a
ring with multiple instances. Two domains are configured on the ring. Switch C is the

master node in domain 2 and Switch D is the master node in domain 1. The primary and
secondary interfaces on each master node are marked in Figure 3-2.
Domain 1 is configured with instance 1, which represents VLANs 100 to 200. When Switch
D is in Complete state, its secondary interface is blocked. Therefore, packets of VLANs
100 to 200 are transmitted though the path Switch A -> Switch C -> Switch E.
Domain 2 is configured with Instance 2, which represents VLANs 201 to 400. When Switch
C is in Complete state, its secondary interface is blocked. Therefore, packets of VLANs
201 to 400 are transmitted though the path Switch B -> Switch D -> Switch E.
Figure 3-2 Networking diagram of RRPP multi-instance

SwitchC
S(Block) Master 2
SwitchA P
Instance1:
VLAN 100-200
SwitchE
Backbone
network
Instance2:
VLAN 201-400
SwitchB P
S(Block) Master 1
SwitchD
Block
P Primary port
S Secondary port
Instance1: VLAN 100-200
Instance2: VLAN 201-400
l Ring group
A ring group is configured for the subrings in the networking of crossed rings with multiple
RRPP instances.
In the networking of crossed rings with multiple RRPP instances, if multiple subrings exist,
the following may occur:
Multiple subrings share the same edge node and the same assistant edge node. In addition,
the edge node and assistant edge node are located on the same major ring. That is, the Edge-
Hello packets of the edge node are transmitted to the assistant edge node along the same
path.

Figure 3-3 Ring group in RRPP multi-instance application
SwitchE
Master
SwitchA SwitchC
Domain 1 sub ring 2

Edge
Domain 2 sub ring 2
Domain 1 Major ring 1
Domain 1 sub ring 3 Domain 2 Major ring 1
Domain 2 sub ring 3

Assistant
Master SwitchB
SwitchF
domain 1
domain 2
To reduce the number of Edge-Hello packets sent and received on a switch and improve
the system performance, you can add the subrings with the same edge node and same
assistant edge node to a ring group. Then configure a member subring to add Edge-Hello
packets to check the channel of protocol packets on the major ring.
There are four subrings in Figure 3-3, namely, ring 2 in domain 1, ring 3 in domain 1, ring
2 in domain 2, and ring 3 in domain 2. The subrings have the same major ring; therefore,
they can be added to a ring group. After the subrings are added to a ring group, only one
subring sends Edge-Hello packets, thus reducing the number of Edge-Hello packets.
l Link-Up-Delay timer
To avoid flapping on the ring caused by frequent changes of transmission paths, you can
set a Link-Up-Delay timer on the master node.
If master node receives its own Hello packet before the Failed timer expires, it transits to
the Complete state after a certain delay. This reduces link flapping on the ring.
The master node processes the Hello packets received from the secondary interface only
after the Link-Up-Delay timer expires.
3.3 Configuring Basic RRPP Functions

This section describes how to configure the basic RRPP functions.

3.3.2 Creating Instances

3.3.3 Configuring Interfaces on the RRPP Ring

3.3.4 Creating an RRPP Domain
3.3.5 Specifying Protected VLANs
3.3.6 Creating a Control VLAN
3.3.7 Creating an RRPP Ring
3.3.8 Enabling the RRPP Ring
3.3.9 Enabling the RRPP Protocol
3.3.10 (Optional) Setting the Hello Timer and Fail Timer of an RRPP Domain
RRPP is used for the networking of a single ring or multiple crossed rings. When configuring
RRPP, you need to configure roles for all nodes on the RRPP ring.
NOTE
Only one protocol, namely, RRPP or STP, can be configured on an interface.

RRPP does not adopt any auto selection mechanism. Therefore, RRPP can realize the ring detection and
protection functions only when each node in the ring is correctly configured. Make sure all the
configurations are correct.
Before configuring RRPP functions, complete the following tasks:
l Establishing the physical ring topology

l Configuring link attributes for interfaces
Data Preparation
To configure RRPP functions, you need the following data.
No. Data
1 ID of the RRPP domain
2 ID of the control VLAN in the RRPP domain
3 IDs of all RRPP rings in the RRPP domain
4 Values of the Hello timer and Fail timer in the RRPP domain
5 Names of the interfaces on the RRPP rings

Context
Do as follows on the S5300 that you want to add to an RRPP domain with multiple instances.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The MST region view is displayed.
Step 3 Run the following commands as required.

l Run:
The mapping between an instance and VLANs is configured.

l Run:
vlan-mapping modulo modulo
The default algorithm is used to determine the mapping between instances and VLANs.
The vlan-mapping modulo command is used to map a VLAN to the instance with the ID being
(VLAN ID - 1)%modulo + 1. Assume that modulo is set to 16. The S5300 maps VLAN 1 to
instance 1, VLAN 2 to instance 2, VLAN 16 to instance 16, VLAN 17 to instance 1, and so
forth.
The control VLANs of the major ring and the subrings must be contained in the VLAN list.
A domain supports up to 49 instances, among which instance 0 is the default instance and does
By default, all VLANs are mapped to instance 0.
Step 4 Run:
----End
Context
Do as follows on the S5300 on which interfaces need to be added to the RRPP ring.

Procedure
Step 1 Run:
system-view

Step 2 Run:
The interface view is displayed.

RRPP rings can be configured only on GE interfaces,XGigabitEthernet and Eth-Trunk
interfaces.
An interface cannot be configured as an RRPP interface if the Smart Link, LDT, MUX VLAN
or MSTP is configured on the interface.
The interface is configured as a trunk interface.

By default, an interface is a hybrid interface.
An RRPP interface needs to allow packets of control VLANs and data VLANs to pass through;
therefore, the RRPP interface must be configured as a trunk interface or hybrid interface.
Step 4 Run:
port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } &<1-10> | all }
IDs of the data VLANs whose packets are allowed to pass through the RRPP interface are
specified.
After you specify the control VLAN by running the control-vlan command in the RRPP domain
view and run the ring node-mode command, all the interfaces on the RRPP ring allow packets
of this VLAN to pass through. Therefore, you need only to specify the data VLANs in this step.
Step 5 Run:
stp disable
STP is disabled on the RRPP interface.

By default, STP is enabled on all interfaces of the S5300. Before creating an RRPP ring, disable
STP on the interfaces that need to be added to the RRPP ring.
----End
Context
Do as follows on all S5300s in the RRPP domain.
Procedure
Step 1 Run:
system-view


Step 2 Run:
rrpp domain domain-id
An RRPP domain is created.

When creating an RRPP domain, you need to specify the domain ID. If the domain exists, the
domain view is displayed.
You can create up to eight domains on S5300.
----End
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
The RRPP domain view is displayed.

Step 3 Run:
protected-vlan reference-instance { { instance-id1 [ to instance-id2 ] } &<1-10> |
all }
A list of protected VLANs in the RRPP domain is specified.

All the VLANs whose packets need to pass through an RRPP interface, including the control
VLANs and data VLANs, must be configured as protected VLANs.
NOTE
When configure the list of protected VLANs, pay attention to the following points:
l Protected VLANs must be configured before you configure an RRPP ring.
l You can delete or change existing protected VLANs before configuring an RRPP ring. The protected
VLANs cannot be changed after the RRPP ring is configured.
l In the same physical topology, the control VLAN of a domain cannot be configured as a protected
VLAN of another domain.
l The control VLAN must be included in the protected VLANs; otherwise, the RRPP ring cannot be
configured.
l The control VLAN can be mapped to other instances before the RRPP ring is created. After the RRPP
ring is created, the mapping cannot be changed unless you delete the RRPP domain.
l When the mapping between an instance and VLANs changes, the protected VLANs of the RRPP
domain also change.
l All the VLANs allowed by an RRPP interface should be configured as protected VLANs.
----End

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
control-vlan vlan-id
A control VLAN is created.

A VLAN that transmits RRPP protocol packets in an RRPP domain is called a control VLAN.
A control VLAN can contain only RRPP ports.
An RRPP domain is configured with two control VLANs: the primary control VLAN and the
sub control VLAN. You need to specify only the primary control VLAN. The VLAN whose ID
is one more than the ID of the primary control VLAN becomes the sub control VLAN.
NOTE
The control VLAN specified by vlan-id and the sub-control VLAN specified by vlan-id+1 must be new
VLANs that have not been created before and are not used in port trunking, VLAN mapping, or VLAN
stacking.
After configuring a control VLAN, you cannot directly modify its configuration. To modify the
configuration of the control VLAN, you need to delete the domain, and then configure a new control VLAN.
The sub control VLAN is also deleted when you delete the domain.
----End
Context
NOTE
By default, STP is enabled on all interfaces of the S5300. RRPP and STP cannot be enabled on the same
interface. Therefore, before creating an RRPP ring, you need to use the stp disable command to disable
STP on the interfaces to be added to the RRPP ring.
Procedure
Step 1 Run:
system-view


Step 2 Run:

Step 3 Run:
ring ring-id node-mode { master | transit } primary-port interface-type interface-
number secondary-port interface-type interface-number level level-value
An RRPP ring is created.

interfaces.
The level 0 indicates the major ring, and the level 1 indicates the subring.
A domain can contain only one major ring. Before creating a subring, you must create the major
ring.
The master node on a subring cannot function as an edge node or an assistant edge node.
An S2300EI supports 2 rings, and an S3300 or S5300 supports 16 rings.
NOTE
When the major ring intersects with the subring, broadcast storms may be caused by RRPP packets on the
subring if you configure the subring before configuring the major ring. In this case, RRPP packets on the
major ring are discarded on transit nodes. As a result, the primary and secondary interfaces cannot receive
RRPP packets and thus cannot block related interfaces, causing incorrect RRPP status on the interfaces.
To prevent this problem, configure the major ring and then the subring.
Step 4 Run:
ring ring-id node-mode { edge | assistant-edge } common-port interface-type
interface-number edge-port interface-type interface-number
The edge node and assistant edge node of a subring are configured.
The common port of the edge node and assistant edge node must be on the major ring.
The system automatically sets the level of the ring where the edge node and assistant edge node
reside to 1.
----End
Context
NOTE
The RRPP ring can be activated only when both the RRPP ring and the RRPP protocol are enabled.
Procedure
Step 1 Run:
system-view


Step 2 Run:

Step 3 Run:
ring ring-id enable
The RRPP ring is enabled.
----End
Context
NOTE
Procedure
Step 1 Run:
system-view

Step 2 Run:
rrpp enable
The RRPP protocol is enabled.

By default, the RRPP protocol is disabled.
----End
3.3.10 (Optional) Setting the Hello Timer and Fail Timer of an RRPP
Domain
Context
Do as follows on the master node in the RRPP domain.
Procedure
Step 1 Run:
system-view

Step 2 Run:


Step 3 Run:
timer hello-timer hello-value fail-timer fail-value
The Hello timer and Fail timer of the RRPP domain are set.
The value of the Fail timer must be three times the value of the Hello timer or greater.
----End
Procedure
l Run the display stp region-configuration command to check the mapping between MSTIs
and VLANs.
l Run the display rrpp brief [ domain domain-id ] command to check brief information
about an RRPP domain.
l Run the display rrpp verbose domain domain-id [ ring ring-id ] command to check
detailed information about an RRPP domain.
l Run the display rrpp statistics domain domain-id [ ring ring-id ] command to check the
statistics of packets in an RRPP domain.
----End
Example
Run the display stp region-configurationcommand, and you can view the mapping between
MSTIs and VLANs. The following is an example:
<Quidway> display stp region-configuration
Oper configuration
Format selector :0
Region name :00e0cd568d00
Revision level :0
Instance Vlans Mapped

0 3 to 99, 301 to 4094
1 1, 100 to 200
2 2, 201 to 300
Run the display rrpp brief command, and you can view information such as the node mode,
RRPP status, control VLAN, protected VLAN, and values of timers. The following is an
example:
<Quidway> display rrpp brief
Abbreviations for Switch Node Mode :
M - Master , T - Transit , E - Edge , A - Assistant-Edge
RRPP Protocol Status: Disable

RRPP Working Mode: HW
RRPP Linkup Delay Timer: 1 sec (0 sec default).
Number of RRPP Domains: 1
Domain Index : 1
Control VLAN : major 30 sub 31
Protected VLAN : Reference Instance 10
Hello Timer : 1 sec(default is 1 sec) Fail Timer : 6 sec(default is 6 sec)
Ring Ring Node Primary/Common Secondary/Edge Is

ID Level Mode Port Port Enabled

-------------------------------------------------------------------------------
1 0 M GigabitEthernet0/0/2 GigabitEthernet0/0/3 No
Run the display rrpp verbose command, and you can view detailed information such as the
control VLAN, protected VLAN, timers, node mode, and port status. The following is an
example:
<Quidway> display rrpp verbose domain 1 ring 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Ring State : Complete
Is Enabled : Enable Is Active : Yes
Primary port : GigabitEthernet0/0/1 Port status: UP
Secondary port : GigabitEthernet0/0/2 Port status: BLOCKED
Run the display rrpp statistics command, and you can view the statistics of sent and received
packets. The following is an example:
<Quidway> display rrpp statistics domain 1 ring 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Is Active : Yes
Primary port : GigabitEthernet0/0/1
Packet LINK COMMON COMPLETE EDGE MAJOR Packet
Direct HEALTH DOWN FDB FDB HELLO FAULT Total
-------------------------------------------------------------------------------
Send 2934 0 1 1 0 0 2936
Rcv 0 1 0 0 0 0 1
Secondary port: GigabitEthernet0/0/2
-------------------------------------------------------------------------------
Send 0 0 1 0 0 0 1
Rcv 2928 1 0 0 0 0 2929
3.4 Configuring RRPP Multi-Instance

This section describes how to configure the RRPP multi-instance feature.



3.4.10 (Optional) Creating a Ring Group
3.4.11 (Optional) Setting the Link-Up-Delay Timer
3.4.12 (Optional) Setting the Hello Timer and Fail Timer of an RRPP Domain
RRPP multi-instance meets the requirements of a complicated network, as shown in Figure
3-4. The CE and UPE devices form two RRPP subrings. Each CE device is connected to two
UPE devices. The four UPE devices and a PE device form an RRPP ring. The PE device transmits
user data to the backbone network.

Figure 3-4 Application scenario of RRPP multi-instance
Backbone
network
PE-AGG
UPEC
UPED
domain 1 ring 1
IPTV VLAN101-200
domain 2 ring 1
HSI VLAN601-800 UPEB
UPEA
domain 1 ring2: domain 1 ring 3:
IPTV VLAN101-200 IPTV VLAN101-200
domain 2 ring 2: domain 2 ring 3:

HSI VLAN601-800 HSI VLAN601-800
CEA
CEC
IPTV HSI
IPTV HSI
VLAN101-200 VLAN600-800 VLAN101-200 VLAN600-800
domain 1
domain 2
CE: Customer Edge PE-AGG: PE-Aggregation
UPE: Underlayer Provider Edge IPTV: Internet Protocol Television
HSI: High Speed Internet
The IPTV and HSI services are deployed in two domains and they share the same RRPP ring.
By configuring multiple instances on the RRPP ring, you can implement load balancing for the
IPTV and HSI services. Traffic of IPTV services is transmitted through domain 1, and traffic of
HSI services is transmitted through Domain 2.
Before configuring RRPP multi-instance, complete the following tasks:

l Building the ring topology

l Setting link layer parameters of interfaces
Data Preparation
To configure RRPP multi-instance, you need the following data.
No. Data
1 IDs of the RRPP domains
2 IDs of the control VLANs in each RRPP domain
3 IDs of the protected VLANs in each RRPP domain
4 IDs of all RRPP rings in the RRPP domains
5 Names of the interfaces on the RRPP rings
6 (Optional) Value of the Link-Up timer
7 (Optional) Values of the Hello timer and Fail timer in the RRPP domains
Context
Do as follows on the S5300 that you want to add to an RRPP domain with multiple instances.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The MST region view is displayed.
Step 3 Run the following commands as required.

l Run:
The mapping between an instance and VLANs is configured.

l Run:
vlan-mapping modulo modulo
The default algorithm is used to determine the mapping between instances and VLANs.
The vlan-mapping modulo command is used to map a VLAN to the instance with the ID being
(VLAN ID - 1)%modulo + 1. Assume that modulo is set to 16. The S5300 maps VLAN 1 to

instance 1, VLAN 2 to instance 2, VLAN 16 to instance 16, VLAN 17 to instance 1, and so

forth.
The control VLANs of the major ring and the subrings must be contained in the VLAN list.
A domain supports up to 49 instances, among which instance 0 is the default instance and does
By default, all VLANs are mapped to instance 0.
Step 4 Run:
----End
Context
Do as follows on the S5300 on which interfaces need to be added to the RRPP ring.
Procedure
Step 1 Run:
system-view
Step 2 Run:

interfaces.
An interface cannot be configured as an RRPP interface if the Smart Link, LDT, MUX VLAN
or MSTP is configured on the interface.

The interface is configured as a trunk interface.
By default, an interface is a hybrid interface.
An RRPP interface needs to allow packets of control VLANs and data VLANs to pass through;
therefore, the RRPP interface must be configured as a trunk interface or hybrid interface.
Step 4 Run:
port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } &<1-10> | all }
IDs of the data VLANs whose packets are allowed to pass through the RRPP interface are
specified.

After you specify the control VLAN by running the control-vlan command in the RRPP domain
view and run the ring node-mode command, all the interfaces on the RRPP ring allow packets
of this VLAN to pass through. Therefore, you need only to specify the data VLANs in this step.
Step 5 Run:
stp disable
STP is disabled on the RRPP interface.
By default, STP is enabled on all interfaces of the S5300. Before creating an RRPP ring, disable
STP on the interfaces that need to be added to the RRPP ring.
----End
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
An RRPP domain is created.
When creating an RRPP domain, you need to specify the domain ID. If the domain exists, the
domain view is displayed.
You can create up to eight domains on S5300.
----End
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:

Step 3 Run:
protected-vlan reference-instance { { instance-id1 [ to instance-id2 ] } &<1-10> |
all }
A list of protected VLANs in the RRPP domain is specified.
All the VLANs whose packets need to pass through an RRPP interface, including the control
VLANs and data VLANs, must be configured as protected VLANs.
NOTE
When configure the list of protected VLANs, pay attention to the following points:
l Protected VLANs must be configured before you configure an RRPP ring.
l You can delete or change existing protected VLANs before configuring an RRPP ring. The protected
VLANs cannot be changed after the RRPP ring is configured.
l In the same physical topology, the control VLAN of a domain cannot be configured as a protected
VLAN of another domain.
l The control VLAN must be included in the protected VLANs; otherwise, the RRPP ring cannot be
configured.
l The control VLAN can be mapped to other instances before the RRPP ring is created. After the RRPP
ring is created, the mapping cannot be changed unless you delete the RRPP domain.
l When the mapping between an instance and VLANs changes, the protected VLANs of the RRPP
domain also change.
l All the VLANs allowed by an RRPP interface should be configured as protected VLANs.
----End
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
control-vlan vlan-id
A control VLAN is created.
A VLAN that transmits RRPP protocol packets in an RRPP domain is called a control VLAN.
A control VLAN can contain only RRPP ports.

An RRPP domain is configured with two control VLANs: the primary control VLAN and the
sub control VLAN. You need to specify only the primary control VLAN. The VLAN whose ID
is one more than the ID of the primary control VLAN becomes the sub control VLAN.
NOTE
The control VLAN specified by vlan-id and the sub-control VLAN specified by vlan-id+1 must be new
VLANs that have not been created before and are not used in port trunking, VLAN mapping, or VLAN
stacking.
After configuring a control VLAN, you cannot directly modify its configuration. To modify the
configuration of the control VLAN, you need to delete the domain, and then configure a new control VLAN.
The sub control VLAN is also deleted when you delete the domain.
----End
Context
NOTE
By default, STP is enabled on all interfaces of the S5300. RRPP and STP cannot be enabled on the same
interface. Therefore, before creating an RRPP ring, you need to use the stp disable command to disable
STP on the interfaces to be added to the RRPP ring.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
ring ring-id node-mode { master | transit } primary-port interface-type interface-
number secondary-port interface-type interface-number level level-value
An RRPP ring is created.

interfaces.
The level 0 indicates the major ring, and the level 1 indicates the subring.
A domain can contain only one major ring. Before creating a subring, you must create the major
ring.
The master node on a subring cannot function as an edge node or an assistant edge node.
An S2300EI supports 2 rings, and an S3300 or S5300 supports 16 rings.

NOTE
When the major ring intersects with the subring, broadcast storms may be caused by RRPP packets on the
subring if you configure the subring before configuring the major ring. In this case, RRPP packets on the
major ring are discarded on transit nodes. As a result, the primary and secondary interfaces cannot receive
RRPP packets and thus cannot block related interfaces, causing incorrect RRPP status on the interfaces.
To prevent this problem, configure the major ring and then the subring.
Step 4 Run:
ring ring-id node-mode { edge | assistant-edge } common-port interface-type
interface-number edge-port interface-type interface-number
The edge node and assistant edge node of a subring are configured.
The common port of the edge node and assistant edge node must be on the major ring.
The system automatically sets the level of the ring where the edge node and assistant edge node
reside to 1.
----End
Context
NOTE
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
ring ring-id enable
The RRPP ring is enabled.
----End
Context
NOTE

Procedure
Step 1 Run:
system-view

Step 2 Run:
rrpp enable
The RRPP protocol is enabled.

By default, the RRPP protocol is disabled.
----End
3.4.10 (Optional) Creating a Ring Group
Context
Do as follows on an edge node or assistant edge node (supported by RRPP defined by Huawei)
Procedure
Step 1 Run:
system-view

Step 2 Run:
rrpp ring-group ring-group-id
A ring group is created.

A ring group can be created only on an edge node or assistant edge on a subring.
All the subrings in a ring group must be on the same type of nodes, that is, edge nodes or assistant
edge nodes.
Step 3 Run:
domain domain-id ring { ring-id1 [ to ring-id2 ] } &<1-10>
Subrings are added to the ring group.

The subrings in the same ring group share the same edge node and the same assistant edge node.
A subring can belong to only one ring group. Each ring group can contain up to 15 subrings.
When you add a subring to a ring group or delete a subring from the ring group, pay attention
to the following points:
l To add an activated subring to a ring group, add the subring to the ring group on the assistant
edge node, and then perform the same operation on the edge node.
l To delete an activated subring from a ring group, delete the subring from the ring group on
the edge node, and then perform the same operation on the assistant edge node.
l All subrings in a ring group must have the same common port.
----End

3.4.11 (Optional) Setting the Link-Up-Delay Timer
Context
Do as follows on the master node.
Procedure
Step 1 Run:
system-view
Step 2 Run:
rrpp linkup-delay-timer linkup-delay-timer-value
The delay timer for the RRPP ring to transit from the Failed state to the Complete state is set.
The value of linkup-delay-timer-value must be smaller than or equal to the value of the Fail timer
minus 2 times HELLO timer in any domain.
----End
3.4.12 (Optional) Setting the Hello Timer and Fail Timer of an RRPP
Domain
Context
Do as follows on the master node in the RRPP domain.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
timer hello-timer hello-value fail-timer fail-value
The Hello timer and Fail timer of the RRPP domain are set.
The value of the Fail timer must be three times the value of the Hello timer or greater.
----End

Procedure
l Run the display stp region-configuration command to check the mapping between MSTIs
and VLANs.
l Run the display rrpp brief [ domain domain-id ] command to check brief information
about an RRPP domain.
l Run the display rrpp verbose domain domain-id [ ring ring-id ] command to check
detailed information about an RRPP domain.
l Run the display rrpp statistics domain domain-id [ ring ring-id ] command to check the
statistics of packets in an RRPP domain.
----End
Example
Run the display stp region-configurationcommand, and you can view the mapping between
MSTIs and VLANs. The following is an example:
<Quidway> display stp region-configuration
Oper configuration
Format selector :0
Revision level :0

0 3 to 99, 301 to 4094
1 1, 100 to 200
2 2, 201 to 300
Run the display rrpp brief command, and you can view information such as the node mode,
RRPP status, control VLAN, protected VLAN, and values of timers. The following is an
example:
<Quidway> display rrpp brief
RRPP Protocol Status: Disable

Domain Index : 1
-------------------------------------------------------------------------------
1 0 M GigabitEthernet0/0/2 GigabitEthernet0/0/3 No
Run the display rrpp verbose command, and you can view detailed information such as the
control VLAN, protected VLAN, timers, node mode, and port status. The following is an
example:
<Quidway> display rrpp verbose domain 1 ring 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master


Run the display rrpp statistics command, and you can view the statistics of sent and received
packets. The following is an example:
<Quidway> display rrpp statistics domain 1 ring 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Is Active : Yes
Primary port : GigabitEthernet0/0/1
-------------------------------------------------------------------------------
Send 2934 0 1 1 0 0 2936
Rcv 0 1 0 0 0 0 1
Secondary port: GigabitEthernet0/0/2
-------------------------------------------------------------------------------
Send 0 0 1 0 0 0 1
Rcv 2928 1 0 0 0 0 2929
3.5 Maintaining RRPP

Describes how to clear the RRPP statistics and debug RRPP.
3.5.1 Clearing RRPP Statistics

3.5.2 Debugging RRPP
3.5.1 Clearing RRPP Statistics
Context
CAUTION
RRPP statistics cannot be restored after you clear them. So, confirm the action before you use
the command.
Procedure
Step 1 Run the reset rrpp statistics domain domain-id [ ring ring-id ] command in the user view to
clear the RRPP statistics.
----End

3.5.2 Debugging RRPP
Context
CAUTION
Debugging affects the performance of the system. So, after debugging, run the undo debugging
rrpp all command to disable it immediately.
When an RRPP fault occurs, run the following debugging command in the user view to locate
the fault.
Procedure
Step 1 Run the debugging rrpp [ domain domain-id [ ring ring-id ] ] { error | event | packet | all }
command to enable debugging of the RRPP protocol.
----End

This section provides several configuration examples of RRPP.
3.6.1 Example for Configuring a Single RRPP Ring

3.6.2 Example for Configuring Crossed RRPP Rings with a Single Instance
3.6.3 Example for Configuring Tangent RRPP Rings
3.6.4 Example for Configuring a Single RRPP Ring with Multiple Instances
3.6.5 Example for Configuring Crossed RRPP Rings with Multiple Instances(HW version)
3.6.6 Example for Configuring Tangent RRPP Rings with Multiple Instances
3.6.1 Example for Configuring a Single RRPP Ring

As shown in Figure 3-5, Switch A, Switch B, and Switch C support the RRPP function. Switch
A, Switch B, and Switch C are on ring 1 of RRPP domain 1. The data of VLANs 100 to 300
needs to be protected.

Figure 3-5 Networking diagram of a single RRPP ring

SwitchB
GE0/0/2
GE0/0/1 GE0/0/1
Ring 1
GE0/0/2 GE0/0/2
SwitchC
GE0/0/1
SwitchA
Primary Port
Secondary port
1. Map instance 1 to VLANs 100 to 300.
2. Locate Switch A, Switch B, and Switch C on ring 1 of RRPP domain 1.
3. Configure Switch A as the master node on ring 1, and configure Switch B and Switch C as
transit nodes on ring 1.
Data Preparation
To complete the configuration, you need the following data.
l Numbers of the RRPP interfaces
l Control VLAN ID of ring 1
Procedure
Step 1 Map instance 1 to VLANs 100 to 200.
[Quidway] sysname Switch A
[SwitchA-mst-region] instance 1 vlan 20 21 100 to 300
The configurations of Switch B and Switch C are similar to the configuration of Switch A. The
detailed configurations are omitted here.
Step 2 Create an RRPP domain and the control VLAN.
# On the master node of ring 1, namely Switch A, create RRPP domain 1 and configure VLAN
20 as the main control VLAN.
[SwitchA] rrpp domain 1
[SwitchA-rrpp-domain-region1] control-vlan 20
[SwitchA-rrpp-domain-region1] quit

# On the transit node of ring 1, namely Switch B, create RRPP domain 1 and configure VLAN
[Quidway] sysname SwitchB
[SwitchB] rrpp domain 1
[SwitchB-rrpp-domain-region1] control-vlan 20
[SwitchB-rrpp-domain-region1] quit
# On the master node of ring 1, namely SwitchC, create RRPP domain 1 and configure VLAN
[Quidway] sysname SwitchC
[SwitchC] rrpp domain 1
[SwitchC-rrpp-domain-region1] control-vlan 20
[SwitchC-rrpp-domain-region1] quit
Step 3 Configure the interfaces to be added to the RRPP ring as trunk interfaces, allow VLANs 100 to
300 on the interfaces, and disable STP on the interfaces.
[SwitchA-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[SwitchB-GigabitEthernet0/0/1] port link-type trunk
[SwitchB-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[SwitchB-GigabitEthernet0/0/1] stp disable
[SwitchC-GigabitEthernet0/0/1] port link-type trunk
[SwitchC-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
Step 4 Configure a protection VLAN and create the RRPP ring.

# Configure the protection VLAN on Switch A and configure Switch A as the master node of
RRPP ring 1 and specify the primary interface and secondary interface.
[SwitchA-rrpp-domain-region1] protected-vlan reference-instance 1
[SwitchA-rrpp-domain-region1] ring 1 node-mode master primary-port gigabitethernet

0/0/1 secondary-port gigabitethernet 0/0/2 level 0

[SwitchA-rrpp-domain-region1] ring 1 enable
# Configure the protection VLAN on Switch B and configure Switch B as the transit node of
[SwitchB-rrpp-domain-region1] protected-vlan reference-instance 1
[SwitchB-rrpp-domain-region1] ring 1 node-mode transit primary-port
gigabitethernet 0/0/1 secondary-port gigabitethernet 0/0/2 level 0
[SwitchB-rrpp-domain-region1] ring 1 enable
# Configure the protection VLAN on Switch C and configure Switch C as the transit node of
[SwitchC-rrpp-domain-region1] protected-vlan reference-instance 1
[SwitchC-rrpp-domain-region1] ring 1 node-mode transit primary-port
[SwitchC-rrpp-domain-region1] ring 1 enable
Step 5 Enable RRPP.

After configuring an RRPP ring, enable RRPP on each node on the ring so that the RRPP ring
can be activated.
# Enable RRPP on Switch A.
[SwitchA] rrpp enable
# Enable RRPP on SwitchB.

[SwitchB] rrpp enable
# Enable RRPP on SwitchC.

[SwitchC] rrpp enable

After the configurations are complete and network become stable, run the following commands
to verify the configuration. Take Switch A for example.
l Run the display rrpp brief command on SwitchA. The following information is displayed:
<SwitchA> display rrpp brief
RRPP Protocol Status: Enable

Domain Index : 1
ID Level Mode Port Port
Enabled
---------------------------------------------------------------------------
1 0 M GigabitEthernet0/0/1 GigabitEthernet0/0/2 Yes
You can find that RRPP is enabled on SwitchA. The main control VLAN of domain 1 is
VLAN 20 and the sub control VLAN is VLAN 21. SwitchA is the master node of ring 1.

GigabitEthernet0/0/1 is the primary interface, and GigabitEthernet0/0/2 is the secondary

interface.
l Run the display rrpp verbose domain command on SwitchA. Detailed information about
RRPP domain 1 is displayed as follows:
<SwitchA> display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Secondary port: GigabitEthernet0/0/2 Port status: BLOCKED
----End
Configuration Files
sysname SwitchA
#
vlan batch 20 to 21 100 to 300
#
rrpp enable
#
stp region-
configuration
instance 1 vlan 20 to 21 100 to
300
active region-
configuration
#
rrpp domain 1
control-vlan 20
protected-vlan reference-instance 1
ring 1 node-mode master primary-port GigabitEthernet 0/0/1 secondary-port
GigabitEthernet 0/0/2 level 0
ring 1 enable
#
port trunk allow-pass vlan 20 to 21 100 to 300
stp disable
#
stp disable
#

#
sysname SwitchB
#
#
rrpp enable
#
stp region-
configuration
300

active region-
configuration
#
rrpp domain 1
control-vlan 20
ring 1 node-mode transit primary-port GigabitEthernet 0/0/1 secondary-port
ring 1 enable
#
stp disable
#
stp disable
#
return
#
l Configuration file of the SwitchC

#
sysname SwitchC
#
#
rrpp enable
#
stp region-
configuration
300
active region-
configuration
#
rrpp domain 1
control-vlan 20
ring 1 enable
#
stp disable
#
stp disable
#
return
3.6.2 Example for Configuring Crossed RRPP Rings with a Single

Instance
As shown in Figure 3-6, Switch A, Switch B, Switch C, and Switch D support the RRPP
function. Switch A, Switch B, and Switch D are on ring 1 of domain , which is the major ring.
Switch A, Switch C, and Switch D are on ring 2 of domain 1, which is the subring. Switch A is

the edge node on ring 2 of domain 1, and Switch D is the assistant edge node on ring 2 of domain
1.
The main control VLAN ID is 10. The RRPP rings transmit data of VLAN 2 to VLAN 9.
Figure 3-6 Networking diagram of crossed RRPP rings with a single instance (Huawei version)
SwitchC
GE0/0/2 GE0/0/3
subring
GE0/0/1
SwitchA
GE0/0/1 GE0/0/2
GE0/0/2
GE0/0/3 SwitchD
SwitchB major ring GE0/0/1

GE0/0/1
GE0/0/2
1. Configure ring 1 (major ring) of domain 1 on Switch A, Switch B, and Switch C. Configure
VLAN 10 as the main control VLAN. Add the interfaces on the major ring and subring to
VLAN 2 to VLAN 9 so that the interfaces allow service packets of these VLANs to pass
through.
2. Configure ring 2 (subring) of domain 1on Switch A, Switch B, and Switch D.
3. Configure Switch B as the master node of the major ring and configure Switch A and Switch
D as transit nodes of the major ring.
4. Configure Switch C as the master node of the subring; configure Switch A as the edge node
of the subring; configure Switch D as the assistant edge node of the subring.
Data Preparation
l Numbers of the interfaces to be added to the RRPP rings
l Control VLAN IDs and data VLAN IDs
Procedure
Step 1 Configure Switch B as the master node of the major ring.
# Create data VLANs 2 to 9 on Switch B.
[SwitchB] vlan batch 2 to 9

Configure instance 1, and map it to the VLANs allowed by the RRPP interfaces and protected
VLANs.
[SwitchB] stp region-configuration
[SwitchB-mst-region] instance 1 vlan 2 to 11
[SwitchB-mst-region] active region-configuration
[SwitchB-mst-region] quit
# On SwitchB, configure domain 1. Then configure VLAN 10 as the main control VLAN and
instance 1 as the protected instance of domain 1.
# Disable STP on the interfaces to be added to the RRPP rings, configure the interfaces as trunk
interfaces, and configure the interfaces to allow service packets of VLAN 2 to VLAN 9 to pass
through.
# Configure the primary interface and secondary interface of the master node on the RRPP major
ring.
[SwitchB-rrpp-domain-region1] ring 1 node-mode master primary-port gigabitethernet
Step 2 Configure Switch C as the master node of the subring.
# Create data VLANs 2 to 9 on Switch C.

[SwitchC] vlan batch 2 to 9
VLANs.
[SwitchC] stp region-configuration
[SwitchC-mst-region] instance 1 vlan 2 to 11
[SwitchC-mst-region] active region-configuration
[SwitchC-mst-region] quit
# On Switch C, configure domain 1. Then configure VLAN 10 as the main control VLAN and

through.
# Configure the primary interface and secondary interface of the master node on the RRPP
subring.
[SwitchC-rrpp-domain-region1] ring 2 node-mode master primary-port gigabitethernet
Step 3 Configure Switch A as the transit node of the major ring and the edge transit node of the subring.
# Create data VLANs 2 to 9 on Switch A.
[SwitchA] vlan batch 2 to 9
VLANs.
[SwitchA-mst-region] instance 1 vlan 2 to 11
# On SwitchA, configure domain 1. Then configure VLAN 10 as the main control VLAN and
through.

# Configure the primary interface and secondary interface of the transit node on the RRPP major
ring.
[SwitchA-rrpp-domain-region1] ring 1 node-mode transit primary-port
# Configure the common interface and edge interface of the edge transit node on the subring.
[SwitchA-rrpp-domain-region1] ring 2 node-mode edge common-port gigabitethernet
0/0/2 edge-port gigabitethernet 0/0/3
Step 4 Configure Switch D as the transit node of the major ring and the assistant edge node of the
subring.
# Create data VLANs 2 to 9 on Switch D.
[SwitchD] vlan batch 2 to 9
VLANs.
[Quidway] sysname SwitchD
[SwitchD] stp region-configuration
[SwitchD-mst-region] instance 1 vlan 2 to 11
[SwitchD-mst-region] active region-configuration
[SwitchD-mst-region] quit
# On Switch D, configure domain 1. Then configure VLAN 10 as the main control VLAN and
[SwitchD] rrpp enable
[SwitchD] rrpp domain 1
[SwitchD-rrpp-domain-region1] control-vlan 10
[SwitchD-rrpp-domain-region1] protected-vlan reference-instance 1
[SwitchD-rrpp-domain-region1] quit
through.
[SwitchD] interface gigabitethernet 0/0/1
[SwitchD-GigabitEthernet0/0/1] port link-type trunk
[SwitchD-GigabitEthernet0/0/1] port trunk allow-pass vlan 2 to 9
[SwitchD-GigabitEthernet0/0/1] stp disable
[SwitchD-GigabitEthernet0/0/1] quit
# Configure the primary interface and secondary interface of the transit node on the RRPP major
ring.
[SwitchD-rrpp-domain-region1] ring 1 node-mode transit primary-port


[SwitchD-rrpp-domain-region1] ring 1 enable
# Configure the common interface and edge interface of the assistant edge node on the RRPP
subring.
[SwitchD-rrpp-domain-region1] ring 2 node-mode assistant-edge common-port
gigabitethernet 0/0/2 edge-port gigabitethernet 0/0/3

to verify the configuration:
l Run the display rrpp brief command on Switch B. The following information is displayed:
<SwitchB> display rrpp brief

Domain Index : 1
------------------------------------------------------------------------------
You can find that RRPP is enabled on Switch B. The main control VLAN is VLAN 10, and
the sub control VLAN is VLAN 11.Switch B is the master node of the major ring, with
GigabitEthernet0/0/1 as the primary interface and GigabitEthernet0/0/2 as the secondary
interface.
l Run the display rrpp verbose domain command on Switch B. The following information
is displayed:
<SwitchB> display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Ring State : Completed
You can find that the ring is in Complete state, and the secondary interface of the master
node is blocked.
l Run the display rrpp brief command on SwitchC. The following information is displayed:
<SwitchC> display rrpp brief



Domain Index : 1
-------------------------------------------------------------------------
The output information indicates that RRPP is enabled on SwitchC. The main control VLAN
is VLAN 10, and the sub control VLAN is VLAN 11. Switch C is the master node on the
subring, withGigabitEthernet0/0/1 as the primary interface and GigabitEthernet0/0/2 as the
secondary interface.
l Run the display rrpp verbose domain command on Switch C. The following information
is displayed:
<SwitchC> display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 2
Ring Level : 1
Node Mode : Master
Ring State : Completed
You can find that the subring is in Complete state, and the secondary interface of the master
node on the subring is blocked.
l Run the display rrpp brief command on Switch A. The following information is displayed:
<SwitchA> display rrpp brief

Domain Index : 1
-------------------------------------------------------------------------
1 0 T GigabitEthernet0/0/2 GigabitEthernet0/0/1 Yes
2 1 E GigabitEthernet0/0/2 GigabitEthernet0/0/3 Yes
You can find that RRPP is enabled on Switch A. The main control VLAN is VLAN 10, and
the sub control VLAN is VLAN 11. Switch A is the transit node of the major ring, with
GigabitEthernet0/0/2 as the primary interface and GigabitEthernet0/0/1 as the secondary
interface.
Switch A is also an edge of of the subring, with GigabitEthernet0/0/2 as the common interface
and GigabitEthernet0/0/3 as the edge interface.
l Run the display rrpp verbose domain command on Switch A. The following information
is displayed:
<SwitchA> display rrpp verbose domain 1
Domain Index : 1


RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
Secondary port: GigabitEthernet0/0/1 Port status: UP
RRPP Ring : 2
Ring Level : 1
Node Mode : Edge
Ring State : Linkup
Is Enabled : Disable Is Active : No
Common port :GigabitEthernet0/0/2 Port status: UP
Edge port : GigabitEthernet0/0/3 Port status: UP
l Run the display rrpp brief command on Switch D. The following information is displayed:
<SwitchD> display rrpp brief

Domain Index : 1
-------------------------------------------------------------------------
2 1 A GigabitEthernet0/0/2 GigabitEthernet0/0/3 Yes
You can find that RRPP is enabled on Switch D. The main control VLAN is VLAN 10, and
the sub control VLAN is VLAN 11. Switch D is the transit node of the major ring, with
GGigabitEthernet0/0/2 as the primary interface and GigabitEthernet0/0/1 as the secondary
interface. Switch D is also the assistant edge node of the major ring, with
GigabitEthernet0/0/2 as the common interface and GigabitEthernet0/0/3 as the edge
interface.
l Run the display rrpp verbose domain command on Switch D. The following information
is displayed:
<SwitchD> display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
RRPP Ring : 2
Ring Level : 1
Node Mode : Assistant-edge
Ring State : Linkup
Is Enabled : Disable Is Active : No

Common port : GigabitEthernet0/0/2 Port status: UP

----End
Configuration Files
#
sysname SwitchA
#
vlan batch 2 to 11
rrpp enable
#
stp region-
configuration
instance 1 vlan 2 to
11
active region-
configuration
#
rrpp domain 1
control-vlan 10
ring 1 enable
ring 2 node-mode edge common-port GigabitEthernet 0/0/2 edge-port
GigabitEthernet 0/0/3
ring 2 enable
#
port trunk allow-pass vlan 2 to 11
stp disable
#
stp disable
#
stp disable
#
return

#
sysname SwitchB
#
vlan batch 2 to 11
#
rrpp enable
#
stp region-
configuration
11
active region-
configuration
#
rrpp domain 1
control-vlan 10

ring 1 enable
#
stp disable
#
stp disable
#
return
l Configuration file of the Switch C
#
sysname SwitchC
#
vlan batch 2 to 11
#
rrpp enable
#
stp region-
configuration
11
active region-
configuration
#
rrpp domain 1
control-vlan 10
ring 2 enable
#
stp disable
#
stp disable
#
return
l Configuration file of Switch D
#
sysname SwitchD
vlan batch 2 to 11
#
rrpp enable
#
stp region-
configuration
11
active region-
configuration
#
rrpp domain 1
control-vlan 10
ring 1 enable
ring 2 node-mode assistant-edge common-port GigabitEthernet 0/0/2 edge-port

ring 2 enable
#
stp disable
#
stp disable
#
stp disable
#
return
3.6.3 Example for Configuring Tangent RRPP Rings

As shown in Figure 3-7, SwitchA, SwitchB, SwitchC, SwitchD, and SwitchE support the RRPP
function. SwitchA, SwitchB, and SwitchC are on ring 2 of domain 2. SwitchC, SwitchD, and
SwitchE are on ring 1 of domain 1. SwitchC is the tangent point of the two rings.
Figure 3-7 Networking diagram of tangent RRPP rings
Domain 2 Domain 1
SwtichB GE0/0/2 GE0/0/1 SwtichE
GE0/0/1 GE0/0/3 GE0/0/2 GE0/0/2
Ring 2 SwtichC Ring 1

GE0/0/4 GE0/0/1
GE0/0/2 GE0/0/1
SwtichA GE0/0/1 GE0/0/2 SwtichD
1. Create an instance and add the control VLANs added to the list of protected VLANs.
2. Configure ring 2 of domain 2 on SwitchA, SwitchB, and SwitchC.
3. Configure ring 1 of domain 1 on SwitchC, SwitchD, and SwitchE.
4. Configure SwitchA as the master node on ring 2, and configure SwitchB and SwitchC as

5. Configure SwitchE as the master node on ring 1, and configure SwitchC and SwitchD as
Data Preparation
l Control VLAN IDs of ring 1 and ring 2
Procedure
Step 1 Create an instance and add the control VLANs added to the list of protected VLANs.
[SwitchA-mst-region] instance 2 vlan 20 to 21
[SwitchB] stp region-configuration
[SwitchB-mst-region] instance 2 vlan 20 to 21
[SwitchB-mst-region] active region-configuration
[SwitchB-mst-region] quit
[SwitchC] stp region-configuration
[SwitchC-mst-region] active region-configuration
[SwitchC-mst-region] quit
# Configure SwitchD.
[SwitchD] stp region-configuration
[SwitchD-mst-region] instance 1 vlan 10 to 11
[SwitchD-mst-region] active region-configuration
[SwitchD-mst-region] quit
# Configure SwitchE.
[Quidway] sysname SwitchE
[SwitchE] stp region-configuration
[SwitchE-mst-region] instance 1 vlan 10 to 11
[SwitchE-mst-region] active region-configuration
[SwitchE-mst-region] quit
Step 2 Create RRPP domains and configure the control VLANs and protected VLANs of the domains.
# Configure domain 1 on SwitchE, which is the master node of ring 1. Configure VLAN 10 as
the main control VLAN of domain 1, and configure the list of protected VLANs mapping
instance 1.

[SwitchE] rrpp domain 1

[SwitchE-rrpp-domain-region1] control-vlan 10
[SwitchE-rrpp-domain-region1] protected-vlan reference-instance 1
[SwitchE-rrpp-domain-region1] quit
# Configure domain 1 on SwitchC, which is the transit node of ring 1. Configure VLAN 10 as
instance 1.
# Configure domain 1 on SwitchD, which is the transit node of ring 1. Configure VLAN 10 as
the main control VLAN of domain 1, and configure the list of protected VLANs of instance 1.
[SwitchD-rrpp-domain-region1] control-vlan 10
[SwitchD-rrpp-domain-region1] protected-vlan reference-instance 1
# Configure domain 2 on SwitchE, which is the master node of ring 2. Configure VLAN 20 as
instance 1.
# Configure domain 2 on SwitchB, which is the transit node of ring 2. Configure VLAN 20 as
# Configure domain 2 on SwitchC, which is the transit node of ring 2. Configure VLAN 20 as
Step 3 Set the timers of the RRPP domains

NOTE
You can set two timers for the tangent point because the two tangent rings reside in different domains.
# Set the Hold timer and Fail timer for SwitchE, the master node on ring 1.
[SwitchE-rrpp-domain-region1] timer hello-timer 2 fail-timer 7
# Set the Hold timer and Fail timer for SwitchD, the transit node on ring 1 .
[SwitchD-rrpp-domain-region1] timer hello-timer 2 fail-timer 7
# Set the Hold timer and Fail timer for SwitchC, the transit node on ring 1.
[SwitchC-rrpp-domain-region1] timer hello-timer 2 fail-timer 7
# Set the Hold timer and Fail timer for SwitchA, the master node on ring 2.


[SwitchA-rrpp-domain-region2] timer hello-timer 3 fail-timer 10
# Set the Hold timer and Fail timer for SwitchB, the transit node on ring 2.
[SwitchB-rrpp-domain-region2] timer hello-timer 3 fail-timer 10
# Set the Hold timer and Fail timer for SwitchC, the transit node on ring 2.
[SwitchC-rrpp-domain-region2] timer hello-timer 3 fail-timer 10
Step 4 Disable STP on the interfaces to be added to the RRPP rings.

# Disable STP on the interfaces to be added to the RRPP ring on SwitchA.
# Disable STP on the interfaces to be added to the RRPP ring on SwitchB.

# Disable STP on the interfaces to be added to the RRPP ring on SwitchC.

# Disable STP on the interfaces to be added to the RRPP ring on SwitchE.

[SwitchE] interface gigabitethernet 0/0/1
[SwitchE-GigabitEthernet0/0/1] stp disable
[SwitchE-GigabitEthernet0/0/1] quit
[SwitchE] interface gigabitethernet 0/0/2
[SwitchE-GigabitEthernet0/0/2] stp disable
[SwitchE-GigabitEthernet0/0/2] quit
# Disable STP on the interfaces to be added to the RRPP ring on SwitchD.

Step 5 Create RRPP rings.

Configure nodes on ring 2. The configuration procedure is as follows:

# Configure SwitchA as the master node of ring 2 and specify the primary and secondary
interfaces.
[SwitchA-rrpp-domain-region2] ring 2 node-mode master primary-port gigabitethernet
# Configure SwitchB as a transit node of ring 2 (major ring) and specify the primary and
secondary interfaces.
[SwitchB-rrpp-domain-region2] ring 2 node-mode transit primary-port
# Configure SwitchC as a transit node of RRPP ring 2 and specify the primary and secondary
interfaces.
Configure nodes on ring 1. The configuration procedure is as follows:

# Configure SwitchE as the master node of ring 1 (major ring) and specify the primary and
secondary interfaces.
[SwitchE-rrpp-domain-region1] ring 1 node-mode master primary-port gigabitethernet
[SwitchE-rrpp-domain-region1] ring 1 enable
[SwitchE-rrpp-domain-region1] quit
# Configure SwitchC as a transit node of ring 1 and specify the primary and secondary interfaces.
# Configure SwitchD as a transit node of ring 1 and specify the primary and secondary interfaces.
[SwitchD-rrpp-domain-region1] ring 1 node-mode transit primary-port
Step 6 Enable RRPP.

After configuring an RRPP ring, enable RRPP on each node on the ring. Then the RRPP ring
can be activated.
# Enable RRPP on SwitchA.
# Enable RRPP on SwitchB.

# Enable RRPP on SwitchC.

# Enable RRPP on SwitchE.

[SwitchE] rrpp enable
# Enable RRPP on SwitchD.

[SwitchD] rrpp enable
to verify the configuration. Take the tangent point SwitchC for example.
l Run the display rrpp brief command on SwitchC. The following information is displayed:
[SwitchC] display rrpp brief

Domain Index : 1
---------------------------------------------------------------------------
Domain Index : 2
---------------------------------------------------------------------------
You can find that RRPP is enabled on SwitchC. The main control VLAN of domain 1 is
VLAN 10 and the sub control VLAN is VLAN 11. SwitchC is the master node of ring 1,
with GigabitEthernet0/0/1 as the primary interface and GigabitEthernet0/0/2 as the secondary
interface.
The main control VLAN of domain 2 is VLAN 20, and the sub control VLAN is VLAN 21.
SwitchC is a transit node on ring 2, with GigabitEthernet0/0/3 as the primary interface and
GigabitEthernet0/0/4 as the secondary interface.
l Run the display rrpp verbose domain command on SwitchC to view the domain
information.
# View detailed information about domain 1.
[SwitchC] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : Linkup


# View detailed information about domain 2.

[SwitchC] display rrpp verbose domain 2
Domain Index : 2
RRPP Ring : 2
Ring Level : 0
Node Mode : Transit
Ring State : Linkup
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 20 to 21
#
rrpp enable
#
stp region-
configuration
21
#
rrpp domain 2
control-vlan 20
timer hello-timer 3 fail-timer 10
ring 2 enable
#
port hybrid tagged vlan 20 to 21
stp disable
#
stp disable
#

#
sysname SwitchB
#
vlan batch 20 to 21
#
rrpp enable
#
stp region-
configuration
21
#

rrpp domain 2
control-vlan 20
ring 2 enable
#
stp disable
#
stp disable
#
return
#
l Configuration file of the SwitchC
#
sysname SwitchC
#
#
rrpp enable
#
stp region-
configuration
instance 1 vlan 10 to 11
21
#
rrpp domain 1
control-vlan 10
ring 1 enable
#
rrpp domain 2
control-vlan 20
ring 2 node-mode transit primary-port GigabitEthernet 0/0/3 secondary-
portGigabitEthernet 0/0/4 level 0
ring 2 enable
#
interface GigabitEthernet 0/0/1
stp disable
#
pport hybrid tagged vlan 10 to 11
stp disable
#
stp disable
#
stp disable
#
return
l Configuration file of SwitchD
#

sysname SwitchD
#
vlan batch 10 to 11
#
rrpp enable
#
stp region-
configuration
11
#
rrpp domain 1
control-vlan 10
ring 1 enable
#
stp disable
#
stp disable
#
return
l Configuration file of SwitchE

#
sysname SwitchE
#
vlan batch 10 to 11
#
rrpp enable
#
stp region-
configuration
11
#
rrpp domain 1
control-vlan 10
ring 1 enable
#
stp disable
#
stp disable
#
return
3.6.4 Example for Configuring a Single RRPP Ring with Multiple

Instances

As shown in Figure 3-8, UPE A, UPE B, UPE C, and PE-AGG form a multi-instance RRPP
ring.
Two rings are involved in the networking, ring 1 in domain 1 and ring 1 in domain 2.
VLANs 100 to 300 are configured on CE. Domain 1 and domain 2 share the traffic of packets
from VLANs 100 to 300. Packets from VLANs 100 to 200 are transmitted through domain 1,
and packets from VLANs 201 to 300 are transmitted through domain 2.
Table 3-1 shows the mapping between protected VLANs and instances in domain 1 and domain
2.
Table 3-1 Mapping between protected VLANs and instances

Ring Control VLAN Instance ID of Data VLAN ID Instance ID of
ID ID Control VLAN Data VLAN
Domain VLAN 5, VLAN 6 Instance 1 VLAN 100-200 Instance 1

1
Domain VLAN 10, VLAN Instance 2 VLAN 201-300 Instance 2

2 11
Table 3-2 shows the master node of each ring, and the primary port and secondary port on the
master node.
Table 3-2 Master nodes, and primary and secondary ports on the master nodes
Ring ID Master Node Primary Port Secondary Port
Ring 1 in domain 1 PE-AGG GE 0/0/1 GE 0/0/2

Figure 3-8 Networking diagram of single RRPP ring with multiple instances
UPE B
GE0/0/1 GE0/0/2
CE 1
VLAN 100-300
PE-AGG
GE0/0/2 GE0/0/1
Ring 1 Master 1 Backbone
UPEA network
Master 2
GE0/0/1 GE0/0/2
CE 2
VLAN 100-300
Domain 1 ring 1
GE0/0/2 GE0/0/1
Domain 2 ring 1
UPEC
1. Map instance 1 to VLANs 100 to 200. Map instance 2 to VLANs 201 to 300.
2. Add UPE A, UPE B, UPE C, and PE-AGG to ring 1 in domain 1.
3. Add UPE A, UPE B, UPE C, and PE-AGG to ring 1 in domain 2.
4. Configure protected VLANs in domain 1 and domain 2.
5. Configure control VLANs in domain 1 and domain 2.
6. Configure PE-AGG as the master node on ring 1 in domain 1 and configure UPE A, UPE
B, and UPE C as transit nodes.
7. Configure PE-AGG as the master node on ring 1 in domain 2 and configure UPE A, UPE
B, and UPE C as transit nodes.
Data Preparation
l Instance IDs
l Range of the protected VLANs
l IDs of the control VLANs
Procedure
Step 1 Create instances.

l Configure UPE A.
# Create data VLANs 100 to 300 on UPE A.
[Quidway] sysname UPEA
[UPEA] vlan batch 100 to 300
# Create instance 1 and map it to control VLANs VLAN 5 VLAN 6 and data VLANs 100 to
200 in domain 1.
[UPEA] stp region-configuration
[UPEA-mst-region] instance 1 vlan 5 6 100 to 200
# Create instance 2 and map it to control VLANs VLAN 10 and VLAN 11 and data VLANs 201
to 300 in domain 2.
# Activate the configuration.

[UPEA-mst-region] active region-configuration
[UPEA-mst-region] quit
l # Configure UPE B.
# Create data VLANs 100 to 300 on UPE B.
[Quidway] sysname UPEB
[UPEB] vlan batch 100 to 300
to 200 in domain 1.
[UPEB] stp region-configuration
[UPEB-mst-region] instance 1 vlan 5 6 100 to 200
to 300 in domain 2.

[UPEB-mst-region] active region-configuration
[UPEB-mst-region] quit
l Configure UPE C.
# Create data VLANs 100 to 300 on UPE C.
[Quidway] sysname UPEC
[UPEC] vlan batch 100 to 300
to 200 in domain 1.
[UPEC] stp region-configuration
[UPEC-mst-region] instance 1 vlan 5 6 100 to 200
to 300 in domain 2.

[UPEC-mst-region] active region-configuration

[UPEC-mst-region] quit
l Configure PE-AGG.
# Create data VLANs 100 to 300 on PE-AGG.
[Quidway] sysname PE-AGG
[PE-AGG] vlan batch 100 to 300
to 200 in domain 1.
[PE-AGG] stp region-configuration
[PE-AGG-mst-region] instance 1 vlan 5 6 100 to 200
to 300 in domain 2.

[PE-AGG-mst-region] active region-configuration
[PE-AGG-mst-region] quit
l Verify the configuration.

Run the display stp region-configuration command on the devices to view the mapping
between instances and VLANs. The displayed information on UPE A is as follows:
[UPEA] display stp region-configuration
Oper configuration
Format selector :0
Revision level :0

0 1 to 4, 7 to 9, 12 to 99, 301 to 4094
1 5 to 6, 100 to 200
2 10 to 11, 201 to 300
Step 2 Configure RRPP interfaces.

l Configure UPE A.
# Disable STP on the interfaces that need to be added to the RRPP ring on UPE A. Configure
the RRPP interfaces to allow packets of VLANs 100 to 300 to pass through.
[UPEA] interface gigabitethernet 0/0/1
[UPEA-GigabitEthernet0/0/1] port link-type trunk
[UPEA-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[UPEA-GigabitEthernet0/0/1] stp disable
[UPEA-GigabitEthernet0/0/1] quit
# Disable STP on the interfaces that need to be added to the RRPP ring on UPE B. Configure
[UPEB] interface gigabitethernet 0/0/1
[UPEB-GigabitEthernet0/0/1] port link-type trunk
[UPEB-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300

[UPEB-GigabitEthernet0/0/1] stp disable

[UPEB-GigabitEthernet0/0/1] quit
l Configure UPE C.
# Disable STP on the interfaces that need to be added to the RRPP ring on UPE C. Configure
[UPEC] interface gigabitethernet 0/0/1
[UPEC-GigabitEthernet0/0/1] port link-type trunk
[UPEC-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[UPEC-GigabitEthernet0/0/1] stp disable
[UPEC-GigabitEthernet0/0/1] quit
l Configure PE-AGG.
# Disable STP of the interfaces that need to be added to the RRPP ring on PE-AGG. Configure
[PE-AGG] interface gigabitethernet 0/0/1
[PE-AGG-GigabitEthernet0/0/1] port link-type trunk
[PE-AGG-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[PE-AGG-GigabitEthernet0/0/1] stp disable
[PE-AGG-GigabitEthernet0/0/1] quit
Step 3 Create RRPP domains and configure the protected VLANs and control VLANs.
l Configure UPE A.
# Configure the VLANs mapping instance 1 as the protected VLANs in domain 1. Configure
VLAN 5 as the control VLAN.
[UPEA] rrpp domain 1
[UPEA-rrpp-domain-region1] protected-vlan reference-instance 1
[UPEA-rrpp-domain-region1] control-vlan 5
[UPEA-rrpp-domain-region1] quit
[UPEB] rrpp domain 1
[UPEB-rrpp-domain-region1] protected-vlan reference-instance 1
[UPEB-rrpp-domain-region1] control-vlan 5
[UPEB-rrpp-domain-region1] quit

l Configure UPE C.
[UPEC] rrpp domain 1
[UPEC-rrpp-domain-region1] protected-vlan reference-instance 1
[UPEC-rrpp-domain-region1] control-vlan 5
[UPEC-rrpp-domain-region1] quit
l Configure PE-AGG.
[PE-AGG] rrpp domain 1
[PE-AGG-rrpp-domain-region1] protected-vlan reference-instance 1
[PE-AGG-rrpp-domain-region1] control-vlan 5
[PE-AGG-rrpp-domain-region1] quit

l Configure UPE A.
# Configure UPE A as a transit node of ring 1 in domain 1 and specify primary and secondary
ports on UPE A.
[UPEA-rrpp-domain-region1] ring 1 node-mode transit primary-port gigabitethernet
[UPEA-rrpp-domain-region1] ring 1 enable
ports on UPE A.

# Configure UPE B as a transit node of ring 1 in domain 1 and specify primary and secondary
ports on UPE B.
[UPEB-rrpp-domain-region1] ring 1 node-mode transit primary-port gigabitethernet
[UPEB-rrpp-domain-region1] ring 1 enable
ports on UPE B.
l Configure UPE C.
# Configure UPE C as a transit node of ring 1 in domain 1 and specify primary and secondary
ports on UPE C.
[UPEC-rrpp-domain-region1] ring 1 node-mode transit primary-port gigabitethernet
[UPEC-rrpp-domain-region1] ring 1 enable
ports on UPE C.
l Configure PE-AGG.
# Configure PE-AGG as the master node of ring 1 in domain 1. Configure GE 0/0/1 as the
primary port and GE 0/0/2 as the secondary port.
[PE-AGG-rrpp-domain-region1] ring 1 node-mode master primary-port gigabitethernet
[PE-AGG-rrpp-domain-region1] ring 1 enable
Step 5 Enable the RRPP protocol.

After configuring an RRPP ring, you need to enable RRPP on each node on the ring to activate
the RRPP ring. The configuration procedure is as follows:
l Configure UPE A.
# Enable the RRPP protocol.
[UPEA] rrpp enable

[UPEB] rrpp enable
l Configure UPE C.
[UPEC] rrpp enable
l Configure PE-AGG.
[PE-AGG] rrpp enable

After the preceding configurations are complete and the network topology becomes stable,
perform the following operations to verify the configuration. Here, UPE A and PE-AGG are
used as examples.
l Run the display rrpp brief command on UPE A. The following information is displayed:
[UPEA] display rrpp brief

Domain Index : 1
----------------------------------------------------------------------------
Domain Index : 2
----------------------------------------------------------------------------
You can see that the RRPP protocol is enabled on UPE A.

In domain 1, VLAN 5 is the control VLAN; VLANs mapping instance 1 are the protected
VLANs; UPE A is a transit node on ring 1. The primary port is GE 0/0/1, and the secondary port
is GE 0/0/2.
VLANs; UPE A is a transit node on ring 1. The primary port is GE 0/0/1, and the secondary port
is GE 0/0/2.
l Run the display rrpp brief command on PE-AGG. The following information is displayed:
[PE-AGG] display rrpp brief


Domain Index : 1
Enabled
---------------------------------------------------------------------------
Domain Index : 2
Protected VLAN: Reference Instance 2
Enabled
---------------------------------------------------------------------------
The preceding information shows that the RRPP protocol is enabled on PE-AGG.
VLANs; PE-AGG is the master node on ring 1. The primary port is GigabitEthernet 0/0/1, and
the secondary port is GigabitEthernet 0/0/2.
VLANs; PE-AGG is the master node on ring 1. The primary port is GigabitEthernet 0/0/2, and
the secondary port is GigabitEthernet0/0/1.
l Run the display rrpp verbose domain command on UPE A. You can obtain the following
results:
# View detailed information about UPE A in domain 1.
[UPEA] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : LinkUp
The preceding information shows that VLAN 5 is the control VLAN in domain 1 and VLANs
mapping instance 1 are the protected VLANs. UPE A is a transit node in domain 1 and is in
LinkUp state.
# View detailed information about UPE A in domain 2.
[UPEA] display rrpp verbose domain 2
Domain Index : 2

RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : LinkUp
The preceding information shows that VLAN 10 is the control VLAN in domain 2, and VLANs
mapping instance 2 are the protected VLANs. UPE A is a transit node in domain 2 and is in
LinkUp state.
l Run the display rrpp verbose domain command on PE-AGG. You can obtain the following
results:
# View detailed information about PE-AGG in domain 1.
[PE-AGG] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
mapping instance 1 are the protected VLANs.
PE-AGG is the master node in domain 1 and is in Complete state.
The primary port is GigabitEthernet 0/0/1, and the secondary port is GigabitEthernet 0/0/2.
Domain Index : 2
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
The primary port is GigabitEthernet 0/0/2, and the secondary port is GigabitEthernet 0/0/1.
----End
Configuration Files
l Configuration file of UPE A

#
sysname UPEA
#
vlan batch 5 to 6 10 to 11 100 to 300
#
rrpp enable
#
instance 1 vlan 5 to 6 100 to 200
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#
port trunk allow-pass vlan 5 to 6 10 to 11 100 to 300
stp disable
#
stp disable
#
return
l Configuration file of UPE B
#
sysname UPEB
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#
stp disable
#


stp disable
#
return
l Configuration file of UPE C
#
sysname UPEC
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#
stp disable
#
stp disable
#
return
l Configuration file of PE-AGG
#
sysname PE-AGG
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#


stp disable
#
stp disable
#
return
3.6.5 Example for Configuring Crossed RRPP Rings with Multiple

Instances(HW version)
As shown in Figure 3-9, UPE A, UPE B, UPE C, UPE D, and PE-AGG form two multi-instance
major rings: ring 1 in domain 1 and ring 1 in domain 2.
CE1, UPE B, and UPE C form two subrings: ring 2 in domain 1 and ring 2 in domain 2. CE1 is
connected to the major rings through GE 0/0/3 of UPE B and GE 0/0/3 of UPE C. UPE B is an
edge node, and UPE is an assistant edge node.
CE2, UPE B, and UPE C form two subrings: ring 3 in domain 1 and ring 3 in domain 2. CE2 is
connected to the major rings through GE 0/0/4 of UPE B and GE 0/0/4 of UPE C. UPE B is an
edge node, and UPE is an assistant edge node.
Table 3-3 shows the mapping between protected VLANs and instances in domain 1 and domain
2.

Domain ID Control Instance ID Data VLAN ID Instance ID of
VLAN ID of Control Data VLAN
VLAN
Domain 1 VLAN 5, Instance 1 VLAN 100-200 Instance 1

VLAN 6
Domain 2 VLAN 10, Instance 2 VLAN 201-300 Instance 2

VLAN 11
Table 3-4 shows the master node of each ring, and the primary port and secondary port on each
master node.

Ring ID Master Primary Secondary Port Ring Type
Node Port
Ring 1 in PE-AGG GE 0/0/1 GE 0/0/2 Major ring

domain 1
Ring 1 in PE-AGG GE 0/0/2 GE 0/0/1 Major ring

domain 2
Ring 2 in CE1 GE 0/0/1 GE 0/0/2 Sub ring

domain 1

domain 2

domain 1

domain 2
Table 3-5 shows the edge nodes, assistant edge nodes, public port, and edge port of the subrings.
Table 3-5 Edge nodes, assistant edge nodes, public port, and edge port of the subrings
Ring Edge Comm Edge Port Edge- Common Edge Port
ID Node on Port Assistant Port
Node
Ring 2 UPE B GE GE 0/0/3 UPE C GE 0/0/2 GE 0/0/3

in 0/0/1
domain
1

in 0/0/1
domain
1

in 0/0/1
domain
2

in 0/0/1
domain
2
To reduce the Edge-Hello packets sent on the major ring and increase available bandwidth, you
can add the four subrings to a ring group.

To prevent topology flapping, you need to set the Link-Up timer on the master nodes.
Figure 3-9 Networking diagram of crossed RRPP rings with multiple instances
Backbone
network
GE0/0/1 GE0/0/2
PE-AGG
Master 1
GE0/0/2 Master 2 GE/1/0/0
UPE A UPED
Domain 1 ring 1
GE0/0/1
GE2/0/00
Domain 2 ring 1
GE0/0/2 Edge Assistant GE0/0/1

UPE B GE0/0/1 GE0/0/2 UPEC
GE0/0/3 GE0/0/3
GE0/0/4 GE0/0/4
Domain 2 ring 2 Domain 2 ring 3

GE0/0/1 GE0/0/2
Master 1 Master 1
Master 2 Master 2
GE0/0/2 Domain 1 ring 2 Domain 1 ring 3 GE0/0/1
CE 1 CE 2
VLAN 100-300 VLAN 100-300
Domain 1
Domain 2
2. Add UPE A, UPE B, UPE C, UPE D, and PE-AGG to ring 1 in domain 1 and ring 1 in
domain 2.
3. Add CE1, UPE B, and UPE C to ring 2 in domain 1 and ring 2 in domain 2.
4. Add CE2, UPE B, and UPE C to ring 3 in domain 1 and ring 3 in domain 2.


7. Configure PE-AGG as the master node and configure UPE A, UPE B, and UPE C as transit
nodes on ring 1 in domain 1 and ring 1 in domain 2.
8. Configure CE1 as the master node and configure UPE B and UPE C as transit nodes on
ring 2 in domain 1 and ring 2 in domain 2.
9. Configure CE2 as the master node and configure UPE B and UPE C as transit nodes on
ring 3 in domain 1 and ring 3 in domain 2.
10. Configure a ring group.
11. Set the link-Up timer.
Data Preparation
l Instance IDs
l ID of the ring group
l Link-Up-Delay timer
Procedure
l Configure CE1.
# Create data VLANs 100 to 300 on CE1.
[Quidway] sysname CE1
[CE1] vlan batch 100 to 300
# Create instance 1 and map it to control VLANs VLAN 5 and VLAN 6 and data VLANs
100 to 200 in domain 1.
[CE1] stp region-configuration
[CE1-mst-region] instance 1 vlan 5 6 100 to 200

[CE1-mst-region] active region-configuration
[CE1-mst-region] quit
l Configure CE2.
# Create data VLANs 100 to 300 on CE2.
[Quidway] sysname CE2
[CE2] vlan batch 100 to 300
[CE2] stp region-configuration


[CE2-mst-region] active region-configuration
[CE2-mst-region] quit
l Configure UPE A.


l Configure UPE C.


l Configure UPE D.
# Create data VLANs 100 to 300 on UPE D.
[Quidway] sysname UPED
[UPED] vlan batch 100 to 300
[UPED] stp region-configuration
[UPED-mst-region] instance 1 vlan 5 6 100 to 200

[UPED-mst-region] active region-configuration
[UPED-mst-region] quit
l Configure PE-AGG.
[Quidway] sysname PE-AGG

[PE-AGG-mst-region] quit

View the mapping between instances and VLANs. The displayed information on UPE A is
as follows:
Oper configuration
Format selector :0
Revision level :0

0 1 to 4, 7 to 9, 12 to 99, 301 to 4094
1 5 to 6, 100 to 200
2 10 to 11, 201 to 300

l Configure CE1.
# Disable STP on the interfaces that need to be added to the RRPP ring on CE1. Configure
[CE1] interface gigabitethernet 0/0/1
[CE1-GigabitEthernet0/0/1] port link-type trunk
[CE1-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[CE1-GigabitEthernet0/0/1] stp disable

[CE1-GigabitEthernet0/0/1] quit
l Configure CE2.
# Disable STP on the interfaces that need to be added to the RRPP ring on CE2. Configure
l Configure UPE A.
l Configure UPE C.


l Configure UPE D.
# Disable STP on the interfaces that need to be added to the RRPP ring on UPE D. Configure
[UPED] interface gigabitethernet 0/0/1
[UPED-GigabitEthernet0/0/1] port link-type trunk
[UPED-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[UPED-GigabitEthernet0/0/1] stp disable
[UPED-GigabitEthernet0/0/1] quit
l Configure PE-AGG.
# Disable STP of the interfaces that need to be added to the RRPP ring on PE-AGG. Configure
l Configure CE1.
[CE1] rrpp domain 1
[CE1-rrpp-domain-region1] protected-vlan reference-instance 1
[CE1-rrpp-domain-region1] control-vlan 5
[CE1-rrpp-domain-region1] quit
[CE1] rrpp domain 2
l Configure CE2.

[CE2] rrpp domain 1

[CE2] rrpp domain 2
l Configure UPE A.
l Configure UPE C.
l Configure UPE D.
[UPED] rrpp domain 1
[UPED-rrpp-domain-region1] protected-vlan reference-instance 1
[UPED-rrpp-domain-region1] control-vlan 5
[UPED-rrpp-domain-region1] quit

l Configure PE-AGG.
Step 4 Create an RRPP ring.

l Configure PE-AGG.
[PE-AGG-rrpp-domain-region1] ring 1 node-mode master primary-port
# Configure PE-AGG as the master node of ring 1 in domain 2. Configure GE0/0/2 as the
primary port and GE0/0/1 as the secondary port.
[PE-AGG-rrpp-domain-region2] ring 1 node-mode master primary-port
l Configure UPE A.
ports on UPE A.
[UPEA-rrpp-domain-region1] ring 1 node-mode transit primary-port
ports on UPE A.
[UPEA-rrpp-domain-region2] ring 1 node-mode transit primary-port
l Configure UPE D.
# Configure UPE D as a transit node of ring 1 in domain 1 and specify primary and secondary
ports on UPE D.
[UPED-rrpp-domain-region1] ring 1 node-mode transit primary-port


[UPED-rrpp-domain-region1] ring 1 enable
ports on UPE D.
[UPED-rrpp-domain-region2] ring 1 node-mode transit primary-port
ports on UPE B.
[UPEB-rrpp-domain-region1] ring 1 node-mode transit primary-port
gigabitethernet 0/0/1 secondary-port ggigabitethernet 0/0/2 level 0
ports on UPE B.
[[UPEB] rrpp domain 2
[UPEB-rrpp-domain-region2] ring 1 node-mode transit primary-port
# Configure UPE B as an edge node of ring 2 in domain 1. Configure GE 0/0/1 as the public
port and GE 0/0/3 as the edge port.
[UPEB-rrpp-domain-region1] ring 2 node-mode edge common-port gigabitethernet
l Configure UPE C.
ports on UPE C.
[UPEC-rrpp-domain-region1] ring 1 node-mode transit primary-port


ports on UPE C.
[UPEC-rrpp-domain-region2] ring 1 node-mode transit primary-port
[UPEC-rrpp-domain-region1] ring 2 node-mode assistant-edge common-port
# Configure UPE C as an edge node of ring 3 in domain 1. Configure GE 0/0/1 as the public
# Configure UPE C as an edge node of ring 3 in domain 2. Configure GE 0/0/2 as the public
l Configure CE1.
# Configure CE1 as the master node of ring 2 in domain 1. Configure GE 0/0/1 as the primary
port and GE 0/0/2 as the secondary port.
[CE1] rrpp domain 1
[CE1-rrpp-domain-region1] ring 2 node-mode master primary-port gigabitethernet
[CE1-rrpp-domain-region1] ring 2 enable
[CE1] rrpp domain 2
l Configure CE2.
[CE2] rrpp domain 1


[CE2] rrpp domain 2

l Configure PE-AGG.
l Configure UPE A.
[UPEA] rrpp enable
l Configure UPE D.
[UPED] rrpp enable
[UPEB] rrpp enable
l Configure UPE C.
[UPEC] rrpp enable
l Configure CE1.
[CE1] rrpp enable
l Configure CE2.
[CE2] rrpp enable
Step 6 Configure a ring group.

l Configure UPE C (assistant edge node).
# Create ring group 1, which consists of four subrings: ring 2 in domain 1, ring 3 in domain
1, ring 2 in domain 2, and ring 3 in domain 2.
[UPEC] rrpp ring-group 1
[UPEC-rrpp-ring-group1] domain 1 ring 2 to 3
[UPEC-rrpp-ring-group1] domain 2 ring 2 to 3
[UPEC-rrpp-ring-group1] quit
l Configure UPE B (edge node).

# Create ring group 1, which consists of four subrings: ring 2 in domain 1, ring 3 in domain
1, ring 2 in domain 2, and ring 3 in domain 2.
[UPEB] rrpp ring-group 1
[UPEB-rrpp-ring-group1] domain 1 ring 2 to 3

[UPEB-rrpp-ring-group1] domain 2 ring 2 to 3

[UPEB-rrpp-ring-group1] quit
Step 7 Set the link-Up timer.

l Configure CE1.
# Set the link-Up timer to 1 second.
[CE1] rrpp linkup-delay-timer 1
l Configure CE2.
[CE2] rrpp linkup-delay-timer 1
l Configure PE-AGG.
[PE-AGG] rrpp linkup-delay-timer 1
perform the following operations to verify the configuration. Here, UPE B and PE-AGG are
used as examples.
l Run the display rrpp brief command on UPE B. The following information is displayed.
[UPEB] display rrpp brief

RRPP Linkup Delay Timer: 0 sec(default is 0 sec)
Domain Index : 1
Enabled
-------------------------------------------------------------------------------
--
Domain Index : 2
Enabled
-------------------------------------------------------------------------------
--
You can see that the RRPP protocol is enabled on UPE B.

In domain 1:
VLAN 5 is the control VLAN and VLANs mapping instance 1 are the protected VLANs.

UPE B is a transit node on ring 1; GE 0/0/1 is the primary port; GE 0/0/2 is the secondary
port.
UPE B is an edge transit node on ring 2. GE 0/0/1 is the public port and GE 0/0/3 is the edge
port.
port.
In domain 2:
UPE B is a transit node on ring 1. GE 0/0/1 is the primary port, and GE 0/0/2 is the secondary
port.
port.
port.
l Run the display rrpp brief command on PE-AGG. The following information is displayed:
[PE-AGG] display rrpp brief

RRPP Linkup Delay Timer: 1 sec(default is 0 sec)
Domain Index : 1
Enabled
-------------------------------------------------------------------------------
--
Domain Index : 2
Enabled
-------------------------------------------------------------------------------
--
The preceding information shows that the RRPP protocol is enabled on PE-AGG, and the
link-Up timer is 2 seconds.
VLANs; PE-AGG is the master node on ring 1. GE 0/0/1 is the primary port, and GE 0/0/2
is the secondary port.
VLANs; PE-AGG is the master node on ring 1. GE 0/0/2 is the primary port, and GE 0/0/1
is the secondary port.
l Run the display rrpp verbose domain command on UPE B. You can obtain the following
results:

# View detailed information about UPE B in domain 1.

[UPEB] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : LinkUp
RRPP Ring : 2
Ring Level : 1
Node Mode : Edge
Ring State : LinkUp
RRPP Ring : 3
Ring Level : 1
Node Mode : Edge
Ring State : LinkUp
UPE B is a transit node on ring 1 in domain 1 and is in LinkUp state.
UPE B is a transit node on ring 2 in domain 1 and is in LinkUp state. GE 0/0/1 is the public
port, and GE 0/0/3 is the edge port.
# View detailed information about UPE B in domain 2.
<UPEB> display rrpp verbose domain 2
Domain Index : 2
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : LinkUp
RRPP Ring : 2
Ring Level : 1
Node Mode : Edge
Ring State : LinkUp
RRPP Ring : 3
Ring Level : 1
Node Mode : Edge
Ring State : LinkUp


The preceding information shows that VLAN 10 is the control VLAN in domain 2, and
VLANs mapping instance 2 are the protected VLANs.
UPE B is a transit node in domain 2 and is in LinkUp state.
l Run the display rrpp verbose domain command on PE-AGG. You can obtain the following
results:
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
GE 0/0/1 is the primary port, and GE 0/0/2 is the secondary port.
Domain Index : 2
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
The preceding information shows that VLAN 10 is the control VLAN in domain 2, and
VLANs mapping instance 2 are the protected VLANs.
GE 0/0/2 is the primary port, and GE 0/0/1 is the secondary port.
l Run the display rrpp ring-group command on UPE B to view the configuration of the ring
group.
# View the configuration of ring group 1.
[UPEB] display rrpp ring-group 1
Ring Group 1:

domain 1 ring 2 to 3
----End
Configuration Files
l Configuration file of CE1
#
sysname CE1
#
#
rrpp enable
rrpp linkup-delay-timer 1
#
#
rrpp domain 1
control-vlan 5
ring 2 enable
rrpp domain 2
control-vlan 10
ring 2 enable
#
port trunk allow-pass vlan 6 11 100 to 300
stp disable
#
stp disable
#
return

#
#
sysname CE2
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 3 enable
rrpp domain 2

control-vlan 10
ring 3 enable
#
stp disable
#
stp disable
#
return
#
#
sysname UPEA
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#
stp disable
#
stp disable
#
return
#
sysname UPEB
#
#
rrpp enable
#
#

rrpp domain 1
control-vlan 5
ring 1 enable
ring 2 enable
ring 3 enable
rrpp domain 2
control-vlan 10
ring 1 enable
ring 2 enable
ring 3 enable
#
rrpp ring group 1
#
stp disable
#
stp disable
#
stp disable
#
stp disable
#
return
#
sysname UPEC
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable


ring 2 enable
ring 3 enable
rrpp domain 2
control-vlan 10
ring 1 enable
ring 2 enable
ring 3 enable
#
rrpp ring group 1
#
stp disable
#
stp disable
#
stp disable
#
stp disable
#
return
l Configuration file of UPE D
#
sysname UPED
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable

#
stp disable
#
stp disable
#
return

#
sysname PE-AGG
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#
stp disable
#
stp disable
#
return
3.6.6 Example for Configuring Tangent RRPP Rings with Multiple

Instances
As shown in Figure 3-10, UPE A, UPE B, UPE C, and UPE D form two multi-instance rings:
ring 1 in domain 1 and ring 1 in domain 2. UPE D, UPE E, UPE F, and UPE G form ring 1 in
domain 3. Packets of the data VLANs connected to CE are forwarded to the backbone network
through the two tangent rings.
The tangent point of the two rings is UPE D.

Table 3-6 shows the mapping between protected VLANs and instances in domain 1, domain 2,
and domain 3.

Domain ID Control VLAN Instance ID Protected VLAN Instance ID
Domain 1 VLAN 5, 6 Instance 1 VLAN 100-200 Instance 1
Domain 3 (on VLAN 20, 21 Instance 3 VLAN 100-300 Instance 1 and

UPE D) instance 2
Table 3-7 shows the master node of each ring, and the primary port and secondary port on each
master node.
Ring ID Master Node Primary Port Secondary Port
Ring 1 in domain 1 UPE D GE 0/0/1 GE 0/0/2
Ring 1 in domain 2 UPE D GE 0/0/2 GE 0/0/1
Ring 1 in domain 3 UPE F GE 0/0/1 GE 0/0/2

Figure 3-10 Networking diagram of tangent RRPP rings with multiple instances
UPEB UPEE
GE0/0/1 GE/0/0/2 GE0/0/1 GE0/0/2
Domain 1 ring 1
GE/0/0/2
GE0/0/1 GE0/0/3 GE0/0/1
Master 1 UPEF
UPEA UPED Master 3
Master 2
CE GE0/0/1 GE0/0/2 GE0/0/4
GE0/0/2
VLAN 100-300 Domain 2 ring 1 Domain 3 ring 1
GE0/0/1
GE/0/0/2 GE0/0/1 GE/0/0/2
UPEC UPEG
domain 1
domain 2
domain 3
2. Add UPE A, UPE B, UPE C, and UPE D to ring 1 in domain 1 and ring 1 in domain 2.
3. Add UPE D, UPE E, UPE F, and UPE G to ring 1 in domain 3.
6. Configure the control VLAN in domain 3.
7. Configure UPE D as the master node and configure UPE A, UPE B, and UPE C as transit
nodes on ring 1 in domain 1 and ring 1 in domain 2.
8. Configure UPE F as the master node and configure UPE D, UPE E, and UPE G as transit
nodes on ring 1 in domain 3.
Data Preparation
l Instance IDs

Procedure
l Configure UPE A.
to 200 in domain 1.
to 300 in domain 2.

to 200 in domain 1.
to 300 in domain 2.

l Configure UPE C.
to 200 in domain 1.
to 300 in domain 2.


l Configure UPE D.
# Create data VLANs 100 to 300 on UPE D.
[Quidway] sysname UPED
[UPED] vlan batch 100 to 300
to 200 in domain 1.
[UPED] stp region-configuration
to 300 in domain 2.
# Create instance 3 and map it to control VLANs VLAN 20 and VLAN 21 in domain 3.
[UPED-mst-region] instance 3 vlan 20 21

[UPED-mst-region] active region-configuration
[UPED-mst-region] quit
l Configure UPE E.
# Create data VLANs 100 to 300 on UPE E.
[Quidway] sysname UPEE
[UPEE] vlan batch 100 to 300
to 300 in domain 3.
[UPEE] stp region-configuration
[UPEE-mst-region] instance 1 vlan 20 21 100 to 300

[UPEE-mst-region] active region-configuration
[UPEE-mst-region] quit
l Configure UPE F.
# Create data VLANs 100 to 300 on UPE F.
[Quidway] sysname UPEF
[UPEF] vlan batch 100 to 300
to 300 in domain 3.
[UPEF] stp region-configuration
[UPEF-mst-region] instance 1 vlan 20 21 100 to 300

[UPEF-mst-region] active region-configuration

[UPEF-mst-region] quit
l Configure UPE G.
# Create data VLANs 100 to 300 on UPE G.

[Quidway] sysname UPEG
[UPEG] vlan batch 100 to 300
to 300 in domain 3.
[UPEG] stp region-configuration
[UPEG-mst-region] instance 1 vlan 20 21 100 to 300

[UPEG-mst-region] active region-configuration
[UPEG-mst-region] quit
Run the display stp region-configuration command on the devices to view the mapping
between instances and VLANs. The displayed information on UPE A is as follows:
Oper configuration
Format selector :0
Revision level :0

0 1 to 4, 7 to 9, 12 to 99, 301 to 4094
1 5 to 6, 100 to 200
2 10 to 11, 201 to 300

l Configure UPE A.


l Configure UPE C.
l Configure UPE D.
# Disable STP on the interfaces that need to be added to the RRPP ring on UPE D. Configure
l Configure UPE E.
# Disable STP on the interfaces that need to be added to the RRPP ring on UPE E. Configure
[UPEE] interface gigabitethernet 0/0/1
[UPEE-GigabitEthernet0/0/1] port link-type trunk
[UPEE-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[UPEE-GigabitEthernet0/0/1] stp disable
[UPEE-GigabitEthernet0/0/1] quit
[UPEE] interface gigabitethernet 0/0/2
[UPEE-GigabitEthernet0/0/2] port link-type trunk
[UPEE-GigabitEthernet0/0/2] port trunk allow-pass vlan 100 to 300
[UPEE-GigabitEthernet0/0/2] stp disable
[UPEE-GigabitEthernet0/0/2] quit
l Configure UPE F.
# Disable STP on the interfaces that need to be added to the RRPP ring on UPE F. Configure
[UPEF] interface gigabitethernet 0/0/1
[UPEF-GigabitEthernet0/0/1] port link-type trunk
[UPEF-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[UPEF-GigabitEthernet0/0/1] stp disable

[UPEF-GigabitEthernet0/0/1] quit
[UPEF] interface gigabitethernet 0/0/2
[UPEF-GigabitEthernet0/0/2] port link-type trunk
[UPEF-GigabitEthernet0/0/2] port trunk allow-pass vlan 100 to 300
[UPEF-GigabitEthernet0/0/2] stp disable
[UPEF-GigabitEthernet0/0/2] quit
l Configure UPE G.
# Disable the STP function on the interfaces to be added to the RRPP ring on UPE G. Configure
[UPEG] interface gigabitethernet 0/0/1
[UPEG-GigabitEthernet0/0/1] port link-type trunk
[UPEG-GigabitEthernet0/0/1] port trunk allow-pass vlan 100 to 300
[UPEG-GigabitEthernet0/0/1] stp disable
[UPEG-GigabitEthernet0/0/1] quit
[UPEG] interface gigabitethernet 0/0/2
[UPEG-GigabitEthernet0/0/2] port link-type trunk
[UPEG-GigabitEthernet0/0/2] port trunk allow-pass vlan 100 to 300
[UPEG-GigabitEthernet0/0/2] stp disable
[UPEG-GigabitEthernet0/0/2] quit
l Configure UPE A.
l Configure UPE C.

l Configure UPE D.
# Configure the VLANs mapping instances 1 to 3 as the protected VLANs in domain 3.

Configure VLAN 20 as the control VLAN.
[UPED-rrpp-domain-region3] protected-vlan reference-instance 1 2 3
l Configure UPE E.
# Configure VLAN 20 as the control VLAN in domain 3.
[UPEE] rrpp domain 3
[UPEE-rrpp-domain-region3] protected-vlan reference-instance 1
[UPEE-rrpp-domain-region3] control-vlan 20
[UPEE-rrpp-domain-region3] quit
l Configure UPE F.
[UPEF] rrpp domain 3
[UPEF-rrpp-domain-region3] protected-vlan reference-instance 1
[UPEF-rrpp-domain-region3] control-vlan 20
[UPEF-rrpp-domain-region3] quit
l Configure UPE G.
[UPEG] rrpp domain 3
[UPEG-rrpp-domain-region3] protected-vlan reference-instance 1
[UPEG-rrpp-domain-region3] control-vlan 20
[UPEG-rrpp-domain-region3] quit

l Configure UPE A.
ports on UPE A.


ports on UPE A.
ports on UPE B.
0/0/1 secondary-port 0/0/2 level 0
ports on UPE B.
[UPEB-rrpp-domain-region2] ring 1 node-mode transit primary-port 0/0/1 secondary-
port 0/0/2 level 0
l Configure UPE C.
ports on UPE C.
[UPEC-rrpp-domain-region1] ring 1 node-mode transit primary-port 0/0/1 secondary-
port 0/0/2 level 0
ports on UPE C.
[UPEC-rrpp-domain-region2] ring 1 node-mode transit primary-port 0/0/1 secondary-
port 0/0/2 level 0
l Configure UPE D.
# Configure UPE D as the master node of ring 1 in domain 1. Configure GE 0/0/1 as the primary
[UPED-rrpp-domain-region1] ring 1 node-mode master primary-port 0/0/1 secondary-
port 0/0/2 level 0
# Configure UPE D as the master node of ring 1 in domain 2. Configure GE 0/0/2 as the primary
[UPED-rrpp-domain-region2] ring 1 node-mode master primary-port 0/0/2 secondary-

port 0/0/1 level 0

ports on UPE D.
[UPED-rrpp-domain-region3] ring 1 node-mode transit primary-port 0/0/2 secondary-
port 0/0/4 level 0
l Configure UPE E.
# Configure UPE E as a transit node of ring 1 in domain 3 and specify primary and secondary
ports on UPE E.
[UPEE] rrpp domain 3
[UPEE-rrpp-domain-region3] ring 1 node-mode transit primary-port 0/0/1 secondary-
port 0/0/2 level 0
[UPEE-rrpp-domain-region3] ring 1 enable
[UPEE-rrpp-domain-region3] quit
l Configure UPE F.
# Configure UPE F as the master node of ring 1 in domain 3. Configure GE 0/0/1 as the primary
[UPEF] rrpp domain 3

[UPEF-rrpp-domain-region3] ring 1 node-mode master primary-port 0/0/1 secondary-
port 0/0/2 level 0
[UPEF-rrpp-domain-region3] ring 1 enable
[UPEF-rrpp-domain-region3] quit
l Configure UPE G.
# Configure UPE G as a transit node of ring 1 in domain 3 and specify primary and secondary
ports on UPE G.
[UPEG] rrpp domain 3
[UPEG-rrpp-domain-region3] ring 1 node-mode transit primary-port 0/0/1 secondary-
port 0/0/2 level 0
[UPEG-rrpp-domain-region3] ring 1 enable
[UPEG-rrpp-domain-region3] quit

l Configure UPE A.
[UPEA] rrpp enable
<UPEB> system-view
[UPEB] rrpp enable
l Configure UPE C.
[UPEC] rrpp enable

l Configure UPE D.
[UPED] rrpp enable
l Configure UPE E.
[UPEE] rrpp enable
l Configure UPE F.
[UPEF] rrpp enable
l Configure UPE G.
[UPEG] rrpp enable

perform the following operations to verify the configuration. Here, UPE D is taken for example.
l Run the display rrpp brief command on UPE D. The following information is displayed:
[UPED] display rrpp brief

Domain Index : 1
----------------------------------------------------------------------------
Domain Index : 2
----------------------------------------------------------------------------
Domain Index : 3
Protected VLAN : Reference Instance 1 to 3
----------------------------------------------------------------------------
The preceding information shows that the RRPP protocol is enabled on UPE D.
In domain 1:

UPE D is the master on ring 1; GE 0/0/1 is the primary port; GE 0/0/2 is the secondary port.
In domain 2:
UPE D is the master node on ring 1. The primary port is GE 0/0/21, and the secondary port is
GE 0/0/1.
In domain 3:
VLAN 20 is the control VLAN and VLANs mapping instance 1 to 3 are the protected VLANs.
UPE D is a transit node on ring 1. The primary port is GE 0/0/3, and the secondary port is GE
0/0/4.
l Run the display rrpp verbose domain command on UPE D. You can obtain the following
results:
# View detailed information about UPE D in domain 1.
[UPED] display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Is Enabled : Enable Is Active: Yes
UPE D is the master node in domain 1 and is in Complete state.
The primary port is GE 0/0/1, and the secondary port is GE 0/0/2.
Domain Index : 2
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
UPE D is the master node in domain 2 and is in Complete state.


Domain Index : 3
Protected VLAN : Reference Instance 1 to 3
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : LinkUp
Secondary port : GigabitEthernet0/0/4 Port status: UP
mapping instance 1 to 3 are the protected VLANs.
UPE D is a transit node in domain 3 and is in LinkUp state.
----End
Configuration Files
#
sysname UPEA
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#
stp disable
#
stp disable
#
return


#
sysname UPEB
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#
stp disable
#
stp disable
#
return

#
sysname UPEC
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 1
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
#
stp disable
#

stp disable
#
Return
l Configuration file of UPE D
#
sysname UPED
#
vlan batch 5 to 6 10 to 11 20 to 21 100 to 300
#
rrpp enable
#
instance 3 vlan 20 to 21
#
rrpp domain 1
control-vlan 5
ring 1 enable
rrpp domain 2
control-vlan 10
ring 1 enable
rrpp domain 3
control-vlan 20
protected-vlan reference-instance 1 2 3
ring 1 enable
#
stp disable
#
stp disable
#
stp disable
#
stp disable
#
return
l Configuration file of UPE E
#
sysname UPEE
#
#
rrpp enable
#

#
rrpp domain 3
control-vlan 20
ring 1 enable
#
stp disable
#
stp disable
#
return
l Configuration file of UPE F
#
sysname UPEF
#
#
rrpp enable
#
#
rrpp domain 3
control-vlan 20
ring 1 enable
#
stp disable
#
stp disable
#
return
l Configuration file of UPE G
#
sysname UPEG
#
#
rrpp enable
#
#
rrpp domain 3
control-vlan 20

#
stp disable
#
stp disable
#
return

Configuration Guide - Reliability 4 Ethernet OAM Configuration
4 Ethernet OAM Configuration
About This Chapter
This chapter describes the principle, configuration procedure, and configuration example of
Ethernet operations administration and maintenance (OAM).
4.1 Introduction to Ethernet OAM

This section describes the concept of Ethernet OAM.
4.2 Ethernet OAM Supported by the S5300
This section describes the Ethernet OAM features supported by the S5300.
4.3 Configuring Basic Functions of EFM OAM
This section describes how to configure basic functions of EFM OAM
4.4 Configuring EFM OAM Link Monitoring
This section describes how to configure the EFM OAM link monitoring function.
4.5 Testing the Packet Loss Ratio on a Physical Link
This section describes how to configure remote loopback of EFM OAM to test the packet loss
ratio on a link by sending test packets.
4.6 Configuring Basic Functions of Ethernet CFM
This section describes how to configure basic functions of Ethernet CFM.
4.7 Adjusting Parameters of Ethernet CFM
By adjusting parameters of Ethernet CFM, you can better implement end-to-end Ethernet CFM
on a device.
4.8 Configuring Fault Acknowledgement on the Ethernet
This section describes how to check connectivity of the Ethernet through the 802.1ag MAC ping
or Gmac ping.
4.9 Configuring Fault Location on the Ethernet
This section describes how to locate connectivity fault on the Ethernet through 802.1ag MAC
trace or Gmac trace.
4.10 Associating EFM OAM with an Interface
This section describes how to associate EFM OAM with an interface.
4.11 Configuring Association Between an EFM OAM Module and an Interface

4 Ethernet OAM Configuration Configuration Guide - Reliability
If association between an EFM OAM module and an interface is configured on a device, when
the EFM OAM module detects a fault, the EFM OAM module on the local device sends a fault
notification message to the OAM management module and triggers the physical status of the
interface bound to the EFM OAM module to go Down. When the physical status of the interface
becomes Down, the OAM management module sends a fault notification message to the EFM
OAM module. Then the EFM OAM module encapsulates the fault notification message to an
OAMPDU and sends it to the remote device.
4.12 Configuring Association Between EFM OAM Modules
The association between EFM OAM modules is applicable to the scenario where EFM OAM is
configured on both ends of a device. When an EFM OAM module on one side detects a link
fault, the EFM OAM module on the local device sends a fault notification message to the OAM
management module. The OAM management module finds the outbound interface and sends
the fault notification message to the EFM OAM module on the other side. The fault notification
message is encapsulated in an OAMPDU, and then transmitted to the remote device.
4.13 Associating Ethernet CFM with an Interface
This section describes how to associate Ethernet CFM with an interface.
4.14 Configuring Association Between an Ethernet CFM Module and an Interface
If association between an Ethernet CFM module and an interface is configured on a device, when
Ethernet CFM detects a fault, the Ethernet CFM module on the local device sends a fault
interface bound to the Ethernet CFM module to go Down. When the physical status of the
interface becomes Down, the OAM management module sends a fault notification message to
the Ethernet CFM module. Then the Ethernet CFM module encapsulates the fault notification
message to an OAMPDU and sends it to the remote device.
4.15 Associating EFM OAM with Ethernet CFM
This section describes how to associate EFM OAM with Ethernet CFM.
4.16 Configuring Association Between Ethernet CFM and Ethernet CFM
This section describes how to configure association between Ethernet CFM and Ethernet CFM.
4.17 Configuring Association Between Ethernet CFM and SEP
This section describes how to configure association between Ethernet CFM and SEP.
4.18 Configuring the One-way Frame Delay Measurement in a VLAN
You can configure the one-way frame delay measurement in the VLAN bound to an MA and
estimate the quality of services based on the calculated one-way frame delay.
4.19 Configuring the Two-way Frame Delay Measurement in a VLAN
You can configure the two-way frame delay measurement in the VLAN bound to an MA and
estimate the quality of services based on the calculated two-way frame delay.
4.20 Maintaining Ethernet OAM
This section describes how to debug EFM OAM and monitor the operation of Ethernet OAM.
This section provides several configuration examples of Ethernet OAM.

4.1 Introduction to Ethernet OAM

This section describes the concept of Ethernet OAM.
Background
Ethernet has developed as the major local area network (LAN) technology because of its low
costs and easy implementation. Recently, along with the applications of Gigabit Ethernet and
10-Gigabit Ethernet, Ethernet has extended into the metropolitan area network (MAN) and wide
area network (WAN).
Compared with MANs and WANs, LANs do not require high reliability and stability. The
Ethernet cannot function as the Internet service provider (ISP) network due to lack of an OAM
mechanism. Therefore, Ethernet OAM is becoming a trend.
Functions of OAM
Ethernet OAM improves the network management and maintenance capabilities on the Ethernet
and guarantees stability.
The functions of Ethernet OAM are as follows:
l Fault management
– OAM detects the network connectivity by sending detection packets at scheduled
intervals or through manual triggering.
– OAM locates faults on the Ethernet by using means similar to ping and traceroute tools
on IP networks.
– OAM works with the protection switching protocol and triggers protection switching
when a connectivity fault is detected. Service interruption can be limited to 50 ms or
shorter, which meets requirements for carrier-class operation.
l Performance management
Performance management is used to measure the packet loss ratio, delay, and jitter during
transmission of packets. It also collects statistics on various types of packets. Performance
management is performed at the user access points. By using performance management
tools, an ISP can monitor the network running status and locate faults through the NMS.
The ISP can then check whether the forwarding capacity of the network complies with the
Service Level Agreement (SLA).
4.2 Ethernet OAM Supported by the S5300

This section describes the Ethernet OAM features supported by the S5300.
EFM OAM
802.3ah, also referred to as Ethernet in the First Mile (EFM), defines the specifications of the
Ethernet physical layer and OAM used for user access. EFM OAM detects the link in the last
mile. EFM OAM is a link-level OAM mechanism. The S5300 provides the following EFM OAM
functions:
l Peer discovery

When the EFM OAM function is enabled on an interface of the S5300 and the peer interface,
the two interfaces match their EFM OAM configurations by sending and responding to
OAM Protocol Data Units (OAMPDUs). If the EFM OAM configurations on both
interfaces match, the two interfaces start the EFM OAM handshake. During the handshake,
the two interfaces send OAMPDUs periodically to maintain the neighbor relationship.
l Link monitoring
When an interface detects an errored frame event or an errored frame error seconds event,
the interface sends an OAMPDU to notify the peer device of the event.
– An errored frame event occurs when the number of errored frames detected on an
interface reaches or exceeds the specified threshold within a certain period.
– An errored code event occurs when the number of errored codes reaches or exceeds the
specified threshold within a certain period.
– An errored frame seconds occurs when that the number of errored frame seconds
detected on an interface reaches or exceeds the specified threshold within a certain
period.
The detection duration is measured in seconds. If at least one errored frame is detected
within a second, this second is called an errored frame second.
l Fault notification
When an errored frame event or severe fault event occurs on the local device, the local node
sends fault notification messages to notify the peer device. At the same time, the local
device records the fault event in the log and reports the fault to the NMS. Fault events
include the following:
– System reboot
– Fault of a physical link
– Timeout of OAMPDUs
– Errors reported by the OAM module
When receiving the notification message, the peer records the event contained in the
message to the log and reports it to the NMS.
l Remote loopback
When a local interface sends non-OAMPDUs to the peer, the peer does not forward the
non-OAMPDUs according to their destination MAC addresses. Instead, the peer loops back
non-OAMPDUs to the local interface. This is called remote loopback. Remote loopback
can be used to locate the link fault and test the link quality.
Each interface enabled with EFM OAM works in a certain mode. EFM OAM has two operation
modes: active mode and passive mode. OAM discovery and remote loopback are initiated only
by the interface in active mode.
Ethernet CFM
802.1ag, referred to as Connectivity Fault Management (CFM), defines the OAM function used
to detect the connectivity of the Ethernet bearer network.

Table 4-1 Differences between IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007
Feature draft7 standard2007 Remarks
MD Supported Supported The features and

configurations supported
by 802.1ag Draft 7 and
Standard 802.1ag-2007 are
the same.
Default MD Not supported Supported -
MA Supported Supported The features and

the same.
MEP Supported Supported The features and

the same.
RMEP Supported Supported The features and

the same.
MIP Supported Supported 802.1ag Draft 7 and

Standard 802.1ag-2007
contain the same types of
MIP creation rules, that is,
default, explicit, and none.
The differences are as
follows:
l In 802.1ag Draft 7, MIPs
are created based on the
interface.
l In Standard
802.1ag-2007, MIPs are
created based on the MD
or default MD.
MP Supported Supported The features and

the same.
l Terms

– MD
A maintenance domain (MD) is a network or a part of the network where CFM is
performed. Devices in an MD are managed by a single ISP.
– Default MD
According to IEEE Standard 802.1ag-2007, each device can be configured with one
default MD. The default MD must be of a higher level than all MDs to which MEPs
configured on the local device belong. In addition, the default MD must be of the same
level as the high-level MD. The default MD transmits high-level CCMs and creates
MIPs to reply LTR packets.
– MA
A maintenance association (MA) is a part of an MD. An MD can be divided into one
or multiple MAs. On the S5300, an MA is associated with a VLAN. Ethernet CFM
checks connectivity in each MA.
– MEP
A maintenance association end point (MEP) is an edge node of an MA.
For a network device running Ethernet CFM, its MEP is called the local MEP. For the
other devices in the same MA, their MEPs are called the remote maintenance association
end points (RMEPs).
CAUTION
One Trunk interface can be configured with only one MEP.
– MIP
A maintenance association intermediate point (MIP) is an internal node of an MA.
MIPs reside on the interfaces on the S5300 and are automatically created by the
S5300.
l Connectivity check
Ethernet CFM divides a network into one MD or multiple MDs. Each MD is divided into
one MA or multiple MAs. The MEPs in an MA exchange Continuity Check messages
(CCMs) periodically to detect the connectivity between them.
l Fault acknowledgement
– 802.1ag MAC ping
Similar to ping, 802.1ag MAC ping sends test packets and waits for a reply to test
whether the destination device is reachable. 802.1ag MAC ping is initiated by a MEP
and destined for a RMEP or MIP in the same MA.
– Gmac ping
Gmac ping works similarly to 802.1ag MAC ping. A MEP, however, is not required to
initiate Gmac ping. The destination node may not be a RMEP or a MIP. Gmac ping can
be implemented without configuring the MD, MA, or MEP on the source device, the
intermediate device, and the destination device.
l Fault location
– 802.1ag MAC trace
Similar to traceroute (or tracert for short), 802.1ag MAC trace sends test packets and
waits for a reply to test the path between the local device and the destination device and

to locate faults. 802.1ag MAC trace is initiated by a MEP and destined for a RMEP or
MIP in the same MA.
– Gmac trace
Gmac trace works similarly to 802.1ag MAC trace. A MEP, however, is not required
to initiate Gmac trace. The destination node may not be a RMEP or a MIP. That is,
Gmac trace can be implemented without configuring the MD, MA, or MEP on the source
device, the intermediate device, and the destination device. All the intermediate devices
can respond with a Linktrace Reply (LTR).
Fault Association
You can configure the following types of association between an EFM OAM module and an
interface.
l After EFM OAM detects a fault, the OAM management module blocks the interface
intermittently. That is, the module shuts down the interface for seven seconds, and then it
unblocks the interface.
l When EFM OAM detects a fault, the interface bound to the EFM OAM module is shut
down or a Port-Down event is sent. When the interface is Down, a fault notification message
is sent to the EFM OAM module of the peer device through association.
l Association between an EFM OAM module and an interface
After association between an EFM OAM module and an interface is configured, when the
EFM OAM module detects a link fault, no packets except OAMPDUs can be forwarded
through the bound interface, and Layer 2 and Layer 3 services are blocked. Therefore, the
association between an EFM OAM module and an interface may greatly affect services.
When the current interface detects link fault recovery through EFM OAM, all packets can
be forwarded on the interface and Layer 2 and Layer 3 services are unblocked.
In addition, you can configure the association between EFM OAM and an interface only
after EFM OAM at both ends are in detect state.
l Association between EFM OAM modules
After a fault is detected, the OAM management module transmits a fault notification
message through association.
– An EFM OAM module on an interface transmits a fault message to an EFM OAM
module on the other interface.
– EFM OAM modules on the two interfaces report faults to each other.
l Association between an Ethernet CFM module and an interface
You can configure the following types of association between an Ethernet CFM module
and an interface.
– When a connectivity fault is detected on the link between the MEP and the RMEP in
an MA, the OAM management module blocks the interface intermittently. That is, the
module shuts down the interface for seven seconds, and then unblocks the interface.
– After Ethernet CFM detects a fault, the interface associated with the Ethernet CFM
module is shut down or a Down event is sent. When the interface becomes Down, the
Ethernet CFM status bound to the interface also becomes Down.
l Association between an Ethernet CFM module and an EFM OAM module
When the Ethernet CFM module detects a fault in an MA, the OAM management module
reports the fault to the peer device enabled with EFM OAM through the interface. When
the EFM OAM module detects a fault, the OAM management module reports the fault to
the MA through the interface. The fault report mode can be the following:

– An Ethernet CFM module sends a fault notification message to an EFM OAM module.
– An EFM OAM module a fault notification message to an Ethernet CFM module.
– An Ethernet CFM module and an EFM OAM module report faults to each other.
l Association between Ethernet CFM modules
When the Ethernet CFM module detects a fault in an MA, the OAM management module
reports the fault to the bound MA at the other side. The fault report mode can be the
following:
– An Ethernet CFM module at one side sends a fault notification message to an Ethernet
CFM module at the other side.
– Ethernet CFM modules at both sides report faults to each other.
4.3 Configuring Basic Functions of EFM OAM

This section describes how to configure basic functions of EFM OAM

4.3.2 Enabling EFM OAM Globally
4.3.3 Setting the Working Mode of EFM OAM on an Interface
4.3.4 (Optional) Setting the Maximum Length of an EFM OAMPDU
4.3.5 Enabling EFM OAM on an Interface
You can perform the configuration task to detect the connectivity between two directly connected
devices, as shown in Figure 4-1.
Figure 4-1 Networking diagram for configuring basic functions of EFM OAM
EFM OAM
interface 1 interface 2
(Active mode) (Passive mode)
None.
Data Preparation
To configure basic functions of EFM OAM, you need the following data.

No. Data
1 (Optional) Maximum length of an EFM OAMPDU
4.3.2 Enabling EFM OAM Globally

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

Step 2 Run:
efm enable
EFM OAM is enabled globally.

By default, EFM OAM is disabled globally.
----End
4.3.3 Setting the Working Mode of EFM OAM on an Interface

Context
NOTE
The working mode of EFM OAM on the interface can be set only after EFM OAM is enabled globally and
before EFM OAM is enabled on the interface. The working mode of EFM OAM on an interface cannot be
changed after EFM OAM is enabled on the interface.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the 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 set.

By default, EFM OAM on an interface works in active mode.

At least one interface at either end of the link must be configured to work in active mode. The
interface in active mode initiates OAM discovery after EFM OAM is enabled on the interface.
Instead of initiating OAM discovery, the interface in passive mode waits for an OAMPDU sent
from the interface in active mode. Interfaces on both ends of the link can work in active mode
at the same time, but they cannot work in passive mode at the same time because link detection
cannot be performed.
NOTE
You must run the bpdu enable command on the interface configured with EFM OAM to enable the BPDU
tunnel function; otherwise, OAM PDUs are discarded. By default, the BPDU tunnel function is disabled
on an interface.
----End
4.3.4 (Optional) Setting the Maximum Length of an EFM OAMPDU

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of an interface at one end of the link is displayed.

Step 3 Run:
efm packet max-size size
The maximum length of an EFM OAMPDU is set.

By default, the maximum length of an EFM OAMPDU on an interface is 128 bytes.
EFM OAMPDUs longer than 128 bytes are discarded as invalid packets.
If the maximum length of an EFM OAMPDU is set differently on both interfaces of the link,
the two interfaces negotiate and determine the value during the OAM discovery. The smaller
maximum length of an EFM OAMPDU set on the local interface and the peer is selected.
----End
4.3.5 Enabling EFM OAM on an Interface

Context
Procedure
Step 1 Run:

system-view

Step 2 Run:

Step 3 Run:
efm enable
EFM OAM is enabled on the interface.

By default, EFM OAM is disabled on an interface.
----End

Prerequisite
The configuration of basic functions of EFM OAM is complete.
Procedure
l Run the display efm { all | interface interface-type interface-number } command to check
information about EFM OAM on an interface.
l Run the display efm session { all | interface interface-type interface-number } command
to check the status of the EFM OAM protocol on an interface.
----End
Example
Run the display efm command, and you can view all the EFM OAM configurations on the local
interface and part of the EFM OAM configurations on the remote interface.
<Quidway> display efm interface gigabitethernet 0/0/1
Item Value
----------------------------------------------------
Interface: GigabitEthernet0/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
Hold Up Time: 0
ThresholdEvtTriggerErrDown: disable
TriggerIfDown: disable
TriggerMacRenew: disable
Remote MAC: 0018-2000-0083
Remote EFM Enable Flag: enable
Remote Mode: passive
Remote MaxSize: 128
Remote State: --

Run the display efm session command. If the EFM OAM protocol on the interface is in the
Detect state, it indicates that the configuration is successful, and the two interfaces succeed in
negotiation and starts the handshake.
<Quidway> display efm session interface gigabitethernet 0/0/1
Interface EFM State Loopback Timeout
--------------------------------------------------------------------
GigabitEthernet0/0/1 detect --
4.4 Configuring EFM OAM Link Monitoring

This section describes how to configure the EFM OAM link monitoring function.

4.4.2 (Optional) Detecting Errored Frames of EFM OAM
4.4.3 (Optional) Detecting Errored Codes of EFM OAM
4.4.4 (Optional) Detecting Errored Frame Seconds of EFM OAM
4.4.5 (Optional) Associating a Threshold Crossing Event with an Interface
The link monitoring function is used to detect faults on the link layer. Event notification
OAMPDUs are used in link monitoring. When a fault is detected on the local link, the EFM
OAM module notifies the remote OAM entity of the fault by sending an event notification
OAMPDU.
Before configuring EFM OAM link monitoring, complete the following task:
l Configuring Basic Functions of 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 frames of EFM OAM
3 (Optional) Period and threshold for detecting errored frame seconds of EFM OAM

4.4.2 (Optional) Detecting Errored Frames of EFM OAM
Context
When an interface is enabled to report the errored frame event, the S5300 generates an errored
frame event and notifies the peer of the event, if the number of errored frames reaches or exceeds
the threshold within a certain period.
Do as follows on one end or both ends of the link.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
efm error-frame period period
The period for detecting errored frames on the interface is set.
By default, the period for detecting errored frames on an interface is 1 second.
Step 4 Run:
efm error-frame threshold threshold
The threshold of number of errored frames on the interface is set.
By default, the threshold of number of errored frames on an interface is 1.
Step 5 Run:
efm error-frame notification enable
The interface is enabled to report the errored frame event.
By default, an interface is disabled from reporting the errored frame event.
----End
4.4.3 (Optional) Detecting Errored Codes of EFM OAM
Context
When an interface is enabled to report the errored code event of EFM OAM, the S9300 generates
an errored code event and notifies the peer if the number of errored codes within a set period
reaches or exceeds the threshold.

Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
efm error-code period period
The period for detecting errored codes on the interface is set.
By default, the period for detecting errored codes on an interface is 1 second.
Step 4 Run:
efm error-code threshold threshold
The threshold of number of errored codes on the interface is set.
By default, the threshold of number of errored codes on an interface is 1.
Step 5 Run:
efm error-code notification enable
The interface is enabled to report the errored code event.
By default, an interface cannot report errored code events of EFM OAM.
----End
4.4.4 (Optional) Detecting Errored Frame Seconds of EFM OAM
Context
The detection duration is measured in seconds. If at least one errored frame is detected within a
second, this second is call an errored frame second. EFM OAM counts the number of seconds
in which errored frames are detected within M seconds.
When an interface is enabled to report the errored frame seconds event, the S5300 generates an
errored frame seconds event and notifies the peer, if the number of errored frame seconds reaches
or exceeds the threshold within a set period.
Procedure
Step 1 Run:
system-view
Step 2 Run:


Step 3 Run:
efm error-frame-second period period
The period for detecting errored frames 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 of number of errored frame seconds on the interface is set.

By default, the threshold of number of errored frame seconds on an interface is 1.
The threshold of number of errored frame seconds on an interface must be smaller than or equal
to the period for detecting errored frame seconds on the interface.
Step 5 Run:
efm error-frame-second notification enable
The interface is enabled to report the errored frame seconds event.

By default, an interface cannot report the errored frame seconds event.
----End
4.4.5 (Optional) Associating a Threshold Crossing Event with an

Interface
Context
When an interface on a link is enabled to detect errored frames, errored codes, or errored frame
seconds, the link is considered unavailable, if the number of errored frames, errored codes, or
errored frame seconds detected by the interface reaches or exceeds the threshold within a set
period. The errored frame event, errored code event, and errored frame seconds summary event
are called threshold crossing events. In this case, you can associate a threshold crossing event
with the interface so that the system sets the administrative state of the interface to Down. As a
result, the link actually goes Down and all services on the interface are interrupted.
Do as follows on the device at one end or devices at both ends of a link:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
efm threshold-event trigger error-down

A threshold crossing event is associated with the interface.
By default, no threshold crossing event is associated with interfaces.
----End
Follow-up Procedure
After a threshold crossing event is associated with an interface, you can configure the interface
to go administratively Up by using either of the following methods:
l Run the error-down auto-recovery cause efm-threshold-event interval interval-value
command in the system view to configure the interface to go administratively Up after the
auto-recovery delay.
l Run the shutdown command and then the undo shutdown command in the interface view
to restore the administrative state of the interface to Up.
Prerequisite
The configuration of the link monitoring function of EFM OAM is complete.
Procedure
Step 1 Run the display efm { all | interface interface-type interface-number } command to check
----End
Example
Run the display efm command, and you can view information about link monitoring on an
interface.
<Quidway> display efm interface gigabitethernet0/0/1
Item Value
----------------------------------------------------
Mode: active
OAMPDU MaxSize: 128
ErrCodePeriod: 5
ErrCodeThreshold: 5
ErrFramePeriod: 5
Hold Up Time: 0
Remote MAC: 0018-2000-0083
Remote MaxSize: 128
Remote State: --

4.5 Testing the Packet Loss Ratio on a Physical Link

This section describes how to configure remote loopback of EFM OAM to test the packet loss
ratio on a link by sending test packets.

4.5.2 Enabling Remote Loopback of EFM OAM
4.5.3 Sending Test Packets
4.5.4 Checking the Statistics on Returned Test Packets
4.5.5 (Optional) Disabling Remote Loopback of EFM OAM

CAUTION
The forwarding of service data is affected after remote loopback is enabled. Therefore, enable
the EFM OAM remote loopback on the link that does not need to forward service data.
Perform this configuration task when you need to detect the packet loss ratio on a link.
As shown in Figure 4-2, enable EFM OAM on Switch A and Switch B and enable remote
loopback on GE 0/0/1 on Switch A. Send test packets from Switch A to Switch B. You can
obtain the packet loss ratio on the link by observing the received test packets on Switch A.
Figure 4-2 Networking diagram for testing the packet loss ratio on the link
Test packets
EFM OAM
SwitchA SwitchB
GE 0/0/1 GE0/0/1
(Active mode) (Passive mode)
Flow of test packets
Before testing the packet loss ratio on a link, complete the following task:

l Configuring Basic Functions of EFM OAM
Data Preparation
To test the packet loss ratio on the link, you need the following data.
No. Data
1 Timeout period for remote loopback
2 Destination MAC address, VLAN tag, outgoing interface, size, number, and sending
rate of test packets
4.5.2 Enabling Remote Loopback of EFM OAM
Context
Do as follows on the S5300 with an active interface on the link.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
efm loopback start [ timeout timeout ]
Remote loopback is enabled on the interface.
Before changing the value of timeout timeout, run the efm loopback stop command to disable
remote loopback on the interface.
By default, the timeout period for remote loopback is 20 minutes. After 20 minutes, remote
loopback is disabled automatically. You can set the timeout period to 0 for a link to retain the
remote loopback state.
Remote loopback can be implemented only when the EFM OAM sessions on the local interface
and the peer are in handshake state and the local interface works in active mode. You can use
the display efm session command to check whether the EFM OAM sessions on the local
interface and the peer are in handshake state.
----End

4.5.3 Sending Test Packets

Context
Procedure
Step 1 Run:
system-view

Step 2 Run:
test-packet start interface interface-type interface-number [ -c count | -s size ]
*
The S5300 is configured to send test packets.

By default, the size of a test packet is 64 bytes; five test packets are sent at the rate of 1 Mbit/s.
The outgoing interface of the test packets is the interface that is connected to the link to be tested.
----End
Follow-up Procedure
The parameters in this command cannot be modified when test packets are being sent.
Press Ctrl+C to stop sending test packets.
4.5.4 Checking the Statistics on Returned Test Packets

Context
Procedure
Step 1 Run:
display test-packet result
The statistics on the returned test packets are displayed.

The displayed information includes:
l Number of sent test packets

l Number of received packets
l Number of discarded packets
l Total length of sent packets, in bytes
l Total length of received packets, in bytes
l Total length of discarded packets, in bytes
l Start time of sending packets

l End time of sending packets
You can obtain the packet loss ratio on the link based on the preceding data.
<Quidway> display test-packet result
TestResult Value
--------------------------------------------------------
PacketsSend : 5
PacketsReceive : 0
PacketsLost : 5
BytesSend : 320
BytesReceive : 0
BytesLost : 320
StartTime : 08-03-2009 20:41:14 UTC+03:00
EndTime : 08-03-2009 20:41:21 UTC+03:00
----End
4.5.5 (Optional) Disabling Remote Loopback of EFM OAM
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
efm loopback stop
Remote loopback is disabled on the interface.
Users may forget to disable EFM OAM remote loopback, which causes the link to fail to forward
service data for a long time. To avoid this, the S5300 automatically disables EFM OAM remote
loopback when remote loopback times out. By default, the timeout period of remote loopback
is 20 minutes. After 20 minutes, remote loopback stops. If you need to disable remote loopback
manually, perform the preceding configuration steps.
----End
Procedure
Step 1 Run the display efm session { all | interface interface-type interface-number } command to
check the status of the EFM OAM session on an interface.
----End

Example
Run the display efm session command on the device with an active interface on the link. If the
EFM OAM protocol on the active interface is in the Loopback (control) state, which indicates
that the active interface initiates remote loopback, it indicates that the configuration is successful.
<SwitchA> display efm session interface gigabitethernet 0/0/1
----------------------------------------------------------------------
GigabitEthernet0/0/1 Loopback(control) 20
Run the display efm session command on the device with a passive interface on the link. If the
EFM OAM protocol on the passive interface is in the Loopback (be controlled) state, which
indicates that the passive interface responds to remote loopback, it indicates that the
configuration is successful.
<SwitchB> display efm session interface gigabitethernet 0/0/1
----------------------------------------------------------------------
GigabitEthernet0/0/1 Loopback(be controlled) --
Run the display efm session command on either of the devices on the link. If the EFM OAM
protocol on the interface is in the Detect or Discovery state, it indicates that the configuration is
successful.
<SwitchA> display efm session interface gigabitethernet 0/0/1
----------------------------------------------------------------------
4.6 Configuring Basic Functions of Ethernet CFM

This section describes how to configure basic functions of Ethernet CFM.

4.6.2 Switching the IEEE 802.1ag Version
4.6.3 Enabling Ethernet CFM Globally
4.6.4 Creating an MD
4.6.5 (Optional) Creating the Default MD
4.6.6 Creating an MA
4.6.7 Creating a MEP
4.6.8 Creating an RMEP
4.6.9 (Optional) Setting the MIP Creation Rule
4.6.10 Configuring Continuity Check
4.6.11 (Optional) Creating a VLAN

You can perform this configuration task to implement the following functions on the Ethernet:
l Automatic end-to-end connectivity detection

l Automatic connectivity detection on direct links
To implement automatic end-to-end connectivity detection on the Ethernet, you need to perform
the following:
l Classify MDs based on the ISPs that manage the devices. All the devices that are managed
by a single ISP and enabled with CFM are added to the same MD.
l Classify MAs based on service instances. Associate each MA with a VLAN. A VLAN
generally maps to a service instance. When MAs are classified, connectivity faults can be
detected on the network where a service instance is transmitted.
l Determine the interfaces at the edge of the MA, that is, determine the interfaces where
MEPs must be configured.
When implementing automatic connectivity detection on direct links, you need to perform the
following:
l Add the devices at both ends of the link to the same MA in an MD.
l Associate the MA with a VLAN.
l Configure MEPs on the interfaces at both ends of the direct link.
None.
Data Preparation
To configure basic functions of Ethernet CFM, you need the following data.
No. Data
1 Name and level of an MD
2 Name of an MA and ID of the VLAN associated with the MA
3 ID of a MEP, name of the interface on which the MEP is configured, and type of the
MEP
4 (Optional) ID of an RMEP and bridge MAC address of the device on which the RMEP
is configured
5 Rule for creating a MIP
6 Interval at which an MEP sends or detects CCMs in an MA

4.6.2 Switching the IEEE 802.1ag Version
Context
By default, IEEE 802.1ag Draft 7 is enabled on a device. To use IEEE Standard 802.1ag-2007,
do as follows on each S5300.
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm version { draft7 | standard }
The IEEE 802.1ag version is changed.
CAUTION
After the IEEE 802.1ag version is changed, the original CFM configuration will be deleted.
Therefore, use this command with caution.
NOTE
All the devices on the entire network must use either IEEE 802.1ag Draft 7 or IEEE Standard 802.1ag-2007.
IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007 cannot be enabled together on a network.
----End
4.6.3 Enabling Ethernet CFM Globally
Context
Do as follows on the S5300 that requires Ethernet CFM.
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm enable
Ethernet CFM is enabled globally.
By default, Ethernet CFM is disabled globally on the S5300.
----End

4.6.4 Creating an MD
Context
Do as follows on the S5300 where Ethernet CFM needs to be configured.
Procedure
Step 1 Run:
system-view
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.
By default, an MD is at level 0, which is the lowest level.
Repeat Step 2 to create more MDs. Up to 16 MDs can be created on an S5300.
format, no-md-name, dnsname-and-mdname, mac-address,and md-name are only

supported by IEEE Standard 802.1ag-2007.
After an MD is created, its parameters cannot be modified. To modify the parameters, delete the
MD and create a new one.
NOTE
The 802.1ag packets from a low-level MD are discarded in a high-level MD. The 802.1ag packets from a
high-level MD can be transmitted through a low-level MD.
----End
4.6.5 (Optional) Creating the Default MD
Context
Do as follows on each S5300 where Ethernet CFM needs to be configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm default md [ level level ]
The default MD is created and the default MD view is displayed.
By default, the default MD is at level 7, which is the highest level.
Only one default MD can be created on each device.

After the default MD is created, its parameters cannot be modified. To modify the parameters,
delete the default MD and create a new one.
NOTE
The default MD must be of a higher level than all MDs that MEPs configured on the local device belong
to. In addition, the default MD must be of the same level as the high-level MD. The default MD transmits
high-level CCMs and creates MIPs to send LTRs.
NOTE
IEEE 802.1ag has two versions, that is, IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007. The cfm
default md command can be used only on the device complying with IEEE Standard 802.1ag-2007. Before
using the cfm default md command, you must use the cfm version command to set the IEEE 802.1ag
version to IEEE Standard 802.1ag-2007.
----End
4.6.6 Creating an MA
Context
Do as follows on the S5300 that requires Ethernet CFM.
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name
The MD view is displayed.

Step 3 Run:
ma ma-name
An MA is created and the MA view is displayed.

You can create up to 256MAs in an MD. You can create up to 256 MAs on an S5300.
Each MA is associated with a VLAN.
NOTE
If an interface-based MEP is configured in an MA, the MA cannot be associated with a VLAN.
Step 4 (Optional)Run:
map vlan vlan-id
The MA is associated with a VLAN.

By default, an MA is not associated with any VLAN.
Ethernet CFM checks connectivity in each MA. After an MA is associated with a VLAN,
Ethernet CFM can detect the connectivity fault on the network within the VLAN.
This step is optional. If an MA is used to detect the connectivity fault between two directly
connected devices, the MA does not needs to be associated with a VLAN. In other cases, the
MA must be associated with a VLAN.

An MA can be associated with only one VLAN.
----End
Follow-up Procedure
Perform the preceding steps as required:
l To create multiple MAs in an MD, repeat Step 3 and Step 4.
l To create MAs in multiple MDs, repeat Step 2 to Step 4.
4.6.7 Creating a MEP

Context
When creating a MEP in an MA, pay attention to the following points:
l When creating an inward MEP, ensure that the MA has been associated with a VLAN and
the interface on which the MEP is located has been added to the VLAN. An inward MEP
sends 802.1ag packets through all the interfaces in the VLAN associated with the MA
except the interface on which the MEP is located. That is, an inward MEP broadcasts
802.1ag packets in the VLAN associated with the MA.
l Then the protocol packets sent from the outward MEP is forwarded by this interface.
The requirements for the MEPs created in an MA on the same S5300 are as follows:
l The inward MEP and outward MEP are mutually exclusive.
l Only one outward MEP can be created. Multiple inward MEPs can be created, but only
one inward MEP can be created on an interface.
Up to 8191 MEPs can be created in an MA.
Do as follows on the edge devices of an MA.
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name
The MA view is displayed.

Step 4 Run:
mep mep-id mep-id interface interface-type interface-number [ vlan vlan-id | pe-
vid pe-vid ce-vid ce-vid ] { inward | outward }
A MEP is created on an interface.
----End

Follow-up Procedure
l To create multiple MEPs in an MA, repeat Step 4.
l To create MEPs in multiple MAs, repeat Step 3 and Step 4.
l To create MEPs in multiple MDs, repeat Step 2 to Step 4.
4.6.8 Creating an RMEP

Context
To detect the connectivity between a device and an RMEP, you need to create the RMEP first.
Up to 32K RMEPs can be created on an S5300.
Do as follows on the edge devices of an MA.
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
remote-mep mep-id mep-id [ mac mac-address ]
An RMEP in the MA is created.
----End
Follow-up Procedure
l To create multiple RMEPs in an MA, repeat Step 4.
l To create RMEPs in multiple MAs, repeat Step 3 to Step 4.
l To create multiple RMEPs in multiple MDs, repeat Step 2 and Step 4.
4.6.9 (Optional) Setting the MIP Creation Rule

Context
Do as follows on each S5300 where Ethernet CFM needs to be configured.

Procedure
Step 1 Run:
system-view

Step 2 Set the MIP creation rule.
Run the following command as required. You can set the MIP creation rule in accordance with
IEEE 802.1ag Draft 7 or IEEE Standard 802.1ag-2007.
l Run the following command to set the MIP creation rule in accordance with IEEE 802.1ag
Draft 7.
Run:
mip create-type { default | explicit | none } [ interface interface-type
interface-number ]
The MIP creation rule in accordance with IEEE 802.1ag Draft 7 is set.
l Run the following commands to set the MIP creation rule in accordance with IEEE Standard
802.1ag-2007.
1. Run:
cfm md md-name [ format { no-md-name | dnsname-and-mdname | mac-address |
md-name } ] [ level level ]

Or, run:
The default MD view is displayed.
You can choose either view.
2. Run:
mip create-type { default | explicit | none }
The MIP creation rule in accordance with IEEE Standard 802.1ag-2007 is set.
By default, the MIP creation rule is none. The rule is classified into the following types:
l default: A MIP can be created on an interface if neither a MEP of a higher level nor a MIP
of a lower level is configured on the interface.
l explicit: A MIP cannot be created on an interface if no MEP of a lower level exists. A MIP
can be created on an interface if neither a MEP of a higher level nor a MIP of a lower level
exists.
l none: A MIP cannot be created on the interface that the MD or default MD belongs to.
If the MIP creation rule is default or explicit, a device creates a MIP automatically according
to the rule.
The level of a MIPs depends on the MIP creation rule and the level of the MD where MIPs are
created.
----End
4.6.10 Configuring Continuity Check

Context
Do as follows on the edge devices (MEPs) are located in all MAs.

Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
ccm-interval interval
The interval at which the MEP sends or detects CCMs in the local MA is set.
By default, the MEP sends or detects CCMs every 1 second.
Do not change the interval for sending or detecting CCMs in an MA if:
l The sending of CCMs is enabled by using the mep ccm-send enable command in the MA.
l The receiving of CCMs is enabled by using the remote-mep ccm-receive enable command
in the MA.
To change the interval for sending or detecting CCMs in an MA, you must run the related undo
commands to disable the sending or receiving of CCMs.
Step 5 Run:
mep ccm-send [ mep-id mep-id ] enable
The MEPs are enabled to send CCM packets.

By default, a MEP is disabled from sends 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 local MEP is enabled to receive CCM packets from the RMEP in the same MA.
By default, the local MEP cannot receive CCMs from the RMEP.
When the local device is enabled to receive CCMs from an RMEP, and if a connectivity fault
is detected between the local device and the RMEP through continuity check, the local device
generates an alarm of RMEP connectivity.
If mep-id mep-id is not specified, the MEP is enabled to receive CCMs from all the RMEPs in
the same MA.
----End
Follow-up Procedure

l To enable continuity check in multiple MAs, repeat Step 3 to Step 6.

l To enable continuity check in multiple MDs, repeat Step 2 to Step 6.
4.6.11 (Optional) Creating a VLAN
Context
Do as follows on the device where a VLAN needs to be created.
Procedure
Step 1 Run:
system-view
Step 2 Run:
The default MD is created and the default MD view is displayed.
Step 3 Run:
vlan { vlan-id1 [ to vlan-id2 ] }&<1-10>
A VLAN is created.
NOTE
IEEE 802.1ag has two versions, that is, IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007. The cfm
default md command can be used only on the device complying with IEEE Standard 802.1ag-2007. Before
using the cfm default md command, you must use the cfm version command to set the IEEE 802.1ag
----End
Prerequisite
The configurations of basic functions of Ethernet CFM are complete.
Procedure
l Run the display cfm md [ md-name ] command to check the configuration of an MD.
l Run the display cfm ma [ md md-name [ ma ma-name ] ] command to check detailed
information about an MA.
l Run the display cfm mep [ md md-name [ ma ma-name [ mep-id mep-id ] ] ] command
to check detailed information about a MEP.
l Run the display cfm remote-mep md md-name ma ma-name [ mep-id mep-id ] or display
cfm remote-mep [ md md-name [ ma ma-name ] ] [ cfm-state { up | down | disable } ]
command to check detailed information about an RMEP.
l Run the display mip create-type [ interface interface-type interface-number ] command
to check the MIP creation rule.

l Run the display cfm mip [ interface interface-type interface-number | level level ]
command to check information about a MIP.
----End
Example
# In IEEE 802.1ag Draft 7, If an MD is created successfully, you can view the MD and the level
of the MD after running the display cfm md command.
<Quidway> display cfm md
The total number of MDs is : 1
MD-Name Level
--------------------------------------------------
md1 0
In IEEE Standard 802.1ag-2007, if an MD is created successfully,you can view the MD and the
level of the MD after running the display cfm md command.
<Quidway> display cfm md md1
MD Name : md1
MD Name Format : md-name
Level : 0
MIP Create-type : none
SenderID TLV-type : defer
MA list :
MA Name : ma1
Interval : 1000
Vlan ID : 10
VSI Name : --
MA Name : ma
Interval : 1000
Vlan ID : --
VSI Name : --
In IEEE 802.1ag Draft 7, If an MA is created successfully, you can view information about the
MA after running the display cfm ma command.
<Quidway> display cfm ma
The total number of MAs is : 1
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
Interval : 1000
Priority : 6
Vlan ID : --
VSI Name : --
MEP Number : 0
RMEP Number : 0
In IEEE 802.1ag Draft 7, If a MEP is created successfully, you can view information about the
MEP after running the display cfm mep command.
<Quidway> display cfm mep
The total number of MEPs is : 2
--------------------------------------------------
MD Name : md2
Level : 7
MA Name : ma3
MEP ID : 40
Vlan ID : 10
VSI Name : --
Interface Name : GigabitEthernet0/0/1
CCM Send : enabled
Direction : outward

# In IEEE Standard 802.1ag-2007, display information about the MEP with the ID being 10 in
ma1 of md1.
<Quidway> display cfm mep md md1 ma ma1 mep-id 10
MD Name : md1
Level : 0
MA Name : ma1
MEP ID : 11
Vlan ID : 221
VSI Name : --
CCM Send : disabled
Direction : inward
MAC Address : 0018-2000-0083
Run the display cfm remote-mep command. If information about the RMEP is displayed, it
indicates that the configuration is successful.
<Quidway> display cfm remote-mep
The total number of RMEPs is : 2
The status of RMEPS : 2 up, 0 down, 0 disable
--------------------------------------------------
MD Name : md2
Level : 7
MA Name : ma3
RMEP ID : 110
Vlan ID : 20
VSI Name : --
MAC : 0000-0121-0222
CCM Receive : enabled
Trigger-If-Down : disabled
CFM Status : up
MD Name : md2
Level : 4
MA Name : ma3
RMEP ID : 30
Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
In IEEE 802.1ag Draft 7,run the display mip create-type command. If the MIP creation rule is
correct, it indicates that the configuration is successful.
<Quidway> display mip create-type interface gigabitethernet0/0/1
Interface Name MIP Create-Type MIP Create-Type On Interface
---------------------------------------------------------------------------
GigabitEthernet0/0/1 none --
Run the display cfm mip command. If information about the MIP is displayed, it indicates that
the configuration is successful.
<Quidway> display cfm mip
Interface Name Level
-----------------------------------
GigabitEthernet0/0/1 0
4.7 Adjusting Parameters of Ethernet CFM

By adjusting parameters of Ethernet CFM, you can better implement end-to-end Ethernet CFM
on a device.


4.7.2 (Optional) Setting the Activation Time for Receiving CCMs from the RMEP
4.7.3 (Optional) Setting the Anti-Jitter Time During Alarm Restoration
4.7.4 (Optional) Setting the Anti-Jitter Time During Alarm Generation
If Ethernet CFM is enabled, you can adjust related parameters. According to different application
environments, you can adjust the following parameters:
l Activation time for receiving CCMs from the RMEP

After the local device is enabled with the function of receiving CCMs from a certain RMEP,
the local device displays the RMEP connectivity alarm in one of the following situations:
– A connectivity fault is detected between the local MEP and the RMEP through CC.
– The physical link works normally between the local MEP and the RMEP. The peer
device is not configured with a MEP when CC is performed or the MEP configuration
is later than the CC. In this case, if the local MEP does not receive CCMs from the
RMEP in consecutive three intervals for sending CCMs, the local device considers that
a connectivity fault occurs between the local MEP and the RMEP.
According to the preceding information, the RMEP connectivity fault alarm is incorrect.
To solve the problem, you can set the activation time for receiving CCMs from the
RMEP.
If a device is configured with the activation time for receiving CCMs from the RMEP, after
the local device is enabled to receive CCMs from a certain RMEP, the local device can
receive CCMs at the set activation time for receiving CCMs from the RMEP. That is, the
activation time for receiving CCMs from the RMEP is the time reserved for configuring
the RMEP.
At the set activation time for receiving CCMs from the RMEP, if the local MEP does not
receive CCMs in consecutive three intervals for sending CCMs, the local device considers
that a connectivity fault occurs between the local MEP and the RMEP. Then the local device
displays the RMEP connectivity fault alarm.
l Anti-jitter time during alarm restoration
All the RMEPs of each MA use the following timers:
– Alarm generation timer: The interval is the anti-jitter time during alarm generation.
– Alarm restoration timer: The interval is the anti-jitter time during alarm restoration.
When the RMEP detects an alarm, the alarm generation timer is activated. After the timer
expires, the alarm is reported to the device. When the RMEP detects that the alarm is
restored, the alarm restoration timer is activated. After the timer expires, the alarm
restoration event is reported to the device.
If the RMEP frequently detects alarms and alarm restoration signals, it indicates that alarm
flapping occurs.
To suppress alarm flapping, you can set the anti-jitter time during alarm generation.
l Specified VLAN

All interfaces of the specified VLAN generate MIPs according to the MIP creation rule in
the MD.
None.
Data Preparation
To adjust parameters of Ethernet CFM, you need the following data.
No. Data
1 (Optional) Activation time for receiving CCMs from the RMEP
2 (Optional) Anti-jitter time during alarm restoration
3 (Optional) Anti-jitter time during alarm generation
4.7.2 (Optional) Setting the Activation Time for Receiving CCMs

from the RMEP
Context
Do as follows on edge devices of an MA.
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
active time time
The activation time for receiving CCMs from the RMEP is set.
By default, the activation time for receiving CCMs from the RMEP is 0s.
If an RMEP is configured in an MA, the activation time cannot be set for the RMEP.

NOTE
IEEE 802.1ag has two versions, that is, IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007. The active
time time command can be used only on the device complying with IEEE Standard 802.1ag-2007. Before
using the active time time command, you must use the cfm version command to set the Ethernet CFM
----End
4.7.3 (Optional) Setting the Anti-Jitter Time During Alarm

Restoration
Context
Do as follows on the device where the anti-jitter time during alarm restoration needs to be set.
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
alarm finish time time
The anti-jitter time during alarm restoration is set.
By default, the anti-jitter time during alarm restoration is 10000 ms.
NOTE
IEEE 802.1ag has two versions, that is, IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007. The alarm
finish time time command can be used only on the device complying with IEEE Standard 802.1ag-2007.
Before using the alarm finish time time command, you must use the cfm version command to set the
Ethernet CFM version to IEEE Standard 802.1ag-2007.
----End
4.7.4 (Optional) Setting the Anti-Jitter Time During Alarm

Generation
Context
Do as follows on the device where the anti-jitter time during alarm generation needs to be set.

Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
alarm occur time time
The anti-jitter time during alarm generation is set.

By default, the anti-jitter time during alarm generation is 2500 ms.
NOTE
IEEE 802.1ag has two versions, that is, IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007. The alarm
occur time time command can be used only on the device complying with IEEE Standard 802.1ag-2007.
Before using the alarm occur time time command, you must use the cfm version command to set the
Ethernet CFM version to IEEE Standard 802.1ag-2007.
----End
4.8 Configuring Fault Acknowledgement on the Ethernet

This section describes how to check connectivity of the Ethernet through the 802.1ag MAC ping
or Gmac ping.

4.8.2 (Optional) Performing 802.1ag MAC Ping
4.8.3 (Optional) Performing Gmac Ping

When you need to check connectivity between two devices manually, you can configure the
local device to send test packets and wait response packets on the local device to check whether
the remote device is reachable. Based on the type of the link to be tested, you can adopt the
following methods to check the link connectivity:
l To check connectivity of the link between MEPs or between a MEP and a MIP in the same
MA on a network with MDs, MAs, and MEPs, use 802.1ag MAC ping.
l To check connectivity of the link between two devices on a network without MDs, MAs,
and MEPs, use Gmac ping.

Before performing 802.1ag MAC ping, complete the following task:
l Configuring Basic Functions of Ethernet CFM
No pre-configuration task is required for Gmac ping.
Data Preparation
To test connectivity of the Ethernet, you need the following data.
No. Data
1 (Optional) MAC address or ID of the destination MEP
2 (Optional) MAC address of the destination MIP
3 (Optional) Number, size, timeout period, and outgoing interface of MAC ping packets
4 (Optional) VLAN that the destination node belongs to
4.8.2 (Optional) Performing 802.1ag MAC Ping
Context
Do as follows on the S5300 at one end of the link to be tested. Ensure that a MEP is created on
the S5300.
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
ping mac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ pe-vid pe-vid ce-
vid ce-vid ] [ -c count | interface interface-type interface-number | -s
packetsize | -t timeout ] *
802.1ag MAC ping is performed to check connectivity of the link between the S5300 and the
specified RMEP or MIP.
When implementing 802.1ag MAC ping, pay attention to the following points:

l The MA must be associated with a VLAN.

l The MEP must be configured in the MA.
l The outgoing interface (if specified) cannot be configured with an inward MEP.
l If the destination node is an RMEP, either mac mac-address or mac mac-address can be
selected. If remote-mep mep-id mep-id is selected, the RMEP must already be created by
using the remote-mep command and the bridge MAC address of the device on which the
RMEP is located must be specified.
l If the destination node is a MIP, select mac mac-address.
An intermediate device on a link is only used to forward LBMs and LBR messages; therefore,
the intermediate device does not need to be configured with the MD, MA, or MEP.
----End
4.8.3 (Optional) Performing Gmac Ping
Context
Perform step 1 and step 2 on the S5300s at both ends of the link to be tested. Perform step 3 on
either of the S5300s.
Procedure
Step 1 Run:
system-view
Step 2 Run:
ping mac enable
Gmac ping is enabled globally.
By default, Gmac ping is disabled.
When Gmac ping is enabled, the S5300 can:
l Send Gmac ping packets.

l Respond to received Gmac ping packets.
Step 3 Run:
ping mac mac-address vlan vlan-id [ interface interface-type interface-number | -c
count | -s packetsize | -t timeout ] *
Gmac ping is performed to check connectivity of the link between the S5300 and the remote
device.
Gmac ping does not need to be initiated by a MEP, and the destination node may not be a MEP
or a MIP. That is, Gmac ping can be implemented without configuring the MD, MA, or MEP
on the source device, the intermediate device, or the destination device.
The two devices must be configured with IEEE 802.1ag of the same version. If the local device
is configured with IEEE 802.1ag Draft 7 and the peer device is configured with IEEE Standard

802.1ag-2007, when you use the ping mac command to check the connection between the local
device and the peer device, the local device cannot ping the peer device.
----End
4.9 Configuring Fault Location on the Ethernet

This section describes how to locate connectivity fault on the Ethernet through 802.1ag MAC
trace or Gmac trace.

4.9.2 (Optional) Performing 802.1ag MAC Trace
4.9.3 (Optional) Performing Gmac Trace
By sending test packets on the local device and checking the received response packets, you can
check the reachability of the path from the local device to the destination device and locate the
faulty node on the path. You can use different methods according to the type of the link to be
tested:
l To locate faults on the link between MEPs or between a MEP and a MIP in the same MA
on a network where MDs, MAs, and MEPs are configured, use 802.1ag MAC trace.
l To locate faults on the link between two devices on a network where MDs, MAs, or MEPs
are not configured, use the Gmac trace.
Before performing 802.1ag MAC trace, complete the following task:
l Configuring Basic Ethernet CFM Functions
Data Preparation
To perform 802.1ag MAC trace, you need the following data.
No. Data
1 (Optional) MAC address or ID of the destination MEP
2 (Optional) MAC address of the destination MIP
3 (Optional) Outbound interface of MAC trace packets
4 (Optional) Timeout interval for waiting for a response packet
5 (Optional) Maximum number of hops of trace packets
6 (Optional) VLAN that the destination node belongs to

4.9.2 (Optional) Performing 802.1ag MAC Trace
Context
Do as follows on the S5300 at one end of the link to be tested. Ensure that a MEP is created on
the S5300.
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
trace mac-8021ag { mac mac-address | remote-mep mep-id mep-id } [ pe-vid pe-vid ce-
vid ce-vid ] [ interface interface-type interface-number | -t timeout | ttl ttl ]
*
802.1ag MAC trace is performed to locate faults on the link between the S5300 and the specified
RMEP or MIP.
When performing 802.1ag MAC trace, pay attention to the following points:
l The MA must be associated with a VLAN.

l The MEP must be configured in the MA.
l The outgoing interface (if specified) cannot be configured with an inward MEP.
l If the destination node is an RMEP, either mac mac-address or mac mac-address can be
selected. If remote-mep mep-id mep-id is selected, the RMEP must already be created by
using the remote-mep command and the bridge MAC address of the device on which the
RMEP is located 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.
----End
4.9.3 (Optional) Performing Gmac Trace
Context
Do as follows on all the S9300s on the tested link.

Procedure
l Configuring the S5300s on both ends of a link and intermediate S5300s
Do as follows on the S5300s on both ends of the link to be tested and intermediate
S5300s.
1. Run:
system-view

2. Run:
trace mac enable
Gmac trace is enabled globally.

By default, Gmac trace is disabled.
The following operations can be performed only after MAC trace is enabled:
– Performing Gmac trace on the S5300.
– Responding to the received Gmac trace packets
.
l Performing Gmac trace
Do as follows on the S5300 at either end of the link to be tested.
1. Run:
system-view

2. Run:
trace mac mac-address vlan vlan-id [ interface interface-type interface-
number | -t timeout ] *
Gmac trace is performed to locate the faults on the link between the S5300 and the
remote device.
A MEP is not required to initiate Gmac trace, and the destination node may not be a
MEP or a MIP. That is, Gmac trace can be implemented without configuring the MD,
MA, or MEP on the source device, the intermediate device, and the destination device.
All the intermediate devices respond to the Gmac trace packets with LTR messages.
The two devices must be configured with IEEE 802.1ag of the same version. If the
local device is configured with IEEE 802.1ag Draft 7 and the peer device is configured
with IEEE Standard 802.1ag-2007, when you use the trace mac command to check
the connection between the local device and the peer device, the local device cannot
ping the peer device.
----End
4.10 Associating EFM OAM with an Interface

This section describes how to associate EFM OAM with an interface.

4.10.2 Configuring Association Between an EFM OAM Module and an Interface

4.10.3 (Optional) Setting the Faulty-State Hold Timer

As shown in Figure 4-3, EFM OAM is enabled on Switch A and Switch B. EFM OAM is
associated with GE 0/0/1 on Switch A. When the EFM OAM module on Switch A detects a
connectivity fault between Switch A and Switch B, no other packets except EFM protocol
packets can be forwarded on the interface GE 0/0/1and Layer 2 and Layer 3 services are blocked.
Therefore, the association of EFM OAM and the current interface may greatly affect services.
When the current interface detects the link fault recovery through EFM OAM, all packets can
be forwarded on the interface and Layer 2 and Layer 3 services are unblocked.
Figure 4-3 Diagram of associating EFM OAM with an interface

EFM
OAM
GE0/0/1 GE0/0/1
SwitchB
SwitchA
Interface associated with EFM OAM
Before associating EFM OAM with an interface, complete the following task:
l 4.3 Configuring Basic Functions of EFM OAM
Data Preparation
To associate EFM OAM with an interface, you need the following data.
No. Data
1 Type and number of the interface associated with EFM OAM
4.10.2 Configuring Association Between an EFM OAM Module and

an Interface
Context
Before configuring association between an EFM OAM module and an interface, ensure that the
EFM OAM protocol at both ends is in detect state.

By default, an interface is not associated with EFM OAM.

Procedure
l Run:
system-view

l Run:

l Run:
efm trigger if-down
By default, an interface is not associated with an EFM OAM module.

Before associating an EFM OAM module with an interface, you must enable EFM OAM
on the interface by using the efm enable command.
The EFM OAM module is associated with the interface.
If an EFM OAM module is associated with an interface, the interface cannot forward any
PDUs except the OAMPDUs when EFM OAM detects a connectivity fault on the link.
Then Layer 2 and Layer 3 services are all blocked on the interface. Therefore, associating
EFM OAM with an interface affects services. When the interface detects that the
connectivity fault is rectified through EFM OAM, the interface starts to forward PDUs and
notifies all the Layer 2 and Layer 3 services on the interface.
If Layer 2 and Layer 3 services are blocked because of misoperation, you can run the undo
efm trigger if-down command in the interface view to restore the services.
----End
4.10.3 (Optional) Setting the Faulty-State Hold Timer
Context
Do as follows on the device at one end or devices at both ends of a link:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
efm holdup-timer time

The faulty-state hold timer is set.

By default, the timeout period of the faulty-state hold timer is 0s.
After the efm trigger if-down command is used to associate EFM OAM with an interface, when
EFM OAM detects a connectivity fault, the faulty state displayed on the interface remains
unchanged within the set timeout period of the faulty-state hold timer, even though the fault is
rectified. EFM OAM does not detect whether the connectivity fault is cleared until the timeout
period of the faulty-state hold timer expires.
----End

Prerequisite
The configuration of association between EFM OAM and an interface is complete.
Procedure
Step 1 Run the display efm { all | interface interface-type interface-number } command to check
----End
Example
If EFM OAM is associated with an interface in the interface view, you can find that
TriggerIfDown is displayed as enable after running the display efm command.
<Quidway> display efm interface gigabitethernet0/0/1
Item Value
----------------------------------------------------
Mode: active
OAMPDU MaxSize: 128
ErrCodePeriod: 5
ErrCodeThreshold: 5
ErrFramePeriod: 5
Hold Up Time: 0
TriggerIfDown: enable
Remote MAC: 0018-2000-0083
Remote MaxSize: 128
Remote State: --

4.11 Configuring Association Between an EFM OAM

Module and an Interface
OAM module. Then the EFM OAM module encapsulates the fault notification message to an
OAMPDU and sends it to the remote device.

4.11.2 Configuring Association Between an EFM OAM Module and an Interface
As shown in Figure 4-4, PE1 and PE2 are enabled with EFM OAM. When the link between
PE1 and PE2 is faulty, CEs need to detect faults to ensure the reliability of service transmission.
In this case, you can configure association between an EFM OAM module and an interface on
PE1 and PE2. Take PE2 as an example. When EFM OAM detects a link fault, the EFM OAM
module on PE2 sends a fault notification message to the OAM management module and triggers
the physical status of GE 1/0/2 bound to the EFM OAM module to go Down. Then CE2 detects
the link fault. The reliability of service transmission is thus ensured.
Figure 4-4 Networking diagram for configuring association between an EFM OAM module and
an interface
PE1 EFM OAM PE2
GE0/0/1 GE0/0/1
GE0/0/2 GE0/0/2
CE1 CE2
Interface associated with EFM OAM
Interface enabled with EFM OAM
If an EFM OAM module and an interface are configured to report faults to each other on PE1
and PE2, when GE 0/0/2 connecting PE2 and CE2 becomes Down, the OAM management

module sends a fault notification message to the EFM OAM module bound to GE 0/0/2. The
fault notification message is encapsulated into an OAMPDU and sent to PE1. After receiving
the OAMPDU, the OAM management module on PE1 triggers the physical status of GE 0/0/2
to go Down. Then CE2 detects the fault. The reliability of service transmission is thus ensured.
Before configuring association between an EFM OAM module and an interface in the OAM
management view, complete the following tasks:
Data Preparation
To configure association between an EFM OAM module and an interface in the OAM
management view, you need the following data.
No. Data
1 Type and number of the interface associated with an EFM OAM module
2 Type and number of the interface enabled with EFM OAM
4.11.2 Configuring Association Between an EFM OAM Module and

an Interface
Context
To configure association between an EFM OAM module and an interface, perform steps 3 and
4 or perform step 5.
Do as follows on the device where association between an EFM OAM module and an interface
needs to be configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
oam-mgr
The OAM management view is displayed.
Step 3 Run:
oam-bind ingress efm interface interface-type1 interface-number1 trigger if-down
egress interface interface-type2 interface-number2
An EFM OAM module is configured to report faults to an interface.

When an EFM OAM module detects a fault, the physical status of the interface bound to the
EFM OAM module becomes Down.
interface interface-type1 interface-number1: specifies the interface enabled with EFM OAM.
interface interface-type2 interface-number2: specifies the interface bound to an EFM OAM

module.
Step 4 Run:
oam-bind ingress interface interface-type1 interface-number1 egress efm interface
interface-type2 interface-number2 trigger if-down
An interface is configured to report faults to an EFM OAM module.
When an interface bound to an EFM OAM module becomes Down, the OAM management
module sends a fault notification message to the bound EFM OAM module. Then the fault
notification message is encapsulated into an OAMPDU and sent to the remote device.

module.
Step 5 Run:
oam-bind efm interface interface-type1 interface-number1 trigger if-down interface
interface-type2 interface-number2
An EFM OAM module and an interface are configured to report faults to each other.

module.
NOTE
If you perform step 5, two records of the oam-bind ingress efm interface interface-type1 interface-
number1 trigger if-down egress interface interface-type2 interface-number2 and oam-bind ingress
interface interface-type1 interface-number1 egress efm interface interface-type2 interface-number2
trigger if-down commands are displayed. In the records, the directions where fault notification messages
are transmitted are reverse.
----End
Prerequisite
The configurations of association between an EFM OAM module and an interface are complete.
Procedure
Step 1 Run the display this command in the OAM management view to check whether association
between an EFM OAM module and an interface is configured successfully.
----End

Example
Run the display this command, and you can view association between an EFM OAM module
and an interface.
[Quidway-oam-mgr] display this
#
oam-mgr
oam-bind ingress interface GigabitEthernet0/0/1 egress efm interface
GigabitEthernet0/0/2 trigger if-down
oam-bind ingress efm interface GigabitEthernet0/0/2 trigger if-down egress
#
return
4.12 Configuring Association Between EFM OAM Modules

The association between EFM OAM modules is applicable to the scenario where EFM OAM is
configured on both ends of a device. When an EFM OAM module on one side detects a link
fault, the EFM OAM module on the local device sends a fault notification message to the OAM
management module. The OAM management module finds the outbound interface and sends
the fault notification message to the EFM OAM module on the other side. The fault notification
message is encapsulated in an OAMPDU, and then transmitted to the remote device.

4.12.2 Configuring Association Between EFM OAM Modules
EFM OAM is used to detect faults on a link between directly connected devices. As shown in
Figure 4-5, EFM OAM is configured between Switch1 and Switch2, and between Switch2 and
Switch3. When the link between Switch2 and Switch3 is faulty, Switch1 needs to detect faults
to ensure the reliability of service transmission. In this case, you can configure association
between EFM OAM modules. When EFM OAM between Switch2 and Switch3 detects faults
on the link, the EFM OAM modules on Switch2 send a fault notification message to the OAM
management module. The OAM management module finds the outbound interface GE 0/0/3
and sends the fault notification message to the EFM OAM module on the other side. The EFM
OAM module encapsulates the fault notification message in an OAMPDU and sends it to
Switch1. In this manner, the reliability of service transmission is improved.
Figure 4-5 Networking diagram for configuring association between EFM OAM modules
EFM OAM EFM OAM
GE0/0/3 GE0/0/1 GE0/0/1

Switch1 Switch2 Switch3

Before configuring association between EFM OAM modules, complete the following task:
Data Preparation
To configure association between EFM OAM modules, you need the following data.
No. Data
1 Number of the interface where association between EFM OAM modules is

configured
4.12.2 Configuring Association Between EFM OAM Modules
Context
In the procedure for configuring association between EFM OAM modules, steps 3 and 4 are
optional, and can be selected as required.
Do as follows on the device where association between EFM OAM modules needs to be
configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:
oam-mgr

Step 3 Run:
oam-bind ingress efm interface interface-type interface-number egress efm
An EFM OAM module is configured to report faults to another EFM OAM module.
Step 4 Run:
oam-bind efm interface interface-type interface-number efm interface interface-
type interface-number
EFM OAM modules are configured to report faults to each other.
NOTE
If you perform step 4, two records of the oam-bind ingress efm interface interface-type interface-
number egress efm interface interface-type interface-number command are displayed. In the records, the
directions where fault notification messages are transmitted are reverse.
----End

Prerequisite
The configurations of association between EFM OAM modules are complete.
Procedure
l Run the display this command in the OAM management view to check whether association
between EFM OAM modules is configured.
#
oam-mgr
oam-bind ingress efm interface GigabitEthernet0/0/1 egress efm interface
GigabitEthernet0/0/2
#
return
----End
4.13 Associating Ethernet CFM with an Interface

This section describes how to associate Ethernet CFM with an interface.

4.13.2 Configuring Association Between an Ethernet CFM Module and an Interface
After association between an Ethernet CFM module and an interface is configured, if a MEP
detects a connectivity fault between the MEP and a specified RMEP in the same MA, the OAM
management module blocks and then unblocks the interface where the MEP is located so that
other modules can detect the fault.
Figure 4-6 Application scenario of association between an Ethernet CFM module and an
interface (1)
Ethernet CFM
GE0/0/1 GE0/0/1
SwitchA SwitchB
The interface associated with Ethernet CFM

interface (2)
Ethernet CFM
GE0/0/1 GE0/0/1 GE0/0/2 GE0/0/1

SwitchA SwitchC SwitchB
The interface associated with Ethernet CFM
Figure 4-6 and Figure 4-7 show the application of CFM on a direct link and a multi-hop link
respectively. Ethernet CFM is configured between SwitchA and SwitchB, and the Ethernet CFM
module is associated with GE 0/0/1 of SwitchA. When the CFM OAM module on SwitchA
detects a connectivity fault between SwitchA and SwitchB, the OAM management module
blocks and then unblocks GE 0/0/1 so that the other interfaces on SwitchA can detect the fault.
interface (3)
Ethernet CFM
GE0/0/1 Link1 GE0/0/1
GE0/0/2 Link2 GE0/0/2
SwitchA SwitchB
Link3
GE0/0/3 GE0/0/3
Active link
Inactive link MEPs in MA1
MEPs in MA2
Aggregation group in MEPs in MA3
static LACP mode
A link aggregation group (LAG) in static LACP mode is configured on SwitchA and SwitchB.
Ethernet CFM is enabled on SwitchA and SwitchB; SwitchA and SwitchB belong to the same
MD; MEPs are configured on all the member interfaces of the LAG; MEPs on the interfaces of
the same link belong to the same MA; MEPs on interfaces on different links belong to different
MAs. MEPs at both ends of a link sends CCMs to check connectivity of the link. The association
between an Ethernet CFM module and an interface is configured.
When a connectivity fault occurs on Link1, the OAM modules on SwitchA and SwitchB block
and unblock their GE 0/0/1 interfaces respectively. In this manner, the LACP module detects
the connectivity fault on Link1 and switches the service data from Link1 to the inactive Link3.
This implements protection switching within 50 ms to achieve carrier-class reliability.

interface (4)
SwitchC
GE0/0/1 GE0/0/2
M Ethe
rn et C F rn et C
GE0/0/1 Ethe FM GE0/0/1
Eth-Trunk1 Eth-Trunk1
SwitchA SwitchB
GE0/0/2 Ethe FM GE0/0/2
rnet C
CFM rnet
Ethe
GE0/0/1 GE0/0/2
SwitchD
Aggregation group in 1:1 Active link MEPs in MA1
active/standby mode Inactive link MEPs in MA2
MEPs in MA3
MEPs in MA4
An LAG in 1:1 backup mode is configured on SwitchA and SwitchB. Ethernet CFM is
configured between SwitchA and SwitchC, SwitchA and SwitchD, SwitchB and SwitchC, and
SwitchB and SwitchD. The Ethernet CFM modules are associated with GE 0/0/1 and GE
0/0/2 respectively on SwitchA and SwitchB.
When a connectivity fault occurs on the link between SwitchA and SwitchC, the Ethernet CFM
module detects the fault and reports the fault to the OAM management module. The OAM
management module blocks and then unlocks GE 0/0/1. Then the LAG detects the fault and
switches data to the inactive link. The process of handling faults on other links is similar to that
on the link between SwitchA and SwitchC. This implements protection switching within 50 ms
to achieve carrier-class reliability.
Before configuring association between an Ethernet CFM module and an interface, complete
the following tasks:
l Configuring an LAG
l 4.6 Configuring Basic Functions of Ethernet CFM
Data Preparation
To configure association between an Ethernet CFM module and an interface, you need the
following data.
No. Data
1 Type and number of an interface
2 Names of the MD and MA and ID of the RMEP

4.13.2 Configuring Association Between an Ethernet CFM Module

and an Interface
Procedure
l Configuring association between an Ethernet CFM module and an interface in the interface
view
1. Run:
system-view

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

3. Run:
cfm md md-name ma ma-name remote-mep mep-id mep-id trigger if-down
Ethernet CFM is associated with the interface.
By default, an interface is not associated with Ethernet CFM.
Before running the cfm md md-name ma ma-name remote-mep mep-id mep-id

trigger if-down command to associate Ethernet CFM with an interface, make sure
that the specified MA is configured with an outward MEP and that the MEP is
configured on the interface to be associated.
An interface can be configured with only one RMEP. To change the association of an
interface with an MA and an RMEP, you need to delete the current association and
configure an association again.
If multiple member interfaces exist in an LAG, repeat step 2 and step 3 to associate
an Ethernet CFM module with all the member interfaces.
4. Run:
cfm md md-name ma ma-name trigger clear-arp vlan vlan-id
The function of clearing an ARP entry on a physical interface is configured.
When the CFM module detects a fault, it notifies the OAM management module of
the fault. The OAM management module searches the CFM fault relationship table
according to the interface and VLAN ID, and then clears the ARM entry that
corresponds to the VLANIF interface.
----End
Prerequisite
The configuration of association between Ethernet CFM and an interface is complete.

Procedure
Step 1 Run the display cfm remote-mep md md-name ma ma-name mep-id mep-id command to check
detailed information about an RMEP.
----End
Example
Run the display cfm remote-mep command. If the Trigger If-down field for the RMEP is
displayed as enable, it indicates that the configuration is successful.
<Quidway> display cfm remote-mep
The total number of RMEPs is 2
--------------------------------------------------
MD Name : md1
Level : 4
MA Name : ma1
RMEP ID : 50
Vlan ID : 10
VSI Name : --
MAC : 0000-0121-0222
Trigger-If-Down : enabled
CFM Status : up
MD Name : md2
Level : 7
MA Name : ma1
RMEP ID : 30
Vlan ID : --
VSI Name : --
MAC : --
Trigger-If-Down : enabled
CFM Status : up
4.14 Configuring Association Between an Ethernet CFM

If association between an Ethernet CFM module and an interface is configured on a device, when
Ethernet CFM detects a fault, the Ethernet CFM module on the local device sends a fault
interface bound to the Ethernet CFM module to go Down. When the physical status of the
interface becomes Down, the OAM management module sends a fault notification message to
the Ethernet CFM module. Then the Ethernet CFM module encapsulates the fault notification
message to an OAMPDU and sends it to the remote device.

4.14.2 Configuring Association Between an Ethernet CFM Module and an Interface

As shown in Figure 4-10, PE1 and PE2 are enabled with Ethernet CFM. When the link between
PE1 and PE2 is faulty, CEs need to detect faults to ensure the reliability of service transmission.
In this case, you can configure association between an Ethernet CFM module and an interface
on PE1 and PE2. Take PE2 as an example. When Ethernet CFM detects a link fault, the Ethernet
CFM module on PE2 sends a fault notification message to the OAM management module and
triggers the physical status of GE 0/0/2 bound to the Ethernet CFM module to go Down. Then
CE2 detects the link fault. The reliability of service transmission is thus ensured.
Figure 4-10 Networking for configuring association between an Ethernet CFM module and an
interface
PE1 Ethernet CFM PE2
GE0/0/1 GE0/0/1
GE0/0/2 GE0/0/2
CE1 CE2
Interface associated with Ethernet CFM
Interface enabled with Ethernet CFM
If an Ethernet CFM module and an interface are configured to report faults to each other on PE1
and PE2, when GE 0/0/2 connecting PE2 and CE2 becomes Down, the OAM management
module sends a fault notification message to the Ethernet CFM module bound to GE 0/0/2. The
fault notification message is encapsulated into a CFM protocol packet and sent to PE1. After
receiving the CFM protocol packet, the OAM management module on PE1 triggers the physical
status of GE 0/0/2 to go Down. Then CE2 detects the fault. The reliability of service transmission
is thus ensured.
Before configuring association between an Ethernet CFM module and an interface in the OAM
management view, complete the following task:
Data Preparation
To configure association between an Ethernet CFM module and an interface in the OAM
management view, you need the following data.
No. Data
1 Type and number of the interface associated with an Ethernet CFM module

No. Data
2 Type and number of the interface enabled with Ethernet CFM
4.14.2 Configuring Association Between an Ethernet CFM Module

and an Interface
Context
To configure association between an Ethernet CFM module and an interface, perform steps 3
and 4 or perform step 5.
Do as follows on the device where association between an Ethernet CFM module and an interface
needs to be configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
oam-mgr
Step 3 Run:
oam-bind ingress cfm md md-name ma ma-name trigger if-down egress interface
interface-type interface-number
An Ethernet CFM module is configured to report faults to an interface.
When an Ethernet CFM module detects a fault, the physical status of the interface bound to the
Ethernet CFM module is triggered to go Down.
Step 4 Run:
oam-bind ingress interface interface-type interface-number egress cfm md md-name
ma ma-name trigger if-down
An interface is configured to report faults to an Ethernet CFM module.
When an interface bound to an Ethernet CFM module becomes Down, the OAM management
module sends a fault notification message to the bound Ethernet CFM module. Then the fault
notification message is encapsulated into a CFM protocol packet and sent to the remote device.
Step 5 Run:
oam-bind cfm md md-name ma ma-name trigger if-down interface interface-type
interface-number
An Ethernet CFM module and an interface are configured to report faults to each other.

NOTE
If you perform step 5, two records of the oam-bind ingress cfm md md-name ma ma-name trigger if-
down egress interface interface-type interface-number and oam-bind ingress interface interface-type
interface-number egress cfm md md-name ma ma-name trigger if-down commands are displayed. In the
records, the directions where fault notification messages are transmitted are reverse.
----End
Prerequisite
The configurations of association between an Ethernet CFM module and an interface are
complete.
Procedure
Step 1 Run the display this command in the OAM management view to check whether association
between an Ethernet CFM module and an interface is configured successfully.
----End
Example
Run the display this command, and you can view association between an Ethernet CFM module
and an interface.
#
oam-mgr
oam-bind ingress interface GigabitEthernet0/0/1 egress cfm md md1 ma ma1 trigger
if-down
oam-bind ingress cfm md md1 ma ma1 trigger if-down egress interface
#
return
4.15 Associating EFM OAM with Ethernet CFM

This section describes how to associate EFM OAM with Ethernet CFM.

4.15.2 Associating EFM OAM with Ethernet CFM

IEEE 802.1ah is designed for the last mile of the Ethernet to detect the direct link between a CE
device and a PE device. IEEE 802.1ag is designed for a group of services or certain network
devices to detect faults on the network. It functions between CE devices, PE devices, or CE and

PE devices. As shown in Figure 4-11, EFM OAM runs between CE1 and PE1, and between
CE2 and PE2; Ethernet CFM runs between CE1 and CE2. After Ethernet OAM is associated
with Ethernet CFM, the Ethernet CFM module can detect faults on the link between CE1 and
PE2 and notify CE2.
Figure 4-11 Association between EFM OAM and Ethernet CFM
GE0/0/1 GE0/0/1
GE0/0/2 GE0/0/2
EFM OAM EFM OAM
CE1 CE2
Before associating EFM OAM and Ethernet CFM, complete the following tasks:

Data Preparation
To associate EFM OAM and Ethernet CFM, you need the following data.
No. Data
1 Interface to be associated
2 Name of the MD and MA
4.15.2 Associating EFM OAM with Ethernet CFM
Context
Do as follows on the CE devices.
Procedure
Step 1 Run:
system-view

Step 2 Run:
oam-mgr
Step 3 Run the following command as required.

l Run:
oam-bind cfm md md-name ma ma-name efm interface interface-type interface-number
The EFM OAM and Ethernet CFM modules are configured to send fault messages to each
other.
l Run:
oam-bind ingress efm interface interface-type interface-number egress cfm md md-
name ma ma-name
The EFM OAM module is configured to send fault messages to the Ethernet CFM module.
l Run:
oam-bind ingress cfm md md-name ma ma-name egress efm interface interface-type
interface-number
The Ethernet CFM module is configured to send fault messages the EFM OAM module.
NOTE
After Ethernet OAM is associated with other functional modules,

l If EFM OAM is disabled on an interface, the association between EFM OAM and other functional
modules is deleted.
l If an MA or MD is deleted, the association between Ethernet CFM and other functional modules is
deleted.
NOTE
If you run oam-bind cfm md md-name ma ma-name efm interface interface-type interface-number
command, two records of the oam-bind ingress efm interface interface-type interface-number egress
cfm md md-name ma ma-name and oam-bind ingress cfm md md-name ma ma-name egress efm
interface interface-type interface-number commands are displayed. In the records, the directions where
fault notification messages are transmitted are reverse.
----End
Prerequisite
The Configuration of association between EFM OAM and Ethernet CFM are complete.
Procedure
Step 1 In the OAM management view, run the display this command to check association between
EFM OAM and Ethernet CFM.
#
oam-mgr
oam-bind ingress efm interface GigabitEthernet0/0/1 egress cfm md md1 ma ma1
oam-bind ingress cfm md md1 ma ma1 egress efm interface GigabitEthernet0/0/1
#
----End

4.16 Configuring Association Between Ethernet CFM and

Ethernet CFM
This section describes how to configure association between Ethernet CFM and Ethernet CFM.

4.16.2 Configuring Association Between Ethernet CFM and Ethernet CFM
IEEE 802.1ag is designed for a group of services or certain network devices to detect faults on
the network. IEEE 802.1ag is used between CE devices, PE devices, or CE and PE devices. As
shown in Figure 4-12, Ethernet CFM runs between CE1 and PE1, and between CE2 and PE2;
Ethernet CFM runs between CE1 and CE2. After Ethernet CFM is associated with Ethernet
CFM, the Ethernet CFM module can detect faults on the link between CE1 and PE1 and notify
CE2.
Figure 4-12 Networking diagram for configuring association between Ethernet CFM and
Ethernet CFM
GE0/0/1 GE0/0/1
GE0/0/2 GE0/0/2
Ethernet CFM Ethernet CFM
CE1 CE2
Before configuring association between Ethernet CFM and Ethernet CFM, complete the
following task:
Data Preparation
To configure association between Ethernet CFM and Ethernet CFM, you need the following
data.

No. Data
1 Interface to be associated and number of the interface
2 Names of the MD and MA
4.16.2 Configuring Association Between Ethernet CFM and

Ethernet CFM
Context
Do as follows on the devices where association between Ethernet CFM and Ethernet CFM needs
to be configured.
Procedure
Step 1 Run:
system-view
Step 2 Run:
oam-mgr

oam-bind ingress cfm md md-name1 ma ma-name1 egress cfm md md-name2 ma ma-name2
Unidirectional fault tranmission is enabled betwen Ethernet CFM modules at the two ends of
the link.

oam-bind cfm md md-name1 ma ma-name1 cfm md md-name2 ma ma-name2
Bidirectional fault transmission is enabled betwen Ethernet CFM modules at the two ends of the
link.
Steps 3 to 4 are optional and can be selected as required.
NOTE
After bidirectional transmission of fault messages is configured, the system displays two configuration
records of unidirectional fault message transmission, whose directions are mutually reverse.
----End
Prerequisite
The configurations of association between Ethernet CFM and Ethernet CFM are complete.

Procedure
Step 1 In the OAM management view, run the display this command to check association between
Ethernet CFM and Ethernet CFM.
#
oam-mgr
oam-bind ingress cfm md md1 ma ma1 egress cfm md md1 ma ma2
#
----End
4.17 Configuring Association Between Ethernet CFM and

SEP
This section describes how to configure association between Ethernet CFM and SEP.

4.17.2 Configuring Association Between Ethernet CFM and SEP
Association between Ethernet CFM and SEP is configured on edge devices of the SEP segment.
When Ethernet CFM detects a fault on the upper-layer network, the edge device encapsulates a
fault message into a CFM protocol packet and sends it to the OAM management module. In
addition, the edge device triggers the physical status of the interface on the edge device bound
to Ethernet CFM to go Down.
When the interface on the edge device bound to Ethernet CFM becomes Down, the peer device
(on the SEP segment) of the edge device needs to send FLUSH-FDB packets to report the
topology change to other nodes on the SEP segment. After the nodes on the SEP segment receive
FLUSH-FDB packets, the blocking interface on the SEP segment needs to enter the forwarding
state and send FLUSH-FDB packets to trigger the updating of MAC address tables and ARP
tables of nodes on the SEP segment. In this manner, the lower-level network can detect faults
on the upper-level network and the reliability of service transmission is improveded.
Before configuring association between Ethernet CFM and SEP, complete the following tasks:

l Configuring Basic SEP Functions
Data Preparation
To configure association between Ethernet CFM and SEP, you need the following data.

No. Data
1 Number of the interface where association between Ethernet CFM and SEP is
configured
2 Names of MDs and MAs
3 SEP segment
4 Number of the interface added to the SEP segment
4.17.2 Configuring Association Between Ethernet CFM and SEP

Context
Do as follows on the device where association between Ethernet CFM and SEP needs to be
configured.
Procedure
Step 1 Run:
system-view

Step 2 Run:
oam-mgr

Step 3 Run:
oam-bind ingress cfm md md-name ma ma-name egress sep segment segment-id interface
interface-type interface-number
Association between Ethernet CFM and SEP is configured.

The interface specified by interface interface-type interface-number must be added to the SEP
segment.
----End

Prerequisite
The configurations of association between Ethernet CFM and SEP are complete.
Procedure
Step 1 Run the display this command in the OAM management view to check association between
Ethernet CFM and SEP.
#
oam-mgr

oam-bind ingress cfm md md1 ma ma1 egress sep segment 1 interface

#
----End
4.18 Configuring the One-way Frame Delay Measurement

in a VLAN
You can configure the one-way frame delay measurement in the VLAN bound to an MA and
estimate the quality of services based on the calculated one-way frame delay.

Before configuring the one-way frame delay measurement, familiarize yourself with the
applicable environment, complete the pre-configuration tasks, and obtain the required data. This
can help you complete the configuration task quickly and accurately.
4.18.2 Binding an MA to a VLAN
Binding an MA to a VLAN is a prerequisite for configuring the one-way frame delay
measurement in the VLAN.
4.18.3 (Optional) Setting an Alarm Threshold for the One-way Frame Delay Measurement
4.18.4 Configuring DM Frame Reception on a Remote MEP
The One-way frame delay measurement can work normally only when DM frame reception is
configured on a remote MEP.
4.18.5 Enabling the One-way Frame Delay Measurement in a VLAN
The one-way frame delay measurement in a VLAN can work normally only after you enable
the one-way frame delay measurement in the VLAN.
After the one-way frame delay measurement is configured in a VLAN, you can view the statistics
about the delay in bidirectional service traffic transmission in the VLAN.

Before configuring the one-way frame delay measurement, familiarize yourself with the
You can configure the one-way frame delay measurement to collect statistics about the delay in
bidirectional service traffic transmission.
the one-way frame delay measurement is commonly performed on point-to-point MEPs. After
a MEP receives a Delay Measurement (DM) message from the remote MEP, it calculates the
time delay experienced across the network by comparing the timestamp in the DM frame and
the local time. During the one-way frame delay measurement, ensure that clocks on MEPs are
synchronous.
NOTE
Before enabling the one-way delay measurement in the VLAN on the local device, you must configure the
DM frame reception function on the remote device.

Before configuring the one-way delay measurement in the VLAN, complete the following tasks:
l Configuring VLAN
Data Preparation
To configure the one-way delay measurement in the VLAN, you need the following data:
No. Data
2 ID of the MEP, name of the interface on which the MEP resides, and type of the MEP
3 Name of the VLAN bound to the MA
4 (Optional) Interval for sending AIS packets
5 (Optional) Alarm threshold of the one-way frame delay measurement

Binding an MA to a VLAN is a prerequisite for configuring the one-way frame delay
Context
Do as follows on the devices configured with MEPs:
Procedure
Step 1 Run:
system-view

Step 2 Run:
cfm md md-name

Step 3 Run:
ma ma-name

Step 4 Run:
map vlan vlan-id
The MA is bound to a VLAN.
----End

4.18.3 (Optional) Setting an Alarm Threshold for the One-way

Frame Delay Measurement
Context
Do as follows on the devices configured with MEPs:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
delay-measure one-way threshold threshold-value
An alarm threshold is set for the two-way frame delay measurement.
----End
4.18.4 Configuring DM Frame Reception on a Remote MEP

The One-way frame delay measurement can work normally only when DM frame reception is
Context
Do as follows on a remote MEP:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name

Step 4 Run:
delay-measure one-way receive
DM frame reception is configured on the remote MEP.
----End
4.18.5 Enabling the One-way Frame Delay Measurement in a VLAN

The one-way frame delay measurement in a VLAN can work normally only after you enable
the one-way frame delay measurement in the VLAN.
Context
To implement the one-way frame delay measurement, you need to specify the remote MEP ID
or the destination MAC address, the interval for sending DM frames, and the number of DM
frames sent each time.
To implement one-way frame delay measurement, you need to specify the RMEP ID or the
destination MAC address, the interval for sending DM frames, and the measurement period.
l If the local MEP has not learnt the MAC address of the RMEP, you must specify the
destination MAC address for one-way frame delay measurement.
l If the local MEP has learnt the MAC address of the RMEP, you can specify the RMEP ID
for one-way frame delay measurement.
One-way frame delay measurement is implemented between the transmitting and receiving
MEPs by exchanging DM frames. After one-way frame delay measurement is configured, a
MEP periodically sends DM frames with the TxTimeStampf (the timestamp at the transmission
time of the DM frame). After receiving a DM frame, the RMEP parses the value of the
TxTimeStampf and compares this value with the RxTimef (the time at the reception of the DM
frame) and then calculates the one-way frame delay as:
Frame delay = RxTimef - TxTimeStampf
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
delay-measure one-way { mac mac-address | remote-mep mep-id mep-id } interval
interval-value count count-value

The two-way frame delay measurement is configured.
----End

After the one-way frame delay measurement is configured in a VLAN, you can view the statistics
Prerequisite
All the configurations of the one-way frame delay measurement in a VLAN are complete.
Procedure
l Run the display y1731 statistic-type oneway-delay md md-name ma ma-name command
to check the performance statistics collected through Y.1731.
----End
Example
After the configurations, run the display y1731 statistic-type command on the devices where
MEPs reside, and you can view the value of the average delay.
<Quidway> display y1731 statistic-type oneway-delay md md1 ma ma1
1DM received Delay 30555 usec Delay variation: 0 usec
1DM received Delay 30586 usec Delay variation: 3sec
--- Delay measurement statistics ---
Packets transmitted:10, valid packets received: 10
Average delay: 30607, Average delay variation: 27 usec
Best case delay 30555 usec, worst case delay: 30678 usec
4.19 Configuring the Two-way Frame Delay Measurement

in a VLAN
You can configure the two-way frame delay measurement in the VLAN bound to an MA and
estimate the quality of services based on the calculated two-way frame delay.

Before configuring the two-way frame delay measurement, familiarize yourself with the
Binding an MA to a VLAN is a prerequisite for configuring the two-way frame delay
4.19.3 (Optional) Setting an Alarm Threshold for the Two-way Frame Delay Measurement

You can set an alarm threshold for the two-way frame delay measurement in each MA. When
the two-way delay exceeds the alarm threshold, an alarm is generated.
4.19.4 Configuring DMM Frame Reception on a Remote MEP
The two-way frame delay measurement can work normally only when DM frame reception is
4.19.5 Enabling the Two-way Frame Delay Measurement in a VLAN
The two-way frame delay measurement in a VLAN can work normally only after you enable
the two-way frame delay measurement in the VLAN.
After the two-way frame delay measurement is configured in a VLAN, you can view the statistics

Before configuring the two-way frame delay measurement, familiarize yourself with the
You can configure the two-way frame delay measurement to collect statistics about the delay in
bidirectional service traffic transmission.
The two-way frame delay measurement is commonly performed on end-to-end MEPs. After a
remote MEP receives a DM frame from a local MEP, the remote MEP adds the RxTimeStampf
value (timestamp at the time of receiving the DM frame) to the DM frame, generates a DMR
frame with the TxTimeStampb value, and sends the message to the local MEP. Every field in
the DM frame is copied to the DMR frame except that the source and destination MAC addresses
are swapped and the message type is changed from DM to DMR. Upon receiving the DMR
frame, the local MEP calculates the two-way frame delay based on the timestamps.
NOTE
Before enabling the two-way delay measurement in the VLAN on the local device, you must configure the
DM frame reception function on the remote device.
Before configuring the two-way delay measurement in the VLAN, complete the following tasks:
l Configuring VLAN
Data Preparation
To configure the two-way delay measurement in the VLAN, you need the following data:
No. Data
2 ID of the MEP, name of the interface on which the MEP resides, and type of the MEP

No. Data
3 Name of the VLAN bound to the MA
4 (Optional) Interval for sending AIS packets
5 (Optional) Alarm threshold of the two-way frame delay measurement

Binding an MA to a VLAN is a prerequisite for configuring the two-way frame delay
Context
Do as follows on the devices configured with MEPs on two ends of the link:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
map vlan vlan-id
The MA is bound to a VLAN.
----End
4.19.3 (Optional) Setting an Alarm Threshold for the Two-way

Frame Delay Measurement
You can set an alarm threshold for the two-way frame delay measurement in each MA. When
the two-way delay exceeds the alarm threshold, an alarm is generated.
Context

Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
delay-measure two-way threshold threshold-value
An alarm threshold is set for the two-way frame delay measurement.
----End
4.19.4 Configuring DMM Frame Reception on a Remote MEP

The two-way frame delay measurement can work normally only when DM frame reception is
Context
Do as follows on a remote MEP:
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
delay-measure two-way receive
DMM frame reception is configured on the remote MEP.
----End

4.19.5 Enabling the Two-way Frame Delay Measurement in a VLAN

The two-way frame delay measurement in a VLAN can work normally only after you enable
the two-way frame delay measurement in the VLAN.
Context
To implement the two-way frame delay measurement, you need to specify the remote MEP ID
or the destination MAC address, the interval for sending DM frames, and the number of DM
frames sent each time.
l If the local MEP has not learnt the MAC address of the remote MEP, you must specify the
destination MAC address for the two-way frame delay measurement.
l If the local MEP has learnt the MAC address of the remote MEP, you can specify the remote
MEP ID for the two-way frame delay measurement.
The two-way frame delay measurement is performed on end-to-end MEPs. A MEP receives a
DM frame and returns a DMR frame to carry out the two-way frame delay measurement. After
the two-way frame delay measurement is configured, a MEP periodically sends DM frames with
the TxTimeStampf value (timestamp at the time of sending the DM frame). After receiving the
DM frame, the remote MEP adds the RxTimeStampf value (timestamp at the time of receiving
the DM frame) to the DM frame, generates a DMR frame with the TxTimeStampb value
(timestamp at the time of sending the DMR frame), and sends the message to the requesting
MEP. Every field in the DM frame is copied to the DMR frame except that the source and
destination MAC addresses are swapped and the message type is changed from DM to DMR.
Upon receiving the DMR frame, the requesting MEP calculates the two-way frame delay based
on the following formula:
Two-way frame delay = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)
Procedure
Step 1 Run:
system-view
Step 2 Run:
cfm md md-name
Step 3 Run:
ma ma-name
Step 4 Run:
delay-measure two-way { mac mac-address | remote-mep mep-id mep-id } interval
interval-value count count-value
The two-way frame delay measurement is configured.
----End


After the two-way frame delay measurement is configured in a VLAN, you can view the statistics
Prerequisite
All the configurations of the two-way frame delay measurement in a VLAN are complete.
Procedure
l Run the display y1731 statistic-type twoway-delay md md-name ma ma-name command
to check the performance statistics collected through Y.1731.
----End
Example
After the configurations, run the display y1731 statistic-type command on the devices where
MEPs reside, and you can view the value of the average delay.
<Quidway> display y1731 statistic-type twoway-delay md md2 ma ma2
DMR received Delay 0018-82d1-b6bf Delay 2692 usec Variation: 0 usec
4.20 Maintaining Ethernet OAM

This section describes how to debug EFM OAM and monitor the operation of Ethernet OAM.
4.20.1 Debugging EFM OAM
4.20.1 Debugging EFM OAM

Context
CAUTION
all command to disable it immediately.
When an EFM OAM fault occurs, run the following debugging command in the user view to
view the debugging information and locate the fault.

For the procedure for enabling debugging, see Debugging and Diagnosis in the Configuration
Guide - Device Management.
Procedure
l Run the debugging efm interface interface-type interface-number { all | error | event |
message | packet { all | receive | send } | process } command in the user view to enable
the debugging of the EFM OAM management module on the specified interface.
l Run the debugging eoam-1ag { all | event | error | msg | packet-type ccm-packet md
md-name [ ma ma-name [ remote-mep mep-id mep-id ]] [ -c connt ] } command in the
user view to enable the MD debugging.
----End

This section provides several configuration examples of Ethernet OAM.
4.21.1 Example for Configuring EFM OAM

4.21.2 Example for Testing the Packet Loss Ratio on a Link
4.21.3 Example for Configuring Basic Functions of Ethernet CFM
4.21.4 Example for Configuring the Default MD for Ethernet CFM
In this example, you can configure the default MD on a device in a low-level MD. A high-level
MD can detect topology changes in a low-level MD.
4.21.5 Example for Configuring Association Between an EFM OAM Module and an Interface
OAM module. Then the EFM OAM module sends the fault notification message to the remote
device.
4.21.6 Example for Configuring Association Between EFM OAM Modules
4.21.7 Example for Configuring Association Between an Ethernet CFM Module and an Interface
4.21.8 Example for Configuring Association Between an EFM OAM Module and an Ethernet
CFM Module
4.21.9 Example for Configuring Association Between Ethernet CFM with Ethernet CFM
4.21.10 Example for Associating Ethernet CFM with Smart Link
4.21.11 Example for Associating Ethernet CFM with RRPP
4.21.12 Example for Associating SEP with Ethernet CFM
SEP runs at the access layer to implement link redundancy and topology display. Association
between Ethernet CFM and SEP can be configured on edge devices of the SEP segment. When
Ethernet CFM detects a fault at the aggregation layer, the related edge device encapsulates a
fault message into a CFM protocol packet and sends it to the OAM management module to
switch the physical status of the interface bound to Ethernet CFM to Down.

4.21.13 Example for Configuring the One-way Frame Delay Measurement in a VLAN
When you need to estimate service qualities, you can configure the one-way frame delay
measurement on point-to-point MEPs to obtain the performance of the network.
4.21.14 Example for Configuring the Two-way Frame Delay Measurement in a VLAN
When you need to estimate service qualities, you can configure the two-way frame delay
4.21.1 Example for Configuring EFM OAM

As shown in Figure 4-13, a user network is connected to an ISP network through Switch A and
Switch B. Switch A functions as the CE device, and Switch B functions as the underlayer PE
(UPE) device. The networking requirements are as follows:
l Automatic connectivity detection can be performed between Switch A and Switch B. After
detecting connectivity faults, Switch A and Switch B generate alarms.
l Switch B monitors the errored frames, errored codes, and errored frame seconds on GE
0/0/1. When the number of errored frames, errored codes, or errored frame seconds exceeds
the threshold, Switch B generates an alarm.
Figure 4-13 Networking diagram for configuring EFM OAM
SwitchA SwitchB
User ISP
network network
GE0/0/1 GE0/0/1
1. Enable EFM OAM globally on Switch A and Switch B.
2. Configure EFM OAM on n GE 0/0/1 of Switch A to work in passive mode.
3. Enable EFM OAM on n GE 0/0/1 on Switch B. Enable EFM OAM on n GE 0/0/1 on Switch
A.
4. Configure n GE 0/0/1 of Switch B to detect the errored frames, errored codes, and errored
frame seconds.
Data Preparation

l Period for detecting errored frames on n GE 0/0/1 of Switch B (5 seconds) and threshold
of number of errored frames (5)
l Period for detecting errored codes on n GE 0/0/1 of Switch B (5 seconds) and threshold of
number of errored codes (5)
l Period for detecting errored frame seconds on n GE 0/0/1 of Switch B (120 seconds) and
threshold of number of errored frame seconds (5)
Procedure
Step 1 Enable EFM OAM globally.
# Enable EFM OAM globally on Switch A.

[SwitchA] efm enable
# Enable EFM OAM globally on Switch B.

[SwitchB] efm enable
Step 2 Configure EFM OAM on n GE 0/0/1 of Switch A to work in passive mode.

[SwitchA-GigabitEthernet0/0/1] efm mode passive
Step 3 Enable EFM OAM on n GE 0/0/1 of Switch B and GE 1/0/1 of Switch A.
# Enable EFM OAM on n GE 0/0/1 of Switch A.

[SwitchA-GigabitEthernet0/0/1] efm enable
# Enable EFM OAM of n GE 0/0/1 on Switch B.

[SwitchB-GigabitEthernet0/0/1] efm enable
Step 4 Configure n GE 0/0/1 of Switch B to detect the errored frames, errored codes, and errored frame
seconds.
# Configure n GE 0/0/11 of Switch B to detect the errored frames.

[SwitchB-GigabitEthernet0/0/1] efm error-frame period 5
[SwitchB-GigabitEthernet0/0/1] efm error-frame threshold 5
[SwitchB-GigabitEthernet0/0/1] efm error-frame notification enable
# Configure n GE 0/0/1 of Switch B to detect the errored codes.

[SwitchB-GigabitEthernet0/0/1] efm error-code period 5
[SwitchB-GigabitEthernet0/0/1] efm error-code threshold 5
[SwitchB-GigabitEthernet0/0/1] efm error-code notification enable
# Configure n GE 0/0/1 of Switch B to detect the errored frames seconds.

[SwitchB-GigabitEthernet0/0/1] efm error-frame-second period 120
[SwitchB-GigabitEthernet0/0/1] efm error-frame-second threshold 5
[SwitchB-GigabitEthernet0/0/1] efm error-frame-second notification enable

# If EFM OAM is configured correctly on Switch A and Switch B, n GE 0/0/1 and n GE 0/0/1
start the handshake after negotiation. Run the display efm session command on Switch A or
Switch B, and you can find that the EFM OAM protocol is in detect state.
[SwitchB] display efm session interface gigabitethernet 0/0/1
--------------------------------------------------------------------
# Run the display efm command on Switch B. If the function of detecting errored frames, errored
codes, and errored frame seconds on GE 2/0/1 is configured corrected, the following information
is displayed:
[SwitchB] display efm interface gigabitethernet 0/0/1
Item Value
-------------------------------------
Mode: active
OAMPDU MaxSize: 128
ErrCodePeriod: 5
ErrCodeThreshold: 5
ErrFramePeriod: 5
Hold Up Time: 0
Remote MAC: 0010-0010-0010
Remote MaxSize: 128
Remote State: --
----End
Configuration Files
#
sysname SwitchA
#
efm enable
#
efm mode passive
efm enable
#
return

#
sysname SwitchB
#
efm enable
#
efm enable
efm error-frame period 5
efm error-frame threshold 5
efm error-frame notification enable
efm error-frame-second period 120

efm error-frame-second threshold 5

efm error-frame-second notification enable
efm error-code period 5
efm error-code threshold 5
efm error-code notification enable
#
return
4.21.2 Example for Testing the Packet Loss Ratio on a Link
As shown in Figure 4-14, a user network is connected to an ISP network through Switch A and
Switch B. Switch A functions as the CE device, and Switch B functions as the UPE device. The
link between Switch A and Switch B is newly established. The ISP needs to test the packet loss
ratio on the link on Switch B before using the link.
Figure 4-14 Networking diagram for testing the packet loss ratio on the link
SwitchA SwitchB
User ISP
network network
GE0/0/1 GE0/0/1
1. Enable EFM OAM on Switch A and Switch B. Configure EFM OAM on GE 0/0/1 of Switch
A to work in passive mode.
2. Enable EFM OAM remote loopback on Switch B.
3. Send test packets from Switch B to Switch A.
4. Check the returned test packets on Switch B.
Data Preparation
l Timeout interval for EFM OAM remote loopback

l Size, number, and sending rate of test packets

Procedure
Step 1 Configure basic functions of EFM OAM.
# Enable EFM OAM globally on Switch B.
# Enable EFM OAM globally on Switch A.

# Configure EFM OAM on GE 0/0/1 of Switch A to work in passive mode.

# Enable EFM OAM on GE 0/0/1 of Switch A.

# Enable EFM OAM on GE GE 0/0/1 of Switch B.

# Verify the configuration.

# If EFM OAM is configured correctly on Switch A and Switch B, GE 0/0/1 and GE 0/0/1 start
the handshake after negotiation. Run the display efm session command on Switch A or Switch
B, and you can find that the EFM OAM protocol is in detect state.
--------------------------------------------------------------------
Step 2 Enable EFM OAM remote loopback.

# Enable EFM OAM remote loopback on Switch B.
[SwitchB-GigabitEthernet0/0/1] efm loopback start

Run the display efm session command on Switch B. If the EFM OAM protocol on GE 0/0/1 is
in Loopback (control) state, that is, GE 0/0/1 initiates remote loopback, it indicates that the
configuration is successful. The displayed information is as follows:
----------------------------------------------------------------------
GigabitEthernet0/0/1 Loopback(control) 20
Run the display efm session command on Switch A. If the EFM OAM protocol on GE 0/0/1 is
in Loopback (be controlled) state, that is, GE 0/0/1 responds to remote loopback, it indicates
that the configuration is successful. The displayed information is as follows:
[SwitchA] display efm session interface gigabitethernet 0/0/1

----------------------------------------------------------------------
GigabitEthernet0/0/1 Loopback(be controlled) --
Step 3 Send test packets from Switch B to Switch A.

[SwitchB] test-packet start interface gigabitethernet 0/0/1
Test Packet is sending ,press CTRL_C to break |
Info: The test is complete.
Step 4 Check the returned test packets on Switch B.

[SwitchB] display test-packet result
Test Result Value
------------------------------------------
PacketsSend : 5
PacketsReceive : 5
PacketsLost : 0
BytesSend : 128
BytesReceive : 128
BytesLost : 0
StartTime : 2009-02-21 18:07:01 UTC+03:00
EndTime : 2009-02-21 18:07:02 UTC+03:00
You can obtain the packet loss ratio on the link based on the preceding data.
Step 5 Disable EFM OAM remote loopback.
[SwitchB-GigabitEthernet0/0/1] efm loopback stop
NOTE
By default, the timeout interval for remote loopback is 20 minutes. After 20 minutes, remote loopback
stops. To disable remote loopback, you can perform the preceding step.

Run the display efm session command on Switch A or Switch B. If the EFM OAM protocol on
the interfaces is in Detect or Discovery state, it indicates that the configuration is successful.
The displayed information on Switch B is as follows:
----------------------------------------------------------------------
GigabitEthernet0/0/1 Detect --
----End
Configuration Files
#
sysname SwitchA
#
efm enable
#
efm mode passive
efm enable
#
return

#
sysname SwitchB
#
efm enable
#

efm enable
#
return
4.21.3 Example for Configuring Basic Functions of Ethernet CFM
As shown in Figure 4-15, the Ethernet is managed by two ISPs. Switch A, Switch B, and Switch
D are managed by ISP 1; Switch C, Switch E, Switch F, Switch G, Switch H, and Switch I are
managed by ISP 2. Connectivity of links needs to be tested on the network.
Figure 4-15 Networking diagram for configuring basic functions of Ethernet CFM
VLAN2
GE0/0/1
SwitchA SwitchE
SwitchI GE0/0/3
GE0/0/3 GE0/0/1
SwitchB
VLAN2 GE0/0/2 MD2 SwitchF
GE0/0/1 GE0/0/1
GE0/0/3 GE0/0/2
SwitchD
GE0/0/3 SwitchC
MD1 SwitchG
SwitchH
GE0/0/2 GE0/0/1 GE0/0/3
VLAN2 VLAN3 VLAN3
MD1 MD2
MEP in MA1 MEP in MA3
MEP in MA2
1. Create VLANs and add interfaces to the VLANs.

2. Create MD 1 at level 6 on all the Switchs.

3. Create MA 1 in MD 1 on all the Switchs except Switch G. Associate MA 1 with VLAN 2.

4. Create MA 1 in MD 1 on all the Switchs except Switch E and Switch I. Associate MA 2
with VLAN 3.
5. Create MD 2 at level 4 and create MA 3 in MD 2 on Switch A, Switch B, Switch C, and
Switch D. Associate MA 3 with VLAN 4.
6. Create MEPs and RMEPs in MA 1 of MD 1 on Switch I, Switch H, and Switch E.
7. Create MEPs and RMEPs in MA 2 of MD 1 on Switch H and Switch G.
8. Create MEPs and RMEPs in MA 3 of MD 2 on Switch A, Switch C, and Switch D.
9. Enable sending and receiving of CCMs.
Data Preparation
l Level of MD 1: 6
l Level of MD 2: 4
Procedure
Step 1 Create VLANs and add interfaces to the VLANs. The configuration procedure is not mentioned
here.
Step 2 Create MD 1.
# Create MD 1 on Switch A.
[SwitchA] cfm enable
[SwitchA] cfm md md1 level 6
# Create MD 1 on Switchs B to I.
The configurations of these Switchs are similar to the configuration of Switch A, and are not
mentioned here.
Step 3 Create MA 1 in MD 1 on all the Switchs except Switch G.
# Create MA 1 in MD 1 on Switch A.
[SwitchA-md-md1] ma ma1
[SwitchA-md-md1-ma-ma1] map vlan 2
[SwitchA-md-md1-ma-ma1] quit
# Create MA 1 in MD 1 on Switches B to I.
The configurations of these Switches are similar to the configuration of Switch A, and are not
mentioned here.
Step 4 Create MA 2 in MD 1 on all the Switches except Switch E and Switch I.
[SwitchA-md-md1] quit
# Create MA 2 in MD 1 on Switchs B to H.

The configurations of these Switchs are similar to the configuration of Switch A, and are not
mentioned here.
Step 5 Create MD 2 and create MA 3 in MD 2 on Switch A, Switch B, Switch C, and Switch D.
# Create MD 2 and create MA 3 in MD 2 on Switch A.
Create MD 2 and create MA 3 in MD 2 on Switch A, Switch B, Switch C, and Switch D.

mentioned here.
Step 6 Create MEPs and RMEPs in MA 1 of MD 1 on Switch I, Switch H, and Switch E.
# Create a MEP in MA 1 of MD 1 on Switch E.
[SwitchE] cfm md md1
[SwitchrE-md-md1] ma ma1
[SwitchE-md-md1-ma-ma1] mep mep-id 3 interface gigabitethernet 0/0/1 inward
# Create a MEP in MA 1 of MD 1 on Switch H.

[SwitchH] cfm md md1
[SwitchH-md-md1] ma ma1
[SwitchH-md-md1-ma-ma1] mep mep-id 2 interface gigabitethernet 0/0/2 inward
# Create a MEP in MA 1 of MD 1 on Switch I.

[SwitchI] cfm md md1
[SwitchI-md-md1] ma ma1
[SwitchI-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 0/0/1 inward
# Create an RMEP in MA 1 of MD 1 on Switch E.

[SwitchE-md-md1-ma-ma1] remote-mep mep-id 1
# Create an RMEP in MA 1 of MD 1 on Switch H.

[SwitchH-md-md1-ma-ma1] remote-mep mep-id 1
# Create an RMEP in MA 1 of MD 1 on Switch I.

[SwitchI-md-md1-ma-ma1] remote-mep mep-id 2
[SwitchI-md-md1-ma-ma1] remote-mep mep-id 3
Step 7 Create MEPs and RMEPs in MD 1 of MA 2 on Switch H and Switch G.

# Create a MEP in MA 2 of MD 1 on Switch H.
[SwitchH] cfm md md1
[SwitchH-md-md1] ma ma2
[SwitchH-md-md1-ma-ma2] mep mep-id 1 interface gigabitethernet 0/0/1 inward
# Create a MEP in MA 2 of MD 1 on Switch G.

[SwitchG] cfm md md1
[SwitchG-md-md1] ma ma2
[SwitchG-md-md1-ma-ma2] mep mep-id 2 interface gigabitethernet 0/0/3 inward
# Create an RMEP in MA 2 of MD 1 on Switch H.

# Create an RMEP in MA 2 of MD 1 on Switch G.

[SwitchG-md-md1-ma-ma2] remote-mep mep-id 1
Step 8 Create MEPs and RMEPs in MA 3 of MD 2 on Switch A, Switch C, and Switch D.

# Create a MEP in MA 3 of MD 2 on Switch A.
[SwitchA] cfm md md2
[SwitchA-md-md2-ma-ma3] mep mep-id 1 interface gigabitethernet 0/0/3 inward
# Create a MEP in MA 3 of MD 2 on Switch C.

[SwitchC] cfm md md2
[SwitchC-md-md2] ma ma3
[SwitchC-md-md2-ma-ma3] mep mep-id 2 interface gigabitethernet 0/0/3 outward
# Create a MEP in MA 3 of MD 2 on Switch D.

[SwitchD] cfm md md2
[SwitchD-md-md2] ma ma3
[SwitchD-md-md2-ma-ma3] mep mep-id 3 interface gigabitethernet 0/0/3 inward
# Create an RMEP in MA 3 of MD 2 on Switch A.

[SwitchA-md-md2-ma-ma3] remote-mep mep-id 2
# Create an RMEP in MA 3 of MD 2 on Switch C.

[SwitchC-md-md2-ma-ma3] remote-mep mep-id 1
# Create an RMEP in MA 3 of MD 2 on Switch D.

[SwitchD-md-md2-ma-ma3] remote-mep mep-id 1
[SwitchD-md-md2-ma-ma3] remote-mep mep-id 2
Step 9 Enable sending and receiving of CCMs.

# Enable Switch A to send CCMs of all the MEPs.
[SwitchA-md-md2-ma-ma3] mep ccm-send enable
# Enable Switch A to receive CCMs sent from all the RMEPs.

[SwitchA-md-md2-ma-ma3] remote-mep ccm-receive enable
# Enable sending and receiving of CCMs on SwitchC, SwitchD,SwitchE,SwitchG,SwitchH and

SwitchI.
mentioned here.
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 2 to 4
#

cfm enable
#
#
#
#
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 gigabitethernet0/0/3 inward
mep ccm-send mep-id 1 enable
remote-mep mep-id 2
remote-mep ccm-receive mep-id 2 enable
remote-mep mep-id 3
#
return
#
sysname SwitchB
#
vlan batch 2 to 4
#
cfm enable
#
#
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
cfm md md2 level 4
ma ma3
map vlan 4
#
return
#
sysname SwitchC
#
vlan batch 2 to 4
#
cfm enable
#


#
#
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 gigabitethernet0/0/3 outward
remote-mep mep-id 1
remote-mep mep-id 3
#
return
#
sysname SwitchD
#
vlan batch 2 to 4
#
cfm enable
#
#
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
cfm md md2 level 4
ma ma3
map vlan 4
remote-mep mep-id 1
remote-mep mep-id 2
#
return
l Configuration file of Switch E
#
sysname SwitchE
#
vlan batch 2
#
cfm enable
#
#

#
cfm md md1 level 6
ma ma1
map vlan 2
remote-mep mep-id 1
remote-mep mep-id 2
#
return
l Configuration file of Switch F

#
sysname SwitchF
#
vlan batch 2 to 3
#
cfm enable
#
#
#
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
return
l Configuration file of Switch G

#
sysname SwitchG
#
vlan batch 3
#
cfm enable
#
#
#
cfm md md1 level 6
ma ma2
map vlan 3
remote-mep mep-id 1
#
return

l Configuration file of Switch H

#
sysname SwitchH
#
vlan batch 2 to 3
#
cfm enable
#
#
#
#
cfm md md1 level 6
ma ma1
map vlan 2
remote-mep mep-id 1
remote-mep mep-id 3
ma ma2
map vlan 3
remote-mep mep-id 2
#
return
l Configuration file of Switch I

#
sysname SwitchI
#
vlan batch 2
#
cfm enable
#
#
#
cfm md md1 level 6
ma ma1
map vlan 2
remote-mep mep-id 2
remote-mep mep-id 3
#
return

4.21.4 Example for Configuring the Default MD for Ethernet CFM

In this example, you can configure the default MD on a device in a low-level MD. A high-level
MD can detect topology changes in a low-level MD.
As shown in Figure 4-16, Switch B and Switch C are managed by ISP 1, and Switch A, Switch
D, Switch E, and Switch F are managed by ISP 2. The CFM function can be enabled after the
default MD is configured on the device in a low-level MD.
Figure 4-16 Networking diagram for configuring the default MD for Ethernet CFM
VLAN3
SwitchC SwitchE GE0/0/2

SwitchB
G
E0
/1
VLAN2 /0/1 /0
/0
GE0 /2
0
GE
GE0/0/3 SwitchF
GE0/0/1
SwitchA SwitchD GE0/0/3
GE0/0/2
GE0/0/1
VLAN3 VLAN2
MEP of MA1
MEP of MA2
MIP
1. Switch IEEE 802.1ag Draft 7 to IEEE Standard 802.1ag-2007.

3. Create MD 1 at level 6 on all the devices except for Switch B and Switch C.
Create MD 2 at level 4 on Switch B and Switch C.
4. Create the default MD at level 6 on Switch B and Switch C, associate the default MD with
VLAN 2 and VLAN 3, and set the MIP creation rule to default.
5. Create and configure MA 1 in MD 1 on all the devices except for Switch E. Associate MA
1 with VLAN 2.

Create and configure MA 2 in MD 1 on all the devices except for Switch F. Associate MA
2 with VLAN 3.
6. Create and configure MEPs and RMEPs on MA 1 in MD 1 of Switch A and Switch F.
Create and configure MEPs and RMEPs on MA 2 in MD 1 of Switch A and Switch E.
7. Enable the function of sending and receiving CCMs.
Data Preparation
l IDs of VLANs to which the sub-interfaces are to be added

l Level of MD 1: 6
l Level of MD 2: 4
l Level of the default MD: 6
Procedure
Step 1 Switch IEEE 802.1ag Draft 7 to IEEE Standard 802.1ag-2007.
NOTE
By default, IEEE 802.1ag Draft 7 is enabled on a device.
# Switch IEEE 802.1ag Draft 7 to IEEE Standard 802.1ag-2007 on Switch A.

[SwitchA] cfm version standard
Warning: CFM will be disabled before the version of CFM is changed, and all info
rmation about the MD will be deleted . Continue?[Y/N]:y
Info: Succeeded in changing the version of CFM.
# Switch IEEE 802.1ag Draft 7 to IEEE Standard 802.1ag-2007 on Switch B, Switch C, Switch
D, Switch E, and Switch F.
The configurations on Switch B, Switch C, Switch D, Switch E, and Switch F are similar to the
configuration on Switch A, and are not mentioned here.
NOTE
All the devices on the entire network must be enabled with either IEEE 802.1ag Draft 7 or IEEE Standard
802.1ag-2007. IEEE 802.1ag Draft 7 and IEEE Standard 802.1ag-2007 cannot be enabled at the same time
on a network.
Step 2 Create VLANs and add interfaces to the VLANs. The configuration procedure is not mentioned
here.
Step 3 Create MD 1.
# Create MD 1 on Switch A.
# Create MD 1 on Switch D, Switch E, and Switch F.
The configurations on Switch D, Switch E, and Switch F are similar to the configuration on
Switch A, and are not mentioned here.

Step 4 Create MD 2.
# Create MD 2 on Switch B.
[SwitchB] cfm enable
[SwitchB] cfm md md2 level 4
[SwitchB-md-md2] quit
# Create MD 2 on Switch C.
The configuration on Switch C is similar to the configuration on Switch B, and is not mentioned
here.
Step 5 Create the default MD and associate the default MD with VLAN 2 and VLAN 3 on Switch B
and Switch C.
# Create the default MD and associate the default MD to VLAN 2 and VLAN 3 on SwitchB.
[SwitchB] cfm default md level 6
[SwitchB-default-md] vlan 2 to 3
[SwitchB-default-md] quit
# Create the default MD and associate the default MD to VLAN 2 and VLAN 3 on Switch C.
here.
Step 6 Set the MIP creation rule in the default MD on Switch B and Switch C.
# Set the MIP creation rule in the default MD on Switch B.

[SwitchB] cfm default md
[SwitchB-default-md] mip create-type default
[SwitchB-default-md] quit
# Set the MIP creation rule in the default MD on Switch C.
here.
Step 7 Create and configure MA 1 in MD 1 on all the devices except for Switch B and Switch C.
# Create MA 1 in MD 1 on Switch D and Switch F.
The configurations on Switch D and Switch F are similar to the configuration on Switch A, and
Step 8 Create and configure MA 2 in MD 1 on all the devices except for Switch B and Switch C.
# Create MA 2 in MD 1 on Switch D and Switch E.

The configurations on Switch D and Switch E are similar to the configuration on Switch A, and
Step 9 Configure MEPs and RMEPs in MA 1 of MD 1 on Switch A and Switch F.
# Configure a MEP in MA 1 of MD 1 on Switch A.
# Create a MEP in MA 1 of MD 1 on Switch F.

[SwitchF] cfm md md1
[SwitchF-md-md1] ma ma1
[SwitchF-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 0/0/1 inward
# Configure an RMEP in MA 1 of MD 1 on Switch A.

[Switch A-md-md1-ma-ma1] remote-mep mep-id 1
# Configure an RMEP in MA 1 of MD 1 on Switch F.

[SwitchF-md-md1-ma-ma1] remote-mep mep-id 2
Step 10 Configure MEPs and RMEPs in MA 2 of MD 1 on Switch A and Switch E.

# Configure a MEP in MA 2 of MD 1 on Switch A.
# Configure a MEP in MA 2 of MD 1 on Switch E.

[SwitchE] cfm md md1
[SwitchE-md-md1] ma ma2
[SwitchE-md-md1-ma-ma2] mep mep-id 2 interface gigabitethernet 0/0/2 inward
# Configure an RMEP in MA 2 of MD 1 on Switch A.

# Configure an RMEP in MA 2 of MD 1 on Switch E.

Step 11 Enable the function of sending and receiving CCMs.

# Enable the function of sending CCMs in all MEPs on Switch A.
# Enable the function of receiving CCMs from all the RMEPs on Switch A.
# Enable the function of sending CCMs in all MEPs and the function of receiving CCMs from
all the RMEPs on Switch E and Switch F.
The configurations on Switch E and Switch F are similar to the configuration on SwitchA, and
After the preceding configurations are complete and the network becomes stable, run the
following commands to verify the configuration. Take Switch A and Switch B for example.

l Run the display cfm default md command on Switch B, and you can view the following
information:
[SwitchB] display cfm default md
Level MIP-Create-type SenderID TLV-type VLAN-list
-------------------------------------------------------------------------------
--------
6 default Defer 2 to 3
According to the preceding information, on Switch B, the default MD at level 6 is configured

and associated with VLAN 2 and VLAN 3, and the MIP creation rule is default.
l Perform the 802.1ag MAC ping/trace operation on Switch A, and you can view that no
connectivity fault occurs between Switch A and Switch E and the 802.1ag MAC trace
operation is successful. The following information is displayed:
[SwitchA-md-md1-ma-ma1] trace mac-8021ag mac aa99-6600-5600
Tracing the route to aa99-6600-5600 over a maximum of 255 hops:
Hops Mac Ingress Ingress Action
Relay Action
Forwarded Egress Egress Action
Ismep
1 2155-2201-3302 GigabitEthernet0/0/3 IngOK
RlyFDB
Forwarded GigabitEthernet0/0/1 EgrOK No
2 5522-1101-5503 GigabitethErnet0/0/1 IngOK
RlyFDB
Forwarded GigabitethErnet0/0/2 EgrOk No
RlyFDB
RlyFDB
5 aa99-6600-5600 GigabitethErnet0/0/1 IngOK
RlyHit
Not Forwarded
Yes
Info: Succeed in tracing the destination address aa99-6600-5600.
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 2 to 3
#
cfm version standard
cfm enable
#
#
#
#
cfm md md1 level 6
ma ma1

map vlan 2
mep mep-id 2 interface gigabitethernet 0/0/1 inward
remote-mep mep-id 1
ma ma2
map vlan 3
remote-mep mep-id 2
#
return
#
sysname SwitchB
#
vlan batch 2 to 3
#
cfm enable
#
#
#
cfm md md2 level 4
#
cfm default md level 6
mip create-type defaul
vlan 2 to 3
#
return
#
sysname SwitchC
#
vlan batch 2 to 3
#
cfm enable
#
#
#
cfm md md2 level 4
#
cfm default md level 6
mip create-type defaul
vlan 2 to 3
#
return
#
sysname SwitchD
#
vlan batch 2 to 3
#


cfm enable
#
#
#
#
cfm md md1 level 6
ma ma1
map vlan 2
ma ma2
map vlan 3
#
return
l Configuration file of Switch E
#
sysname SwitchE
#
vlan batch 3
#
cfm enable
#
#
#
cfm md md1 level 6
ma ma2
map vlan 3
mep mep-id 2 interface gigabitethernet 0/0//2 inward
remote-mep mep-id 1
#
return
l Configuration file of Switch F
#
sysname SwitchF
#
vlan batch 2
#
cfm enable
#
#
#
cfm md md1 level 6
ma ma1
map vlan 2


remote-mep mep-id 2
#
return
4.21.5 Example for Configuring Association Between an EFM OAM

OAM module. Then the EFM OAM module sends the fault notification message to the remote
device.
As shown in Figure 4-17, EFM OAM is configured between Switch B and Switch C. When GE
0/0/2 on Switch B becomes Down, the EFM OAM module reports the fault to GE 0/0/1 on
Switch C through the association mechanism. Then GE 0/0/1 is triggered to go Down.
Figure 4-17 Networking diagram for configuring association between an EFM OAM module
and an interface
SwitchA SwitchB SwitchC
GE0/0/1 GE0/0/2
GE0/0/1 GE0/0/2
EFM OAM
Interface associated with
EFM OAM
1. Configure EFM OAM between Switch B and Switch C.
2. On Switch B, configure association between an EFM OAM module and GE 0/0/1.
Procedure
Step 1 Configure EFM OAM between Switch B and Switch C.
[SwitchB-GigabitEthernet0/0/2] efm mode passive


[SwitchC] efm enable
[SwitchC-GigabitEthernet0/0/2] efm enable
Run the display efm session interface command on Switch B to check the EFM OAM status,
and you can find that EFM OAM is in detect state.
--------------------------------------------------------------------
GigabitEthernet0/0/2 detect
Step 2 Configure association between an EFM OAM module with an interface.
# Enable GE 0/0/1 on Switch B and the EFM OAM module between Switch B and Switch C to
report faults to each other.
[SwitchB] oam-mgr
[SwitchB-oam-mgr] oam-bind efm interface gigabitethernet 0/0/ trigger if-down
interface gigabitethernet 0/0/1
After GE 0/0/2 on Switch B is shut down, the EFM OAM module reports the fault to GE
0/0/1. Then GE 0/0/1 is triggered to go Down.
[SwitchB] display interface gigabitethernet 0/0/1
GigabitEthernet0/0/1 current state : TRIGGER DOWN
(3AH)
Line protocol current state : DOWN
Description:HUAWEI, Quidway Series, GigabitEthernet0/0/1 Interface
Switch Port,PVID : 1,The Maximum Frame Length is 1600
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 0018-8211-1111
Port Mode: COMBO AUTO
Current Work Mode: COPPER
Speed : 1000, Loopback: NONE
Duplex: FULL, Negotiation: ENABLE
Mdi : AUTO
Last 300 seconds input rate 0 bits/sec, 0 packets/sec
Last 300 seconds output rate 0 bits/sec, 0 packets/sec
Input peak rate 0 bits/sec,Record time: -
Output peak rate 0 bits/sec,Record time: -
Input: 0 packets, 0 bytes
Unicast : 0,Multicast : 0
Broadcast : 0,Jumbo : 0
CRC : 0,Giants : 0
Jabbers : 0,Throttles : 0
Runts : 0,DropEvents : 0
Alignments : 0,Symbols : 0
Ignoreds : 0,Frames : 0
Discard : 0,Total Error : 0
Output: 0 packets, 0 bytes
Collisions : 0,Deferreds : 0
Late Collisions: 0,ExcessiveCollisions: 0
Buffers Purged : 0
Input bandwidth utilization threshold : 100.00%
Output bandwidth utilization threshold: 100.00%

Input bandwidth utilization : 0.00%

Output bandwidth utilization : 0.00%
----End
Configuration Files
#
sysname SwitchB
#
efm enable
#
efm enable
#
efm mode passive
efm enable
#
oam-mgr
oam-bind ingress interface GigabitEthernet0/0/2 egress efm interface
GigabitEthernet0/0/1 trigger if-
down
oam-bind ingress efm interface GigabitEthernet0/0/1 trigger if-down egress
#
return

#
sysname SwitchC
#
efm enable
#
efm enable
#
return
4.21.6 Example for Configuring Association Between EFM OAM

Modules
As shown in Figure 4-18, to implement the end-to-end link fault detection, EFM OAM is
configured between Switch A and Switch B and between Switch B and Switch C. When a fault
occurs on the link between Switch A and Switch B, EFM OAM between Switch A and Switch
B detects the fault and sends fault messages to Switch C through the association mechanism.
Then, alarms are generated on Switch C.
Figure 4-18 Networking diagram for configuring association between EFM OAM modules
GE0/0/1 GE0/0/2
GE0/0/1 GE0/0/2
EFM OAM EFM OAM

1. Enable EFM OAM globally on Switch A, Switch B, and Switch C.
2. Configure EFM OAM on GE 0/0/1 of Switch B and GE 0/0/2S of Switch C to work in
passive mode.
3. Enable EFM OAM on interfaces of the S5300s.
4. Configure association between EFM OAM modules on Switch B.
Procedure
Step 1 Enable EFM OAM globally.
<SwitchB> system-view
<SwitchC> system-view
Step 2 Configure the operation mode of interfaces.

[SwitchB-GigabitEthernet0/0/1] efm mode passive
[SwitchC-GigabitEthernet0/0/2] efm mode passive
Step 3 Enable EFM OAM on interfaces.


Run the display efm session all command to check the EFM OAM status, and you can find that
EFM OAM is in detect state. Take the display on Switch B as an example.
[SwitchB] display efm session all
----------------------------------------------------------------------
Step 4 Configure association between EFM OAM modules.

[SwitchB] oam-mgr
[SwitchB-oam-mgr] oam-bind efm interface gigabitethernet 0/0/1 efm interface
gigabitethernet 0/0/2
In the OAM management view, run the display this command to check association. You can
find that there are two unidirectional association configuration records, whose directions are
mutually reverse.
[SwitchB-oam-mgr] display this
#
oam-mgr
#

# On SwitchC, enable the function of sending debugging information to a terminal.
<SwitchC> terminal logging
<SwitchC> terminal monitor
# Shut down GE 0/0/1 on SwitchA and simulate link faults.

[SwitchA-GigabitEthernet0/0/1] shutdown
# Fault messages between SwitchA and SwitchB are transmitted to SwitchC through the
association mechanism. Then alarms are generated on SwitchC.
<SwitchC>
Mar 9 2010 14:52:33 SwitchC %%01EFM/2/NONTHRESHOLD(l): OID 1.3.6.1.4.1.2011.5
.25.136.1.6.5 Non-threshold-crossing event occurred.
(InterfaceName=GigabitEthernet0/0/1, EventLogIndex=0, EventLogTimestamp=148983996,
EventLogOui=[01.80.c2 (h
ex)], EventLogType=258, EventLogLocation=2, EventLogRunningTotal=0 3)
----End
Configuration Files
#
sysname SwitchA
#
efm enable
#
efm enable
#
return

#
sysname SwitchB

#
efm enable
#
efm mode passive
efm enable
#
efm enable
#
oam-mgr
#
return

#
sysname SwitchC
#
efm enable
#
efm mode passive
efm enable
#
return
4.21.7 Example for Configuring Association Between an Ethernet

CFM Module and an Interface
As shown in Figure 4-19, CFM is used on a direct link and a multi-hop link. Ethernet CFM is
configured between SwitchA and SwitchB, and Ethernet CFM is associated with GE0/0/1 of
SwitchA. When the CFM OAM module on SwitchA detects the connectivity fault on the link
between SwitchA and SwitchB, it shuts down GE0/0/1. In this case, the peer device of
SwitchA detects the fault.
Figure 4-19 Networking diagram for associating an Ethernet CFM module with an interface
CFM OAM
GE0/0/1 GE0/0/2 GE0/0/1

SwitchC SwitchA SwitchB
Interface associated with CFM OAM
1. Configure Ethernet CFM on SwitchA and SwitchB.

2. Associate an Ethernet CFM module with GE0/0/1 on SwitchA.

Procedure
Step 1 Create VLANs and add interfaces to the VLANs.
[SwitchA] vlan 10
[SwitchA-vlan10] quit
[SwitchB] vlan 10
[SwitchB-vlan10] quit
[SwitchB-GigabitEthernet0/0/1] port trunk allow-pass vlan 10
Step 2 Enable Ethernet CFM.

# Enable Ethernet CFM globally on SwitchA.
# Create the MD, MA, MEP, and RMEP on SwitchA.

[SwitchA]cfm md md1
[SwitchA-md-md1]ma ma1
[SwitchA-md-md1-ma-ma1] ccm-interval 1000
[SwitchA-md-md1-ma-ma1] mep mep-id 2 interface gigabitethernet 0/0/2 outward
# Enable Ethernet CFM globally on SwitchB.

# Create the MD, MA, MEP, and RMEP on SwitchB.

[SwitchB]cfm md md1
[SwitchB-md-md1]ma ma1
[SwitchB-md-md1-ma-ma1] map vlan 10
[SwitchB-md-md1-ma-ma1] ccm-interval 1000
[SwitchB-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 0/0/1 outward
[SwitchB-md-md1-ma-ma1] remote-mep mep-id 2
[SwitchB-md-md1-ma-ma1] mep ccm-send enable
[SwitchB-md-md1-ma-ma1] remote-mep ccm-receive enable
[SwitchB-md-md1-ma-ma1] quit

Run the display cfm mep and display cfm remote-mep commands on SwitchA or SwitchB. If
information about the MEP and RMEP is displayed, it indicates that the configuration is
successful. The displayed information on SwitchB is as follows:
[SwitchB]display cfm mep md md1
The total number of MEPs is : 1
--------------------------------------------------
MD Name : md1

Level : 0
MA Name : ma1
MEP ID : 1
Vlan ID : 10
VSI Name : --
CCM Send : enabled
Direction : outward
MAC Address : 0018-82d1-b6df
[SwitchB] display cfm remote-mep md md1
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 2
Vlan ID : 10
VSI Name : --
MAC : 0012-1313-1211
CFM Status : up
Step 3 Associate an Ethernet CFM module with an interface.

Associate an Ethernet CFM module with an interface on SwitchA.
[SwitchA] oam-mgr
[SwitchA-oam-mgr] oam-bind cfm md md1 ma ma1 trigger if-down interface

Shut down GE 0/0/2 on SwitchA.
[SwitchA] interface gigabitethernet0/0/2
After the interface of SwitchA is shut down, the OAM management module reports the fault to
GE 0/0/1. Then GE 0/0/1 is triggered to go Down.
[SwitchA] display interface gigabitethernet 0/0/1

(1AG)
Duplex: FULL, Negotiation: DISABLE
Mdi : AUTO
CRC : 0,Giants : 0

Buffers Purged : 0
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 10
#
cfm enable
#
#
#
cfm md md1
ma ma1
map vlan 10
ccm-interval 10000
mep mep-id 2 interface GigabitEthernet0/0/2 outward
remote-mep mep-id 1
#
oam-mgr
oam-bind ingress interface GigabitEthernet0/0/1 egress cfm md md1 ma ma1
trigger if-down
#
return
#
sysname SwitchB
#
vlan batch 10
#
cfm enable
#
#
cfm md md1
ma ma1
map vlan 10
ccm-interval 10000
remote-mep mep-id 2

#
return
4.21.8 Example for Configuring Association Between an EFM OAM

Module and an Ethernet CFM Module
As shown in Figure 4-20, to implement end-to-end link fault detection, you need to enable EFM
OAM between Switch A and Switch B and between Switch C and Switch D. and enable Ethernet
CFM between Switch B and Switch C. When a fault occurs on the link between Switch A and
Switch B, Ethernet CFM is triggered to send trap message to Switch D. When a fault occurs on
the link between SwitchC and Switch D, Ethernet CFM is triggered to send trap message to
Switch A.
Figure 4-20 Networking diagram for configuring association between an EFM OAM module
and an Ethernet CFM module
SwitchA SwitchB SwitchC SwitchD
GE0/0/1 GE0/0/2 GE0/0/1

VLAN10 VLAN10
GE0/0/1 GE0/0/2 GE0/0/1
GE0/0/2 GE0/0/2
2. Configure EFM OAM between Switch A and Switch B.
3. Configure Ethernet CFM between the Switch B and Switch C.
4. Configure EFM OAM between Switch C and Switch D.
5. Configure association between an EFM OAM module and an Ethernet CFM module on
Switch B and Switch C.
Procedure
Step 1 Create VLAN 10 and add interfaces to VLAN 10.
Step 2 Enable EFM OAM globally onSwitch A and Switch B.


Step 3 Configure Ethernet CFM between the Switch B and Switch C.

[SwitchB] cfm md md1
[SwitchB-md-md1] ma ma1
[SwitchB-md-md1-ma-ma1] return
[SwitchC] cfm enable
[SwitchC-md-md1-ma-ma1] map vlan 10
[SwitchC-md-md1-ma-ma1] mep ccm-send enable
[SwitchC-md-md1-ma-ma1] remote-mep ccm-receive enable
[SwitchC-md-md1-ma-ma1] return
Step 4 Configure EFM OAM between Switch C and Switch D.

# Configure Switch D.
[SwitchD] efm enable
[SwitchD-GigabitEthernet0/0/1] efm mode passive
[SwitchD-GigabitEthernet0/0/1] efm enable
Step 5 Configure association between an EFM OAM module and an Ethernet CFM module.
# Associate EFM OAM between Switch A and Switch B with Ethernet CFM between Switch
B and Switch C in both directions. That is, enable the EFM OAM and Ethernet CFM modules
to send trap messages to each other.
[SwitchB] oam-mgr
[SwitchB-oam-mgr] oam-bind cfm md md1 ma ma1 efm interface gigabitethernet 0/0/1
# Associate EFM OAM between Switch C and Switch D with Ethernet CFM between Switch
B and Switch C in both directions. That is, enable the EFM OAM and Ethernet CFM modules
to send trap messages to each other.
[SwitchC] oam-mgr
[SwitchC-oam-mgr] oam-bind cfm md md1 ma ma1 efm interface gigabitethernet 0/0/1

# On Switch D, enable the function of sending debugging information to a terminal.
<SwitchD> terminal logging
<SwitchD> terminal monitor

# Shut down GE 1/0/0 onSwitch A to simulate a link fault.

After the preceding configuration is complete, when EFM OAM between Switch A and Switch
B detects a fault, Ethernet CFM reports the fault to EFM OAM running between Switch C and
Switch D.
<SwitchD>
Nov 23 2007 18:31:27-05:00 Switch D %%01EFM/2/NONTHRESHOLD(l)[0]:OID 1.3.6.1.4.
1.2011.5.25.136.1.6.5 Non-threshold-crossing event occurred.
(InterfaceName=GigabitEthernet0/0/1, EventLogIndex=0, EventLogTimestamp=7357971,
EventLogOui=[01.80
.c2 (hex)], EventLogType=258, EventLogLocation=1, EventLogRunningTotal=0 1)
Nov 23 2007 18:31:27-05:00 SwitchD %%01OAMMGR/4/CFM_TO_EFM(l)[1]:802.1AG notif
ied malfunction to 802.3AH. (Ma=ma1, Md=md1, InterfaceName=GigabitEthernet0/0/1,
FaultState=1)
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 10
#
efm enable
#
efm mode passive
efm enable
#
#
return

#
sysname SwitchB
#
vlan batch 10
#
efm enable
#
cfm enable
#
efm enable
#
#
cfm md md1
ma ma1
map vlan 10
mep ccm-send enable

remote-mep mep-id 2
#
oam-mgr
#
return

#
sysname SwitchC
#
vlan batch 10
#
efm enable
#
cfm enable
#
efm enable
#
#
cfm md md1
ma ma1
map vlan 10
mep ccm-send enable
remote-mep mep-id 1
#
oam-mgr
#
return

#
sysname SwitchD
#
vlan batch 10
#
efm enable
#
efm mode passive
efm enable
#
#
return

4.21.9 Example for Configuring Association Between Ethernet CFM

with Ethernet CFM
As shown in Figure 4-21, Ethernet CFM is configured between Switch A and Switch B, and
between Switch B and Switch C. When a fault occurs on the link between Switch A and Switch
B, Ethernet CFM is triggered to send fault messages to Switch C. Then, alarms are generated
on Switch C.
Figure 4-21 Networking diagram for configuring association between Ethernet CFM and
Ethernet CFM
GE0/0/1 GE0/0/2
GE0/0/1 GE0/0/2
CFM CFM
MEP in MA1
MEP in MA2

2. Configure Ethernet CFM between Switch A and Switch B, and between SwitchB and
Switch C.
3. Configure association between Ethernet CFM and Ethernet CFM on Switch B and Switch
C.
Procedure
Step 2 Configure Ethernet CFM between Switch A and Switch B.


Step 3 Configure Ethernet CFM between Switch B and Switch C.
[SwitchC-md-md1-ma-ma1] remote-mep ccm-receive enable
[SwitchC-md-md1-ma-ma1] quit
[SwitchC-md-md1] quit
Run the display cfm remote-mep command on Switch B to check the CFM status, and you can
find that the CFM status is Up.
[SwitchB] display cfm remote-mep
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 1
Vlan ID : 10
VSI Name : --
MAC : 0012-1313-1211
CFM Status : up
MD Name : md1
Level : 0
MA Name : ma2
RMEP ID : 2
Vlan ID : 20
VSI Name : --
MAC : 0012-1313-1211
CFM Status : up
Step 4 Configure association between Ethernet CFM and Ethernet CFM.

# Associate Ethernet CFM between Switch A and Switch B with Ethernet CFM between Switch
B and Switch C in both directions. That is, enable Ethernet CFM modules to send trap messages
to each other.
[SwitchB] oam-mgr
[SwitchB-oam-mgr] oam-bind cfm md md1 ma ma1 cfm md md1 ma ma2

Shut down GE 0/0/2 of Switch B. Run the display cfm remote-mep command on Switch A to
check the CFM status between Switch A and Switch B, and you can find that the CFM status is
Down.
[SwitchA]display cfm remote-mep
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 2
Vlan ID : 10
VSI Name : --
MAC : 0018-82d1-b6df
CFM Status : down
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 10
#
cfm enable
#
#
cfm md md1
ma ma1
map vlan 10
remote-mep mep-id 2
#
return

#
sysname SwitchB
#
vlan batch 10 20
#
cfm enable
#
#


#
cfm md md1
ma ma1
map vlan 10
remote-mep mep-id 1
ma ma2
map vlan 20
remote-mep mep-id 2
#
oam-mgr
#
return

#
sysname SwitchC
#
vlan batch 20
#
cfm enable
#
#
cfm md md1
ma ma2
map vlan 20
remote-mep mep-id 1
#
return
4.21.10 Example for Associating Ethernet CFM with Smart Link

As shown in Figure 4-22, enterprise users access Switch A through the DSLAM. To improve
the reliability of the network, Switch A is connected to upstream devices Switch B and Switch
C in dual-homing mode. Smart Link is configured on Switch A to ensure reliability. Etherenet
CFM is enabled on active and standby links of the Smart Link group, and Ethernet CFM is
associated with interfaces. When Ethernet CFM detects faults on the link, OAM Manager notifies
the Smart Link module of the faults. Then, the Smart Link module blocks the active interface
GE 0/0/1 so that the traffic is forwarded through GE 0/0/2. In this manner, fast switchover of
the Smart Link group is implemented.

Figure 4-22 Networking diagram for associating Ethernet CFM with Smart Link
SwitchB
802.1ag
GE0/0/1
GE0/0/1
SwitchA
DSLAM
GE0/0/3 SmartLink
GE0/0/2
GE0/0/2
802.1ag
Enterprise user
SwitchC
1. On Switch A, configure Smart Link multi-instance and add the uplink interfaces to the
Smart Link group.
2. Enable revertive switchover on SwitchA and enable Switch A to send Flush packets.
3. Enable Switch B and Switch C to receive Flush packets.
4. Enable functions of the Smart Link group on Switch A.
5. Configure Ethernet CFM between Switch A and Switch C and between Switch A and
Switch B.
6. Associate Ethernet CFM with interfaces on Switch A.
Procedure
#Configure Switch A
[SwitchA] vlan batch 10 20
[SwitchA-GigabitEthernet0/0/1] port trunk allow-pass vlan 10 20
[SwitchA-GigabitEthernet0/0/2] port trunk allow-pass vlan 10 20
#Configure Switch B

[SwitchB] vlan batch 10 20

[SwitchB-GigabitEthernet0/0/1] port trunk allow-pass vlan 10 20
#Configure Switch C
[SwitchC] vlan batch 10 20
[SwitchC-GigabitEthernet0/0/2] port trunk allow-pass vlan 10 20
Step 2 On Switch A, binding VLANs to an Instance.

[SwitchA-mst-region] instance 1 vlan 10
Step 3 Add the interfaces where STP is disabled to the Smart Link group and specify active and standby
interfaces.
# Disable STP on Switch A.

# Configure active and standby interfaces.

Step 4 Enable the receiving of Flush packets.
simple 123
simple 123
Step 5 Enable functions of the Smart Link group.

Run the display smart-link group command to check information about the Smart Link group
on Switch A.

[SwitchA] display smart-link group 1

Smart link group 1 information:
Smart link group was enabled
Device ID: 00e0-fc00-0100 Control-vlan ID: 10
Member Role State Flush Count Last-Flush-
Time
---------------------------------------------------------------------
GigabitEthernet0/0/1 Master Active 1 2007/08/21
16:37:20 UTC+00:00
GigabitEthernet0/0/2 Slave Inactive 2 2007/08/21
14:45:56 UTC+00:00
Step 6 Configure Ethernet CFM.

[SwitchA-md-md1-ma-ma1] remote-mep ccm-recive enable
[SwitchA-md-md1-ma-ma2] remote-mep ccm-recive enable
[SwitchB-md-md1-ma-ma1] remote-mep ccm-recive enable
[SwitchC-md-md1-ma-ma2] remote-mep ccm-recive enable
[SwitchC-md-md1-ma-ma2] quit
[SwitchC-md-md1] quit
Run the display cfm remote-mep command to check the CFM status. Take the display on Switch
A as an example.
[SwitchA] display cfm remote-mep

--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 3
Vlan ID : 20
VSI Name : --
MAC : 0018-82d1-b6df
CFM Status : up
MD Name : md1
Level : 0
MA Name : ma2
RMEP ID : 4
Vlan ID : 20
VSI Name : --
MAC : 0018-82d1-b6df
Trigger-if-notify : disabled
CFM Status : up
Step 7 Associate Ethernet CFM with interfaces.
[SwitchA] oam-mgr
Disable CC detection of ma1 on Switch A and simulate link faults.

[S5300A] cfm md md1
[SwitchA-md-md1-ma-ma1] undo mep ccm-send enable
# Check the status of GE 0/0/1 that is associated with CFM ma1, and you can find that GE
GE 0/0/1 is in state.
[SwitchA] display interface GigabitEthernet 1/0/0
(1AG)
Mdi : AUTO
CRC : 0,Giants : 0


Buffers Purged : 0
# Check the status of the Smart Link group on Switch A, and you can find that GE 0/0/1 is in
Inactive state and GE 0/0/2 is in Active state.
[SwitchA] display smart-link group 1
Smart link group 1 information:
Smart link group was enabled
Device ID: 00e0-fc00-0100 Control-vlan ID: 10
Member Role State Flush Count Last-Flush-
Time
---------------------------------------------------------------------
GigabitEthernet0/0/1 Master Inactive 2 2007/08/21
16:37:20 UTC+00:00
GigabitEthernet0/0/2 Slave Active 3 2007/08/21
14:45:56 UTC+00:00
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 10 20
#
cfm enable
#
instance 1 vlan 10
#
port trunk allow-pass vlan 10 20
stp disable
#
stp disable
#
#
cfm md md1
ma ma1
map vlan 20
remote-mep mep-id 3
ma ma2
map vlan 20
remote-mep mep-id 4


#
oam-mgr
trigger if-down
trigger if-down
#
smart-link group 1
smart-link enable
#
return

#
sysname SwitchB
#
vlan batch 10 20
#
cfm enable
#
#
cfm md md1
ma ma1
map vlan 20
remote-mep mep-id 1
#
return

#
sysname SwitchC
#
vlan batch 10 20
#
cfm enable
#
#
cfm md md1
ma ma2
map vlan 20
remote-mep mep-id 2
#
return

4.21.11 Example for Associating Ethernet CFM with RRPP

As shown in Figure 4-23, UPEA, UPEB, UPEC, and PE-AGG constitute an RRPP single ring.
VLANs 100 to 300 are configured on the CE; packets are transmitted on ring 1 of domain 1.
Ethernet CFM is configured between UPEA and PE-AGG, and Ethernet CFM is associated with
primary and secondary interfaces on the RRPP ring.
Figure 4-23 Networking diagram for associating Ethernet CFM and RRPP multi-instance
UPEB
GE0/0/1 GE0/0/2
CE1 PE-AGG
VLAN 100-300 GE0/0/2 GE0/0/1
Ring 1 Backbone
UPEA Master 1 network
GE0/0/1 GE0/0/2
Domain 1 ring 1
GE0/0/2 GE0/0/1
UPEC
For details on the protected VLAN in domain 1, and the instance that the protected VLAN
belongs to, see Table 4-2.
Table 4-2 Mapping between instances and protected VLANs

Ring Control VLAN Instance ID of Data VLAN ID Instance ID of
ID ID the Control the Data
VLAN VLAN
Domain VLAN 5 and Instance 1 VLANs 100 to 300 Instance 1

1 VLAN 6
For details on the master node and primary and secondary interfaces on the master node of the
ring, see Table 4-3.

Table 4-3 Master node, and primary and secondary interfaces on the master node
Ring ID Master Node Primary Interface Secondary
Interface
1. Map instance 1 to VLANs 100 to 300.
2. Add UPEA, UPEB, UPEC, and PE-AGG to ring 1 in domain 1.
3. Configure protected VLAN and control VLAN for domain 1.
4. Configure PE-AGG as the master node and configure UPEA, UPEB, and UPE C as transit
nodes on ring 1 in domain 1.
5. Configure Ethernet CFM on PE-AGG and UPEA to detect faults on the two links between
PE-AGG and UPEA.
6. Configure association between Ethernet CFM and primary and secondary interfaces on the
RRPP ring on PE-AGG.
Data Preparation
l IDs of instances
Procedure
l Configure UPEA.
# Create data VLANs 100 to 300 on UPEA.
# Create instance 1, and map control VLANs 5 and 6 and data VLANs 100 to 200 in domain 1
to instance 1.
<UPEA> system-view

l Configure UPEB.
# Create data VLANs 100 to 300 on UPEB.

to instance 1.
<UPEB> system-view

l Configure UPEC.
# Create data VLANs 100 to 300 on UPEC.
to instance 1.
<UPEC> system-view

l Configure PE-AGG.
to instance 1.
<PE-AGG> system-view


After the preceding configuration, run the following command to view the mapping between
instances and VLANs. Take the display on UPEA as an example:
<UPEA> display stp region-configuration
Oper configuration
Format selector :0
Region name :001820000083
Revision level :0

0 1 to 4, 7 to 9, 12 to 99, 301 to 4094
1 5 to 6, 100 to 300
Step 2 Configure the interfaces to be added to the RRPP ring.

l Configure UPEA.
# On UPEA, disable STP on the interfaces to be added to the RRPP ring. Configure the RRPP
interfaces to allow packets of VLANs 100 to 300 to pass through.
<UPEA> system-view


l Configure UPEB.
# On UPEB, disable STP on the interfaces to be added to the RRPP ring. Configure the RRPP
<UPEB> system-view
l Configure UPEC.
# On UPEC, disable STP on the interfaces to be added to the RRPP ring. Configure the RRPP
<UPEC> system-view
[UPEC-GigabitEthernet0/0/2]port link-type trunk
l Configure PE-AGG.
# On PE-AGG, disable STP on the interfaces to be added to the RRPP ring. Configure the RRPP
[PE-AGG-GigabitEthernet0/0/1]port link-type trunk
Step 3 Create RRPP domains and configure protected VLANs and control VLANs.
l Configure UPEA.
# Configure the VLANs mapping instance 1 as protected VLANs in domain 1, and configure
<UPEA> system-view


l Configure UPEB.
<UPEB> system-view
l Configure UPEC.
<UPEC> system-view
l Configure PE-AGG.

l Configure UPEA.
# Configure UPEA as a transit node of ring 1 in domain 1 and specify primary and secondary
interfaces.
<UPEA> system-view
l Configure UPEB.
# Configure UPEB as a transit node of ring 1 in domain 1 and specify primary and secondary
interfaces.
<UPEB> system-view
l Configure UPEC.
# Configure UPEC as a transit node of ring 1 in domain 1 and specify primary and secondary
interfaces.
<UPEC> system-view


l Configure PE-AGG.
# Configure PE-AGG as the master node of ring 1 in domain 1, GE 0/0/1 as the primary interface,
and GE 0/0/2 as the secondary interface.
Step 5 Enable RRPP.

l Configure UPEA.
# Enable RRPP.
<UPEA> system-view
[UPEA] rrpp enable
l Configure UPEB.
# Enable RRPP.
<UPEB> system-view
[UPEB] rrpp enable
l Configure UPEC.
# Enable RRPP.
<UPEC> system-view
[UPEC] rrpp enable
l Configure PE-AGG.
# Enable RRPP.
perform the following operations to verify the configuration. Take the display on UPEA and
PE-AGG as examples.
l On UPEA, run the display rrpp brief or display rrpp verbose domain command. The result
is as follows:
# Check the brief information of RRPP on UPEA.
<UPEA> display rrpp brief

Domain Index : 1


----------------------------------------------------------------------------
RRPP is enabled on UPEA, VLAN 5 is the control VLAN and VLANs mapping instance 1 are
the protected VLANs in domain 1, and UPE A is a transit node on ring 1; GE 0/0/1 is the primary
interface, and GE 0/0/2 is the secondary interface.
# Check detailed information about UPEA in domain 1.

<UPEA> display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Transit
Ring State : LinkUp
mapping instance 1 are the protected VLANs; UPEA is a transit node in domain 1 and is in
LinkUp state; RRPP is enabled on UPEA.
# Check the brief information of RRPP on PE-AGG.

<PE-AGG> display rrpp brief

Domain Index : 1
---------------------------------------------------------------------------
The preceding information shows that RRPP is enabled on PE-AGG. In domain 1, VLAN 5 is
the major control VLAN, VLANs mapping instance 1 are the protected VLANs, and PE-AGG
is the master node on ring 1; GE 0/0/1 is the primary interface, and GE 0/0/2 is the secondary
interface.
# Check detailed information about PE-AGG in domain 1.

<PE-AGG> display rrpp verbose domain 1
Domain Index : 1
RRPP Ring : 1

Ring Level : 0
Node Mode : Master
mapping instance 1 are the protected VLANs. PE-AGG is the master node in domain 1 and is
in Complete state. GE 0/0/1 is the primary interface, and GE 0/0/2 is the secondary interface.
Step 6 Configure Ethernet CFM.
# Configure UPEA.
[UPEA] cfm md md1
[UPEA-md-md1] ma ma1
[UPEA-md-md1-ma-ma1] map vlan 100
[UPEA-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 0/0/2 outward
[UPEA-md-md1-ma-ma1] remote-mep mep-id 2
[UPEA-md-md1-ma-ma1] remote-mep ccm-receive mep-id 2 enable
[UPEA-md-md1-ma-ma1] mep ccm-send enable
[UPEA-md-md1-ma-ma1] quit
[UPEA-md-md1] ma ma2
[UPEA-md-md1-ma-ma2] map vlan 100
[UPEA-md-md1-ma-ma2] mep mep-id 3 interface gigabitethernet 0/0/1 outward
[UPEA-md-md1-ma-ma2] remote-mep mep-id 4
[UPEA-md-md1-ma-ma2] remote-mep ccm-receive mep-id 4 enable
[UPEA-md-md1-ma-ma2] mep ccm-send enable
[UPEA-md-md1-ma-ma2] quit
# Configure PE-AGG.
[PE-AGG] cfm md md1
[PE-AGG-md-md1] ma ma1
[PE-AGG-md-md1-ma-ma1] map vlan 100
[PE-AGG-md-md1-ma-ma1] mep mep-id 2 interface gigabitethernet 0/0/1 outward
[PE-AGG-md-md1-ma-ma1] remote-mep mep-id 1
[PE-AGG-md-md1-ma-ma1] remote-mep ccm-receive mep-id 1 enable
[PE-AGG-md-md1-ma-ma1] mep ccm-send enable
[PE-AGG-md-md1-ma-ma1] quit
[PE-AGG-md-md1] ma ma2
[PE-AGG-md-md1-ma-ma2] map vlan 100
[PE-AGG-md-md1-ma-ma2] mep mep-id 4 interface gigabitethernet 0/0/2 outward
[PE-AGG-md-md1-ma-ma2] remote-mep mep-id 3
[PE-AGG-md-md1-ma-ma2] remote-mep ccm-receive mep-id 3 enable
[PE-AGG-md-md1-ma-ma2] mep ccm-send enable
[PE-AGG-md-md1-ma-ma2] quit
On UPEA or PE-AGG, run the display cfm remote-mep command to check the status of
Ethernet CFM. You can find that Ethernet CFM is in Up state. Take the display on PE-AGG as
an example.
[PE-AGG] diplay cfm remote-mep
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 1
Vlan ID : 100
VSI Name : --
MAC : 0018-82d1-b6df
CFM Status : up
MD Name : md1

Level : 0
MA Name : ma2
RMEP ID : 3
Vlan ID : 100
VSI Name : --
MAC : 0018-82d1-b6df
CFM Status : up
Step 7 Configure the association between Ethernet CFM and interfaces.

# Configure PE-AGG.
[PE-AGG] oam-mgr
[PE-AGG-oam-mgr] oam-bind cfm md md1 ma ma1 trigger if-down interface
[PE-AGG-oam-mgr] oam-bind cfm md md1 ma ma2 trigger if-down interface

Shut down GE 0/0/1 on UPEB and simulate fault on the link of GE 1/0/0 and run the display
cfm remote-mep command on PE-AGG to check the CFM status. The following information
is displayed:
[PE-AGG] diplay cfm remote-mep
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 1
Vlan ID : 100
VSI Name : --
MAC : 0018-82d1-b6df
CFM Status : down
MD Name : md1
Level : 0
MA Name : ma2
RMEP ID : 3
Vlan ID : 100
VSI Name : --
MAC : 0018-82d1-b6df
CFM Status : up
Run the display this interface command on PE-AGG to check the status of GE 0/0/1, and you
can find that GE 0/0/1 is in TRIGGER DOWN (1AG) state.
[PE-AGG] display this interface gigabitethernet0/0/1
(1AG)
Mdi : AUTO


CRC : 0,Giants : 0
Buffers Purged : 0
Run the display rrpp verbose domain 1 command on PE-AGG to check the status of the RRPP
ring and interface, and following information is displayed:
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
Ring State : Failed
Primary port : GigabitEthernet0/0/1 Port status: DOWN
The status of the RRPP ring becomes Failed and the secondary interface changes from
BLOCKED to UP.
Re-enable GE 0/0/1 of UPEB, and you can find that the CFM status on PE-AGG becomes UP.
Run the display rrpp verbose domain 1 command on PE-AGG to check the status of the RRPP
ring and interface, and you can find that the RRPP ring becomes Complete as follows:
Domain Index : 1
RRPP Ring : 1
Ring Level : 0
Node Mode : Master
----End
Configuration Files
l Configuration file of UPEA
#
sysname UPEA

#
#
rrpp enable
#
cfm enable
#
instance 1 vlan 5 6 100 to 300
#
rrpp domain 1
control-vlan 5
ring 1 enable
#
stp disable
#
stp disable
#
cfm md md1
ma ma1
map vlan 100
remote-mep mep-id 2
ma ma2
map vlan 100
remote-mep mep-id 4
#
oam-mgr
if-down
if-down
#
return
l Configuration file of UPEB
#
sysname UPEB
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5


ring 1 enable
#
stp disable
#
stp disable
#
return
l Configuration file of UPEC
#
sysname UPEC
#
#
rrpp enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
#
stp disable
#
stp disable
#
Return
#
sysname PE-AGG
#
#
rrpp enable
#
cfm enable
#
#
rrpp domain 1
control-vlan 5
ring 1 enable
#

stp disable
#
stp disable
#
cfm md md1
ma ma1
map vlan 100
remote-mep mep-id 1
ma ma2
map vlan 100
mep mep-id 4 interface GigabitEthernet0/0/2 0 outward
remote-mep mep-id 3
#
oam-mgr
if-down
if-down
#
return
4.21.12 Example for Associating SEP with Ethernet CFM

SEP runs at the access layer to implement link redundancy and topology display. Association
between Ethernet CFM and SEP can be configured on edge devices of the SEP segment. When
Ethernet CFM detects a fault at the aggregation layer, the related edge device encapsulates a
fault message into a CFM protocol packet and sends it to the OAM management module to
switch the physical status of the interface bound to Ethernet CFM to Down.
As shown in Figure 4-24, Layer 2 switching devices LSW1 to LSW5 form a ring network, which
is connected to the core network. In this networking mode:
l SEP runs at the access layer.
– The topology change notification function needs to be configured at the access layer.
In this way, devices at the aggregation layer can update their MAC address tables and
ARP tables when a fault occurs at the access layer.
– SEP needs to be associated with Ethernet CFM on the devices between the access layer
and aggregation layer. In this way, devices at the access layer can update their MAC
address tables and ARP tables when a fault occurs at the aggregation layer.
l NPE1 and NPE2 form a VRRP group to improve network reliability.
l A BFD session is set up between NPE1 and NPE2 to detect the link status and implement
VRRP fast switchover.

Figure 4-24 Networking diagram of association between SEP and CFM
IP/MPLS Core
NPE1 NPE2
Core
Master Backup
GE1/0/1.1 GE1/0/1.1
10.1.1.1/24 BFD 10.1.1.2/24
Virtual IP Address:
10.1.1.10
GE1/0/2 GE1/0/2
Aggregation
PE-AGG1 GE1/0/3 PE-AGG2
GE1/0/1 GE1/0/1
CFM
GE0/0/2 GE0/0/2
LSW1 LSW5
GE0/0/1 GE0/0/1
SEP
Segment1
GE0/0/1 GE0/0/1
LSW2 LSW4
LSW3
GE0/0/2 GE0/0/2
Access
GE0/0/1 GE0/0/2
GE0/0/3
GE0/0/1 Primary Edge Node

CE1 Secondary Edge Node
Block Port
VLAN
Interface enabled with
100
Ethernet CFM
Interface associated with
Ethernet CFM
1. Configure basic SEP functions.

(1) Configure SEP segment 1 on LSW1 to LSW5 and configure VLAN 10 as the control
VLAN of SEP segment 1.
(2) Add all devices on the ring to SEP segment 1, and configure the roles of GE0/0/1 on
LSW1 and GE0/0/1 on LSW5 in SEP segment 1.
(3) On the device where the primary edge port is located, specify the port in the middle
of the SEP segment as the port to block.
(4) Configure the manual preemption mode on the device where the primary edge port is
located.
2. Configure basic CFM functions.
(1) Configure Ethernet CFM between PE-AGG1 and LSW1.
(2) Associate Ethernet CFM with GE0/0/1 on LSW1.
3. Configure VLANs on PE-AGG1 and PE-AGG2 to transmit VRRP packets and BFD
packets.
4. Set up a single-hop BFD session between NPE1 and NPE2 to detect the interfaces
configured with the VRRP group. The BFD session notifies VRRP of the interface status
so that VRRP fast switchover can be implemented.
5. Configure VRRP.
(1) Create VEEP group 1 on GE 1/0/1 of PE1 and set a higher priority for NPE1 so that
NPE1 functions as the master device in VRRP group 1.
(2) Create VRRP group 1 on GE 1/0/1 of PE2 and retain the default priority of NPE2.
(3) Bind VRRP group 1 to the BFD session.
6. Configure the Layer 2 forwarding function on CE1 and LSW1 to LSW5.
Data Preparation
l SEP segment ID
l Control VLAN of the SEP segment
l Port roles in the SEP segment
l Preemption mode
l Method of selecting the port to block
l Interface where Ethernet CFM is enabled
l Interface associated with Ethernet CFM
l Local discriminators and remote discriminators of the BFD session
Minimum interval for sending BFD packets, minimum interval for receiving packets, and
local detection multiplier (default values used)
l ID and virtual IP address of the VRRP group
l Priority of NPE1 in the VRRP group
Procedure
Step 1 Configure basic SEP functions.
1. Configure SEP segment 1 on LSW1 to LSW5 and configure VLAN 10 as the control VLAN
of SEP segment 1.

# Configure LSW1.
[Quidway] sysname LSW1
[LSW1] sep segment 1
[LSW1-sep-segment1] control-vlan 10
[LSW1-sep-segment1] protected-instance all
[LSW1-sep-segment1] quit
# Configure LSW2.
# Configure LSW3.
# Configure LSW4.
# Configure LSW5.
NOTE
l The control VLAN must be a VLAN that has not been created or used, but the configuration file
automatically displays the command for creating the VLAN.
l Each SEP segment must be configured with a control VLAN. After an interface is added to the
SEP segment configured with a control VLAN, the interface is added to the control VLAN
automatically. The configuration file displays port hybrid tagged vlan under this interface.
2. Add all devices on the ring to SEP segment 1 and configure port roles on the devices.
NOTE
By default, STP is enabled on a Layer 2 interface. Before adding an interface to the SEP segment,
disable STP on the interface.
# Configure LSW1.
[LSW1] interface gigabitethernet 0/0/1
[LSW1-GigabitEthernet0/0/1] stp disable
[LSW1-GigabitEthernet0/0/1] sep segment 1 edge primary
[LSW1-GigabitEthernet0/0/1] quit
# Configure LSW2.
[LSW2-GigabitEthernet0/0/1] sep segment 1
# Configure LSW3.


# Configure LSW4.
# Configure LSW5.
[LSW5-GigabitEthernet0/0/1] sep segment 1 edge secondary
3. Specify a port to block.

# On LSW1 where the primary edge port is located, specify that the port with the highest
priority is blocked.
[LSW1-sep-segment1] block port optimal
4. Set the priority of GE0/0/2 on LSW3.

[LSW3-GigabitEthernet0/0/2] sep segment 1 priority 128
5. Configure the preemption mode.

# Configure the delayed preemption mode on LSW1.
[LSW1-sep-segment1] preempt delay 30
NOTE
l You must set the preemption delay when delayed preemption is adopted because there is no
default delay time.
l After all the faulty ports recover, the edge ports no longer receive fault notification packets. If
the primary edge port does not receive any fault notification packet, it starts the delay timer.
When the delay timer expires, nodes in the SEP segment start blocked port preemption.
To implement delayed preemption in this example, you need to simulate a port fault and then
rectify the fault. For example:
Run the shutdown command on GE0/0/2 of LSW2 to simulate a port fault, and then run the
undo shutdown command on GE0/0/2 to rectify the fault.
After completing the preceding configurations, do as follows to verify the configuration. LSW1
is taken as an example.
l Run the display sep topology command on LSW1 to view detailed topology information of
the SEP segment.
The topology information shows that GE0/0/2 of LSW3 is in Discarding state, and the other
ports are in Forwarding state.
<LSW1> display sep topology
SEP segment 1
----------------------------------------------------------------
System Name Port Name Port Role Port Status

----------------------------------------------------------------
LSW1 GE0/0/1 primary forwarding
LSW2 GE0/0/1 common forwarding
LSW3 GE0/0/2 common discarding
LSW5 GE0/0/1 secondary forwarding
Step 2 Associate SEP with Ethernet CFM.

1. Configure Ethernet CFM between LSW1 and PE-AGG1.
# Configure LSW1.
[LSW1] cfm enable
[LSW1] cfm md md1
[LSW1-md-md1] ma ma1
[LSW1-md-md1-ma-ma1] mep mep-id 1 interface gigabitethernet 0/0/2 outward
[LSW1-md-md1-ma-ma1] remote-mep mep-id 2
[LSW1-md-md1-ma-ma1] mep ccm-send enable
[LSW1-md-md1-ma-ma1] remote-mep ccm-receive enable
[LSW1-md-md1-ma-ma1] quit
[LSW1-md-md1] quit
# Configure PE-AGG1.
[Quidway] PE-AGG1
[PE-AGG1] interface gigabitethernet 1/0/1
[PE-AGG1-GigabitEthernet1/0/1] portswitch
[PE-AGG1-GigabitEthernet1/0/1] undo shutdown
[PE-AGG1-GigabitEthernet1/0/1] quit
[PE-AGG1] cfm enable
[PE-AGG1] cfm md md1
[PE-AGG1-md-md1] ma ma1
[PE-AGG1-md-md1-ma-ma1] mep mep-id 2 interface gigabitethernet 1/0/1 outward
[PE-AGG1-md-md1-ma-ma1] remote-mep mep-id 1
[PE-AGG1-md-md1-ma-ma1] mep ccm-send enable
[PE-AGG1-md-md1-ma-ma1] remote-mep ccm-receive enable
[PE-AGG1-md-md1-ma-ma1] quit
[PE-AGG1-md-md1] quit
NOTE
The interface where the Maintenance Association End Point (MEP) is configured must be a Layer 2
interface. Only one MEP can be configured on an interface.
After the configuration, run the display cfm remote-mep command on LSW1, and you
can find that Ethernet CFM is in Up state.
[LSW1] display cfm remote-mep
--------------------------------------------------
MD Name : md1
Level : 0
MA Name : ma1
RMEP ID : 2
Vlan ID : --
VSI Name : --
MAC : --
CFM Status : up
2. Associate SEP between Ethernet CFM.

[LSW1] oam-mgr
[LSW1-oam-mgr] oam-bind ingress cfm md md1 ma ma1 egress sep segment 1
interface gigabitethernet 0/0/1

Run the shutdown command on GE 1/0/1 of PE-AGG1 to simulate a link fault. The fault
message is transmitted to the SEP segment through the interface configured with Ethernet
CFM and the OAM management module. Run the display sep interface command on
LSW3, and you can find that GE0/0/2 switches from the Disabling state to the Forwarding
state.
<LSW3> display sep interface gigabitethernet 0/0/2
SEP segment 1
----------------------------------------------------------------
Interface Port Role Neighbor Status Port Status
----------------------------------------------------------------
GE0/0/2 common up forwarding
Step 3 Configure VLAN 100 to transmit VRRP packets and configure VLAN 200 to transmit BFD
packets.
[PE-AGG1] vlan batch 100 200
[PE-AGG1-GigabitEthernet1/0/2] port default vlan 200
[PE-AGG1-GigabitEthernet1/0/2] port trunk allow-pass vlan 100
[PE-AGG1-GigabitEthernet1/0/3] port trunk allow-pass vlan 100 200
[PE-AGG2] vlan batch 100 200
[PE-AGG2-GigabitEthernet1/0/2] port default vlan 200
[PE-AGG2-GigabitEthernet1/0/2] port trunk allow-pass vlan 100
[PE-AGG2-GigabitEthernet1/0/3] port trunk allow-pass vlan 100 200
Step 4 Create a BFD session.

1. Configure IP addresses for interfaces.
# Configure an IP address for the interface on NPE1 and create a sub-interface.
[Quidway] sysname NPE1
[NPE1] interface gigabitethernet 1/0/1
[NPE1-GigabitEthernet1/0/1] undo shutdown
[NPE1-GigabitEthernet1/0/1] ip address 11.1.1.1 24
[NPE1-GigabitEthernet1/0/1] quit
[NPE1] interface gigabitethernet 1/0/1.1
[NPE1-GigabitEthernet1/0/1.1] vlan-type dot1q 100
[NPE1-GigabitEthernet1/0/1.1] ip address 10.1.1.1 24
[NPE1-GigabitEthernet1/0/1.1] quit
# Configure an IP address for the interface on NPE2 and create a sub-interface.

[Quidway] sysname NPE2
[NPE2] interface gigabitethernet 1/0/1
[NPE2-GigabitEthernet1/0/1] undo shutdown
[NPE2-GigabitEthernet1/0/1] ip address 11.1.1.2 24
[NPE2-GigabitEthernet1/0/1.1] vlan-type dot1q 100
[NPE2-GigabitEthernet1/0/1.1] ip address 10.1.1.2 24

2. Create a BFD session.

# Enable the BFD function on NPE1 and configure the BFD session between NPE1 and
NPE2.
[NPE1] bfd
[NPE1-bfd] quit
[NPE1] bfd NPE2 bind peer-ip default-ip interface gigabitethernet 1/0/1
[NPE1-bfd-session-npe2] discriminator local 1
[NPE1-bfd-session-npe2] discriminator remote 2
[NPE1-bfd-session-npe2] commit
[NPE1-bfd-session-npe2] quit
# Enable the BFD function on NPE2 and configure the BFD session between NPE1 and
NPE2.
[NPE2] bfd
[NPE2-bfd] quit
[NPE2] bfd NPE1 bind peer-ip default-ip interface gigabitethernet 1/0/1
[NPE2-bfd-session-npe2] discriminator local 2
[NPE2-bfd-session-npe2] discriminator remote 1
After the configuration, run the display bfd session all command on NPE1 and NPE2, and
you can find that the BFD session is set up and its status is Up.
Take the display on NPE1 as an example.
<NPE1> display bfd session all
------------------------------------------------------------------------------
--
Local Remote PeerIpAddr State Type InterfaceName
------------------------------------------------------------------------------
--
1 2 224.0.0.184 Up S_IP_IF GigabitEthernet1/0/1
------------------------------------------------------------------------------
--
Total UP/DOWN Session Number : 1/0
3. Associate the BFD session with the sub-interfaces.

# Configure NPE1.
[NPE1] bfd
[NPE1-bfd] quit
[NPE1] bfd NPE2
[NPE1-bfd-session-npe2] process-interface-status sub-if
# Configure NPE2.
[NPE2] bfd
[NPE2-bfd] quit
[NPE2] bfd NPE1
[NPE2-bfd-session-npe1] process-interface-status sub-if
After the configuration, run the display bfd session all verbose command on NPE1 and
NPE2, and you can find that the value of the Proc interface status field is Enable (Sub-
If).
Take the display on NPE1 as an example.
<NPE1> display bfd session all verbose
------------------------------------------------------------------------------
--
Session MIndex : 257 (One Hop) State : Up Name : npe2
------------------------------------------------------------------------------
--
Local Discriminator : 1 Remote Discriminator : 2
Session Detect Mode : Asynchronous Mode Without Echo Function

BFD Bind Type : Interface(GigabitEthernet1/0/1)

Bind Session Type : Static
Bind Peer IP Address : 224.0.0.184
NextHop Ip Address : 224.0.0.184
Bind Interface : GigabitEthernet1/0/1
FSM Board Id : 0 TOS-EXP : 7
Min Tx Interval (ms) : 1000 Min Rx Interval (ms) : 1000
Actual Tx Interval (ms): 1000 Actual Rx Interval (ms): 1000
Local Detect Multi : 3 Detect Interval (ms) : 3000
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 : 93 Session Detect TmrID : 94
Session Init TmrID : - Session WTR TmrID : -
Session Echo Tx TmrID : -
PDT Index : FSM-0 | RCV-0 | IF-0 | TOKEN-0
Session Description : -
------------------------------------------------------------------------------
--
Step 5 Configure VRRP.

l # Configure an IP address for the sub-interface on NPE1. Create VRRP group 1 on the sub-
interface and set the priority of NPE1 to 120 so that NPE1 functions as the master device in
VRRP group 1.
[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 1 virtual-ip 10.1.1.10
[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 1 priority 120
[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 1 preempt-mode timer delay 10
l # Configure an IP address for the sub-interface on NPE2. Create VRRP group 1 on the sub-
interface and retain the default priority of NPE2 so that NPE2 functions as the backup device
in VRRP group 1.
[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 1 virtual-ip 10.1.1.10
l # Bind VRRP group 1 to the BFD session on NPE1.

[NPE1-GigabitEthernet1/0/1.1] vrrp vrid 1 track bfd-session 1 peer
l # Bind VRRP group 1 to the BFD session on NPE2.

[NPE2-GigabitEthernet1/0/1.1] vrrp vrid 1 track bfd-session 2 peer
After the configuration, run the display vrrp command on NPE1, and you can find that NPE1 is
the master device. Run the display vrrp command on NPE2, and you can find that NPE2 is the
backup device.
<NPE1> display vrrp
GigabitEthernet1/0/1.1 | Virtual Router 1
State : Master
Virtual IP : 10.1.1.10
PriorityRun : 120
PriorityConfig : 120
MasterPriority : 120
Preempt : YES Delay Time : 10
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Config type : normal-vrrp

Config track link-bfd down-number : 0

Track BFD : 1 type: peer
BFD-session state : UP
<NPE2> display vrrp
State : Backup
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Step 6 Configure the Layer 2 forwarding function on CE1, PE-AGG1, PE-AGG2, and LSW1 to LSW5.
For details about the configuration, see the configuration files.
l Run the shutdown command on GE0/0/1 of LSW3 to simulate a port fault, and then run the
display sep interface command on LSW3 to check whether GE0/0/2 of LSW3 switches from
the Discarding state to the Forwarding state.
<LSW3> display sep interface gigabitethernet 0/0/2
SEP segment 1
----------------------------------------------------------------
Interface Port Role Neighbor Status Port Status
----------------------------------------------------------------
GE0/0/2 common up forwarding
l Run the shutdown command on GE1/0/1.1 of NPE1 to simulate a port fault, and then run
the display vrrp command on NPE2 to check whether NPE2 becomes the master device.
<NPE2> display vrrp
State : Master
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
----End
Configuration Files
l Configuration file of LSW1
#
sysname LSW1
#
vlan batch 10 100
#

cfm enable
#
sep segment 1
control-vlan 10
block port optimal
preempt delay 30
protected-instance 0 to 48
#
port hybrid tagged vlan 10 100
stp disable
sep segment 1 edge primary
#
port hybrid tagged vlan 100
#
cfm md md1
ma ma1
remote-mep mep-id 2
#
oam-mgr
oam-bind ingress cfm md md1 ma ma1 egress sep segment 1 interface
#
return
#
sysname LSW2
#
vlan batch 10 100
#
sep segment 1
control-vlan 10
#
stp disable
sep segment 1
#
stp disable
sep segment 1
#
return
#
sysname LSW3
#
vlan batch 10 100
#
sep segment 1
control-vlan 10
#
stp disable
sep segment 1
#
stp disable
sep segment 1

sep segment 1 priority 128

#
#
return
#
sysname LSW4
#
vlan batch 10 100
#
sep segment 1
control-vlan 10
#
stp disable
sep segment 1
#
stp disable
sep segment 1
#
return
#
sysname LSW5
#
vlan batch 10 100
#
sep segment 1
control-vlan 10
#
stp disable
sep segment 1 edge secondary
#
#
return
l Configuration file of NPE1
#
sysname NPE1
#
bfd
#
undo shutdown
ip address 11.1.1.1 255.255.255.0
#
interface GigabitEthernet1/0/1.1
vlan-type dot1q 100
ip address 10.1.1.1 255.255.255.0
vrrp vrid 1 virtual-ip 10.1.1.10
vrrp vrid 1 priority 120
vrrp vrid 1 preempt-mode timer delay 10
vrrp vrid 1 track bfd-session 1 peer
#
bfd npe2 bind peer-ip default-ip interface GigabitEthernet1/0/1
discriminator local 1
discriminator remote 2

process-interface-status sub-if
commit
#
return
l Configuration file of NPE2
#
sysname NPE2
#
bfd
#
undo shutdown
ip address 11.1.1.2 255.255.255.0
#
interface GigabitEthernet1/0/1.1
vlan-type dot1q 100
ip address 10.1.1.2 255.255.255.0
vrrp vrid 1 track bfd-session 2 peer
#
bfd npe1 bind peer-ip default-ip interface GigabitEthernet1/0/1
process-interface-status sub-if
commit
#
return
l Configuration file of PE-AGG1
#
sysname PE-AGG1
#
vlan batch 100 200
#
cfm enable
#
portswitch
undo shutdown
#
portswitch
undo shutdown
port default vlan 200
#
portswitch
undo shutdown
#
cfm md md1
ma ma1
remote-mep mep-id 1
#
return
l Configuration file of PE-AGG2
#
sysname PE-AGG2
#
vlan batch 100 200
#
portswitch

undo shutdown
#
portswitch
undo shutdown
port default vlan 200
#
portswitch
undo shutdown
#
return

#
sysname CE1
#
vlan batch 100
#
#
return
4.21.13 Example for Configuring the One-way Frame Delay

Measurement in a VLAN
When you need to estimate service qualities, you can configure the one-way frame delay
As shown in Figure 4-25, the one-way frame delay measurement is deployed on Switch A. The
interval for sending DM frames is set to 10 seconds and the number of DM frames sent each
time is also set to 10.
Figure 4-25 Networking diagram of configuring the one-way frame delay measurement in a
VLAN
SwitchC SwitchD
GE0/0/2 GE0/0/2
GE0/0/1 GE0/0/1
GE0/0/1 GE0/0/1
SwitchA SwitchB

1. Configure VLANs on Switch A, Switch B, Switch C, and Switch D.
2. Configure MDs and MAs on Switch A and Switch B.
3. Configure outward-facing MEPs on Switch A and Switch B.
4. Set the alarm thresholds of the one-way frame delay measurement on Switch A.
5. Enable the one-way frame delay measurement for the VLANs on Switch A
Data Preparation
l VLAN ID
l Alarm threshold of the one-way frame delay measurement
l Names of the MD and MA
Procedure
Step 1 Configure VLANs.
[SwitchA] vlan 2
[SwitchB] vlan 2
[SwitchC] vlan 2
[SwitchC-vlan2] quit
[SwitchC-GigabitEthernet0/0/1] port trunk allow-pass vlan 2

[SwitchD] vlan 2
[SwitchD-vlan2] quit
[SwitchD-GigabitEthernet0/0/20] port trunk allow-pass vlan 2
Step 2 Configure basic Ethernet CFM functions.

[SwitchB] cfm version standard
Step 3 Configure outward-facing MEPs.

[SwitchA-md-md1-ma-ma1] mep ccm-send mep-id 1 enable
[SwitchA-md-md1-ma-ma1] remote-mep ccm-receive mep-id 2 enable
[SwitchB-md-md1-ma-ma1] mep ccm-send mep-id 2 enable
Step 4 Set the alarm threshold for the two-way frame delay measurement to 1000 on Switch A.
[SwitchA-md-md1-ma-ma1] delay-measure two-way threshold 1000
Step 5 Configure the two-way frame delay measurement in a VLAN.


[SwitchA-md-md1-ma-ma1] delay-measure one-way receive

[SwitchA-md-md1-ma-ma1] delay-measure one-way mac 0018-82d1-b6bf interval 10000
count 10
[SwitchB-md-md1-ma-ma1] delay-measure one-way receive

# After the configuration, run the display y1731 statistics-type oneway-delay md md1 ma
ma1 command, and you can view the statistics about the one-way frame delay.
[SwitchA] display y1731 statistic-type oneway-delay md md2 ma ma2
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 2
#
cfm enable
#
#
cfm md md1
ma ma1
map vlan 2
remote-mep mep-id 2
delay-measure one-way threshold 1000
#
return

#
sysname SwitchB
#

vlan batch 2
#
cfm enable
#
interface GigabitEthernet0/0/1 outward
#
cfm md md1
ma ma1
map vlan 2
remote-mep mep-id 1
#
return

#
sysname SwitchC
#
vlan batch 2
#
#
#
return

#
sysname SwitchD
#
vlan batch 2
#
#
#
return
4.21.14 Example for Configuring the Two-way Frame Delay

Measurement in a VLAN
When you need to estimate service qualities, you can configure the two-way frame delay
As shown in Figure 4-26, the two-way frame delay measurement is deployed both on Switch
A and Switch B. The interval for sending DM frames is set to 10 seconds and the number of DM
frames sent each time is also set to 10.

Figure 4-26 Networking diagram of configuring the two-way frame delay measurement in a
VLAN
SwitchC SwitchD
GE0/0/2 GE0/0/2
GE0/0/1 GE0/0/1
GE0/0/1 GE0/0/1
SwitchA SwitchB
1. Configure VLANs on Switch A, Switch B, Switch C, and Switch D.
2. Configure MDs and MAs on Switch A and Switch B.
3. Configure outward-facing MEPs on Switch A and Switch B.
4. Set the alarm thresholds of the two-way frame delay measurement on Switch A and Switch
B.
5. Enable the two-way frame delay measurement for the VLANs on Switch A and Switch B.
Data Preparation
l VLAN ID
l Alarm threshold of the two-way frame delay measurement
l Names of the MD and MA
Procedure
Step 1 Configure VLANs.
[SwitchA] vlan 2

[SwitchB] vlan 2
[SwitchC] vlan 2
[SwitchC-vlan2] quit
[SwitchD] vlan 2
[SwitchD-vlan2] quit
Step 2 Configure basic Ethernet CFM functions.

[SwitchB] cfm version standard
Step 3 Configure outward-facing MEPs.

[SwitchA-md-md1-ma-ma1] mep ccm-send mep-id 1 enable

[SwitchB-md-md1-ma-ma1] mep ccm-send mep-id 2 enable
Step 4 Set the alarm threshold for the two-way frame delay measurement to 1000.
[SwitchA-md-md1-ma-ma1] delay-measure two-way threshold 1000
[SwitchB-md-md1-ma-ma1] delay-measure two-way threshold 1000
Step 5 Configure the two-way frame delay measurement in a VLAN.

[SwitchA-md-md1-ma-ma1] delay-measure two-way receive
[SwitchA-md-md1-ma-ma1] delay-measure two-way mac 0018-82d1-b6bf interval 10000
count 10
[SwitchB-md-md1-ma-ma1] delay-measure two-way receive
[SwitchB-md-md1-ma-ma1] delay-measure two-way mac 0018-82d1-b6be interval 10000
count 10

# After the configuration, run the display y1731 statistics-type twoway-delay md md1 ma
ma1 command, and you can view the statistics about the two-way frame delay.
[SwitchA] display y1731 statistic-type twoway-delay md md2 ma ma2


----End
Configuration Files
#
sysname SwitchA
#
vlan batch 2
#
cfm enable
#
#
cfm md md1
ma ma1
map vlan 2
remote-mep mep-id 2
delay-measure two-way threshold 1000
#
return

#
sysname SwitchB
#
vlan batch 2
#
cfm enable
#
interface GigabitEthernet0/0/1 outward
#
cfm md md1
ma ma1
map vlan 2
remote-mep mep-id 1
delay-measure two-way threshold 1000
#
return

#
sysname SwitchC
#
vlan batch 2
#


#
port default vlan 2
#
return

#
sysname SwitchD
#
vlan batch 2
#
#
#
return

Configuration Guide - Reliability 5 BFD Configuration
5 BFD Configuration
About This Chapter
This chapter describes the principle and configuration of BFD.
5.1 Introduction to BFD

This section describes the concept of Bidirectional Forwarding Detection (BFD).
5.2 BFD Features Supported by the S5300
This section describes the BFD features supported by the S5300.
5.3 Configuring Single-Hop BFD
This section describes how to configure and apply single-hop BFD.
5.4 Configuring the BFD Passive Echo Function
By configuring the BFD passive Echo function, you can implement the interworking between
the devices that support the Echo function. This function is applicable to only single-hop BFD
sessions.
5.5 Configuring Multi-Hop BFD
This section describes how to configure and apply multi-hop BFD.
5.6 Configuring a Static BFD Session with Automatically Negotiated Discriminators
This section describes how to configure a static BFD session with automatically negotiated
discriminators.
5.7 Adjusting the BFD Detection Parameters
This section describes how to adjust the BFD detection parameters.
5.8 Setting the Interval for Sending Trap Messages
5.9 Maintaining BFD
This section describes how to maintain BFD.
This section provides several configuration examples of BFD.

5 BFD Configuration Configuration Guide - Reliability
5.1 Introduction to BFD

This section describes the concept of Bidirectional Forwarding Detection (BFD).
NOTE
The S5300SI does not support BFD.
BFD is a unified detection mechanism of the entire network to detect communication faults
between forwarding devices. BFD detects the connectivity of data protocols, such as the IP
protocol, between two devices on a path.
BFD provides the following functions:
l Low-load and short-duration detection of faults on the path between adjacent forwarding
devices
l Real-time and unified detection and different detection intervals and overheads for all
media or protocol layers
5.2 BFD Features Supported by the S5300

This section describes the BFD features supported by the S5300.
The S5300s send BFD control packets based on the negotiated period. If an S5300 does not
receive the packet of the peer within the detection time, the S5300 sets the BFD session in Down
state. The upper-layer application can take actions according to the status of the BFD session.
BFD Session Establishment Supported by the S5300

BFD uses the local discriminator and remote discriminator to differentiate multiple BFD sessions
between the same pair of systems. According to the difference in the modes of creating the local
discriminator and the remote discriminator, the S5300 supports the following BFD session types:
l Static BFD sessions with manually specified discriminators

l Static BFD sessions with automatically negotiated discriminators
l Dynamic BFD sessions triggered by a protocol
A dynamic BFD session triggered by a protocol is implemented as follows:

l The local discriminator is allocated automatically.
l The remote discriminator is learned by the local end.
When the two ends of a BFD session create discriminators in different modes:
l If the discriminators on the local end are specified manually, the discriminators on the
remote end must also be specified manually.
l If you configure a static BFD session with automatically negotiated discriminators on the
local end, you can configure a static BFD session with automatically negotiated
discriminators or configure a dynamic BFD session on the peer end.
l If a static BFD session with automatically negotiated discriminators and a dynamic BFD
session are configured at the local end, the following principles are applicable:

– If the dynamic BFD session and static BFD session with automatically negotiated
discriminators share the same configurations (the source address, destination address,
outbound interface, and VPN index), the two BFD sessions coexist.
– If the dynamic BFD session named DYN_local discriminator is configured earlier than
the static BFD session with automatically negotiated discriminators, the name of the
dynamic BFD session is changed to the name of the static BFD session.
– The two BFD sessions use the smaller values of BFD parameters.
Single-Hop BFD
Single-hop BFD detects connectivity of the forwarding link between two directly connected
devices.
Between the two systems detected by the single-hop BFD session, only one BFD session can be
set up on a specified interface enabled with a specified data protocol. Therefore, each BFD
session is bound to an interface. On the S5300, BFD sessions are bound to Layer 2 interfaces.
Multi-Hop BFD
Multi-hop BFD detects IP connectivity of paths between two non-directly-connected devices.
These paths may span multiple hops or overlap. Multi-hop BFD is often used to detect reachable
routes between two devices.
The S5300 provides multi-hop BFD for static routes. Generally, static routes do not have the
detection mechanism. When a network fails, the administrator needs to check the static routes
manually. You can use multi-hop BFD to check the status of static routes. The RM module
determines whether a static route is available according to the status of the BFD session.
BFD for Static Routes

Static routes do not have a detection mechanism. When the network fails, the administrator needs
to check the static routes manually.
Through BFD for static routes, the BFD session can be used to detect the status of IPv4 static
routes on a public network. The RM module determines whether the static route is available
according to the BFD session status.
NOTE
For details on how to configure BFD for static routes, see Configuring BFD for IPv4 Static Routes on a
Public Network in the Quidway S5300 Series Ethernet Switches Configuration Guide - IP Routing.
BFD for Routing Protocols

BFD uses the local discriminator and remote discriminator to differentiate multiple BFD sessions
between the same pair of systems. OSPF support dynamic setup of BFD sessions.
The BFD session dynamically triggered by a routing protocol is implemented as follows:
l The local discriminator is allocated automatically.
l The remote discriminator is learned by the local end.
When the neighbor relationship of a routing protocol is set up successfully, the routing protocol
requests BFD to establish a BFD session through the RM module. The neighbor relationship of
the routing protocol then can be rapidly detected. The detection parameters of the BFD session
are negotiated by both ends through the routing protocol.

When a BFD session detects a fault, the BFD session becomes Down. BFD triggers route
convergence through the RM module.
When the neighbor is unreachable, the routing protocol requests BFD to delete the session
through the RM module.
Dynamically Changing Values of BFD Parameters

After a BFD session is set up, you can change the values of related parameters, such as the
expected interval for sending BFD packets, the minimum interval for receiving BFD packets,
and local detection multiplier, without affecting the status of the session.
5.3 Configuring Single-Hop BFD

This section describes how to configure and apply single-hop BFD.

5.3.2 Enabling BFD Globally
5.3.3 (Optional) Setting the Multicast IP Address of BFD
5.3.4 Creating a BFD Session
5.3.5 (Optional) Configuring the Description of a BFD Session

To quickly detect and monitor the direct links on a network, configure single-hop BFD.
Before configuring single-hop BFD, complete the following tasks:
l Connecting the interfaces
l Setting physical parameters of the interfaces
l Ensuring that the status of the physical layer of the interfaces is Up
Data Preparation
To configure single-hop BFD, you need the following data.
No. Data
1 Name of the BFD session
2 Default multicast address, type and number of the local interface, and IP address of
the remote peer (if the Layer 3 link needs to be detected)
3 Local and remote identifiers of the BFD session

Context
Do as follows on S5300s at both ends of the link to be detected.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd
BFD is enabled globally and the BFD view is displayed.
By default, BFD is disabled globally. Before configuring the BFD functions, you must enable
BFD globally; otherwise, the configuration fails.
----End
5.3.3 (Optional) Setting the Multicast IP Address of BFD
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd
The BFD view is displayed.
Step 3 Run:
default-ip-address ip-address
The multicast IP address of BFD is set.
To implement single-hop BFD on a Layer 2 forwarding link, BFD needs to use a multicast IP
address. By default, BFD uses the multicast IP address 224.0.0.184.

NOTE
l If this multicast IP address is used by other protocols on the network, you must change the multicast
IP address. The S5300s at both ends of the BFD session must use the same multicast IP address.
l If multiple BFD sessions exist on a path, for example, Layer 3 interfaces are connected through Layer
2 switching devices that support BFD, you must configure different default multicast IP addresses for
the devices where different BFD sessions are established. In this manner, BFD packets can be correctly
forwarded.
----End

Context
Procedure
Step 1 Run:
system-view

Step 2 Run the following command as required.
l If the VLANIF interface has 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 ]
– When creating a single-hop BFD session for the first time, you must bind the single-hop
BFD session to the peer IP address and the local address. In addition, the configuration
of the single-hop BFD session cannot be changed after being created.
– When BFD configuration items are created, the system checks only the format of the IP
address rather than the correctness. A BFD session cannot be established if an incorrect
peer IP address or source IP address is bound.
– When BFD and URPF are used together, UPRF checks the source IP address of the
received BFD packets. In this case, you need to specify the correct source IP address of
BFD packets by setting the source-ip parameter when binding a BFD session to prevent
BFD packets from being discarded incorrectly.
l For a Layer 2 interface, run:
bfd cfg-name bind peer-ip default-ip interface interface-type interface-number [ source-
ip source-ip ]
Step 3 Set the discriminators.
l Run:
discriminator local discr-value
The local discriminator is set.

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

When you set the discriminators, ensure that the local discriminator at the local end is the same
as the remote discriminator at the peer end; otherwise, the BFD session fails to be set up. After
local and remote discriminators are set successfully, they cannot be modified.

NOTE
For the BFD sessions that use the default multicast IP address, the local and remote discriminators must
be different.
Step 4 Run:
commit
The configuration is committed.
NOTE
After setting necessary parameters, for example, local and remote discriminators, during the creation of a
single-hop BFD session, you must run the commit command to make the configuration take effect.
----End
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd configuration-name
The BFD session view is displayed.
Step 3 Run:
description description
The description of a BFD session is configured.
By default, the description of a BFD session is null.
----End
Procedure
l Run the display bfd configuration { all | static [ for-ip | name cfg-name ] |
discriminator local-discr-value | dynamic | peer-ip peer-ip [ vpn-instance vpn-name ] |
static-auto } [ verbose ] command to check the configuration of BFD.
l Run the display bfd interface [ interface-type interface-number ] command to check
information about the interface where BFD is enabled.
l Run the display bfd session { { all |static } [ for-ip ] | discriminator discr-value |
dynamic | peer-ip peer-ip [ vpn-instance vpn-name ] | static-auto } [ verbose ] command
to check information about a BFD session.

l Run the display bfd statistics session { { all | static } [ for-ip ] | discriminator discr-
value | dynamic | peer-ip peer-ip [ vpn-instance vpn-name ] | static-auto } command to
check the statistics on a BFD session.
----End
Example
Run the display bfd configuration command, and you can view the configuration of a BFD
session.
<Quidway> display bfd configuration static name bfd2 verbose
--------------------------------------------------------------------------------
BFD Session Configuration Name : bfd2
--------------------------------------------------------------------------------
BFD Bind Type : Interface(Vlanif110)
Bind Interface : Vlanif110
TOS-EXP : 7 Local Detect Multi : 3
Proc Interface Status : Disable WTR Interval (ms) : -
Bind Application : No Application Bind
--------------------------------------------------------------------------------
Run the display bfd interface command, and you can view information about the BFD session
on a specified interface.
<Quidway> display bfd interface GigabitEthernet0/0/1
--------------------------------------------------------------------------------
Interface Name MIndex Sess-Count BFD-State
--------------------------------------------------------------------------------
GigabitEthernet0/0/1 256 1 up
--------------------------------------------------------------------------------
Run the display bfd session command, and you can view information about a BFD session.
<Quidway> display bfd session all
--------------------------------------------------------------------------------
Local Remote PeerIpAddr State Type InterfaceName
--------------------------------------------------------------------------------
20 10 224.0.0.184 UP S_IP_IF GigabitEthernet0/0/1
--------------------------------------------------------------------------------
Run the display bfd statistics session command, and you can view the statistics on a BFD
session.
<Quidway> display bfd statistics session static for-ip
--------------------------------------------------------------------------------
Session MIndex : 4097 (One Hop) State : Init Name : 9to6
--------------------------------------------------------------------------------
Session Type : Static
Bind Type : IP
Local/Remote Discriminator : 20/10
Received Packets : 97
Send Packets : 314
Received Bad Packets : 169
Send Bad Packets : 0
Down Count : 32
ShortBreak Count : 0
Send Lsp Ping Count : 0
Dynamic Session Delete Count : 0
Create Time : 2007/10/14 16:48:13
Last Down Time : 2007/10/14 17:09:11

Total Time From Last DOWN : ---D:--H:--M:--S

Total Time From Create : 000D:00H:20M:59S
--------------------------------------------------------------------------------
Total Session Number : 1
5.4 Configuring the BFD Passive Echo Function

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

Before configuring the BFD passive Echo function, familiarize yourself with the applicable
environment, complete the pre-configuration tasks, and obtain the required data. This can help
you complete the configuration task quickly and accurately.
5.4.2 Configuring the BFD Passive Echo Function
In special scenarios that require interworking between a local device and the device that supports
the Echo function, you can configure the BFD passive Echo function.
By viewing the status, type, and Echo function status of a BFD session, you can check whether
the configurations are successful.

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

SwitchA SwitchB
Single-hop BFD
SwitchA Supports BFD SwitchB Supports BFD

Passive Echo Function Echo Function
As shown in Figure 5-1, the passive Echo function needs to be enabled on Switch 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 that
encapsulates the BFD Echo packet, the destination address and the source address are the IP address of the
outgoing interface of the local end. Therefore, in the ACL rule, both the source addresses of the remote
end and the local end must be permitted.
Data Preparation
To configure the BFD passive Echo function, you need the following data.
No. Data
1 (Optional) ACL number
5.4.2 Configuring the BFD Passive Echo Function

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


By viewing the status, type, and Echo function status of a BFD session, you can check whether
the configurations are successful.
Prerequisite
The configurations of the BFD passive echo function are complete.
Procedure
Step 1 Run the display bfd session{ { all |static } [ for-ip ] | discriminator discr-value | dynamic |
peer-ip peer-ip [ vpn-instance vpn-name ] | static-auto } [ verbose ] command to check
information about the BFD session.
----End
Example
# Display information about all the BFD sessions.
<Quidway> display bfd session all verbose
--------------------------------------------------------------------------------
Session MIndex : 258 (One Hop) State : Up Name : bfd2
--------------------------------------------------------------------------------
Echo Passive : Enable Acl Number : -
Proc Interface Status : Disable
WTR Interval (ms) : -
Active Multi : 3
--------------------------------------------------------------------------------
The command output shows that the Echo Passive field indicates Enable, which means that the
passive echo function is enabled for the BFD session. If the Echo Passive field indicates
Disable, this means that the passive echo function is disabled for the BFD session. The passive
echo function can be enabled for a BFD session only when the passive echo function is globally
enabled, the ACL rule (if configured) is matched, and the echo function is enabled on the peer.
5.5 Configuring Multi-Hop BFD

This section describes how to configure and apply multi-hop BFD.


To quickly detect and monitor the connectivity of IP routes between S5300s, configure multi-
hop BFD.
Before configuring multi-hop BFD, complete the following tasks:
l Connecting the interfaces and setting the physical parameters for the interfaces to ensure
that the status of the physical layer of the interfaces is Up
l Setting the link layer protocol parameters (and IP addresses) of interfaces to ensure that the
link layer of interfaces is Up
l Configuring the routing protocol to ensure that the IP routes between nodes are reachable
Data Preparation
To configure multi-hop BFD, you need the following data.
No. Data
1 IP address of the peer device
3 Local and remote identifiers of the BFD session
Context
Procedure
Step 1 Run:
system-view

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

By default, BFD is disabled globally. Before configuring the BFD functions, you must enable
BFD globally; otherwise, the configuration fails.
----End

Context
If Unicast Reverse Path Forwarding (URPF) is enabled on a device on the transmission path of
BFD packets, this device checks the source IP address of the BFD packets. In this case, you can
specify the correct source IP address of BFD packets by setting the source-ip parameter when
creating a BFD session to prevent BFD packets from being discarded.
Procedure
Step 1 Run:
system-view

Step 2 Run:bfd cfg-name bind peer-ip peer-ip [ vpn-instance vpn-instance-name ] [ source-ip source-
ip ] A BFD session is created.
l When creating a BFD session for the first time, you must bind the BFD session to the peer
IP address. In addition, the configuration of the BFD session cannot be changed after being
created.
l When the BFD configuration items are created, the system checks only the format of the IP
address rather than the correctness. A BFD session cannot be established if an incorrect peer
IP address or source IP address is bound.
l When BFD and URPF are used together, UPRF checks the source IP address of the received
BFD packets. In this case, you need to specify the correct source IP address of BFD packets
by setting the source-ip parameter when creating a BFD session to prevent BFD packets
from being discarded incorrectly.
Step 3 Set the identifiers.
l Run:
discriminator local discr-value
The local discriminator is set.

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

NOTE
When you set the discriminators, ensure that the local discriminator at the local end is the same as the
remote discriminator at the peer end; otherwise, the BFD session fails to be set up.
Step 4 Run:

commit
NOTE
After setting necessary parameters, for example, local and remote discriminators, during the creation of a
single-hop BFD session, you must run the commit command to make the configuration take effect.
----End
Context
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
description description
The description of a BFD session is configured.
By default, the description of a BFD session is null.
----End
Procedure
l Run the display bfd configuration { all | static [ for-ip | name cfg-name ] |
discriminator local-discr-value | dynamic | peer-ip peer-ip [ vpn-instance vpn-name ] |
static-auto } [ verbose ] command to check the configuration of BFD.
l Run the display bfd session { { all |static } [ for-ip ] | discriminator discr-value |
dynamic | peer-ip peer-ip [ vpn-instance vpn-name ] | static-auto } [ verbose ] command
to check information about a BFD session.
l Run the display bfd statistics session { { all | static } [ for-ip ] | discriminator discr-
value | dynamic | peer-ip peer-ip [ vpn-instance vpn-name ] | static-auto } command to
check the statistics on a BFD session.
----End

Example
Run the display bfd configuration command, and you can view the configuration of a BFD
session.
<Quidway> display bfd configuration static name bfd1 verbose
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
<Quidway> display bfd session discriminator 20 verbose
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Active Multi : 3
--------------------------------------------------------------------------------
Run the display bfd statistics session command, and you can view statistics a BFD session.
<Quidway> display bfd statistics session all
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Session Type : Static
Bind Type : IP
Local/Remote Discriminator : 22/11
Received Packets : 178
Send Packets : 177
Received Bad Packets : 0
Send Bad Packets : 0
Down Count : 0
ShortBreak Count : 0
Send Lsp Ping Count : 0
Dynamic Session Delete Count : 0

Create Time : 2007/10/14 22:26:53

Last Down Time : 0000/00/00 00:00:00
Total Time From Last DOWN : ---D:--H:--M:--S
Total Time From Create : 000D:00H:03M:03S
--------------------------------------------------------------------------------
Total Session Number : 1
5.6 Configuring a Static BFD Session with Automatically

Negotiated Discriminators
This section describes how to configure a static BFD session with automatically negotiated
discriminators.

5.6.2 Enabling Global BFD
5.6.3 Configuring a Static BFD Session with Automatically Negotiated Discriminators

If a dynamic BFD session is adopted by the remote device, you must configure a static BFD
session with automatically negotiated discriminators on the local device to interwork with the
remote device and support the static route to track BFD.
To configure a static BFD session with automatically negotiated discriminators, you need the
following data. To configure a static BFD session with automatically negotiated discriminators,
you need the following data.
l Connecting interfaces
l Assigning IP addresses to Layer 3 interfaces
Data preparation
To configure a static BFD session with automatically negotiated discriminators, you need the
following data.
No. Data
1 Configuration name of the BFD session
2 IP addresses of the local and remote ends of the link detected by BFD, and name and
number of the local interface
5.6.2 Enabling Global BFD

Context
Do as follows on the Switch on which the static BFD session with automatically negotiated
discriminators is used to detect the link.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd
Global BFD is enabled on the local node and the BFD view is displayed.
----End
5.6.3 Configuring a Static BFD Session with Automatically

Negotiated Discriminators
Context
Do as follows on the Switch where the static BFD session with automatically negotiated
discriminators is used to detect the link.
Procedure
Step 1 Run:
system-view
Step 2 Run:
bfd cfg-name bind peer-ip ip-address [ vpn-instance vpn-name ] [ interface
interface-type interface-number] source-ip ip-address auto
A BFD session with different parameters is created according to the detected link type.
When creating a BFD session, you must:
l Specify the source IP address.

l Specify the peer IP address instead of the multicast IP address.
Step 3 Run:
commit
----End

Context
The configurations of creating a static BFD session with automatically negotiated discriminators
are complete.
Procedure
Step 1 Run the display bfd session { all | static | dynamic | discriminator discr-value | peer-ip peer-
ip [ vpn-instance vpn-name ] } [ verbose ] command to check information about a BFD session.
----End
Example
# Display detailed information about all the BFD sessions.
<Quidway> display bfd session all verbose
--------------------------------------------------------------------------------
Session MIndex : 256 (Multi Hop) State : Up Name : bfd1
--------------------------------------------------------------------------------
BFD Bind Type : Peer IP Address
Bind Interface : -
Active Multi : 3
Last Local Diagnostic : Neighbor Signaled Session Down(Receive AdminDown)
--------------------------------------------------------------------------------
You can view that a BFD session with the type as Static_Auto is established. The local
discriminator and the remote discriminator of this BFD session are 8100 and 8101 respectively,
which are obtained through automatic negotiation.
5.7 Adjusting the BFD Detection Parameters

This section describes how to adjust the BFD detection parameters.

5.7.2 Adjusting the BFD Detection Time

5.7.3 Setting the WTR Time of a BFD Session

5.7.4 Setting the Priority of BFD Packets
When you set up a BFD session, you can adjust the expected interval for sending BFD packets,
the minimum interval for receiving BFD packets, and local detection multiplier, according to
the network and performance requirements.
You can set the WTR time of the BFD session to avoid frequent switchover of upper layer
applications caused by the BFD session flapping.
The default settings are recommended.
Before adjusting the BFD detection parameters, complete the following task:
l Creating a BFD session
Data Preparation
To adjust the BFD detection parameters, you need the following data.
No. Data
2 Expected interval for sending BFD packets and the minimum interval for receiving
BFD packets
3 Local detection multiplier of BFD packets
4 Priority of BFD packets
5.7.2 Adjusting the BFD Detection Time
Context
To reduce the usage of system resource, when detecting that the BFD session becomes Down,
the system sets the intervals for sending and receiving BFD packets at the local end to a random
value between 1000 and 3000 milliseconds. When the BFD session recovers, the intervals set
by the user are used.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
min-tx-interval interval
The expected interval for sending BFD packets is set.

By default, the interval for sending BFD control packets is 1000 ms.
NOTE
Currently, the value can only be 1000ms.
Step 4 Run:
min-rx-interval interval
The minimum interval for receiving BFD packets is set.

By default, the interval for receiving BFD control packets is 1000 ms.
NOTE
Currently, the value can only be 1000ms.
Step 5 Run:
detect-multiplier multiplier
The local detection time multiplier is set.

By default, the local detection multiplier is 3.
Step 6 Run:
commit
The configuration takes effect.
----End
5.7.3 Setting the WTR Time of a BFD Session

Context
Network instability results in frequent status changes of a BFD session, while the upper layer
application takes actions according to the status of the BFD session. This causes frequent status
changes of the upper layer application.
To avoid the problem, you can set the WTR time of the BFD session. When the BFD session
changes from Down to Up, BFD reports the change to the upper layer application only after the
WTR timer times out. When the BFD session changes from Up to Down, BFD reports the change
to the upper layer application immediately.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
wtr wtr-value
The WTR time is set.

By default, the WTR time is 0 minute. That is, BFD reports the change to the upper layer
application immediately.
NOTE
The BFD session is unidirectional. If the WTR time is set, you need to set the same WTR time at both ends.
Otherwise, when the session status changes at one end, applications at both ends obtain different BFD
session status.
Step 4 Run:
commit
----End
5.7.4 Setting the Priority of BFD Packets

Context
You can change the priority of BFD packets to:
l Check whether packets of different priorities on the same link can be forwarded.
l Ensure that BFD packets with a higher priority are forwarded first.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:

tos-exp tos
The priority of BFD packets is set.

By default, the priority of BFD packets is 7, which is the highest priority. The value 0 is the
lowest priority.
Step 4 Run:
commit
----End
Procedure
Step 1 Run thedisplay bfd configuration { all | static [ for-ip | name cfg-name ] | discriminator local-
discr-value | dynamic | peer-ip peer-ip [ vpn-instance vpn-name ] | static-auto } [ verbose ]
commands to check the configuration of BFD.
Step 2 Run the display bfd session { { all | static } [ for-ip ] | discriminator discr-value | dynamic |
peer-ip peer-ip [ vpn-instance vpn-name ] | static-auto } [ verbose ] command to check
information about a BFD session.
----End
Example
# Run the display bfd configuration command, and you can view the configuration of BFD.
<Quidway> display bfd configuration static for-ip verbose
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Total Commit/Uncommit CFG Number : 1/0
<Quidway> display bfd session all for-ip verbose
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Active Multi : 3
--------------------------------------------------------------------------------
5.8 Setting the Interval for Sending Trap Messages

5.8.2 Setting the Interval for Sending Trap Messages

If BFD is enabled with the SNMP alarm function, the NMS can receive the BFD Up or Down
message. If the BFD session flaps, the NMS receives a large number of trap messages. In this
case, BFD trap messages need to be suppressed. You can prevent overflow of trap messages by
setting the interval for sending trap messages.
Before setting the interval for sending trap messages, complete the following task:
l Enabling global BFD
Data Preparation
To set the interval for sending trap messages, you need the following data.
No. Data
1 Interval for sending trap messages

5.8.2 Setting the Interval for Sending Trap Messages

Context
Do as follows on the switch where the interval for sending trap messages needs to be set.
Procedure
Step 1 Run:
system-view

Step 2 Run:
bfd
Global BFD is enabled 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

Prerequisite
The configurations of setting the interval for sending trap messages are complete.
Procedure
l Run the display current-configuration configuration bfd command to check the BFD
alarm function.
----End
Example
Run the display current-configuration configuration bfd command, and you can view that
the interval for sending trap messages is 300s.
<Quidway> display current-configuration configuration bfd
#
bfd
snmp-agent bfd trap-interval 300
#
return
5.9 Maintaining BFD

This section describes how to maintain BFD.
5.9.1 Clearing the Statistics of BFD

5.9.2 Debugging BFD
5.9.1 Clearing the Statistics of BFD
Context
To clear the statistics of BFD, run the following command in the user view.
Procedure
Step 1 Run the reset bfd statistics { all | discriminator discr-value } command to clear the statistics
of BFD.
----End
5.9.2 Debugging BFD
Context
CAUTION
When a BFD fault occurs, run the following debugging command in the user view to locate the
fault.
Procedure
Step 1 Run the debugging bfd { all | defect-detect |error | event | fsm | ha | message-list | packet |
process | product-interface |session-management | timer } command to enable debugging of
the BFD module.
----End

This section provides several configuration examples of BFD.
5.10.1 Example for Configuring Single-Hop BFD on a Layer 2 Interface

5.10.2 Example for Configuring Single-Hop BFD on a VLANIF Interface
5.10.3 Example for Configuring Multi-Hop BFD

5.10.1 Example for Configuring Single-Hop BFD on a Layer 2

Interface
Interfaces of the S5300 are Layer 2 interfaces. If you need to detect the connectivity of the Layer
2 forwarding link between two directly connected S5300s, configure single-hop BFD, and bind
the BFD session to a multicast IP address and local interface.
As shown in Figure 5-2, a BFD session is created to detect the connectivity of the Layer 2 link
between Switch A and Switch B.
Figure 5-2 Networking diagram of single-hop BFD (for Layer 2 forwarding link)
GE0/0/1 GE0/0/1
SwitchA SwitchB
1. Configure a BFD session on Switch A to detect the direct link from Switch A to Switch B.
2. Configure a BFD session on Switch B to detect the direct link from Switch B to Switch A.
Data Preparation
l Type and number of the interface bound to the BFD session

l Local and remote identifiers of the BFD session
Use the default values of the minimum sending interval, the minimum receiving interval, and
the local detection multiplier of BFD control packets.
Procedure
Step 1 Configure single-hop BFD on Switch A.
# Enable BFD on Switch A.

[SwitchA] bfd
[SwitchA-bfd] quit
# Create a BFD session on Switch A.

[SwitchA] bfd atob bind peer-ip default-ip interface gigabitethernet 0/0/1
[SwitchA-bfd-session-atob] discriminator local 1
[SwitchA-bfd-session-atob] discriminator remote 2

[SwitchA-bfd-session-atob] commit
[SwitchA-bfd-session-atob] quit
Step 2 Configure single-hop BFD on Switch B.

# Enable BFD on Switch B.
[SwitchB] bfd
[SwitchB-bfd] quit
# Create a BFD session on Switch B.

[SwitchB] bfd btoa bind peer-ip default-ip interface gigabitethernet 0/0/1
[SwitchB-bfd-session-btoa] discriminator local 2
[SwitchB-bfd-session-btoa] discriminator remote 1
[SwitchB-bfd-session-btoa] commit
[SwitchB-bfd-session-btoa] quit

After the configuration, run the display bfd session command on Switch A and Switch B, and
you can find that a single-hop BFD session is set up and is in Up state.
Take Switch A for example. The display is as follows:
<SwitchA> display bfd session all verbose
--------------------------------------------------------------------------------
Session MIndex : 257 (One Hop) State : Up Name : atob
--------------------------------------------------------------------------------
BFD Bind Type : Interface(GigabitEthernet0/0/1)
Bind Interface : GigabitEthernet0/0/1
Active Multi : 3
--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname SwitchA
#
bfd
#

bfd atob bind peer-ip default-ip interface GigabitEthernet0/0/1

commit
#
return

#
sysname SwitchB
#
bfd
#
bfd btoa bind peer-ip default-ip interface GigabitEthernet0/0/1
commit
#
return
5.10.2 Example for Configuring Single-Hop BFD on a VLANIF

Interface
The S5300s are connected through the VLANIF interface at Layer 3. To detect the connectivity
of the link between two directly connected S5300s, you can configure single-hop BFD to bind
the BFD session to the VLANIF interface and its IP address.
As shown in Figure 5-3, a BFD session is created to detect the connectivity of the link between
SwitchA and SwitchB.
Figure 5-3 Networking diagram for configuring single-hop BFD on a VLANIF interface
VLANIF 13 VLANIF 13
10.1.1.5/24 10.1.1.6/24
GE0/0/1 GE0/0/1
SwitchA SwitchB
1. Create VLAN 13 on SwitchA and SwitchB.
2. Configure GE 0/0/1 interfaces on SwitchA and SwitchB as hybrid interfaces.
3. Create VLANIF 13 on SwitchA and SwitchB and set their IP addreses.
4. Create a BFD session on SwitchA to detect the link between SwitchA and SwitchB.
5. Create a BFD session on SwitchB to detect the link between SwitchB and SwitchA.
Data Preparation

l Numbers of VLANIF interfaces bound to BFD sessions

l IP addresses of VLANIF interfaces
l Local and remote discriminators of BFD sessions
Default values of minimum intervals for sending BFD control packets, minimum intervals for
receiving BFD control packets, and local detection multipliers
Procedure
Step 1 On SwitchA and SwitchB, create VLAN 13, configure GE 0/0/1 interfaces as hybrid interfaces,
and add GE 0/0/1 interfaces to VLAN 13.
[SwitchA] vlan 13
[SwitchA-GigabitEthernet0/0/1] port hybrid pvid vlan 13
[SwitchA-GigabitEthernet0/0/1] port hybrid untagged vlan 13
[SwitchB] vlan 13
[SwitchB-GigabitEthernet0/0/1] port hybrid pvid vlan 13
[SwitchB-GigabitEthernet0/0/1] port hybrid untagged vlan 13
Step 2 Set IP addresses of VLANIF 13 interfaces so that SwitchA can communicate with SwitchB at
Layer 3.
[SwitchA] interface vlanif13
[SwitchA-Vlanif13] ip address 10.1.1.5 24
[SwitchA-Vlanif13] quit
[SwitchB] interface vlanif13
[SwitchB-Vlanif13] ip address 10.1.1.6 24
[SwitchB-Vlanif13] quit
After the configuration, run the display interface vlanif command on SwitchA or SwitchB. You
can view that the status of VLANIF 13 is Up.
[SwitchA] display interface vlanif 13
Vlanif13 current state : UP
Line protocol current state : UP
Last line protocol up time : 2008-12-16 05:40:48
Description:HUAWEI, Quidway Series, Vlanif13 Interface
Route Port,The Maximum Transmit Unit is 1500
Internet Address is 11.1.1.2/24
IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 0018-82d1-b6df

Input bandwidth utilization : --

Output bandwidth utilization : --
Step 3 Configure single-hop BFD on SwitchA.

# Enable BFD on SwitchA.
[SwitchA] bfd
[SwitchA-bfd] quit
# Create a BFD session on SwitchA.

[SwitchA] bfd atob bind peer-ip 10.1.1.6 interface vlanif 13
Step 4 Configure single-hop BFD on SwitchB.

# Enable BFD on SwitchB.
[SwitchB] bfd
[SwitchB-bfd] quit
# Create a BFD session on SwitchB.

[SwitchB] bfd btoa bind peer-ip 10.1.1.5 interface vlanif 13

After the configuration, run the display bfd session command on SwitchA and SwitchB. You
can view that the single-hop BFD session is set up and the status is Up.
Take the display on SwitchA as an example.
--------------------------------------------------------------------------------
Session MIndex : 256 (Multi Hop) State : Up Name : atob
--------------------------------------------------------------------------------
BFD Bind Type : Interface
(Vlanif13)
Bind Interface :
Vlanif13
Active Multi : 3
Last Local Diagnostic : Neighbor Signaled Session Down(Receive AdminDown)


--------------------------------------------------------------------------------
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 13
#
bfd
#
interface Vlanif13
ip address 10.1.1.5 255.255.255.0
#
port hybrid pvid vlan 13
port hybrid untagged vlan 13
#
bfd atob bind peer-ip 10.1.1.6 interface Vlanif13
commit
#
return

#
sysname SwitchB
#
vlan batch 13
#
bfd
#
interface Vlanif13
ip address 10.1.1.6 255.255.255.0
#
#
bfd atob bind peer-ip 10.1.1.5 interface Vlanif13
commit
#
return
5.10.3 Example for Configuring Multi-Hop BFD

As shown in Figure 5-4, a BFD session is used to test the multi-hop path between Switch A and
Switch C.
Interfaces of the S5300 are Layer 2 interfaces. To configure multi-hop BFD, you need to add an
interface to a VLAN, create a VLANIF interface, and assign an IP address to the VLANIF
interface.

Figure 5-4 Networking diagram of multi-hop BFD
GE0/0/1 GE0/0/1 GE0/0/2 GE0/0/1
VLAN 10 VLAN 20
SwitchA
SwitchB SwitchC
1. Configure a BFD session on Switch A to detect the multi-hop path from Switch A to Switch
C.
2. Configure a BFD session on Switch C to detect the multi-hop path from Switch C to Switch
A.
Data Preparation
l Peer IP address bound to the BFD session

l Local and remote identifiers of the BFD session
l IP address of VLANIF 10 on Switch A: 10.1.1.1/16
l IP address of VLANIF 10 on Switch B: 10.1.1.2/16
l IP address of VLANIF 20 on Switch B: 10.2.1.1/16
l IP address of VLANIF 20 on Switch C: 10.2.1.2/16
Use the default values of the minimum sending interval, the minimum receiving interval, and
the local detection multiplier of a BFD control packet.
Procedure
Step 1 Add interfaces to VLANs, create VLANIF interfaces, and assign an IP address to each VLANIF
interface.
# Create a VLAN on Switch A and add the interface to the VLAN.

[SwitchA] vlan batch 10
# Create a VLNAIF interface and assign an IP address to the VLANIF interface.

[SwitchA] interface vlanif 10

The configurations of Switch B and Switch C are the same as the configuration of Switch A,
and are not mentioned here.
Step 2 Configure a reachable static route between Switch A and Switch C.
[SwitchA] ip route-static 10.2.0.0 16 10.1.1.2
The configuration of Switch C is the same as the configuration of Switch A, and is not mentioned
here.
Step 3 Configure multi-hop BFD on Switch A and Switch C.
# Create a BFD session with Switch C on Switch A.
[SwitchA] bfd
[SwitchA-bfd] quit
[SwitchA] bfd atoc bind peer-ip 10.2.1.2
[SwitchA-bfd-session-atoc] discriminator local 10
[SwitchA-bfd-session-atoc] discriminator remote 20
[SwitchA-bfd-session-atoc] commit
[SwitchA-bfd-session-atoc] quit
# Create a BFD session with Switch A on Switch C.

[SwitchC] bfd
[SwitchC-bfd] quit
[SwitchC] bfd ctoa bind peer-ip 10.1.1.1
[SwitchC-bfd-session-ctoa] discriminator local 20
[SwitchC-bfd-session-ctoa] discriminator remote 10
[SwitchC-bfd-session-ctoa] commit
[SwitchC-bfd-session-ctoa] quit

After the configuration is complete, run the display bfd session command on Switch A and
Switch C, and you can find that a BFD session is set up and is in Up state.
Take Switch A for example. The display is as follows:
--------------------------------------------------------------------------------
Session MIndex : 4096 (Multi Hop) State : Up Name : atoc
--------------------------------------------------------------------------------
BFD Bind Type : Peer IP Address
Bind Interface : -
Active Multi : 3
Last Local Diagnostic : Control Detection Time Expired
Session TX TmrID : 16445 Session Detect TmrID : -
Session Init TmrID : 16447 Session WTR TmrID : -
--------------------------------------------------------------------------------

----End
Configuration Files
#
sysname SwitchA
#
vlan batch 10
#
bfd
#
interface Vlanif10
ip address 10.1.1.1 255.255.0.0
#
#
bfd atoc bind peer-ip 10.2.1.2
commit
#
ip route-static 10.2.0.0 255.255.0.0 10.1.1.2
#
return

#
sysname SwitchB
#
vlan batch 10 20
#
interface Vlanif10
ip address 10.1.1.2 255.255.0.0
#
interface Vlanif20
ip address 10.2.1.1 255.255.0.0
#
#
#
return

#
sysname SwitchC
#
bfd
#
vlan batch 20
#
interface Vlanif20
ip address 10.2.1.2 255.255.0.0
#
#
bfd ctoa bind peer-ip 10.1.1.1

commit
#
ip route-static 10.1.0.0 255.255.0.0 10.2.1.1
#
return

Configuration Guide - Reliability 6 VRRP Configuration
6 VRRP Configuration
About This Chapter
This chapter describes the principle, basic functions, and advanced functions of the Virtual
Router Redundancy Protocol (VRRP).
6.1 Introduction to VRRP

This section describes the concept of VRRP.
6.2 VRRP Features Supported by the S5300
This section describes the VRRP features supported by the S9300.
6.3 Configuring a VRRP Backup Group
This section describes how to configure a VRRP backup group.
6.4 Configuring VRRP to Track the Interface Status
This section describes how to configure VRRP to track the interface status to improve system
reliability.
6.5 Configuring VRRP to Tracking the BFD Session Status
This section describes how to configure VRRP to track the BFD session status to implement fast
switchover.
6.6 Configuring VRRP Authentication
This section describes how to configure the authentication function in a VRRP group.
6.7 Optimizing the VRRP Performance
This section describes how to optimize the VRRP performance by modifying the parameters of
VRRP packets.
6.8 Configuring mVRRP Backup Groups
An mVRRP backup group can be bound to other member backup groups and determine the
status of member backup groups according to the bindings. This is applicable to the scenario
where a device is dual-homed to master and slave devices on a MAN.
6.9 Configuring VRRP Version Upgrade
After being upgraded from version 2 to version 3, VRRP can support both IPv6 and IPv4
networks.
6.10 Maintaining VRRP

6 VRRP Configuration Configuration Guide - Reliability
This section describes how to monitor running of VRRP and debug VRRP.
This section provides several configuration examples of VRRP.

6.1 Introduction to VRRP

This section describes the concept of VRRP.
NOTE
The S5300SI does not support VRRP.
Generally, all hosts on an internal network are configured with the same default route to the
egress gateway, that is, Switch A in Figure 6-1. Thus, hosts can communicate with external
networks. If the egress gateway fails, communication between hosts and external networks is
interrupted.
Figure 6-1 Default gateway of a LAN
Gateway:10.0.0.1
IP Address:10.0.0.2/24
10.0.0.1/24
Gateway:10.0.0.1
IP Address:10.0.0.3/24 Network
Gateway:10.0.0.1 SwitchA
IP Address:10.0.0.4/24
Ethernet
Configuring more than one egress gateway is usually adopted to enhance the system reliability.
The problem of route selection, however, arises.
VRRP is a fault tolerance protocol defined by RFC 2338. It solves the route selection problem
among many gateways by separating physical devices and logical devices.
On a LAN enabled with multicast or broadcast, for example, Ethernet, VRRP offers logical
gateways to ensure high availability links. This prevents service interruption caused by faults of
the gateway, without changing the configuration of routing protocols.
6.2 VRRP Features Supported by the S5300

This section describes the VRRP features supported by the S9300.
VRRP in Master/Backup Mode

The master/backup mode is the basic backup mode provided by VRRP. In this mode, you need
to create a virtual router, which consists of a master device and several backup devices. A virtual
router is a backup group. Normally, the master device processes all the services. When the master
device fails, the backup devices take over the services.

VRRP in Load Balancing Mode

In load balancing mode, you need to create two or more backup groups to share the service load.
A switch can function as the backup device of multiple backup groups and has different priorities
in these backup groups. You can configure multiple backup groups to implement load balancing.
Each backup group consists of a master device and multiple backup devices. These backup
groups can have different master devices.
Interface Status Monitoring

The S5300 can monitor the status of the interfaces in a backup group. When the status of an
interface changes, the priority of the switch changes. Therefore, the sequence of priorities among
the switches in the backup groups changes, and VRRP selects a new master switch.
VRRP Fast Switchover

The S5300 supports bidirectional forwarding detection (BFD), which detects connectivity of
links and routes on the network. VRRP monitors the status of BFD sessions to perform fast
switchover between the master and backup switches. You can configure up to eight BFD
sessions. The switchover can be complete within 1 second. Working with the BFD sessions,
VRRP shortens the duration of the switchover.
Ping to the Virtual IP Address

A VRRP backup group uses a virtual IP address. Failure to ping the virtual IP address causes
problems during the operation of the switch. Ping to the virtual IP address helps to monitor the
operation of the switch but brings risk of Internet Control Message Protocol (ICMP) attacks.
The S5300 provides a command to control the ping to the virtual IP address. You can determine
whether to enable the ping to the virtual IP address according to your requirements.
VRRP Security
For network environments of different security levels, you can set different authentication modes
and passwords in the packet headers.
On a secure network, the default setting can be adopted. That is, the S5300 does not authenticate
the sent or received VRRP packets, and considers that all the received packets are valid. In this
case, you do not need to set the password.
On a network where security is not guaranteed, VRRP provides the simple text authentication.
You can set a password of 1 to 8 characters.
6.3 Configuring a VRRP Backup Group

This section describes how to configure a VRRP backup group.

6.3.2 Creating a VRRP Group and Configuring the Virtual IP Address
6.3.3 Setting the Priority of an Interface in a Backup Group
6.3.4 (Optional) Configuring the Sending Mode of VRRP Packets in Super-VLAN

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

A VRRP backup group works in master/backup mode or load balancing mode.
l The master/backup mode is the basic mode and the principle is as follows:
– Only one backup group is configured.
– The switch with the highest priority in the backup group functions as the master switch
to transmit packets.
– Other switches function as the backup switches and are in monitoring state.
– If the master switch fails, a new master is selected among the backup switches to provide
the routing function.
l In load balancing mode, multiple backup groups are created to share the network traffic.
A switch may belong to multiple backup groups. The principle of the load balancing mode
is as follows:
– Switch A functions as the master switch of backup group 1 and backup switch of backup
group 2.
– Switch B functions as the master switch of backup group 2 and backup switch of backup
group 1.
– Certain hosts use backup group 1 as the gateway, and other hosts use backup group 2
as the gateway.
In this mode, backup groups implement backup and load balancing simultaneously.
NOTE
On the S5300, VRRP functions can be configured only on VLANIF interfaces.
Before configuring a VRRP group, complete the following tasks:
l Setting physical parameters of each interface
l Setting the link-layer parameters of each interface
l Setting the network-layer parameters of each interface to ensure connectivity of the network
Data Preparation
To configure a VRRP backup group, you need the following data.
No. Data
1 VRRP backup group ID
2 Virtual IP address of the VRRP backup group
3 Priorities of switches in the VRRP backup group

6.3.2 Creating a VRRP Group and Configuring the Virtual IP

Address
Context
Do as follows on the S5300s in a VRRP group.
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface vlanif interface-number
The VLANIF interface view is displayed.
Step 3 Run:
vrrp vrid virtual-router-id virtual-ip virtual-address
A VRRP group is created and a virtual IP address is assigned to the VRRP group.
NOTE
l On the S5300, VRRP functions can be configured only on VLANIF interfaces.

l The virtual IP address must be in the same network segment as the IP address of the VLANIF interface.
l Virtual IP addresses of VRRP groups cannot be the same.
l The virtual router IDs of VRRP groups cannot be the same.
l The devices in the same VRRP group must use the same virtual router ID.
l When configuring both a VRRP group and a VRRP6 group, set different virtual router IDs for the two
groups.
When you assign the first IP address to a VRRP group, the system creates the VRRP group.
When you assign additional virtual IP addresses to the VRRP group, the system adds the virtual
IP addresses to the virtual address list of the VRRP group.
For users with the same VRRP reliability requirements on the network, you can assign multiple
virtual IP addresses to the same VRRP group. These virtual IP addresses serve different user
groups. This facilitates user management and prevents default gateways of users from changing
with the VRRP configuration. Each VRRP group can be assigned 16 virtual IP addresses.
To implement load balancing among VRRP groups, you need to repeat the preceding steps to
create multiple VRRP groups. At least two VRRP groups need to be configured on an interface.
VRRP groups are identified by virtual router IDs. Virtual IP addresses of the VRRP groups
cannot be the same.
NOTE
You can configure up to 64 VRRP groups on each interface of the S5300. To configure 64 VRRP groups
on an interface, you need to set the CPCAR of VRRP packets to 256 kbit/s.

CAUTION
l When configuring VRRP and static ARP simultaneously on the S5300, do not use the IP
addresses in the static ARP entries as the virtual IP addresses of VRRP groups. Otherwise,
incorrect host routes are generated, which affects forwarding between devices.
l Do not create VRRP groups on the VLANIF interfaces corresponding to super VLANs
because the configuration degrades the system performance.
----End
6.3.3 Setting the Priority of an Interface in a Backup Group

Context
In master/backup mode, only one backup group is configured. Switches in the backup group
have different priorities. The switch with the highest priority functions as the master and the
others function as the backups.
In load balancing mode, two or more backup groups are configured. Each switch has different
priorities in different backup groups. VRRP identifies the role of a switch in a backup group
according to the priority. Repeat the following steps to ensure that the masters of VRRP backup
groups are distributed on different switches.
Do as follows on the S5300s in a backup group.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
vrrp vrid virtual-router-id priority priority-value
The priority of the S5300 in the specified backup group is set.

By default, the priority is 100. The priority of 0 is reserved in the system for special use. The
priority of 255 is reserved for the IP address owner, and the priority of the IP address owner
cannot be changed. Therefore, the priority that can be set for switches ranges from 1 to 254.
----End
6.3.4 (Optional) Configuring the Sending Mode of VRRP Packets

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

Context
Do as follows on a VRRP switch that is configured with a super-VLAN:
Procedure
Step 1 Run:
system-view
Step 2 Run:
interface vlanif vlan-id
The VLAN interface view is displayed.
Step 3 Run:
vrrp advertise send-mode { sub-vlan-id | all }
The sending mode of VRRP advertising messages is configured.
By default, the super-VLAN does not send advertisement messages to its sub-VLANs.
----End
Prerequisite
The configuration of the VRRP backup group is complete.
Procedure
Step 1 Run the display vrrp [ vlanif interface-type interface-number [ virtual-router-id ] ] command
to check the status of a VRRP backup group.
----End
Example
Run the display vrrp interface vlanif command, and you can view the status of the VRRP group
created on a VLANIF interface.
<Quidway> display vrrp
Vlanif211 | Virtual Router 1
State : Initialize
PriorityRun : 100
MasterPriority : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES

6.4 Configuring VRRP to Track the Interface Status

This section describes how to configure VRRP to track the interface status to improve system
reliability.

6.4.2 Tracking the Status of an Interface

VRRP can monitor the interface status. With this function, VRRP can provide the backup
function when an interface on the switch is faulty, no matter whether the interface is in a VRRP
group.
Implementation of the backup function is as follows:
l When a tracked interface becomes Down, the priority of the switch is reduced by a certain
value in the VRRP group. Therefore, the priority of the switch is lower than those of other
switches in the VRRP group.
l The switch with the highest priority becomes the master.
Before configuring VRRP to track the interface status, complete the following tasks:
l Configuring network layer attributes of interface to ensure network connectivity

l Configuring a VRRP group
Data Preparation
To configure VRRP to track the interface status, you need the following data.
No. Data
1 VRRP group ID
2 Tracked interface and increment or decrement of the priority
6.4.2 Tracking the Status of an Interface

Context
The backup is performed when other interfaces on a switch become Down. This feature is
required by NAT applications.

Do as follows on the S5300 where the tracked interface is located.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
vrrp vrid virtual-router-id track interface interface-type interface-number
[ increased value-increased | reduced value-reduced ]
A VRRP backup group is configured to track the status of the interface.
l By default, when the tracked interface becomes Down, the priority of the switch decreases
by 10.
l increased value-increased: specifies the increment of the priority when the tracked interface
becomes Down. The value ranges from 1 to 255. The maximum value of the priority is 254.
This parameter is valid only when the backup group is in Backup state.
l reduced value-reduced: specifies the decrement of the priority when the tracked interface
becomes Down. The value ranges from 1 to 255. The minimum value of the priority is 1.
l If VRRP tracks BFD sessions and interfaces at the same time, the number of tracked BFD
sessions or interfaces cannot exceed 8. If increased value-increased is specified for all the
tracked BFD sessions and interfaces, the original priority of the backup switch plus the
increments can exceed the priority of the master only if all the monitored BFD sessions and
interfaces are Down. If the sum of the original priority of the backup switch and the
increments exceeds the priority of the master switch when some of interfaces or BFD sessions
become Down, the increments of all BFD sessions and interfaces become invalid when
another interface or BFD session becomes down.
NOTE
You can configure up to eight tracked interfaces on a VRRP group. If an S5300 is the IP address owner,
interfaces of the S5300 cannot be tracked.
----End
Prerequisite
All the configurations required for enabling VRRP to track the interface status are complete.
Procedure
l Run the display vrrp [ interface vlanif interface-number [ virtual-router-id ] ] [ brief ]
command to check information about a specified VRRP group.
----End

Example
Run the display vrrp command, and you can view the status of a VRRP group. In the command
output, the Track IF field indicates the type and number of the tracked interface; the IF State
field indicates the status of the tracked interface (Up or Down).
State : Initialize
PriorityRun : 90
MasterPriority : 0
TimerRun : 1
TimerConfig : 1
Auth Type : SIMPLE TEXT Auth key : 123456
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Track IF : GigabitEthernet0/0/2 priority reduced : 10
IF State : DOWN
Track BFD : 10 Priority reduced : 10
6.5 Configuring VRRP to Tracking the BFD Session Status

This section describes how to configure VRRP to track the BFD session status to implement fast
switchover.

6.5.2 Tracking the Status of a BFD Session
VRRP can monitor the BFD session status. When the BFD session status changes, the VRRP
module is notified so that fast switchover is implemented.
A VRRP group can track the status of multiple normal BFD sessions or interfaces.
When a VRRP group tracks several normal BFD sessions, status changes of one BFD session
do not affect the status of the other BFD sessions.
When the status of a traced normal BFD session changes, the priority of the switch is changed
to trigger the switchover. When the status of the tracked BFD session recovers, the priority of
the switch is restored.
Before configuring VRRP to track the BFD session status, complete the following tasks:
l Configuring network layer attributes of interface to ensure network connectivity


l Creating BFD sessions
Data Preparation
To configure VRRP to track the BFD session status, you need the following data.
No. Data
1 VRRP group ID
2 ID or name of the tracked BFD session
6.5.2 Tracking the Status of a BFD Session

Context
Do as follows on the S5300 that requires the fast VRRP switchover.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the interface that the VRRP backup group belongs to is displayed.
Step 3 Run:
vrrp vrid virtual-router-id track bfd-session { bfd-session-id | session-name bfd-
name } [ increased value-increased | reduced value-reduced ]
The normal BFD session is tracked.

increased value-increased: specifies the value by which the priority increases when the tracked
BFD session goes Down. The value ranges from 1 to 255. The maximum value of the priority
is 254. The value takes effect only when the status of the VRRP backup group is Backup.
reduced value-reduced: specifies the value by which the priority decreases when the tracked
BFD 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 the default
value, ensure that the priority of a backup switchin a backup group is higher than that of a master
switch whose priority is changed. In this manner, the VRRP status can be switched fast.
When a VRRP backup group monitors both BFD sessions and interfaces, the maximum number
of BFD sessions and interfaces is 8. If increased value-increased is specified, the value of the
increased VRRP backup group priority can exceed the priority of the master VRRP backup group
only when all the tracked BFD sessions or interfaces go Down. Otherwise, if the VRRP backup
group takes precedence of the peer because its priority is increased when one or part of tracked

BFD sessions or interfaces go Down, the additional increasing of the priority is of no significance
when other BFD sessions or interfaces go Down.
----End

Prerequisite
The configurations of VRRP fast switchover are complete.
Procedure
Step 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ]
command to view information about a specified VRRP group.
----End
Example
Run the display vrrp command, and you can find that the tracked BFD session is in Up state.
For example:
State : Master
PriorityRun : 90
MasterPriority : 90
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-010a
Check TTL : YES
6.6 Configuring VRRP Authentication

This section describes how to configure the authentication function in a VRRP group.

6.6.2 Setting the Authentication Mode of VRRP Packets

On a secure network, you can use the default configuration on the S5300: The S5300 does not
add authentication information to the VRRP packets to be sent or authenticate received VRRP

packets. That is, it considers all the received VRRP packets to be valid. In this case, you do not
need to set the authentication key.
VRRP provides simple text authentication and MD5 authentication for networks that are
vulnerable to attacks. In simple text authentication mode, the authentication key can be set to a
string of 1 to 8 characters. In MD5 authentication mode, the authentication key can be set to a
string of 1 to 8 characters in plain text or a string of 24 characters in encrypted text.
The process of simple text authentication is as follows:

l The S5300 adds the authentication key to a VRRP packet.
l When receiving the VRRP packet, the receiver compares the authentication key in the
VRRP packet with the key configured locally. If the two keys are the same, the receiver
considers the VRRP packet to be valid; otherwise, the receiver discards the VRRP packet
and sends a trap message to the network management system (NMS).
The process of MD5 authentication is as follows:

l The S5300 adds the authentication key to a VRRP packet.
l The receiver generates a summary based on the local authentication key and compares the
summary of the received VRRP packet with the local summary. If they are the same, the
receiver considers the received VRRP packet to be valid. Otherwise, the receiver considers
discards the VRRP packets and then sends a trap message to the NMS.
Before configuring VRRP authentication, complete the following tasks:
l Setting physical parameters of interfaces

l Configuring link attributes of interfaces
l Configuring network layer attributes of interfaces to ensure network connectivity
Data Preparation
To configure VRRP authentication, you need the following data.
No. Data
1 VRRP group ID
2 Virtual IP address of the VRRP group
3 Authentication key of VRRP packets
6.6.2 Setting the Authentication Mode of VRRP Packets
Context
Do as follows on the S5300 where authentication of VRRP packets is required.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
A VRRP group is created and a virtual IP address is assigned to the VRRP group.
Step 4 Run:
vrrp vrid virtual-router-id authentication-mode { simple key | md5 md5-key }
The authentication mode of VRRP packets is set.

The devices in a VRRP group must be configured with the same authentication mode; otherwise,
the negotiation between the master and backup will fail.
----End

Prerequisite
The configurations of the VRRP authentication are complete.
Procedure
Step 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ] [ brief ]
command to check information about a specified VRRP group.
----End
Example
Run the display vrrp command, and you can view the authentication mode used for VRRP
packets.
State : Master
Virtual IP : 10.1.1.111
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : MD5 Auth key : >6M*PO438G/Q=^Q`MAF4<1!!
Virtual Mac : 0000-5e00-0101
Check TTL : YES

The output information shows that the authentication algorithm is MD5, the authentication key
is >6M*PO438G/Q=^Q`MAF4<1!!.
6.7 Optimizing the VRRP Performance

This section describes how to optimize the VRRP performance by modifying the parameters of
VRRP packets.

6.7.2 Setting the Interval for Sending VRRP Advertisement Packets
6.7.3 Setting the Preemption Delay of Switches in a Backup Group
6.7.4 Disabling a router from Checking Number of Hops in VRRP Packets
6.7.5 Enabling the Ping to Virtual IP Addresses
6.7.6 Setting the Interval for Sending Gratuitous ARP Packets
You can optimize the performance of a VRRP group by:
l Increasing the interval for sending VRRP Advertisement packets to reduce the network
resources used for packet processing
l Setting the same interval for sending VRRP Advertisement packets on all the members in
the VRRP group to prevent the problem of multiple masters in a VRRP group
l Setting the preemption mode and preemption delay on the switches in the VRRP group to
speed up or slow down the switchover between the master and backup switches
l Enabling the ping to the virtual IP address to check connectivity of the network
l Disabling the switches from checking the TTL in VRRP packets to ensure compatibility
between devices of different vendors
l Configuring the network management functions of VRRP so that VRRP can send trap
packets to notify the NMS of faults occurring during communication
l Disabling the switches from checking the hop limit of VRRP packets to ensure
compatibility between devices of different vendors
Before optimizing the VRRP performance, complete the following tasks:
l Setting physical parameters of each interface

l Setting the link-layer parameters of each interface
l Setting the network-layer parameters of each interface to ensure connectivity of the network
l Configuring a VRRP VRRP group

Data Preparation
To optimize the VRRP performance, you need the following data.
No. Data
1 Interval for sending VRRP Advertisement packets
2 Preemption delay of the switches in the VRRP group
3 Interval at which the master switch sends gratuitous ARP packets
6.7.2 Setting the Interval for Sending VRRP Advertisement Packets
Context
The master switch sends VRRP Advertisement packets at intervals to backup switches to notify
the backup switches that it works normally. If the backup switches do not receive any VRRP
packet within the interval, the backup switch with the highest priority becomes the master.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
vrrp vrid virtual-router-id timer advertise adver-interval
The interval for sending VRRP Advertisement packets is set.
By default, the interval for sending VRRP Advertisement packets is 1 second. When multiple
backup groups are configured, a short interval causes frequent switchover of switches. In this
case, you need to increase the interval for sending VRRP Advertisement packets.
NOTE
l If the advertise-interval parameters set for two VRRP devices are the same, the two devices can work
in master and slave mode.
l If the advertise-interval parameters set for two VRRP devices are different, both the two devices are
in master state.
----End

6.7.3 Setting the Preemption Delay of Switches in a Backup Group

Context
Do as follows on the S5300s in a backup group.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
vrrp vrid virtual-router-id preempt-mode timer delay delay-value
The preemption delay is set.

By default, the preemption mode is adopted and the preemption delay is 0 seconds. That is, a
backup switch becomes the master switch immediately after detecting that its priority is higher
than the priority of the master switch. The original master switch then becomes the backup
switch. If the preemption delay is greater than 0, the backup switch becomes the master switch
after the delay.
You can run the vrrp vrid virtual-router-id preempt-mode disable command to configure the
switches in a backup group to work in non-preemption mode. In this mode, after a switch
becomes the master switch, switches with higher priorities cannot become the master until the
master switch fails.
After the IP address owner recovers, it becomes the master immediately without waiting the
preemption delay. The preemption delay refers to the time backup switch waits to become the
master switch. Therefore, the preemption delay does not affect the IP address owner. For the
VRRP backup group that needs to support the preemption delay, the IP address owner cannot
be configured as the master switch.
To restore the default preemption mode, run the vrrp vrid virtual-router-id preempt-mode
command.
NOTE
It is recommended that you set the preemption delay of the backup switches in a VRRP group to 0 and set
a certain preemption delay for the master switch. Thus, when the network environment changes, the
switches wait for some time for the uplink and downlink to recover. This prevents the problem of two
masters or wrong master switch address learned by user devices because of frequent preemption.
----End

6.7.4 Disabling a router from Checking Number of Hops in VRRP

Packets
Context
As defined in RFC 3768, the system checks the TTL value of received VRRP packets. If this
value is not 255, the VRRP packets are discarded.
On a network consisting of devices of different vendors, valid VRRP packets may be discarded
when TTL checking is enabled. In this case, you can configure the system not to check the TTL
value of VRRP packets.
Do as follows on the S5300 where TTL checking needs to be disabled.
Procedure
Step 1 Run:
system-view
Step 2 Run:
Step 3 Run:
vrrp un-check ttl
The S5300 is configured not to check the TTL value of VRRP packets.
By default, the S5300 checks the TTL value of VRRP packets. To enable the S5300 to check
the TTL value of VRRP packets, run the undo vrrp un-check ttl command.
----End
6.7.5 Enabling the Ping to Virtual IP Addresses
Context
The S5300 can ping virtual IP addresses to:
l Check whether the master switch in a backup group works normally.

l Check whether a virtual IP address can be used as the default gateway address to
communicate with external networks.
Do as follows on the S5300 that needs to ping virtual IP addresses.
Procedure
Step 1 Run:
system-view

Step 2 Run:
vrrp virtual-ip ping enable
The ping to virtual IP addresses is enabled.
By default, the ping to virtual IP addresses is enabled. That is, the master switch in a backup
group can respond to the ping packets the virtual IP address of the backup group.
Ping to virtual IP addresses may cause ICMP attacks. To prevent ICMP attacks, run the undo
vrrp virtual-ip ping enable command to disable the ping to virtual IP addresses.
----End
6.7.6 Setting the Interval for Sending Gratuitous ARP Packets
Context
Do as follows on the S5300 that sends gratuitous ARP packets.
Procedure
Step 1 Run:
system-view
Step 2 Run:
vrrp gratuitous-arp timeout time
The interval at which the master switch sends gratuitous ARP packets is set.
The gratuitous ARP packets sent by the master switch contain the virtual MAC address. By
default, the master switch sends gratuitous ARP packets every 300 seconds (5 minutes).
To restore the default interval for sending gratuitous ARP packets, run the undo vrrp
gratuitous-arp timeout command in the system view.
If the S5300 does not need to send gratuitous ARP packets, run the vrrp gratuitous-arp timeout
disable command in the system view.
----End
Prerequisite
The configuration for optimizing the VRRP performance is complete.
Procedure
Step 1 Run the display vrrp [ interface interface-type interface-number [ virtual-router-id ] ] [
brief ] command to check the status of a VRRP backup group.
----End

Example
Run the display vrrp command, and you can view the optimized VRRP performance. For
example, you can see that TimerRun and TimerConfig is 20, indicating that the interval for
sending VRRP Advertisement packets is set to 20 seconds (the default value is 1).
State : Master
Virtual IP : 100.1.1.111
PriorityRun : 120
TimerRun : 20
TimerConfig : 20
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
6.8 Configuring mVRRP Backup Groups

An mVRRP backup group can be bound to other member backup groups and determine the

Before configuring an mVRRP backup group, familiarize yourself with the applicable
6.8.2 Configuring mVRRP Backup Group
Each VRRP backup group needs to maintain its own state machine by sending VRRP packets.
Configuring an mVRRP backup group can reduce bandwidth consumption of VRRP packets.
6.8.3 (Optional) Configuring Member VRRP Backup Groups and Binding them to the mVRRP
Backup Group
Through the bindings between member VRRP backup groups and the mVRRP backup group,
the state machines of member VRRP backup groups can be consistent with the state machine of
the mVRRP backup group.
By viewing all bindings in an mVRRP backup group, you can check whether the configurations
are successful.

Before configuring an mVRRP backup group, familiarize yourself with the applicable

Application Environment
Figure 6-2 mVRRP determines the dual-homing of the master and slave switchs
NPE1
mVRRP
UPE
NPE2
As shown in Figure 6-2, when the convergence layer of the Metro Ethernet (ME) dual NPEs
are deployed for high reliability. The master and standby switchs are determined by mVRRP
between NPEs.
The mVRRP backup group is actually the ordinary VRRP backup group. The difference is that
the mVRRP backup group can be bound to other backup groups of different services. The status
of the backup group of related services depends on the binding relationship.
The mVRRP backup group can be bound to several backup group members. The mVRRP backup
group cannot be bound to other management backup groups.
According to different applications, the binding relationship of the mVRRP backup group is as
follows:
l The VRRP backup group is bound to the mVRRP backup group: UPEs are dual-homed to
NPEs. VRRP is run between NPEs. The master NPE and backup NPE are determined by
the configured priority of VRRP. Multiple VRRP backup groups run between NPEs with
different services.
If each VRRP backup group needs to maintain its own state machine, a huge number of
VRRP packets exist among NPEs. To simplify the process and decrease occupancy of
bandwidth, you can set one VRRP backup group as the mVRRP backup group. Other
backup group members are bound to the mVRRP backup group. The master and slave
switchs are determined directly by the binding relationship.
l The service interfaces are bound to the mVRRP backup group. If the UPEs are dual-homed
to NPEs through two physical links. You can bind the member interfaces to the mVRRP
backup group to determine the master member interfaces and the slave interfaces.
Before configuring mVRRP, complete the following tasks:
l Configuring physical parameters of an interface


l Configuring attributes of network layer of interfaces for connectivity
Data Preparation
To configure mVRRP, you need the following data.
No. Data
1 ID of the mVRRP and IDs of VRRP backup group members
2 Virtual IP address of the mVRRP and virtual IP addresses of VRRP backup group
members
3 Priority of the mVRRP
4 Number of the member interface
5 PW peer IP address
6.8.2 Configuring mVRRP Backup Group

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

l Run:

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

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

Binding them to the mVRRP Backup Group
Through the bindings between member VRRP backup groups and the mVRRP backup group,
the state machines of member VRRP backup groups can be consistent with the state machine of
the mVRRP backup group.

Context
Do as follows on each switch on which the member VRRP backup groups need to be bound to
an mVRRP backup group.
Procedure
l Run:
system-view

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

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

By viewing all bindings in an mVRRP backup group, you can check whether the configurations
are successful.
Prerequisite
The configurations of the mVRRP backup groups function are complete.
Procedure
l Run the display vrrp binding admin-vrrp [ interface interface-type interface-number ]
[ vrid virtual-router-id ] command to check all binding information about the mVRRP
backup group.
l Run the display vrrp binding admin-vrrp [ interface interface-type1 interface-
number1 ] [ vrid virtual-router-id1] member-vrrp [ interface interface-type2 interface-
number2 ] [ vrid virtual-router-id2] command to check the binding between the mVRRP
backup group and the member VRRP backup groups.

l Run the display vrrp admin-vrrp command to check the status of all mVRRP backup
groups in the current configuration.
----End
Example
After the configuration, you can run the display vrrp binding admin-vrrp command to view
all binding information about the member VRRP backup group, interface member, and PW
member.
<Quidway> display vrrp binding admin-vrrp
Interface: Vlanif10, admin-vrrp vrid: 6, state: Master
Member-vrrp number: 1
Interface: Vlanif11, vrid: 8, state: Master
Member-interface number: 1
Interface: Vlanif12, state: Up
6.9 Configuring VRRP Version Upgrade

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

Before configuring VRRP version upgrade, familiarize yourself with the applicable
6.9.2 Configuring VRRPv3
After VRRPv3 is configured, VRRP backup groups can receive both VRRPv2 and VRRPv3
Advertisement packets.
You can view VRRP version information to check whether the configuration is successful.

Before configuring VRRP version upgrade, familiarize yourself with the applicable
Currently, VRRPv2 is adopted. VRRP for IPv4 supports only VRRPv2 packets, whereas VRRP
for IPv6 supports both VRRPv2 and VRRPv3 packets. You can undertake this configuration
task to upgrade the VRRP version as required.
Before configuring VRRP version upgrade, complete the following tasks:
l Installing the device and powering it on properly

l Ensuring that VRRPv2 is running on the device

Data Preparation
To configure VRRP version upgrade, you need the following data.
No. Data
1 VRRP version number
6.9.2 Configuring VRRPv3

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

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

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

By default, the mode v2-only is adopted.
l Configuration for each VRRP backup group:
1. Run:
system-view

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

3. Run:

4. (Optional) Run:
vrrp vrid virtual-router-id version-3 send-packet-mode { v2-only | v3-
only | v2v3-both }
The mode in which Advertisement packets are sent by a VRRP backup group on an
interface enabled with VRRPv3 is set.

By default, VRRPv3 uses the v3-only mode to send Advertisement packets.
NOTE
If the vrrp version-3 send-packet-mode command is run globally, and the vrrp vrid
version-3 send-packet-mode command is run on an interface, the configuration on the
interface takes effect.
----End

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

This section describes how to monitor running of VRRP and debug VRRP.
6.10.1 Debugging VRRP
6.10.1 Debugging VRRP
Context
CAUTION
When a VRRP fault occurs, run the following debugging commands in the user view to locate
the fault.

Procedure
l Run the debugging vrrp packet [ interface vlanif interface-number vrid virtual-router-
id ] command to enable debugging of VRRP packets.
l Run the debugging vrrp state [ interface vlanif interface-number vrid virtual-router-
id ] command to enable debugging of VRRP status.
l Run the debugging vrrp timer [ interface vlanif interface-number vrid virtual-router-
id ] command to enable debugging of the VRRP timer.
----End

This section provides several configuration examples of VRRP.
6.11.1 Example for Configuring VRRP in Master/Backup Mode

6.11.3 Example for Configuring VRRP Fast Switchover

As shown in Figure 6-3, Host A communicates with Host B through the default gateway.
The requirements are as follows:
l The VRRP group that consists of SwitchA and SwitchB functions as the default gateway
of Host A.
l SwitchA functions as the gateway. When SwitchA fails, SwitchB becomes the gateway.
l After SwitchA recovers, it preempts to be the master router within 20 seconds.
Figure 6-3 Networking of a VRRP group in master/backup mode
Backup group 1
Virtual IP Address:
10.1.1.111 SwitchA
Master
GE0/0/1
GE0/0/2
GE0/0/2
SwitchC
HostA GE0/0/1
10.1.1.100/24
GE0/0/3
HostB
GE0/0/1 20.1.1.100/24
GE0/0/2
Ethernet
SwitchB
Backup

Device Interface VLANIF interface IP address

SwitchA GE0/0/1 VLANIF100 10.1.1.1/24
GE0/0/2 VLANIF200 192.168.1.1/24
SwitchB GE0/0/1 VLANIF100 10.1.1.2/24
GE0/0/2 VLANIF400 192.168.2.1/24
SwitchC GE0/0/1 VLANIF300 20.1.1.1/24
GE0/0/2 VLANIF200 192.168.1.2/24
GE0/0/3 VLANIF400 192.168.2.2/24
1. Configure VLANIF interfaces and assign IP addresses to the VLANIF interface.
2. Configure the OSPF protocol between Switch A, Switch B, and Switch C to implement
interworking between them.
3. Create VRRP group 1 on VLANIF 100 of Switch A. Set the highest priority for Switch A
in the VRRP group to ensure that Switch A functions as the master. Configure the
preemption mode on Switch A.
4. Create VRRP group 1 on VLANIF 100 of Switch B and use the default priority.
Data Preparation
l Priorities of Switch A and Switch B in the VRRP group
l Preemption mode
Procedure
Step 1 Configure VLANIF interfaces and assign IP addresses to the VLANIF interface.
# Create VLANs and add physical interfaces to VLANs.
The configurations of Switch B and Switch C are similar to the configuration of Switch A, and
# Configure an IP address for the VLANIF interface on SwitchA.


# Configure an IP address for the VLANIF interface on Switch B.

[SwitchB] interface vlanif 100
# Configure an IP address for the VLANIF interface on Switch C.

[SwitchC] interface vlanif 200
[SwitchC-Vlanif200] ip address 192.168.1.2 24
[SwitchC-Vlanif200] quit
Step 2 Configure the OSPF protocol between Switch A, Switch B, and Switch C.
[SwitchA] ospf 1
[SwitchA-ospf-1] area 0
[SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[SwitchA-ospf-1-area-0.0.0.0] quit
[SwitchA-ospf-1] quit
[SwitchB] ospf 1
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] network 192.168.2.0 0.0.0.255
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
[SwitchC] ospf 1
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 192.168.1.0 0.0.0.255
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
# Configure the default gateway address of Host A to 10.1.1.111 and the default gateway address
of Host B to 20.1.1.1.
Step 3 Configure a VRRP group.
# On Switch A, assign an IP address to the VLANIF interface. Create VRRP group 1 and set
the priority of SwitchA in the VRRP group to 120 so that Switch A functions as the master.
[SwitchA] interface Vlanif 100
[SwitchA-Vlanif100] vrrp vrid 1 virtual-ip 10.1.1.111
[SwitchA-Vlanif100] vrrp vrid 1 priority 120

[SwitchA-Vlanif100] vrrp vrid 1 preempt-mode timer delay 20

# On Switch B, assign an IP address to the VLANIF interface. Create VRRP group 1 and retain
the default priority of SwitchB in the VRRP group so that SwitchB functions as the backup.
[SwitchB] interface Vlanif 100
[SwitchB-Vlanif100] vrrp vrid 1 virtual-ip 10.1.1.111

l The VRRP group can function as the gateway.
After the preceding configuration, Host A can ping Host B. Run the display vrrp command on
Switch A, and you can find that Switch A is the master switch. Run the display vrrp command
on Switch B, and you can find that Switch B is the backup switch.
<SwitchA> display vrrp
state : Master
Virtual IP : 10.1.1.111
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
<SwitchB> display vrrp
state : Backup
Virtual IP : 10.1.1.111
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Run the display ip routing-table command on Switch A and Switch B. You can find a direct
route to the virtual IP address in the routing table of Switch A. In the routing table of Switch B,
this direct route is an OSPF route. The displayed information on Switch A and Switch B is as
follows:
<SwitchA> display ip routing-table
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Tables: Public
Destinations : 9 Routes : 10
Destination/Mask Proto Pre Cost Flags NextHop Interface
10.1.1.0/24 Direct 0 0 D 10.1.1.1 Vlanif100
10.1.1.1/32 Direct 0 0 D 127.0.0.1 InLoopBack0
20.1.1.0/24 OSPF 10 2 D 192.168.1.2 Vlanif200
192.168.1.0/24 Direct 0 0 D 192.168.1.1 Vlanif200
192.168.1.2/32 Direct 0 0 D 192.168.1.2 Vlanif200
192.168.2.0/24 OSPF 10 2 D 10.1.1.2 Vlanif100

<SwitchB> display ip routing-table

Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
10.1.1.0/24 Direct 0 0 D 10.1.1.2 Vlanif100
20.1.1.0/24 OSPF 10 2 D 192.168.2.2 Vlanif200
192.168.1.0/24 OSPF 10 2 D 10.1.1.1 Vlanif100
192.168.2.0/24 Direct 0 0 D 192.168.2.1 Vlanif200
192.168.2.2/32 Direct 0 0 D 192.168.2.2 Vlanif200
l When Switch A fails, Switch B becomes the master switch.

Run the shutdown command on VLANIF 100 of Switch A to simulate a link fault.
Run the display vrrp command on Switch B to view information about the VRRP status. You
can find that Switch B is the master switch.
state : Master
Virtual IP : 10.1.1.111
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
l When Switch A recovers, it preempts to be the master.

Run the undo shutdown command on VLANIF 100 of Switch A. Wait for 20 seconds after
VLANIF 100 recovers to the Up state, and then run the display vrrp command on Switch A to
view the VRRP status. You can find that Switch A is the master switch.
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 100 200
#
interface Vlanif100
ip address 10.1.1.1 255.255.255.0
vrrp vrid 1 preempt-mode timer delay 20
#
interface Vlanif200
ip address 192.168.1.1 255.255.255.0
#
#

#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 10.1.1.0 0.0.0.255
#
return
#
sysname SwitchB
#
vlan batch 100 400
#
interface Vlanif100
ip address 10.1.1.2 255.255.255.0
#
interface Vlanif400
ip address 192.168.2.1 255.255.255.0
#
#
#
ospf 1
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 10.1.1.0 0.0.0.255
#
return
#
sysname SwitchC
#
#
interface Vlanif200
ip address 192.168.1.2 255.255.255.0
#
interface Vlanif300
ip address 20.1.1.1 255.255.255.0
#
interface Vlanif400
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

As shown in Figure 6-4, Host A communicates with Host B through the default gateway.
The requirements are as follows:
l The VRRP group that consists of SwitchA and SwitchB functions as the default gateway
of Host A.
l SwitchA functions as the gateway. When SwitchA fails, SwitchB becomes the gateway.
l After SwitchA recovers, it preempts to be the master router within 20 seconds.
Figure 6-4 Networking of a VRRP group in master/backup mode
Backup group 2
Virtual IP Address: SwitchA
10.1.1.112 group 1:Master
group 2:Backup
GE0/0/2
GE0/0/1
HostA
GE0/0/2
10.1.1.100/24
SwitchC GE0/0/1
GE0/0/3 HostB
20.1.1.100/24
HostC GE0/0/2
10.1.1.101/24 GE0/0/1
SwitchB
Ethernet group 2:Master
Backup group 1 group 1:Backup
Virtual IP Address:
10.1.1.111

GE0/0/2 VLANIF200 192.168.1.1/24
GE0/0/2 VLANIF400 192.168.2.1/24
SwitchC GE0/0/1 VLANIF300 20.1.1.1/24
GE0/0/2 VLANIF200 192.168.1.2/24
GE0/0/3 VLANIF400 192.168.2.2/24

1. Configure VLANIF interfaces and assign IP addresses to the VLANIF interface.
2. Configure the OSPF protocol between SwitchA, SwitchB, and SwitchC to implement
interworking between them.
3. Create VRRP group 1 on VLANIF 100 of SwitchA. Set the highest priority for SwitchA
in the VRRP group to ensure that SwitchA functions as the master. Configure the
preemption mode on SwitchA.
4. Create VRRP group 1 on VLANIF 100 of SwitchB and use the default priority.
Data Preparation
l Priorities of SwitchA and SwitchB in the VRRP group
l Preemption mode
Procedure
Step 1 Configure VLANIF interfaces and assign IP addresses to the VLANIF interface.
# Create VLANs and add physical interfaces to VLANs.
# Configure an IP address for the VLANIF interface on SwitchA.
# Configure an IP address for the VLANIF interface on SwitchB.

# Configure an IP address for the VLANIF interface on SwitchC.


Step 2 Configure the OSPF protocol between SwitchA, SwitchB, and SwitchC.
[SwitchA] ospf 1
[SwitchA-ospf-1] area 0
[SwitchA-ospf-1-area-0.0.0.0] network 10.1.1.0 24
[SwitchA-ospf-1-area-0.0.0.0] network 192.168.1.0 24
[SwitchA-ospf-1-area-0.0.0.0] quit
[SwitchA-ospf-1] quit
[SwitchB] ospf 1
[SwitchB-ospf-1] area 0
[SwitchB-ospf-1-area-0.0.0.0] network 10.1.1.0 24
[SwitchB-ospf-1-area-0.0.0.0] network 192.168.2.0 24
[SwitchB-ospf-1-area-0.0.0.0] quit
[SwitchB-ospf-1] quit
[SwitchC] ospf 1
[SwitchC-ospf-1] area 0
[SwitchC-ospf-1-area-0.0.0.0] network 192.168.1.0 24
[SwitchC-ospf-1-area-0.0.0.0] quit
[SwitchC-ospf-1] quit
# Configure the default gateway address of Host A to 10.1.1.111 and the default gateway address
of Host B to 20.1.1.1.
Step 3 Configure a VRRP group.
# On SwitchA, assign an IP address to the VLANIF interface. Create VRRP group 1 and set the
priority of SwitchA in the VRRP group to 120 so that SwitchA functions as the master.
[SwitchA-Vlanif100] vrrp vrid 1 preempt-mode timer delay 20
# On SwitchB, assign an IP address to the VLANIF interface. Create VRRP group 1 and retain
the default priority of SwitchB in the VRRP group so that SwitchB functions as the backup.

l The VRRP group can function as the gateway.
After the preceding configuration, Host A can ping Host B. Run the display vrrp command on
SwitchA, and you can find that SwitchA is the master switch. Run the display vrrp command
on SwitchB, and you can find that SwitchB is the backup switch.

<SwitchA> display vrrp

state : Master
Virtual IP : 10.1.1.111
PriorityRun : 120
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
state : Backup
Virtual IP : 10.1.1.111
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
Run the display ip routing-table command on SwitchA and SwitchB. You can find a direct
route to the virtual IP address in the routing table of SwitchA. In the routing table of SwitchB,
this direct route is an OSPF route. The displayed information on SwitchA and SwitchB is as
follows:
<SwitchA> display ip routing-table
Route Flags: R - relied, D - download to fib
------------------------------------------------------------------------------
10.1.1.0/24 Direct 0 0 D 10.1.1.1 Vlanif100
20.1.1.0/24 OSPF 10 2 D 192.168.1.2 Vlanif200
192.168.1.0/24 Direct 0 0 D 192.168.1.1 Vlanif200
192.168.1.2/32 Direct 0 0 D 192.168.1.2 Vlanif200
192.168.2.0/24 OSPF 10 2 D 10.1.1.2 Vlanif100
<SwitchB> display ip routing-table
Route Flags: R - relied, D - download to fib
------------------------------------------------------------------------------
10.1.1.0/24 Direct 0 0 D 10.1.1.2 Vlanif100
20.1.1.0/24 OSPF 10 2 D 192.168.2.2 Vlanif200
192.168.1.0/24 OSPF 10 2 D 10.1.1.1 Vlanif100
192.168.2.0/24 Direct 0 0 D 192.168.2.1 Vlanif200
192.168.2.2/32 Direct 0 0 D 192.168.2.2 Vlanif200
l When SwitchA fails, SwitchB becomes the master switch.

Run the shutdown command on VLANIF 100 of SwitchA to simulate a link fault.
Run the display vrrp command on SwitchB to view information about the VRRP status. You
can find that SwitchB is the master switch.
state : Master
Virtual IP : 10.1.1.111
PriorityRun : 100
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Virtual Mac : 0000-5e00-0101
Check TTL : YES
l When SwitchA recovers, it preempts to be the master.

Run the undo shutdown command on VLANIF 100 of SwitchA. Wait for 20 seconds after
VLANIF 100 recovers to the Up state, and then run the display vrrp command on SwitchA to
view the VRRP status. You can find that SwitchA is the master switch.
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 100 200
#
interface Vlanif100
ip address 10.1.1.1 255.255.255.0
#
interface Vlanif200
ip address 192.168.1.1 255.255.255.0
#
#
#
ospf 1
area 0.0.0.0
network 192.168.1.0 0.0.0.255
network 10.1.1.0 0.0.0.255
#
return

#
sysname SwitchB
#
vlan batch 100 400
#

interface Vlanif100
ip address 10.1.1.2 255.255.255.0
#
interface Vlanif200
ip address 192.168.2.1 255.255.255.0
#
#
#
ospf 1
area 0.0.0.0
network 192.168.2.0 0.0.0.255
network 10.1.1.0 0.0.0.255
#
return

#
sysname SwitchC
#
#
interface Vlanif200
ip address 192.168.1.2 255.255.255.0
#
interface Vlanif300
ip address 20.1.1.1 255.255.255.0
#
interface Vlanif400
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
6.11.3 Example for Configuring VRRP Fast Switchover

As shown in Figure 6-5, Switch A, Switch B, Switch C, Switch D and the Universal Medium
Gateway (UMG) form a simple next generation network (NGN).
The networking is as follows:

l The UMG connects to Switch A and Switch B through Switch C and Switch D.
l Switch A and SwitchSwitch B run VRRP. Switch A functions as the master, and Switch
B functions as the backup.
When Switch A fails, or when the GE link between Switch A and Switch B fails, the active/
standby switchover should be completed within 1 second. That is, fast switchover is required
on the bearer network.
Figure 6-5 Networking of VRRP fast switchover
Backbone
Network
GE0/0/2 GE0/0/1
SwitchA SwitchB
GE0/0/1 GE0/0/1
Backup group 10
Virtual IP address: 10.1.1.3/24
SwitchC SwitchD
VLAN
UMG

GE0/0/2 VLANIF200 192.168.0.1/24
GE0/0/2 VLANIF200 192.168.0.2/24
1. Implement networking between the Switch s.

2. Configure a BFD session on Switch A and Switch B to monitor Switch Switch A and its
downlink Switch A - Switch C - Switch D - Switch B.

3. Enable VRRP to track the BFD session on Switch B. When the BFD session becomes
Down, the priority of Switch B increases by 40 and then the switchover is triggered.
NOTE
This example describes only the configurations on Switch and Switch B.
Data Preparation
l Local and remote discriminators of the BFD session
l Priorities of the S5300s in the VRRP group
Procedure
Step 1 Configure interworking between the Switch s.
Assign IP addresses to all interfaces. # Configure OSPF between SwitchA, SwitchB, and
SwitchC.
For details, see Figure 6-5.
Step 2 Create a BFD session.
# Create a BFD session on Switch A.
[SwitchA] bfd
[SwitchA-bfd] quit
[SwitchA] bfd atob bind peer-ip 10.1.1.2 interface Vlanif 100
[SwitchA-bfd-session-atob] min-rx-interval 50
[SwitchA-bfd-session-atob] min-tx-interval 50
# Create a BFD session on Switch B.

[SwitchB] bfd
[SwitchB-bfd] quit
[SwitchB] bfd btoa bind peer-ip 10.1.1.1 interface Vlanif 100
[SwitchB-bfd-session-btoa] min-rx-interval 50
[SwitchB-bfd-session-btoa] min-tx-interval 50
Run the display bfd session command on Switch A and Switch B, and you can see that the BFD
session is Up. Take Switch A for example. The display is as follows:
[SwitchA] display bfd session all
--------------------------------------------------------------------------------
Local Remote Peer IP Address Interface Name State Type
--------------------------------------------------------------------------------
1 2 10.1.1.2 Vlanif100 Up Static
--------------------------------------------------------------------------------

Step 3 Configure VRRP fast switchover.

# Create VRRP group 10 on Switch A and set the priority of Switch A in VRRP group 10 to 160
so that Switch A functions as the master in VRRP group 10.
# Create VRRP group 10 on Switch B and set the priority of Switch B in VRRP group 10 to 140
so that Switch B functions as the backup in VRRP group 10.
[SwitchB-Vlanif100] vrrp vrid 10 priority 140
# Configure VRRP to track the status of the BFD session on the backup device. If the BFD
session becomes Down, the priority of Switch B increases by 40.
[SwitchB-Vlanif100] vrrp vrid 10 track bfd-session 2 increased 40
Run the display vrrp command on Switch A or Switch B, and you can see that Switch A is the
master and Switch B is the backup. You can also view the tracked BFD session and its status on
Switch B.
[SwitchA] display vrrp
state : Master
PriorityRun : 160
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
[SwitchB] display vrrp
state : Backup
PriorityRun : 140
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Track BFD : 2 Priority increased : 40
BFD-Session State : UP

# Run the shutdown command on VLANIF 100 of Switch A to simulate a link fault.
[SwitchA-Vlanif100] shutdown
On Switch B, VRRP fast switchover is performed after BFD fails.

%May 10 15:48:30 2008 SwitchB BFD/5/BFD:Slot=1;IO(1) BFD Session(Discr:2) FSM

Change To Down(Detect)
%May 10 15:48:30 2008 SwitchB VRRP/5/BfdWarning:
Virtual Router 10 | BFD-SESSION 2 : BFD_STATE_UP --> BFD_STATE_DOWN
%May 10 15:48:30 2008 SwitchB VRRP/5/StateWarning:
Vlanif100 | Virtual Router 10 : BACKUP --> MASTER
Run the display vrrp command on Switch A, and you can see that the status of Switch A changes
to Initialize.
[SwitchA] display vrrp
state : Initialize
PriorityRun : 160
MasterPriority : 0
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Run the display vrrp command on Switch B, and you can see that Switch B becomes the master,
and the status of the BFD session changes to Down.
[SwitchB] display vrrp
state : Master
PriorityRun : 180
TimerRun : 1
TimerConfig : 1
Auth Type : NONE
Check TTL : YES
Track BFD : 2 Priority increased : 40
BFD-Session State : DOWN
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 100 200
#
bfd
#
#
interface Vlanif100
ip address 10.1.1.1 255.255.255.0
#
interface Vlanif200
ip address 192.168.0.1 255.255.255.0
#

#
#
bfd atob bind peer-ip 10.1.1.2 interface Vlanif 100
min-tx-interval 50
min-rx-interval 50
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 192.168.0.0 0.0.0.255
#
return

#
sysname SwitchB
#
vlan batch 100 200
#
bfd
#
interface Vlanif100
ip address 10.1.1.2 255.255.255.0
vrrp vrid 10 track bfd-session 2 increased 40
#
interface Vlanif200
ip address 192.168.0.2 255.255.255.0
#
#
#
bfd btoa bind peer-ip 10.1.1.1 interface Vlanif 100
min-tx-interval 50
min-rx-interval 50
commit
#
ospf 1
area 0.0.0.0
network 10.1.1.0 0.0.0.255
network 192.168.0.0 0.0.0.255
#
return

Configuration Guide - Reliability 7 VRRP6 Configuration
7 VRRP6 Configuration
About This Chapter
This section describes the basic concepts and configuration procedures of VRRP6, and provides
examples for configuring VRRP6.
7.1 Introduction to VRRP6

This section describes the working principle of VRRP6.
7.2 VRRP6 Features Supported by the S5300
This section describes the VRRP6 features supported by the S5300.
7.3 Configuring a VRRP6 Backup Group
This section describes how to create a VRRP6 backup group, assign a virtual IPv6 address, and
set the priority of S5300 the VRRP6 backup group.
7.4 Configuring VRRP6 to Track the Status of an Interface
This section describes how to configure VRRP6 to track the interface status to improve system
reliability.
7.5 Configuring VRRP6 to Tracking the BFD Session Status
This section describes how to configure VRRP6 to track the BFD session status to implement
fast switchover.
7.6 Adjusting and Optimizing VRRP6
This section describes how to adjust the related parameters of VRRP6 packets to optimize
VRRP6.
7.7 Configuring mVRRP6 Backup Groups
An mVRRP6 backup group can be bound to other member backup groups and determine the
7.8 Maintaining VRRP6
This section describes how to maintain VRRP6.
This section provides several configuration examples of VRRP6.

7 VRRP6 Configuration Configuration Guide - Reliability
7.1 Introduction to VRRP6

This section describes the working principle of VRRP6.
NOTE
The S5300SI does not support VRRP6.
The Virtual Router Redundancy Protocol for IPv6 (VRRP6) is a fault tolerance protocol that
extends the VRRP protocol. It groups several routers into a virtual router and uses a certain
mechanism to switch traffic to another router when the next hop device of a host is faulty. This
ensures continuous and reliable communication.
The following table lists the functions supported by VRRP6 and VRRP for IPv4.
Function VRRP6 VRRP for IPv4
Master/Backup VRRP Yes Yes
Load balancing VRRP Yes Yes
Interface status monitoring Yes Yes
VRRP fast switchover Yes Yes
Pinging the virtual IP address Yes Yes
VRRP authentication No Yes
7.2 VRRP6 Features Supported by the S5300

This section describes the VRRP6 features supported by the S5300.
l Features configured through related commands:
– Preemption mode
– Accept mode
– Priority
– Interval for sending advertisement messages
– Preemption delay
– Tracked interface
– Function of disabling the checking of the hoplimit value contained in packets
l Protocol for selecting Master and Backup virtual devices
l Generating and sending of VRRP6 advertisement messages
l Receiving and processing VRRP6 advertisement messages
l Maintaining global statistics and interface-based statistics
l High availability
l Configuring the remote nodes through SNMP
l Decreasing the priority by a certain value when a tracked interface is Down

7.3 Configuring a VRRP6 Backup Group

This section describes how to create a VRRP6 backup group, assign a virtual IPv6 address, and
set the priority of S5300 the VRRP6 backup group.

7.3.2 Creating a Backup Group and Configuring a Virtual IPv6 Address
7.3.3 Configuring the Priority of the S5300 in a VRRP6 Group
A VRRP6 backup group supports the backup of virtual addresses.
After the corresponding IPv6 prefixes are added to related interfaces, VRRP6 takes effect if the
interfaces are UP and IPv6 is globally enabled.
Before configuring a VRRP6 backup group, complete the following tasks:
l Configuring physical parameters for interfaces

l Enabling IPv6 globally
l Configuring IPv6 addresses for interfaces
Data Preparation
To configure a VRRP6 virtual group, you need the following data.
No. Data
1 VRRP backup group ID
2 Virtual IPv6 address of the VRRP backup group
3 Priorities of devices in the VRRP6 backup group
7.3.2 Creating a Backup Group and Configuring a Virtual IPv6

Address
Context
Do as follows on S5300s in a VRRP6 backup group.

Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
vrrp6 vrid virtual-router-id virtual-ip virtual-ipv6-address [ link-local ]
A virtual group is created and a virtual IPv6 address is configured.

You must set the first virtual IPv6 address of a VRRP6 group to a link-local address.
NOTE
l The virtual IPv6 addresses of different backup groups must be different.

l On the S5300, virtual router IDs must be different.
l Both ends of the same group must be configured with the same virtual router ID.
l When configuring both a VRRP group and a VRRP6 group, set different virtual router IDs for the two
groups.
When you assign the first IPv6 address to a VRRP6 backup group, the system creates this backup
group. Then, when you assign another virtual IPv6 address to the backup group, the system adds
this address into the virtual IPv6 address list of the backup group.
In the network where users require the same VRRP6 reliability, a backup group can be configured
with multiple virtual IPv6 addresses. This is convenient for managing users and prevents the
address of the default gateway from varying with the VRRP6 configuration.
----End
7.3.3 Configuring the Priority of the S5300 in a VRRP6 Group

Context
The master/backup mode requires only one backup group. Devices have different priorities in
this backup group. The S5300 with the highest priority serves as the master device and other
S5300s are in the backup state.
Do as follows on an interface of the S5300.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
vrrp6 vrid virtual-router-id priority priority-value
The priority of the S5300 in a VRRP6 group is set.
By default, the priority is 100. A greater priority value indicates a higher priority in the VRRP6
group.
The priority 0 is reserved for special use. The priority 255 is reserved for the IPv6 address owner
and cannot be changed. You can set the priority to a value ranging from 1 to 254 by using this
command.
----End
Procedure
l Run the display vrrp6 [ interface interface-type interface-number [ vrid virtual-router-
id ] ] [ brief ]command check the status of VRRP6.
----End
Example
After the configuration succeeds, you can run the display vrrp6 command to view the status of
a VRRP6 virtual router.
<Quidway> display vrrp6
State : Initialize
Virtual IP : FE80::10
PriorityRun : 90
MasterPriority : 0
TimerRun : 100
TimerConfig : 100
Uncheck hop limit : NO
Accept Mode : OFF
Track IF : Vlanif100 priority reduced : 10
IF State : UP
BFD-session state : DOWN
7.4 Configuring VRRP6 to Track the Status of an Interface

This section describes how to configure VRRP6 to track the interface status to improve system
reliability.

7.4.2 Configuring VRRP6 to Track the Status of an Interface

VRRP6 can track the status of interfaces. That is, VRRP6 provides backup routes when a fault
occurs on an interface in a backup group or other interfaces on the S5300.
The methods of tracking the interface status are as follows:
l When a tracked interface is Down, the priority of the S5300 in the backup group reduces
by a certain value between 1 and 254 automatically to be lower than those of other
S5300es in the group.
l The S5300 with the highest priority becomes the master and completes the switchover.
Before configuring VRRP6 to track the status of an interface, complete the following tasks:
l Configuring physical parameters for interfaces

l Configuring IPv6 addresses for interface
l Configuring a VRRP6 backup group
Data Preparation
To configure VRRP6 to track the status of an interface, you need the following data.
No. Data
1 ID of a backup group
2 Interface to be tracked
3 Value by which the priority decreases
7.4.2 Configuring VRRP6 to Track the Status of an Interface
Context
Do as follows on the S5300 where the interface to be tracked resides.
Procedure
Step 1 Run:
system-view
Step 2 Run:

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

By default, when the tracked interface is Down, its priority decreases by 10.
l increased value-increased: specifies the increment of the priority when the tracked interface
becomes Down. The value ranges from 1 to 255. The maximum value of the priority is 254.
This parameter is valid only when the backup group is in Backup state.
l reduced value-reduced: specifies the decrement of the priority when the tracked interface
becomes Down. The value ranges from 1 to 255. The minimum value of the priority is 1.
l If VRRP6 tracks BFD sessions and interfaces at the same time, the number of tracked BFD
sessions or interfaces cannot exceed 8. If increased value-increased is specified for all the
tracked BFD sessions and interfaces, the original priority of the backup switch plus the
increments can exceed the priority of the master only if all the monitored BFD sessions and
interfaces are Down. If the sum of the original priority of the backup switch and the
increments exceeds the priority of the master switch when some of interfaces or BFD sessions
become Down, the increments of all BFD sessions and interfaces become invalid when
another interface or BFD session becomes down.
NOTE
An S5300 can track up to eight interfaces.
----End

Procedure
l Run the display vrrp6 [ interface interface-type interface-number [ vrid virtual-router-
id ] ] [ brief ] command check the status of VRRP6.
----End
Example
After the configuration succeeds, you can run the display vrrp6 command to view the status of
a VRRP6 backup group.
display vrrp6 interface vlanif 100 vrid 254
State : Initialize
PriorityRun : 90
MasterPriority : 0
TimerRun : 100
TimerConfig : 100
Accept Mode : OFF
IF State : UP

7.5 Configuring VRRP6 to Tracking the BFD Session Status

This section describes how to configure VRRP6 to track the BFD session status to implement
fast switchover.

7.5.2 Configuring VRRP6 to Tracking the BFD Session Status

VRRP6 can track the BFD session status. When the BFD session status changes, the VRRP6
module is notified so that fast switchover is implemented.
When a VRRP6 group tracks several normal BFD sessions, status changes of one BFD session
do not affect the status of the other BFD sessions.
When the status of a traced normal BFD session changes, the priority of the switch is changed
to trigger the switchover. When the status of the tracked BFD session recovers, the priority of
the switch is restored. If VRRP6 tracks a peer BFD session or a link BFD session, VRRP6
triggers active/standby switchover without changing the priority of the switch when the status
of the BFD session changes.
Before configuring VRRP6 to track the BFD session status, complete the following tasks:
l Setting physical parameters of interfaces
l Configuring network layer attributes of interfaces to ensure network connectivity
l Configuring a VRRP6 group
l Creating BFD sessions
Data Preparation
To configure VRRP6 to track the BFD session status, you need the following data.
No. Data
1 VRRP6 backup ID.

7.5.2 Configuring VRRP6 to Tracking the BFD Session Status

Context
Do as follows on the switch that need to perform VRRP6 fast switchover.
NOTE
To configure VRR6 to track a peer BFD session, you must configure the peer BFD session on both ends
of the session. Otherwise, network flapping may occur.
Procedure
Step 1 Run:
system-view

Step 2 Run:
The view of the interface configured with a VRRP6 group is displayed.

Step 3 Run:
vrrp6 vrid virtual-router-id track bfd-session { bfd-session-id | session-name bfd-
name } [ increased value-increased | reduced value-reduced ]
The VRRP6 group is configured to track the status of a common BFD session.
increased value-increased: specifies the increment of the priority when the tracked BFD session
becomes Down. The value ranges from 1 to 255. The priority can increase to 254. This parameter
is valid only when the VRRP6 group is in Backup state.
reduced value-reduced: specifies the decrement of the priority when the tracked BFD session
becomes Down. The value ranges from 1 to 255. The priority can decrease to 1. By default,
when the tracked BFD session becomes Down, the priority of the VRRP6 group decreases by
10.
When setting the increment or decrement of the priority, especially when using the default value,
note that the priority of the backup device in a VRRP6 group must be higher than that of the
master device after the priority is changed. Then, fast switchover can be implemented.
When a VRRP6 group monitors both BFD sessions and interfaces, the total number of BFD
sessions and interfaces cannot exceed 8. If increased value-increased is specified for all BFD
sessions and interfaces, the increased priority of the backup device can exceed the priority of
the master device only when all the tracked BFD sessions or interfaces go Down. If the increased
priority of the backup device exceeds the priority of the master device when some of interfaces
or BFD sessions become Down, the increments of other BFD sessions or interfaces are invalid.
NOTE
An S5300 can track up to eight BFD sessions.
----End

Prerequisite
The configurations of VRRP6 fast switchover are complete.

Procedure
Step 1 Run the display vrrp6 [ interface interface-type interface-number [ vrid virtual-router-id ] ]
[ brief ] command to check information about a specified VRRP6 group.
----End
Example
Run the display vrrp6 command, and you can find that the tracked BFD session is in Up state.
For example:
State : Initialize
PriorityRun : 90
MasterPriority : 0
TimerRun : 100
TimerConfig : 100
Accept Mode : OFF
IF State : UP
7.6 Adjusting and Optimizing VRRP6

This section describes how to adjust the related parameters of VRRP6 packets to optimize
VRRP6.

7.6.2 Setting the Interval for Sending VRRP6 Advertisement Messages
7.6.3 Setting the Preemption Delay on the S5300
7.6.4 Disabling Checking of the Hop Limit of VRRP6 Packets
7.6.5 Disabling Preemption Mode on an Interface
You can configure the related parameters of VRRP6 packets to optimize the functions of the
backup group.
l Prolonging the interval for sending VRRP6 advertisement messages by the member of the
backup group can reduce the network load caused by protocol packets.

l Setting the same interval for sending VRRP6 advertisement messages by the members of
the backup group can avoid the coexistence of multiple masters in the backup group.
l Barring the test of the hoplimit value in VRRP6 packets can improve the compatibility
between Huawei devices and non-Huawei devices.
l Configuring the preemption mode and preemption delay on the S5300 in the backup group
can quicken or slower the speed of the switchover between devices.
Before adjusting and optimizing VRRP6, complete the following tasks:
l Configuring physical parameters of interfaces
l Configuring a VRRP6 backup group
Data Preparation
To adjust and optimize VRRP6, you need the following data.
No. Data
1 Interval for sending VRRP6 advertisement messages
2 Preemption delay
7.6.2 Setting the Interval for Sending VRRP6 Advertisement

Messages
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
vrrp6 vrid virtual-router-id timer advertise interval
The interval for sending VRRP6 advertisement messages is set.

The master device sends VRRP6 advertisement messages at the interval to the backup devices
in the group to notify that the master device works normally. If the backup devices do not receive
any VRRP6 advertisement message after the interval expires, the backup device with the highest
priority becomes the master device automatically.

The interval for sending VRRP6 advertisement messages ranges from 100 to 4095, in
centiseconds. By default, the value is 100.
----End
7.6.3 Setting the Preemption Delay on the S5300
Context
Configuring the interval of preemption can effectively avoid frequent status change.
Do as follows on the S5300 in the VRRP backup group where the preemption delay needs to be
adjusted.
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
vrrp6 vrid virtual-router-id preempt-mode timer delay delay-value
The preemption delay of the S5300 in the backup group is set.

The preemption delay ranges from 0 to 3600, in centiseconds.
By default, the preemption mode is adopted, and the delay is 0 centisecond, that is, immediate
preemption.
In the immediate preemption mode, when the priority of a backup device is higher than that of
the current master device, the backup device immediately becomes the new master device.
----End
7.6.4 Disabling Checking of the Hop Limit of VRRP6 Packets
Context
Procedure
Step 1 Run:
system-view

Step 2 Run:


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

By default, the hop-limit value of VRRP6 packets is checked.
In certain situations especially when the S5300 is connected to devices of other vendors, packets
may be discarded incorrectly if the hop limit of VRRP6 packets is checked. In this case, you can
run the vrrp6 un-check hop-limit command to disable the S5300 from checking the hop limit
of VRRP6 packets.
----End
7.6.5 Disabling Preemption Mode on an Interface

Context
Do as follows on the S5300:
Procedure
Step 1 Run:
system-view

Step 2 Run:

Step 3 Run:
vrrp6 vrid virtual-router-id preempt-mode disable
The preemption mode is disabled on the interface.

By default, the preemption mode is enabled on interfaces.
To enable the device with higher priority to become the master device in a VRRP6 group, you
need to enable the preemption mode on the device.
When the preemption mode is disabled, the S5300 remains the backup device even if its priority
is higher than the priority of the master device.
----End

Procedure
l Run the display vrrp6 [ interface vlanif interface-number [ vrid virtual-router-id ] ]
command to check the status of VRRP6.
l Run the display vrrp6 command to check the global VRRP6 configuration.
l Run the display vrrp6 statistics command to check the global VRRP6 configuration.

l Run the display vrrp6 [ interface vlanif interface-number ] [ vrid virtual-router-id ]

statistics command to check the statistics about a specified VRRP6 group.
----End
Example
# Display the global VRRP6 configuration.
State : Initialize
PriorityRun : 90
MasterPriority : 0
TimerRun : 100
TimerConfig : 100
Accept Mode : OFF
IF State : UP
# Display the VRRP6 configuration on a specified interface.

<Quidway> display vrrp6 interface vlanif 12
State : Initialize
PriorityRun : 90
MasterPriority : 0
TimerRun : 100
TimerConfig : 100
Accept Mode : OFF
IF State : UP
# Display the global VRRP6 statistics.

<Quidway> display vrrp6 statistics
Checksum errors : 0
Version errors : 0
Vrid errors : 0
Vlanif240 | virtual router 11

Transited to master : 0
Received advertisements : 0
Advertisement interval errors : 0
Failed to authentication check : 0
Received ip ttl errors : 0
Received packets with priority zero : 0
Sent packets with priority zero : 0
Received invalid type packets : 0
Received unmatched address list packets : 0

Unknown authentication type packets : 0

Mismatched authentication type : 0
Packet length errors : 0
Discarded packets since track admin-vrrp : 0
# Display the VRRP statistics on a specified interface.

<Quidway> display vrrp6 interface vlanif 10 vrid 1 statistics
Vlanif10 | virtual router 1
Transited to master : 0
Received advertisements : 0
Advertisement interval errors : 0
Failed to authentication check : 0
Received ip ttl errors : 0
Received packets with priority zero : 0
Sent packets with priority zero : 0
Received invalid type packets : 0
Received unmatched address list packets : 0
Unknown authentication type packets : 0
Mismatched authentication type : 0
Packet length errors : 0
Discarded packets since track admin-vrrp : 0
7.7 Configuring mVRRP6 Backup Groups

An mVRRP6 backup group can be bound to other member backup groups and determine the

Before configuring an mVRRP6 backup group, familiarize yourself with the applicable
7.7.2 Configuring mVRRP6 Backup Group
Each VRRP6 backup group needs to maintain its own state machine by sending VRRP6 packets.
Configuring an mVRRP6 backup group can reduce bandwidth consumption of VRRP6 packets.
7.7.3 (Optional) Configuring Member VRRP6 Backup Groups and Binding them to the
mVRRP6 Backup Group
Through the bindings between member VRRP6 backup groups and the mVRRP6 backup group,
the state machines of member VRRP6 backup groups can be consistent with the state machine
of the mVRRP6 backup group.
By viewing all bindings in an mVRRP6 backup group, you can check whether the configurations
are successful.

Before configuring an mVRRP6 backup group, familiarize yourself with the applicable

Application Environment
Figure 7-1 mVRRP6 determines the dual-homing of the master and slave routers
NPE1
mVRRP
UPE
NPE2
As shown in Figure 7-1, when the convergence layer of the Metro Ethernet (ME) dual NPEs
are deployed for high reliability. The master and standby routers are determined by mVRRP6
between NPEs.
The mVRRP6 backup group is actually the ordinary VRRP6 backup group. The difference is
that the mVRRP6 backup group can be bound to other backup groups of different services. The
status of the backup group of related services depends on the binding relationship.
The mVRRP6 backup group can be bound to several backup group members. The mVRRP6
backup group cannot be bound to other management backup groups.
According to different applications, the binding relationship of the mVRRP6 backup group is
as follows:
l The VRRP6 backup group is bound to the mVRRP6 backup group: UPEs are dual-homed
to NPEs. VRRP6 is run between NPEs. The master NPE and backup NPE are determined
by the configured priority of VRRP6. Multiple VRRP6 backup groups run between NPEs
with different services.
If each VRRP6 backup group needs to maintain its own state machine, a huge number of
VRRP6 packets exist among NPEs. To simplify the process and decrease occupancy of
bandwidth, you can set one VRRP6 backup group as the mVRRP6 backup group. Other
backup group members are bound to the mVRRP6 backup group. The master and slave
routers are determined directly by the binding relationship.
l The service interfaces are bound to the mVRRP6 backup group. If the UPEs are dual-homed
to NPEs through two physical links. You can bind the member interfaces to the mVRRP6
backup group to determine the master member interfaces and the slave interfaces.
Before configuring mVRRP6, complete the following tasks:
l Configuring physical parameters of an interface


l Configuring attributes of network layer of interfaces for connectivity
Data Preparation
To configure mVRRP6, you need the following data.
No. Data
1 ID of the mVRRP6 and IDs of VRRP6 backup group members
2 Virtual IP address of the mVRRP6 and virtual IP addresses of VRRP6 backup group
members
3 Priority of the mVRRP6
4 Number of the member interface
5 PW peer IP address
7.7.2 Configuring mVRRP6 Backup Group

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

l Run:

l Run:
admin-vrrp6 vrid virtual-router-id
This VRRP6 backup group is configured as an mVRRP backup group.

----End
7.7.3 (Optional) Configuring Member VRRP6 Backup Groups and

Binding them to the mVRRP6 Backup Group
Through the bindings between member VRRP6 backup groups and the mVRRP6 backup group,
the state machines of member VRRP6 backup groups can be consistent with the state machine
of the mVRRP6 backup group.

Context
Do as follows on each switch on which the member VRRP6 backup groups need to be bound to
an mVRRP6 backup group.
Procedure
l Run:
system-view

l Run:
The VLANIF interface view of a VRRP6 member is displayed.

l Run:
vrrp vrid virtual-router-id1 track admin-vrrp interface interface-type
interface-number [ .subinterface-number ] vrid virtual-router-id2
The member VRRP6 backup group is bound to the mVRRP6 backup group.
After the member VRRP6 backup group is bound to the mVRRP6 backup group, the state
machine of the member VRRP6 backup group becomes dependent. That is, the member
VRRP6 backup group deletes the protocol timer, and no longer sends or receives packets,
and implements its state machine by directly copying the status of the mVRRP6 backup
group. The backup member can be bound to only one mVRRP6.
----End

By viewing all bindings in an mVRRP6 backup group, you can check whether the configurations
are successful.
Prerequisite
The configurations of the mVRRP6 backup groups function are complete.
Procedure
l Run the display vrrp6 binding admin-vrrp6 [ interface interface-type1 interface-
number1 ] [vrid virtual-router-id1 ] member-vrrp [ interface interface-type2 interface-
number2 ] [ vrid virtual-router-id2 ] command to check the binding between the mVRRP6
backup group and member VRRP6 backup groups.
----End
7.8 Maintaining VRRP6

This section describes how to maintain VRRP6.
7.8.1 Resetting VRRP6 Statistics
7.8.1 Resetting VRRP6 Statistics

Context
WARNING
VRRP6 statistics cannot be restored after you clear them. So, confirm the action before you use
the command.
To clear the VRRP6 statistics, run the following reset command in the user view.
Procedure
l Run the reset vrrp6 [ interface interface-type interface-number ] [ vrid virtual-router-
id ] statistics command to reset the statistics about a specified VRRP6 group.
----End

This section provides several configuration examples of VRRP6.
7.9.1 Example for Configuring VRRP6 on an Interface

7.9.2 Example for Configuring VRRP6 in Load Balancing Mode
7.9.1 Example for Configuring VRRP6 on an Interface

Switch A and Switch B elect a master device according to the configured priorities in a VRRP6
group.
Once the master device is determined in the group, only the master device responds to IPv6
messages. If the master device goes down, the backup device becomes the master device and
the hosts in the private network can still communicate with external networks.
The configured virtual address can be same as the address of any physical interface of the Switch
A or Switch B.

Figure 7-2 Networking of VRRP6
Virtual IP Address:
2000::1
GE0/0/1
SwitchA
Vlanif100
Master
2000::2
HostA
GE0/0/2
Vlanif100 SwitchB
HostB 2000::3
Network
Backup
Ethernet
1. Configure IPv6 addresses for interfaces.
2. Configure virtual IPv6 addresses.
Data Preparation
l VRRP6 group ID
l Priorities of the Switches in the VRRP6 group
l IPv6 addresses to be configured for interfaces
l Virtual IPv6 addresses to be configured for interfaces in the VRRP6 group
Procedure
Step 1 Enable IPv6 forwarding.
[SwitchA] ipv6
[SwitchB] ipv6
Step 2 Configure IPv6 addresses for interfaces.

[SwitchA] vlan 100


[[SwitchA] interface vlanif 100
[SwitchA-Vlanif100] ipv6 enable
[SwitchA-Vlanif100] ipv6 address 2000::2 link-local
[SwitchB] vlan 100
[SwitchB] interface gigabitethernet0/0/1
[SwitchB-GigabitEthernet0/0/1] port hybrid pvid vlan 100
[SwitchB-GigabitEthernet0/0/10] port hybrid untagged vlan 100
[[SwitchB] interface vlanif 100
[SwitchB-Vlanif100] ipv6 enable
[SwitchB-Vlanif100] ipv6 address 2000::3 link-local
Step 3 Configure virtual IPv6 addresses on interfaces in the VRRP6 group.

[SwitchA-Vlanif100] vrrp6 vrid 24 virtual-ip fe80::1 link-local
[SwitchA-Vlanif100] vrrp6 vrid 24 virtual-ip 2000::1
[SwitchA-Vlanif100] vrrp6 vrid 24 accept-mode enable
[SwitchB-Vlanif100] vrrp6 vrid 24 virtual-ip fe80::1 link-local
[SwitchB-Vlanif100] vrrp6 vrid 24 virtual-ip 2000::1
[SwitchB-Vlanif100] vrrp6 vrid 24 accept-mode enable
Step 4 Set the priority of SwitchB to a value lower than the priority of SwitchA.
[SwitchB-Vlanif100] vrrp6 vrid 24 priority 25

The following information shows that SwitchA is the master device, and SwitchB is the backup
device.
[SwitchA] display vrrp6 interface vlanif100
State : Master
2000::1
PriorityRun : 250
MasterPriority : 1
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0218
Accept Mode : ON
[SwitchB] display vrrp6 interface vlanif100
State : Backup
2000::1
PriorityRun : 25
PriorityConfig : 25
MasterPriority : 1
TimerRun : 100
TimerConfig : 100

Virtual Mac : 0000-5e00-0218

Accept Mode : ON
----End
Configuration Files
#
sysname SwitchA
#
vlan batch 100
#
ipv6
#
interface Vlanif100
ipv6 enable
ipv6 address 2000::2/64
vrrp6 vrid 24 virtual-ip FE80::1 link-local
vrrp6 vrid 24 virtual-ip 2000::1
vrrp6 vrid 24 accept-mode enable
#
interaface GigabitEthernet0/0/1
#
return

#
sysname SwitchB
#
vlan batch 100
#
ipv6
#
interface Vlanif100
ipv6 enable
vrrp6 vrid 24 priority 25
vrrp6 vrid 24 accept-mode enable
#
interaface GigabitEthernet0/0/1
#
return
7.9.2 Example for Configuring VRRP6 in Load Balancing Mode

As shown in Figure 7-3,
l SwitchA is the master device in VRRP group 1 and the backup device in VRRP group 2.
l SwitchB is the master device in VRRP group 2 and the backup device in VRRP group 1.
l Host A on the LAN uses the virtual IPv6 address of VRRP group 1 as the gateway address,
and Host B uses the virtual IPv6 address of VRRP group 2 as the gateway address. The
two VRRP groups load balance traffic and back up each other.

Figure 7-3 Networking of VRRP in load balancing mode

Backup group 1
Virtual IP Address
2000::100 SwitchA
group 1：Master
group 2：Backup
GE0/0/2
GE0/0/1
GE0/0/1
HostA
2000::3/64 GE0/0/3
SwitchC
HostC
GE0/0/2 2003::1/64
HostB GE0/0/1 GE0/0/2

2000::4/64
SwitchB
Etherent group 1：Backup
Backup group 2 group 2：Master
Virtual IP Address
2000::60

SwitchA GE0/0/1 VLANIF100 2000::1/64
GE0/0/2 VLANIF200 2002::1/64
SwitchB GE0/0/1 VLANIF100 2000::2/64
GE0/0/2 VLANIF400 2001::1/64
SwitchC GE0/0/1 VLANIF200 2002::2/64
GE0/0/2 VLANIF400 2001::2/64
GE0/0/3 VLANIF300 2003::2/64
1. Create VRRP group 1 and VRRP group 2 on VLANIF 100 of SwitchA. Ensure that
SwitchA is the master device in VRRP group 1 and the backup device in VRRP group 2.
2. Create VRRP group 1 and VRRP group 2 on VLANIF 100 of SwitchB. Ensure that
SwitchB is the backup device in VRRP group 1 and the master device in VRRP group 1.

Data Preparation
l IPv6 addresses of the interfaces
l IDs and virtual IPv6 addresses of the VRRP groups
l Priorities of the switchs in each VRRP group
Procedure
Step 1 Configure IP addresses for the interfaces. The configuration procedure is not mentioned here.
Step 2 Configure OSPFv3 on SwitchA, SwitchB, and SwitchC so that they can communicate with each
other. The configuration procedure is not mentioned here.
Step 3 Configure the hosts.
Set the default gateway address of Host A to 2000::10, which is the virtual IPv6 address of VRRP
group 1. Set the default gateway address of Host B to 2000::60, which is the virtual IPv6 address
of VRRP group 2. Set the default gateway address of Host C to 2003::2.
Step 4 Configure VRRP6 groups.
# Create VRRP group 1 and VRRP group 2 on VLANIF 100 of SwitchA. Set the priority of
SwitchA in VRRP group 1 to 120 so that SwitchA becomes the master device in VRRP group
1. Use the default priority of SwitchA in VRRP group 2 so that SwitchA becomes the backup
device in VRRP group 2.
[SwitchA] interface vlanif100
[SwitchA-Vlanif100] vrrp6 vrid 1 virtual-ip FE80::1 link-local
[SwitchA-Vlanif100] vrrp6 vrid 1 virtua-ip 2000::100
[SwitchA-Vlanif100] vrrp6 vrid 1 priority 120
[SwitchA-Vlanif100] vrrp6 vrid 2 virtual-ip FE80::2 link-local
[SwitchA-Vlanif100] vrrp6 vrid 2 virtua-ip 2000::60
# Create VRRP group 1 and VRRP group 2 on VLANIF 100 of SwitchB. Use the priority of
SwitchB in VRRP group 1 to 120 so that SwitchB becomes the backup device in VRRP group
1. Set the priority of SwitchB in VRRP group 2 to 120 so that SwitchB becomes the master
[SwitchB-Vlanif100] vrrp6 vrid 1 virtual-ip FE80::1 link-local
[SwitchB-Vlanif100] vrrp6 vrid 1 virtua-ip 2000::100
[SwitchB-Vlanif100] vrrp6 vrid 2 virtual-ip FE80::2 link-local
[SwitchB-Vlanif100] vrrp6 vrid 2 virtua-ip 2000::60
[SwitchB-Vlanif100] vrrp6 vrid 2 priority 120

After the preceding configuration is complete, Host A and Host C can ping Host B successfully.
Run the display vrrp6 command on SwitchA, and you can find that VRRP group 1 and VRRP
group 2 are created on SwitchA. SwitchA is the master device in VRRP group 1 and the backup
<Switch>A display vrrp6
State : Master

2000::100
PriorityRun : 120
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
State : Backup
2000::60
PriorityRun : 100
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0102
Uncheck hop limit : YES
Accept Mode : ON
Run the display vrrp6 command on SwitchB, and you can find that VRRP group 1 and VRRP
group 2 are created on SwitchB. SwitchB is the backup device in VRRP group 1 and the master
<Switch>A display vrrp6
State : Backup
2000::100
PriorityRun : 100
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0201
Accept Mode : ON
State : Master
2000::60
PriorityRun : 120
TimerRun : 100
TimerConfig : 100
Virtual Mac : 0000-5e00-0102
Accept Mode : ON
----End

Configuration Files
#
sysname SwitchA
#
vlan batch 100 200
#
ipv6
#
ospfv3 1
router-id 1.1.1.1
#
interface Vlanif100
ipv6 enable
ospfv3 1 area 0.0.0.0
#
interface Vlanif200
ipv6 enable
#
port hybrid pvid untagged 100
#
#
return

#
sysname SwitchB
#
vlan batch 100 400
#
ipv6
#
ospfv3 1
router-id 1.1.1.1
#
interface Vlanif100
ipv6 enable
#
interface Vlanif200
ipv6 enable
#
#


#
return

#
sysname SwitchC
#
#
ipv6
#
ospfv3 1
router-id 3.3.3.3
#
interface Vlanif200
ipv6 enable
ipv6 address 2002::2
#
interface Vlanif300
ipv6 enable
#
interface Vlanif400
ipv6 enable
#
#
#
#
return


Configuration Guide - Reliability (V100R005C01 02) PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuration Guide - Reliability (V100R005C01 02) PDF

Uploaded by

Copyright:

Available Formats

Quidway S5300 Series Ethernet Switches

Configuration Guide - Reliability

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2010-12-01) Huawei Proprietary and Confidential i

About This Document

This document describes how to configure the reliability.

This document is intended for:

l Data configuration engineers

Indicates a hazard with a high level of risk, which if not

Indicates a hazard with a medium or low level of risk, which

Indicates a potentially hazardous situation, which if not

NOTE Provides additional information to emphasize or supplement

Issue 02 (2010-12-01) Huawei Proprietary and Confidential iii

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

# A line starting with the # sign is comments.

Changes in Issue 02 (2010-12-01)

Changes in Issue 01 (2010-08-15)

iv Huawei Proprietary and Confidential Issue 02 (2010-12-01)

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

2 Smart Link and Monitor Link Configuration.......................................................................2-1

Issue 02 (2010-12-01) Huawei Proprietary and Confidential v

2.2.9 Checking the Configuration...................................................................................................................2-9

vi Huawei Proprietary and Confidential Issue 02 (2010-12-01)

3.4.7 Creating an RRPP Ring........................................................................................................................3-22

4 Ethernet OAM Configuration..................................................................................................4-1

Issue 02 (2010-12-01) Huawei Proprietary and Confidential vii

4.6.1 Establishing the Configuration Task....................................................................................................4-22

viii Huawei Proprietary and Confidential Issue 02 (2010-12-01)

4.14 Configuring Association Between an Ethernet CFM Module and an Interface..........................................4-54

Issue 02 (2010-12-01) Huawei Proprietary and Confidential ix

4.21.10 Example for Associating Ethernet CFM with Smart Link.............................................................4-112

x Huawei Proprietary and Confidential Issue 02 (2010-12-01)

5.9.2 Debugging BFD...................................................................................................................................5-25

Issue 02 (2010-12-01) Huawei Proprietary and Confidential xi

6.9.2 Configuring VRRPv3...........................................................................................................................6-26

xii Huawei Proprietary and Confidential Issue 02 (2010-12-01)

Figure 1-1 Crossed connection of fibers..............................................................................................................1-2

Issue 02 (2010-12-01) Huawei Proprietary and Confidential xiii

xiv Huawei Proprietary and Confidential Issue 02 (2010-12-01)

Table 3-1 Mapping between protected VLANs and instances...........................................................................3-52

Issue 02 (2010-12-01) Huawei Proprietary and Confidential xv

About This Chapter

1.1 Introduction to DLDP

Issue 02 (2010-12-01) Huawei Proprietary and Confidential 1-1

1.1 Introduction to DLDP

Figure 1-1 Crossed connection of fibers

Figure 1-2 Disconnection of one fiber

1-2 Huawei Proprietary and Confidential Issue 02 (2010-12-01)

1.2 Configuring DLDP Functions

1.2.1 Establishing the Configuration Task

1.2.1 Establishing the Configuration Task

l Configuring the interfaces at both ends to work in non-auto-negotiation mode

1 Type and number of each interface

2 (Optional)Name of the interface group

Issue 02 (2010-12-01) Huawei Proprietary and Confidential 1-3