HP 5130 EI Configuration Manual

Download

Page 1

HP 5130 EI Switch Series

High Availability Configuration Guide

Part number: 5998-5475a

Software version: Release 31xx

Document version: 6W100-20150731

Page 2

Legal and notice information

No part of this documentation may be reproduced or transmitted in any form or by any means without prior written consent of Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice.

HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Page 3

Configuring Ethernet OAM ········································································································································· 1

Major functions of Ethernet OAM ·························································································································· 1 Ethernet OAMPDUs ·················································································································································· 1 How Ethernet OAM works ······································································································································ 1

Protocols and standards ·········································································································································· 3 Ethernet OAM configuration task list ······························································································································ 4 Configuring basic Ethernet OAM functions ···················································································································· 4 Configuring the Ethernet OAM connection detection timers ························································································ 4 Configuring link monitoring ············································································································································· 5

Configuring errored symbol event detection ········································································································· 5

Configuring errored frame event detection ··········································································································· 6

Configuring errored frame period event detection ······························································································· 7

Configuring errored frame seconds event detection ···························································································· 7 Configuring the action a port takes after it receives an Ethernet OAM event from the remote end ························ 8 Configuring Ethernet OAM remote loopback ················································································································ 9

Configuration guidelines ········································································································································· 9

Enabling Ethernet OAM remote loopback on a specific port ············································································· 9

Enabling Ethernet OAM remote loopback on the port ······················································································ 10

Rejecting the Ethernet OAM remote loopback request from a remote port ···················································· 10 Displaying and maintaining Ethernet OAM ················································································································ 10 Ethernet OAM configuration example ························································································································· 11

Network requirements ··········································································································································· 11

Configuration procedure ······································································································································ 11

Configuring CFD ························································································································································ 13

Basic CFD concepts ··············································································································································· 13

CFD functions ························································································································································· 16

EAIS ········································································································································································ 18

Enabling CFD ························································································································································· 19

Configuring service instances ······························································································································ 19

Configuring MEPs ·················································································································································· 20

Configuring MIP auto-generation rules ··············································································································· 20 Configuring CFD functions ············································································································································ 21

Configuration prerequisites ·································································································································· 21

Configuring CC on MEPs ····································································································································· 21

Configuring LB on MEPs ······································································································································· 22

Configuring LT on MEPs ········································································································································ 22

Configuring AIS ····················································································································································· 23

Configuring LM ······················································································································································ 23

Configuring one-way DM ····································································································································· 23

Configuring two-way DM ····································································································································· 24

Configuring TST ····················································································································································· 24 Configuring EAIS ···························································································································································· 25 Displaying and maintaining CFD ································································································································· 25

Page 4

CFD configuration example ·········································································································································· 26

Configuring DLDP ······················································································································································· 32

Basic concepts ······················································································································································· 33

How DLDP works ··················································································································································· 34 Configuration restrictions and guidelines ···················································································································· 36 DLDP configuration task list ··········································································································································· 36 Enabling DLDP ································································································································································ 37 Setting the interval to send advertisement packets ····································································································· 37 Setting the DelayDown timer ········································································································································ 37 Setting the port shutdown mode ··································································································································· 38 Configuring DLDP authentication ·································································································································· 38 Displaying and maintaining DLDP ································································································································ 39 DLDP configuration examples ······································································································································· 39

Automatically shutting down unidirectional links ······························································································· 39

Manually shutting down unidirectional links ······································································································ 42

Configuring RRPP ······················································································································································· 47

Basic RRPP concepts ·············································································································································· 48

RRPPDUs ································································································································································· 50

RRPP timers ····························································································································································· 51

How RRPP works ···················································································································································· 51

Typical RRPP networking ······································································································································· 53

Protocols and standards ······································································································································· 55 RRPP configuration task list············································································································································ 56 Creating an RRPP domain ············································································································································· 56 Configuring control VLANs ··········································································································································· 56 Configuring protected VLANs ······································································································································· 57 Configuring RRPP rings ·················································································································································· 58

Configuring RRPP ports ········································································································································· 58

Configuring RRPP nodes ······································································································································· 59 Activating an RRPP domain ··········································································································································· 61 Configuring RRPP timers ················································································································································ 61 Configuring an RRPP ring group ·································································································································· 62 Displaying and maintaining RRPP ································································································································ 62 RRPP configuration examples ········································································································································ 63

Single ring configuration example ······················································································································ 63

Intersecting ring configuration example ·············································································································· 65

Dual-homed rings configuration example ··········································································································· 71

Load-balanced intersecting-ring configuration example···················································································· 81 Troubleshooting RRPP ···················································································································································· 91

Configuring Smart Link ·············································································································································· 93

Terminology ··························································································································································· 94

How Smart Link works ·········································································································································· 94

Smart Link collaboration mechanisms ················································································································· 95 Smart Link configuration task list ·································································································································· 96 Configuring a Smart Link device ·································································································································· 96

Configuring protected VLANs for a smart link group ························································································ 96

Configuring member ports for a smart link group ····························································································· 97

Configuring role preemption for a smart link group·························································································· 98

Enabling the sending of flush messages ············································································································· 98

Page 5

Configuring the collaboration between Smart Link and Track ········································································· 99 Configuring an associated device ······························································································································· 99

Enabling the receiving of flush messages ··········································································································· 99 Displaying and maintaining Smart Link ····················································································································· 100 Smart Link configuration examples ···························································································································· 100

Single smart link group configuration example ······························································································· 100

Multiple smart link groups load sharing configuration example ···································································· 105

Smart Link and Track collaboration configuration example ··········································································· 109

Configuring Monitor Link ········································································································································ 115

Overview ······································································································································································· 115 Configuration restrictions and guidelines ·················································································································· 116 Monitor Link configuration task list ····························································································································· 116 Enabling Monitor Link globally ··································································································································· 116

Creating a monitor link group ··························································································································· 116

Configuring monitor link group member interfaces ························································································· 117

Configuring the switchover delay for the downlink interfaces in a monitor link group ······························· 117 Displaying and maintaining Monitor Link ················································································································· 118 Monitor Link configuration example ·························································································································· 118

Configuring BFD ······················································································································································ 123

BFD session establishment ·································································································································· 123

BFD session modes and operating modes ········································································································ 123

Supported features ·············································································································································· 124

Configuring echo packet mode ························································································································· 125

Configuring control packet mode ······················································································································ 125

Configuring a BFD template ······························································································································· 127 Displaying and maintaining BFD ································································································································ 128

Configuring Track ··················································································································································· 129

Collaboration fundamentals ······························································································································· 129

Collaboration application example ··················································································································· 130 Track configuration task list ········································································································································· 130 Associating the Track module with a detection module ··························································································· 131

Associating Track with NQA ····························································································································· 131

Associating Track with BFD ································································································································ 131

Associating Track with CFD ······························································································································· 132

Associating Track with interface management ································································································· 132 Associating the Track module with an application module ····················································································· 133

Associating Track with static routing ················································································································· 133

Associating Track with PBR ································································································································ 134

Associating Track with Smart Link ····················································································································· 136 Displaying and maintaining track entries ·················································································································· 136 Track configuration examples ····································································································································· 136

Static routing-Track-NQA collaboration configuration example ···································································· 136

Static routing-Track-BFD collaboration configuration example ······································································· 141

Smart Link-Track-CFD collaboration configuration example ··········································································· 144

Support and other resources ·································································································································· 145

Contacting HP ······························································································································································ 145

Subscription service ············································································································································ 145

iii

Page 6

Related information ······················································································································································ 145

Documents ···························································································································································· 145

Websites ······························································································································································· 145 Conventions ·································································································································································· 146

Index ········································································································································································ 148

Page 7

Configuring Ethernet OAM

Overview

Ethernet Operation, Administration and Maintenance (OAM) is a tool that monitors Layer 2 link status and addresses common link-related issues on the "last mile." Ethernet OAM improves Ethernet management and maintainability. You can use it to monitor the status of the point-to-point link between two directly connected devices.

Major functions of Ethernet OAM

Ethernet OAM provides the following functions:

• Link performance monitoring—Monitors the performance indices of a link, including packet loss,

delay, and jitter, and collects traffic statistics of various types.

• Fault detection and alarm—Checks the connectivity of a link by sending OAM protocol data units

(OAMPDUs) and reports to the network administrators when a link error occurs.

• Remote loopback—Checks link quality and locates link errors by looping back OAMPDUs.

Ethernet OAMPDUs

Ethernet OAM operates on the data link layer. Ethernet OAM reports the link status by periodically exchanging OAMPDUs between devices, so that the administrator can effectively manage the network.

Ethernet OAMPDUs include the following types shown in Table 1.

Table 1 Functions of

OAMPDU t

Information OAMPDU

Event Notification OAMPDU

Loopback Control OAMPDU

NOTE:

Throughout this document, an Ethernet OAM-enabled port is called an Ethernet OAM entity or an OAM entity.

different types of OAMPDUs

e Function

Used for transmitting state information of an Ethernet OAM entity, including the information about the local device and remote devices, and customized information, to the remote Ethernet OAM entity, and maintaining OAM connections.

Used by link monitoring to notify the remote OAM entity when it detects problems on the link in between.

Used for remote loopback control. By inserting the information used to enable/disable loopback to a loopback control OAMPDU, you can enable/disable loopback on a remote OAM entity.

How Ethernet OAM works

This section describes the working procedures of Ethernet OAM.

Page 8

Ethernet OAM connection establishment

Ethernet OAM connection is the basis of all the other Ethernet OAM functions. OAM connection establishment is also known as the Discovery phase, where an Ethernet OAM entity discovers the remote OAM entity to establish a session.

In this phase, two connected OAM entities exchange Information OAMPDUs to advertise their OAM configuration and capabilities to each other for a comparison. If their Loopback, link detection, and link event settings match, the OAM entities establish an OAM connection.

An OAM entity operates in active mode or passive mode. OAM entities in active mode initiate OAM connections, and OAM entities in passive mode wait and respond to the OAM connection requests. To set up an OAM connection between two OAM entities, you must set at least one entity to operate in active mode.

Table 2 sho

ws the actions that a device can perform in different modes.

Table 2 Active Ethernet OAM mode and passive Ethernet OAM mode

Item Active Ethernet OAM mode

Initiating OAM Discovery Available Unavailable

Responding to OAM Discovery Available Available

Transmitting Information OAMPDUs

Transmitting Event Notification OAMPDUs

Transmitting Information OAMPDUs without any TLV

Transmitting Loopback Control OAMPDUs

Responding to Loopback Control OAMPDUs

Available Available

Available Unavailable

Available when both sides are operating in active OAM mode

Passive Ethernet OAM mode

Available

After an Ethernet OAM connection is established, the Ethernet OAM entities exchange Information OAMPDUs at the handshake packet transmission interval to detect the availability of the Ethernet OAM connection. If an Ethernet OAM entity receives no Information OAMPDU within the Ethernet OAM connection timeout time, the Ethernet OAM connection is considered disconnected.

Link monitoring

Error detection in an Ethernet is difficult, especially when the physical connection in the network is not disconnected, but network performance is degrading gradually.

Link monitoring detects link faults in various environments. Ethernet OAM entities monitor link status by exchanging Event Notification OAMPDUs. When detecting one of the link error events listed in Table 3, an O

AM entity sends an Event Notification OAMPDU to its peer OAM entity. The network administrator

can keep track of network status changes by retrieving the log.

Table 3 Ethernet OAM link error events

Ethernet OAM link events Descri

An errored symbol event occurs when the number of detected symbol errors

Errored symbol event

in the detection window (specified number of received symbols) exceeds the predefined threshold.

tion

Page 9

Ethernet OAM link events Description

Errored frame event

Errored frame period event

Errored frame seconds event

Remote fault detection

Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established OAM connections. In a network where traffic is interrupted due to device failures or unavailability, the flag field defined in Information OAMPDUs allows an Ethernet OAM entity to send error information (any critical link event type shown in Table 4) to its peer status and troubleshoot problems promptly.

Table 4 Critical link events

e Description OAMPDU transmission frequencies

An errored frame event occurs when the number of detected error frames in the detection window (specified detection interval) exceeds the predefined threshold.

An errored frame period event occurs when the number of frame errors in the detection window (specified number of received frames) exceeds the predefined threshold.

An errored frame seconds event occurs when the number of errored frame seconds (the second in which an errored frame appears is called an errored frame second) detected on a port in the detection window (specified detection interval) reaches the predefined threshold.

. You can use the log information to track ongoing link

Link Fault Peer link signal is lost. Once per second.

Dying Gasp

Critical Event An undetermined critical event happened. Non-stop.

The switch is able to receive Information OAMPDUs carrying the critical link events listed in Table 4.

The switch is able to send Information OAMPDUs carrying Link Fault events.

The switch is able to send Information OAMPDUs carrying Dying Gasp events when the switch is rebooted or relevant ports are manually shut down. Physical IRF ports, however, are unable to send this type of OAMPDUs.

The switch is unable to send Information OAMPDUs carrying Critical Events.

Remote loopback

Remote loopback is available only after the Ethernet OAM connection is established. With remote loopback enabled, the Ethernet OAM entity in active mode sends non-OAMPDUs to its peer. After receiving these frames, the peer does not forward them according to their destination addresses. Instead, it returns them to the sender along the original path.

Remote loopback enables you to check the link status and locate link failures. Performing remote loopback periodically helps to detect network faults promptly. Furthermore, performing remote loopback by network segments helps to locate network faults.

An unexpected fault, such as power failure, occurred.

Non-stop.

Protocols and standards

IEEE 802.3ah, Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications

Page 10

Ethernet OAM configuration task list

Tasks at a glance

(Required.) Configuring basic Ethernet OAM functions

(Optional.) Configuring the Ethernet OAM connection detection timers

(Optional.) Configuring link monitoring

• Configuring errored symbol event detection

• Configuring errored frame event detection

• Configuring errored frame period event detection

• Configuring errored frame seconds event detection

(Optional.) Configuring the action a port takes after it receives an Ethernet OAM event from the remote end

(Optional.) Configuring Ethernet OAM remote loopback

• Enabling Ethernet OAM remote loopback on a specific port

• Enabling Ethernet OAM remote loopback on the port

• Rejecting the Ethernet OAM remote loopback request from a remote port

Configuring basic Ethernet OAM functions

To set up an Ethernet OAM connection between two Ethernet OAM entities, you must set at least one entity to operate in active mode. An Ethernet OAM entity can initiate OAM connection only in active mode.

To change the Ethernet OAM mode on an Ethernet OAM-enabled port, first disable Ethernet OAM on the port.

To configure basic Ethernet OAM functions:

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet port

view.

3. Set the Ethernet OAM mode.

4. Enable Ethernet OAM.

System-view N/A

interface interface-type

interface-number

oam mode { active | passive }

oam enable

Remarks

N/A

The default is active Ethernet OAM mode.

Ethernet OAM is disabled by default.

Configuring the Ethernet OAM connection detection timers

After an Ethernet OAM connection is established, the Ethernet OAM entities exchange Information OAMPDUs at the handshake packet transmission interval to detect the availability of the Ethernet OAM

Page 11

connection. If an Ethernet OAM entity receives no Information OAMPDU within the Ethernet OAM connection timeout time, the Ethernet OAM connection is considered disconnected.

By adjusting the handshake packet transmission interval and the connection timeout timer, you can change the detection time resolution for Ethernet OAM connections.

You c an c onfig ure this c ommand i n syste m view o r port view. The config urat ion i n syste m view ta kes ef fect on all ports, and the configuration in port view takes effect on the specified port. For a port, the configuration in port view takes precedence.

After the timeout timer of an Ethernet OAM connection expires, the local OAM entity ages out its connection with the peer OAM entity, causing the OAM connection to disconnect. To keep the Ethernet OAM connections stable, HP recommends that you set the connection timeout timer to be at least five times the handshake packet transmission interval.

To configure the Ethernet OAM connection detection timers globally:

Step Command

1. Enter system view.

2. Configure the Ethernet OAM

handshake packet transmission interval.

3. Configure the Ethernet OAM

connection timeout timer.

To configure the Ethernet OAM connection detection timers on a port:

System-view N/A

oam global timer hello interval The default is 1000 milliseconds.

oam global timer keepalive interval

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet port

view.

3. Configure the Ethernet OAM

handshake packet transmission interval.

4. Configure the Ethernet OAM

connection timeout timer.

System-view N/A

interface interface-type interface-number

oam timer hello interval

oam timer keepalive interval

Remarks

The default is 5000 milliseconds.

Remarks

N/A

By default, an interface uses the value configured globally.

Configuring link monitoring

After Ethernet OAM connections are established, the link monitoring periods and thresholds configured in this section automatically take effect on all Ethernet ports.

Configuring errored symbol event detection

An errored symbol event occurs when the number of detected symbol errors in the detection window (specified number of received symbols) exceeds the predefined threshold.

Page 12

To configure errored symbol event detection globally:

Step Command

1. Enter system view.

2. Configure the errored symbol

event detection window.

3. Configure the errored symbol

event triggering threshold.

To configure errored symbol event detection on a port:

system-view N/A

oam global errored-symbol-period window window-value

oam global errored-symbol-period threshold threshold-value

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet port

view.

3. Configure the errored symbol

event detection window.

4. Configure the errored symbol

event triggering threshold.

system-view N/A

interface interface-type interface-number

oam errored-symbol-period window window-value

oam errored-symbol-period threshold threshold-value

Remarks

By default, the errored symbol event detection window is

100000000.

By default, the errored symbol event triggering threshold is 1.

Remarks

N/A

By default, an interface uses the value configured globally.

Configuring errored frame event detection

An errored frame event occurs when the number of times that error frames in the detection window (specified detection interval) are detected exceeds the predefined threshold.

To configure errored frame event detection globally:

Step Command

1. Enter system view.

2. Configure the errored frame

event detection window.

3. Configure the errored frame

event triggering threshold.

To configure errored frame event detection on a port:

Step Command

1. Enter system view.

system-view N/A

oam global errored-frame window window-value

oam global errored-frame threshold threshold-value

system-view N/A

Remarks

By default, the errored frame event detection window is 1000 milliseconds.

By default, the errored frame event triggering threshold is 1.

Remarks

2. Enter Layer 2 Ethernet port

view.

interface interface-type interface-number

N/A

Page 13

Step Command

3. Configure the errored frame

event detection window.

oam errored-frame window

window-value

Remarks

By default, an interface uses the value configured globally.

4. Configure the errored frame

event triggering threshold.

oam errored-frame threshold

threshold-value

By default, an interface uses the value configured globally.

Configuring errored frame period event detection

An errored frame period event occurs when the number of times that frame errors in the detection window (specified number of received frames) are detected exceeds the predefined threshold.

To configure errored frame period event detection globally:

Step Command

1. Enter system view.

2. Configure the errored frame

period event detection window.

3. Configure the errored frame

period event triggering threshold.

system-view N/A

oam global errored-frame-period window window-value

oam global errored-frame-period threshold threshold-value

Remarks

By default, the errored frame period event detection window is

10000000.

By default, the errored frame period event triggering threshold is

To configure errored frame period event detection on a port:

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet port

view.

3. Configure the errored frame

period event detection window.

4. Configure the errored frame

period event triggering threshold.

system-view N/A

interface interface-type interface-number

oam errored-frame-period window window-value

oam errored-frame-period threshold threshold-value

Remarks

N/A

By default, an interface uses the value configured globally.

Configuring errored frame seconds event detection

CAUTION:

Make sure the errored frame seconds tri

indow. Otherwise, no errored frame seconds event can be generated.

ering threshold is less than the errored frame seconds detection

Page 14

An errored frame seconds event occurs when the number of times that errored frame seconds are detected on a port in the detection window (specified detection interval) exceeds the predefined threshold.

To configure errored frame seconds event detection globally:

Step Command

1. Enter system view.

2. Configure the errored frame

seconds event detection window.

3. Configure the errored frame

seconds event triggering threshold.

To configure errored frame seconds event detection on a port:

system-view N/A

oam global errored-frame-seconds window window-value

oam global errored-frame-seconds threshold threshold-value

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet port

view.

3. Configure the errored frame

seconds event detection window.

4. Configure the errored frame

seconds event triggering threshold.

system-view N/A

interface interface-type interface-number

oam errored-frame-seconds window window-value

oam errored-frame-seconds threshold threshold-value

Remarks

By default, the errored frame seconds event detection window is 60000 milliseconds.

By default, the errored frame seconds event triggering threshold is 1.

Remarks

N/A

By default, an interface uses the value configured globally.

Configuring the action a port takes after it receives an Ethernet OAM event from the remote end

This feature enables a port to log events and automatically terminate the OAM connection and set the link state to down.

To configure the action the port takes after it receives an Ethernet OAM event from the remote end:

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet port

view.

system-view N/A

interface interface-type

interface-number

Remarks

N/A

Page 15

Step Command

3. Configure the action the port

takes after it receives an Ethernet OAM event from the remote end.

oam remote-failure { connection-expired | critical-event | dying-gasp | link-fault } action error-link-down

Remarks

By default, the port only logs the Ethernet OAM event it receives from the remote end.

Configuring Ethernet OAM remote loopback

CAUTION:

Use this function with caution, because enabling Ethernet OAM remote loopback impacts other services.

When you enable Ethernet OAM remote loopback on a port, the port sends Loopback Control OAMPDUs to a remote port, and the remote port enters the loopback state. The port then sends test frames to the remote port. By observing how many of these test frames return, you can calculate the packet loss ratio on the link and evaluate the link performance.

You can enable Ethernet OAM remote loopback on a specific port in user view, system view, or Layer 2 Ethernet port view. The configuration effects are the same.

Configuration guidelines

• Ethernet OAM remote loopback is available only after the Ethernet OAM connection is established,

and can be performed only by Ethernet OAM entities operating in active Ethernet OAM mode.

• Remote loopback is available only on full-duplex links that support remote loopback at both ends.

• Ethernet OAM remote loopback must be supported by both the remote port and the sending port.

• Enabling Ethernet OAM remote loopback interrupts data communications. After Ethernet OAM

remote loopback is disabled, all the ports involved will shut down and then come up. Ethernet OAM remote loopback can be disabled by any of the following events: disabling Ethernet OAM, disabling Ethernet OAM remote loopback, and Ethernet OAM connection timing out.

• Enabling internal loopback test on a port in remote loopback test can terminate the remote

loopback test. For more information about loopback test, see Layer 2—LAN Switching Configuration Guide

Enabling Ethernet OAM remote loopback on a specific port

Step Command

1. (Optional.) Enter system view.

2. Enable Ethernet OAM remote

loopback on a specific port.

system-view N/A

oam remote-loopback start interface interface-type interface-number

Remarks

By default, Ethernet OAM remote loopback is disabled.

This command can be executed in user view or system view.

Page 16

Enabling Ethernet OAM remote loopback on the port

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet port

view.

3. Enable Ethernet OAM remote

loopback on the port.

system-view N/A

interface interface-type interface-number

oam remote-loopback start

Remarks

N/A

By default, Ethernet OAM remote loopback is disabled.

Rejecting the Ethernet OAM remote loopback request from a remote port

The Ethernet OAM remote loopback function impacts other services. To solve this problem, you can disable a port from being controlled by the Loopback Control OAMPDUs sent by a remote port. The local port then rejects the Ethernet OAM remote loopback request from the remote port.

To reject the Ethernet OAM remote loopback request from a remote port:

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet port

view.

system-view N/A

interface interface-type interface-number

Remarks

N/A

By default, a port does not reject the Ethernet OAM remote loopback request from a remote

3. Reject the Ethernet OAM

remote loopback request from a remote port.

oam remote-loopback reject-request

port.

This setting does not affect the loopback test that has been performed on the port. It takes effect when the next loopback starts on the port.

Displaying and maintaining Ethernet OAM

Execute display commands in any view and reset commands in user view:

Purpose Command

Display information about an Ethernet OAM connection.

Display Ethernet OAM configuration.

Display the statistics on critical events after an Ethernet OAM connection is established.

display oam { local | remote } [ interface interface-type interface-number ]

display oam configuration [ interface interface-type interface-number ]

display oam critical-event [ interface interface-type interface-number ]

Page 17

Purpose Command

Display the statistics on Ethernet OAM link error events after an Ethernet OAM connection is established.

Clear statistics on Ethernet OAM packets and Ethernet OAM link error events.

display oam link-event { local | remote } [ interface interface-type interface-number ]

reset oam [ interface interface-type interface-number ]

Ethernet OAM configuration example

Network requirements

On the network shown in Figure 1, perform the following operations:

• Enable Ethernet OAM on Device A and Device B to auto-detect link errors between the two devices

• Determine the performance of the link between Device A and Device B by collecting statistics about

the error frames received by Device A

Figure 1 Network diagram

Configuration procedure

1. Configure Device A:

# Configure GigabitEthernet 1/0/1 to operate in active Ethernet OAM mode, and enable Ethernet OAM for it.

<DeviceA> system-view [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] oam mode active [DeviceA-GigabitEthernet1/0/1] oam enable

# Set the errored frame event detection window to 20000 milliseconds, and set the errored frame event triggering threshold to 10.

[DeviceA] oam errored-frame period 200 [DeviceA] oam errored-frame threshold 10 [DeviceA-GigabitEthernet1/0/1] quit

2. Configure Device B:

# Configure GigabitEthernet 1/0/1 to operate in passive Ethernet OAM mode (the default), and enable Ethernet OAM for it.

<DeviceB> system-view [DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] oam mode passive [DeviceB-GigabitEthernet1/0/1] oam enable [DeviceB-GigabitEthernet1/0/1] quit

3. Verify the configuration:

Page 18

Use the display oam critical-event command to display the statistics of Ethernet OAM critical link events. For example:

# Display the statistics of Ethernet OAM critical link events on all the ports of Device A.

[DeviceA] display oam critical-event

-----------[GigabitEthernet1/0/1] ---------- Local link status : UP Event statistics Link fault : Not occurred Dying gasp : Not occurred Critical event : Not occurred

The output shows that no critical link event occurred on the link between Device A and Device B.

Use the display oam link-event command to display the statistics of Ethernet OAM link events. For example:

# Display Ethernet OAM link event statistics of the local end of Device A.

[DeviceA] display oam link-event local

------------ [GigabitEthernet1/0/1] ---------- Link status: UP OAM local errored frame event Event time stamp : 5789 x 100 milliseconds Errored frame window : 200 x 100 milliseconds Errored frame threshold : 10 error frames Errored frame : 13 error frames Error running total : 350 error frames Event running total : 17 events

The output shows that 350 errors occurred after Ethernet OAM is enabled on Device A, 17 of which were caused by error frames. The link is unstable.

Page 19

Configuring CFD

Overview

Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault Management (CFM) and ITU-T Y.1731, is an end-to-end per-VLAN link layer OAM mechanism. CFD is used for link connectivity detection, fault verification, and fault location.

Basic CFD concepts

Maintenance domain

A maintenance domain (MD) defines the network or part of the network where CFD plays its role. An MD is identified by its MD name.

To accurately locate faults, CFD introduces eight levels (from 0 to 7) to MDs. The bigger the number, the higher the level and the larger the area covered. Domains can touch or nest (if the outer domain has a higher level than the nested one) but cannot intersect or overlap.

MD levels facilitate fault location and make fault location more accurate. As shown in Figure 2, MD_A light blue nests MD_B in dark blue. If a connectivity fault is detected at the boundary of MD_A, any of the devices in MD_A, including Device A through Device E, might fail. If a connectivity fault is also detected at the boundary of MD_B, the failure points can be any of Device B through Device D. If the devices in MD_B can operate correctly, at least Device C is operational.

Figure 2 Two nested MDs

CFD exchanges messages and performs operations on a per-domain basis. By planning MDs correctly in a network, you can use CFD to rapidly locate failure points.

Maintenance association

A maintenance association (MA) is a part of an MD. You can configure multiple MAs in an MD as needed. An MA is identified by the MD name + MA name.

Page 20

An MA serves the specified VLAN or no VLAN. An MA that serves a VLAN is considered to be carrying VL AN attribute. An MA that serves no VLAN is considered to be carrying no VLAN attribute. An MP can receive packets sent by other MPs in the same MA. The level of an MA equals the level of the MD that the MA belongs to.

Maintenance point

An MP is configured on a port and belongs to an MA. MPs include the following types: maintenance association end points (MEPs) and maintenance association intermediate points (MIPs).

• MEP

MEPs define the boundary of the MA. Each MEP is identified by a MEP ID.

The MA to which a MEP belongs defines the VLAN of packets sent by the MEP. The level of a MEP equals the level of the MD to which the MEP belongs. The level of packets sent by a MEP equals the level of the MEP.

The level of a MEP determines the levels of packets that the MEP can process. A MEP forwards packets at a higher level and processes packet of its level or lower. The processing procedure is specific to packets in the same VLAN. Packets of different VLANs are independent.

MEPs include inward-facing MEPs and outward-facing MEPs:

{ An outward-facing MEP sends packets to its host port.

{ An inward-facing MEP does not send packets to its host port. Rather, it sends packets to other

ports on the device.

• MIP

A MIP is internal to an MA. It cannot send CFD packets actively; however, it can handle and respond to CFD packets. By cooperating with MEPs, a MIP can perform a function similar to ping and traceroute. A MIP forwards packets of a different level without any processing and only processes packet of its level.

The MA to which a MIP belongs defines the VLAN of packets that the MIP can receive. The level of a MIP is defined by its generation rule and the MD to which the MIP belongs. MIPs are generated on each port automatically according to related MIP generation rules:

{ Default rule—If no lower-level MIP exists on an interface, a MIP is created on the current level.

A MIP can be created even if no MEP is configured on the interface.

{ Explicit rule—If no lower-level MIP exists and a lower-level MEP exists on an interface, a MIP is

created on the current level. A MIP can be created only when a lower-level MEP is created on the interface.

If a port has no M IP, t he sy stem will check the M As in each M D (fr om low to high le vels ), an d fol low the procedure as described in Figure 3 to create or not

to create MIPs at the current level.

Page 21

Figure 3 Procedure of creating MIPs

Figure 4 demonstrates a grading example of the CFD module. Four levels of MDs (0, 2, 3, and 5) are

designed. The bigger the number, the higher the level and the larger the area covered. MPs are configured on the ports of Device A through Device F. Port 1 of Device B is configured with the following MPs: a level 5 MIP, a level 3 inward-facing MEP, a level 2 inward-facing MEP, and a level 0 outward-facing MEP.

MEP list

Figure 4 CFD grading example

A MEP list is a collection of local MEPs allowed to be configured and the remote MEPs to be monitored in the same MA. It lists all the MEPs configured on different devices in the same MA. The MEPs all have unique MEP IDs. When a MEP receives from a remote device a continuity check message (CCM) that carries a MEP ID not included in the MEP list of the MA, it drops the message.

Page 22

The local device must send CCM messages carrying the Remote Defect Indication (RDI) flag bits; otherwise, the peer device cannot sense certain failures. When at least one local MEP in an MA has not learned all remote MEPs in the MEP list, the MEPs in the MA do not carry the RDI flag bits in CCMs.

CFD functions

CFD functions, which are implemented through the MPs, include:

• Continuity check (CC)

• Loopback (LB)

• Linktrace (LT)

• Alarm indication signal (AIS)

• Loss measurement (LM)

• Delay measurement (DM)

• Test (TST)

Continuity check

Connectivity faults are usually caused by device faults or configuration errors. Continuity check checks the connectivity between MEPs. This function is implemented through periodic sending of CCMs by the MEPs. A CCM sent by one MEP is intended to be received by all the other MEPs in the same MA. If a MEP fails to receive the CCMs within 3.5 times the sending interval, the link is considered as faulty and a log is generated. When multiple MEPs send CCMs at the same time, the multipoint-to-multipoint link check is achieved. CCM frames are multicast frames.

Loopback

Linktrace

AIS

Similar to ping at the IP layer, loopback verifies the connectivity between a source device and a target device. To implement this function, the source MEP sends loopback messages (LBMs) to the target MEP. Depending on whether the source MEP can receive a loopback reply message (LBR) from the target MEP, the link state between the two can be verified. LBM frames and LBR frames are unicast frames.

LBM frames are multicast and unicast frames. HP devices support sending and receiving unicast LBM frames and receiving multicast LBM frames. HP devices do not support sending multicast LBM frames. LBR frames are unicast frames.

Linktrace is similar to traceroute. It identifies the path between the source MEP and the target MP. The source MEP sends the linktrace messages (LTMs) to the target MP. After receiving the messages, the target MP and the MIPs that the LTM frames pass send back linktrace reply messages (LTRs) to the source MEP. Based on the reply messages, the source MEP can identify the path to the target MP. LTM frames are multicast frames and LTRs are unicast frames.

The AIS function suppresses the number of error alarms reported by MEPs. If a local MEP does not receive any CCM frames from its peer MEP within 3.5 times the CCM transmission interval, it immediately starts sending AIS frames. The AIS frames are sent periodically in the opposite direction of CCM frames. When the peer MEP receives the AIS frames, it suppresses the error alarms locally, and continues to send the AIS frames. If the local MEP receives CCM frames within 3.5 times the CCM transmission interval, it stops sending AIS frames and restores the error alarm function. AIS frames are multicast frames.

Page 23

NOTE:

This function is supported only by Release 3108P01 and later versions.

The LM function measures the frame loss in a certain direction between a pair of MEPs. The source MEP sends loss measurement messages (LMMs) to the target MEP. The target MEP responds with loss measurement replies (LMRs). The source MEP calculates the number of lost frames according to the counter values of the two consecutive LMRs (the current LMR and the previous LMR). LMMs and LMRs are unicast frames.

This function is supported only by Release 3108P01 and later versions.

The DM function measures frame delays between two MEPs, including the following types:

• One-way frame delay measurement

The source MEP sends a one-way delay measurement (1DM) frame, which carries the transmission time, to the target MEP. When the target MEP receives the 1DM frame, it does the following:

{ Records the reception time.

{ Calculates and records the link transmission delay and jitter (delay variation) according to the

transmission time and reception time.

NOTE:

TST

1DM frames are unicast frames.

• Two-way frame delay measurement

The source MEP sends a delay measurement message (DMM), which carries the transmission time, to the target MEP. When the target MEP receives the DMM, it responds with a delay measurement reply (DMR). The DMR carries the reception time and transmission time of the DMM and the transmission time of the DMR. When the source MEP receives the DMR, it does the following:

{ Records the DMR reception time.

{ Calculates the link transmission delay and jitter according to the DMR reception time and DMM

transmission time.

DMM frames and DMR frames are unicast frames.

This function is supported only by Release 3108P01 and later versions.

The TST function tests the bit errors between two MEPs. The source MEP sends a TST frame, which carries the test pattern, such as pseudo random bit sequence (PRBS) or all-zero, to the target MEP. When the target MEP receives the TST frame, it determines the bit errors by calculating and comparing the content of the TST frame. TST frames are unicast frames.

NOTE:

This function is supported only by Release 3108P01 and later versions.

Page 24

EAIS

Ethernet Alarm Indication Signal (EAIS) enables collaboration between the Ethernet port status and the AIS function. When a port on the device (not necessarily an MP) goes down, it immediately starts to send EAIS frames periodically to suppress the error alarms. When the port goes up again, it immediately stops sending EAIS frames. When the MEP receives the EAIS frames, it suppresses the error alarms locally, and continues to send the EAIS frames. If a MEP receives no EAIS frames within 3.5 times the EAIS frame transmission interval, the fault is considered cleared. The port stops sending EAIS frames and restores the error alarm function. EAIS frames are multicast frames.

NOTE:

This function is supported only by Release 3108P01 and later versions.

Protocols and standards

• IEEE 802.1ag, Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault

Management

• ITU-T Y.1731, OAM functions and mechanisms for Ethernet based networks

CFD configuration task list

For CFD to work correctly, design the network by performing the following tasks:

• Grade the MDs in the entire network, and define the boundary of each MD.

• Assign a name for each MD. Make sure that the devices in the same MD use the same MD name.

• Define the MA in each MD according to the VLAN you want to monitor.

• Assign a name for each MA. Make sure that the devices in the same MA in the same MD use the

same MA name.

• Determine the MEP list of each MA in each MD. Make sure that devices in the same MA maintain

the same MEP list.

• At the edges of MD and MA, MEPs should be designed at the device port. MIPs can be designed

on devices or ports that are not at the edges.

To configure CFD, perform the following tasks:

Tasks at a glance

Configuring basic CFD settings:

• (Required.) Enabling CFD

• (Required.) Configuring service instances

• (Required.) Configuring MEPs

• (Required.) Configuring MIP auto-generation rules

Configuring CFD functions:

• (Required.) Configuring CC on MEPs

Page 25

Tasks at a glance

• (Optional.) Configuring LB on MEPs

• (Optional.) Configuring LT on MEPs

• (Optional.) Configuring AIS

• (Optional.) Configuring LM

• (Optional.) Configuring one-way DM

• (Optional.) Configuring two-way DM

• (Optional.) Configuring TST

(Optional.) Configuring EAIS

Typically, a port blocked by the spanning tree feature can not re ceive or se nd C FD messag es exce pt i n th e following cases:

• The port is configured as an outward-facing MEP.

• The port is configured as a MIP or inward-facing MEP, which can still receive and send CFD

messages except CCM messages.

For more information about the spanning tree feature, see Layer 2—LAN Switching Configuration Guide.

Configuring basic CFD settings

Enabling CFD

Step Command

1. Enter system view.

2. Enable CFD.

system-view

cfd enable By default, CFD is disabled.

Configuring service instances

Before configuring the MEPs and MIPs, you must first configure service instances. A service instance is a set of service access points (SAPs), and belongs to an MA in an MD.

The MD and MA define the level attribute and VLAN attribute of the messages handled by the MPs in a service instance. The MPs of the MA that carry no VLAN attribute do not belong to any VLAN.

To configure a service instance with the MD name:

Step Command

1. Enter system view.

2. Create an MD.

system-view N/A

cfd md md-name [ index index-value ] level level-value

Remarks

N/A

Remarks

By default, no MD is created.

cfd service-instance instance-id ma-id { icc-based icc-name |

3. Create a service instance.

integer ma-num | string ma-name

| vlan-based [ vlan-id ] } [ ma-index index-value ] md md-name [ vlan vlan-id ]

By default, no service instance exists.

Page 26

Configuring MEPs

CFD is implemented through various operations on MEPs. As a MEP is configured on a service instance, the MD level and VLAN attribute of the service instance become the attribute of the MEP.

Before creating MEPs, configure the MEP list. A MEP list is a collection of local MEPs that can be configured in an MA an d the remote MEPs to be mon itored. You ca nnot create a MEP if the MEP I D is not included in the MEP list of the service instance.

On the same level of an interface, you can configure an outward-facing MEP for only one MA with no VLAN attribute.

Follow these guidelines when you configure MEPs:

• Configurations in Ethernet interface view take effect only on the current interface.

• Configurations in aggregate interface view take effect on the aggregate interface and all its

member ports.

• Configurations on a member port take effect only when the member port leaves the aggregation

group.

To configure a MEP:

Step Command

1. Enter system view.

2. Configure a MEP list.

3. Enter Layer 2 Ethernet

interface view or Layer 2 aggregate interface view.

4. Create a MEP.

system-view N/A

cfd meplist mep-list service-instance instance-id

interface interface-type

interface-number

cfd mep mep-id service-instance instance-id { inbound | outbound }

Configuring MIP auto-generation rules

As functional entities in a service instance, MIPs respond to various CFD frames, such as LTM and LBM frames. You can configure MIP auto-generation rules for the system to automatically create MIPs.

Any of the following events can cause MIPs to be created or deleted after you have configured the cfd mip-rule command:

• Enabling or disabling CFD.

• Creating or deleting MEPs on a port.

• Changes occur to the VLAN attribute of a port.

Remarks

By default, no MEP list is configured.

N/A

By default, no MEP is configured.

• The rule specified in the cfd mip-rule command changes.

An MA carrying no VLAN attribute is mainly used to detect direct link status. It cannot generate MIPs.

For an MA carrying VLAN attribute, if the same or higher level MEP exists on the interface, no MIP is generated for the MA on the interface.

To configure the rules for generating MIPs:

Page 27

Step Command

1. Enter system view.

2. Configure MIP

auto-generation rules.

system-view N/A

cfd mip-rule { default | explicit } service-instance instance-id

Configuring CFD functions

Configuration prerequisites

Complete basic CFD settings.

Configuring CC on MEPs

Configure CC before configuring other CFD functions. After the CC function is configured, MEPs in an MA can periodically send CCM frames to maintain connectivity. When the lifetime of a CCM frame expires, the link to the sending MEP is considered disconnected. When setting the CCM interval, use the settings described in Table 5.

Remarks

By default, no rules for generating MIPs are configured, and the system does not automatically create any MIP.

Table 5 CCM interval field encoding

CCM interval field

1 10/3 milliseconds 35/3 milliseconds

2 10 milliseconds 35 milliseconds

3 100 milliseconds 350 milliseconds

4 1 second 3.5 seconds

5 10 seconds 35 seconds

6 60 seconds 210 seconds

7 600 seconds 2100 seconds

Transmission interval

Maximum CCM lifetime

Follow these guidelines when you configure CC on a MEP:

• Configure the same CCM interval field value for all MEPs in the same MA.

• The switch does not support a CCM interval field value in the range of 1 to 3. If you configure a

CCM interval field value of 1, 2, or 3, the value of 4 takes effect.

• Configurations in Ethernet interface view take effect only on the current interface.

• Configurations in aggregate interface view take effect on the aggregate interface and all its

member ports.

• Configurations on a member port take effect only when the member port leaves the aggregation

group.

To configure CC on a MEP:

Page 28

Step Command

1. Enter system view.

system-view N/A

Remarks

2. (Optional.) Set the CCM

interval field.

3. Enter Layer 2 Ethernet

interface view or Layer 2 aggregate interface view.

4. Enable CCM sending on a

MEP.

Configuring LB on MEPs

The LB function can verify the link state between the local MEP and the remote MEP or MIP.

To configure LB on a MEP:

Task Command

Enable LB.

cfd cc interval interval-value service-instance instance-id

interface interface-type interface-number

cfd cc service-instance instance-id mep mep-id enable

cfd loopback service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id }

[ number number ]

By default, the interval field value is

N/A

By default, CCM sending is disabled on a MEP.

Remarks

By default, LB is disabled.

Available in any view.

Configuring LT on MEPs

LT can trace the path between source and target MEPs, and can locate link faults by automatically sending LT messages. The two functions are implemented in the following way:

• Tracing path—The source MEP first sends LTM messages to the target MEP. Based on the LTR

messages in response to the LTM messages, the path between the two MEPs is identified.

• LT messages automatic sending—If the source MEP fails to receive the CCM frames from the target

MEP within 3.5 times the transmission interval, the link between the two is considered faulty. LTM frames (with the target MEP as the destination and the TTL field in the LTM frames set to the maximum value 255) will be sent out. Based on the LTRs that the MIPs return, the fault source is located.

IMPORTANT:

Before you configure LT on a MEP in an MA carrying VLAN attribute, create the VLAN to which the M belongs.

To configure LT on MEPs:

Step Command

1. Find the path between a

source MEP and a target MEP.

cfd linktrace service-instance

instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ ttl ttl-value ] [ hw-only ]

Remarks

Available in any view.

Page 29

Step Command

2. Enter system view.

system-view N/A

Remarks

3. Enable LT messages automatic

sending.

Configuring AIS

The AIS function suppresses the number of error alarms reported by MEPs.

For a MEP in the service instance to send AIS frames, set the AIS frame transmission level to be higher than the MD level of the MEP.

Enable AIS and configure a correct AIS frame transmission level on the target MEP, so the target MEP can perform the following tasks:

• Suppress the error alarms.

• Send the AIS frame to the MD of a higher level.

If you enable AIS but do not configure a correct AIS frame transmission level, the target MEP can suppress the error alarms, but cannot send the AIS frames.

To configure AIS:

Ste

1. Enter system view.

cfd linktrace auto-detection [ size size-value ]

Command

system-view

By default, LT messages automatic sending is disabled.

Remarks

N/A

2. Enable AIS. cfd ais enable By default, AIS is disabled.

3. Configure the AIS frame

transmission level.

4. Configure the AIS frame

transmission interval.

cfd ais level level-value service-instance instance-id

cfd ais period period-value service-instance instance-id

Configuring LM

The LM function measures frame loss between MEPs. Frame loss statistics include the number of lost frames, the frame loss ratio, and the average number of lost frames for the source and target MEPs.

To configure LM:

Task

Configure LM.

Command

cfd slm service-instance instance-id mep mep-id

{ target-mac mac-address | target-mep target-mep-id } [ number number ]

Configuring one-way DM

By default, the AIS frame transmission level is not configured.

By default, the AIS frame transmission interval is 1 second.

Remarks

Available in any view.

The one-way DM function measures the one-way frame delay between two MEPs, and monitors and manages the link transmission performance.

Page 30

One-way DM requires that the clocks at the transmitting MEP and the receiving MEP be synchronized. For the purpose of frame delay variation measurement, the requirement for clock synchronization can be relaxed.

To view the test result, use the display cfd dm one-way history command on the target MEP.

To configure one-way DM:

Task

Configure one-way DM.

Configuring two-way DM

The two-way DM function measures the two-way frame delay, average two-way frame delay, and two-way frame delay variation between two MEPs. It also monitors and manages the link transmission performance.

To configure two -way DM:

Task

Configure two-way DM.

Command

cfd dm one-way service-instance

instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ number number ]

Command

cfd dm two-way service-instance

instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ number number ]

Remarks

Available in any view.

Remarks

Available in any view.

Configuring TST

The TST function detects bit errors on a link, and monitors and manages the link transmission performance.

To view the test result, use the display cfd tst command on the target MEP.

To configure TST:

Task

Configure TST.

Command

cfd tst service-instance instance-id mep mep-id { target-mac

mac-address | target-mep target-mep-id } [ number number ]

[ length-of-test length ] [ pattern-of-test { all-zero | prbs } [ with-crc ] ]

Remarks

Available in any view.

Page 31

Configuring EAIS

You can configure EAIS on a device that does not support or is not configured with CFD. However, EAIS must collaborate with the CFD function in the network, so you must configure CFD in the network.

For a port to send the EAIS frames, configure port status-AIS collaboration, and configure the correct EAIS frame transmission level and interval. If you only enable port status-EAIS collaboration, but do not configure the EAIS frame transmission level and interval, the port cannot send EAIS frames.

If you do not specify the VLANs where the EAIS frames can be transmitted, the EAIS frames will be transmitted in the default VLAN of the current port. Otherwise, the EAIS frames will be transmitted in the intersection of the following VLANs:

• Specified VLANs where the EAIS frames can be transmitted.

• VLANs to which the port belongs.

You can configure EAIS on the member port of an aggregation group, but the configuration does not take effect. If you configure EAIS on the port and then add it to an aggregation group, the EAIS configuration immediately fails to take effect. After the port leaves the aggregation group, the EAIS configuration takes effect.

If the intersection of the configured VLANs where the EAIS frames can be transmitted and the VLANs to which the port belongs is empty, no EAIS frame is sent. If the intersection contains more than 70 VLANs and the EAIS frame transmission interval is 1 second, the CPU usage will be too high. In this case, HP recommends that you set the EAIS frame transmission interval to 60 seconds.

To configure EAIS:

Step Command

1. Enter system view.

2. Enable port status-AIS

collaboration.

3. Enter Layer 2 Ethernet

interface view or Layer 2 aggregate interface view.

4. Configure the EAIS frame

transmission level.

5. Configure the EAIS frame

transmission interval.

6. Specify the VLANs where the

EAIS frames can be transmitted.

system-view

cfd ais-track link-status global

interface interface-type interface-number

cfd ais-track link-status level

level-value

cfd ais-track link-status period

period-value

cfd ais-track link-status vlan

vlan-list

Displaying and maintaining CFD

Remarks

N/A

By default, port status-AIS collaboration is disabled.

N/A

By default, the EAIS frame transmission level is not configured.

By default, the EAIS frame transmission interval is not configured.

By default, the EAIS frames can be transmitted only within the default VLAN of the port.

Execute display commands in any view and reset commands in user view.

Page 32

Purpose Command

Display the AIS configuration and information on the specified MEP.

Display the AIS configuration and information associated with the status of the specified port.

Display the one-way DM result on the specified MEP.

Display LTR information received by a MEP.

Display the content of the LTR messages received as responses to the automatically sent LTMs.

Display MD configuration information. display cfd md

Display the attribute and running information of the MEPs.

Display MEP list in a service instance. display cfd meplist [ service-instance instance-id

Display MP information.

Display information about a remote MEP.

Display service instance configuration information. display cfd service-instance [ instance-id ]

display cfd ais [ service-instance instance-id [ mep mep-id ] ]

display cfd ais-track link-status [ interface interface-type interface-number ]

display cfd dm one-way history [ service-instance instance-id [ mep mep-id ] ]

display cfd linktrace-reply [ service-instance instance-id [ mep mep-id ] ]

display cfd linktrace-reply auto-detection [ size size-value ]

display cfd mep mep-id service-instance instance-id

display cfd mp [ interface interface-type interface-number ]

display cfd remote-mep service-instance instance-id mep mep-id

Display CFD status. display cfd status

Display the TST result on the specified MEP.

Clear the one-way DM result on the specified MEP.

Clear the TST result on the specified MEP.

CFD configuration example

Network requirements

As shown in Figure 5:

• The network comprises five devices and is divided into two MDs: MD_A (level 5) and MD_B (level

3). All ports belong to VLAN 100, and the MAs in the two MDs all serve VLAN 100. Assume that the MAC addresses of Device A through Device E are 0010-FC01-6511, 0 010 - F C 02 - 6512, 0010 - FC03 -6513, 0 010 - FC 04 - 6514, a n d 0 010 -FC 05 -6515, re sp e ctive ly.

• MD_A has three edge ports: GigabitEthernet 1/0/1 on Device A, GigabitEthernet 1/0/3 on

Device D, and GigabitEthernet 1/0/4 on Device E, and they are all inward-facing MEPs. MD_B has two edge ports: GigabitEthernet 1/0/3 on Device B and GigabitEthernet 1/0/1 on Device D, and they are both outward-facing MEPs.

display cfd tst [ service-instance instance-id [ mep mep-id ] ]

reset cfd dm one-way history [ service-instance instance-id [ mep mep-id ] ]

reset cfd tst [ service-instance instance-id [ mep mep-id ] ]

• In MD_A, Device B is designed to have MIPs when its port is configured with low level MEPs. Port

GigabitEthernet 1/0/3 is configured with MEPs of MD_B, and the MIPs of MD_A can be configured on this port. You should configure the MIP generation rule of MD_A as explicit.

Page 33

• The MIPs of MD_B are designed on Device C, and are configured on all ports. You must configure

the MIP generation rule as default.

• Configure CC to monitor the connectivity among all the MEPs in MD_A and MD_B. Configure LB to

locate link faults, and use the AIS and EAIS functions to suppress the error alarms that are reported.

• After the status information for the entire network is obtained, use LT, LM, one-way DM, two-way

DM, and TST to detect link faults.

Figure 5 Network diagram

Configuration procedure

1. Configure a VLAN and assign ports to it:

On each device shown in Figure 5, c through GigabitEthernet 1/0/4 to VLAN 100.

2. Enable CFD:

# Enable CFD on Device A.

<DeviceA> system-view [DeviceA] cfd enable

# Configure Device B through Device E in the same way Device A is configured. (Details not shown.)

3. Configure service instances:

# Create MD_A (level 5) on Device A, and create service instance 1 (in which the MA is identified by a VLAN and serves VLAN 100).

[DeviceA] cfd md MD_A level 5 [DeviceA] cfd service-instance 1 ma-id vlan-based md MD_A vlan 100

# Configure Device E in the same way Device A is configured. (Details not shown.)

# Create MD_A (level 5) on Device B, and create service instance 1 (in which the MA is identified by a VLAN and serves VLAN 100).

[DeviceB] cfd md MD_A level 5 [DeviceB] cfd service-instance 1 ma-id vlan-based md MD_A vlan 100

# Create MD_B (level 3), and create service instance 2 (in which the MA is identified by a VLAN and serves VLAN 100)

reate VLAN 100 and assign ports GigabitEthernet 1/0/1

Page 34

[DeviceB] cfd md MD_B level 3 [DeviceB] cfd service-instance 2 ma-id vlan-based md MD_B vlan 100

# Configure Device D in the same way Device B is configured. (Details not shown.)

# Create MD_B (level 3) on Device C, and create service instance 2 (in which the MA is identified by a VLAN and serves VLAN 100).

[DeviceC] cfd md MD_B level 3 [DeviceC] cfd service-instance 2 ma-id vlan-based md MD_B vlan 100

4. Configure MEPs:

# On Device A, configure a MEP list in service instance 1, and create inward-facing MEP 1001 in service instance 1 on GigabitEthernet 1/0/1.

[DeviceA] cfd meplist 1001 4002 5001 service-instance 1 [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] cfd mep 1001 service-instance 1 inbound [DeviceA-GigabitEthernet1/0/1] quit

# On Device B, configure a MEP list in service instances 1 and 2.

[DeviceB] cfd meplist 1001 4002 5001 service-instance 1 [DeviceB] cfd meplist 2001 4001 service-instance 2

# Create outward-facing MEP 2001 in service instance 2 on GigabitEthernet 1/0/3.

[DeviceB] interface gigabitethernet 1/0/3 [DeviceB-GigabitEthernet1/0/3] cfd mep 2001 service-instance 2 outbound [DeviceB-GigabitEthernet1/0/3] quit

# On Device D, configure a MEP list in service instances 1 and 2.

[DeviceD] cfd meplist 1001 4002 5001 service-instance 1 [DeviceD] cfd meplist 2001 4001 service-instance 2

# Create outward-facing MEP 4001 in service instance 2 on GigabitEthernet 1/0/1.

[DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] cfd mep 4001 service-instance 2 outbound [DeviceD-GigabitEthernet1/0/1] quit

# Create inward-facing MEP 4002 in service instance 1 on GigabitEthernet 1/0/3.

[DeviceD] interface gigabitethernet 1/0/3 [DeviceD-GigabitEthernet1/0/3] cfd mep 4002 service-instance 1 inbound [DeviceD-GigabitEthernet1/0/3] quit

# On Device E, configure a MEP list in service instance 1.

[DeviceE] cfd meplist 1001 4002 5001 service-instance 1

# Create inward-facing MEP 5001 in service instance 1 on GigabitEthernet 1/0/4.

[DeviceE] interface gigabitethernet 1/0/4 [DeviceE-GigabitEthernet1/0/4] cfd mep 5001 service-instance 1 inbound [DeviceE-GigabitEthernet1/0/4] quit

5. Configure MIPs:

# Configure the MIP generation rule in service instance 1 on Device B as explicit.

[DeviceB] cfd mip-rule explicit service-instance 1

# Configure the MIP generation rule in service instance 2 on Device C as default.

[DeviceC] cfd mip-rule default service-instance 2

6. Configure CC:

Page 35

# On Device A, enable the sending of CCM frames for MEP 1001 in service instance 1 on GigabitEthernet 1/0/1.

[DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] cfd cc service-instance 1 mep 1001 enable [DeviceA-GigabitEthernet1/0/1] quit

# On Device B, enable the sending of CCM frames for MEP 2001 in service instance 2 on GigabitEthernet 1/0/3.

[DeviceB] interface gigabitethernet 1/0/3 [DeviceB-GigabitEthernet1/0/3] cfd cc service-instance 2 mep 2001 enable [DeviceB-GigabitEthernet1/0/3] quit

# On Device D, enable the sending of CCM frames for MEP 4001 in service instance 2 on GigabitEthernet 1/0/1.

[DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] cfd cc service-instance 2 mep 4001 enable [DeviceD-GigabitEthernet1/0/1] quit

# Enable the sending of CCM frames for MEP 4002 in service instance 1 on GigabitEthernet 1/0/3.

[DeviceD] interface gigabitethernet 1/0/3 [DeviceD-GigabitEthernet1/0/3] cfd cc service-instance 1 mep 4002 enable [DeviceD-GigabitEthernet1/0/3] quit

# On Device E, enable the sending of CCM frames for MEP 5001 in service instance 1 on GigabitEthernet 1/0/4.

[DeviceE] interface gigabitethernet 1/0/4 [DeviceE-GigabitEthernet1/0/4] cfd cc service-instance 1 mep 5001 enable [DeviceE-GigabitEthernet1/0/4] quit

7. Configure AIS:

# Enable AIS on Device B. Configure the AIS frame transmission level as 5 and AIS frame transmission interval as 1 second in service instance 2.

[DeviceB] cfd ais enable [DeviceB] cfd ais level 5 service-instance 2 [DeviceB] cfd ais period 1 service-instance 2

8. Configure EAIS:

# Enable port status-AIS collaboration on Device B.

[DeviceB] cfd ais-track link-status global

# On GigabitEthernet 1/0/3 of Device B, configure the EAIS frame transmission level as 5 and the EAIS frame transmission interval as 60 seconds. Specify the VLANs where the EAIS frames can be transmitted as VLAN 100.

[DeviceB] interface gigabitethernet 1/0/3 [DeviceB-GigabitEthernet1/0/3] cfd ais-track link-status level 5 [DeviceB-GigabitEthernet1/0/3] cfd ais-track link-status period 60 [DeviceB-GigabitEthernet1/0/3] cfd ais-track link-status vlan 100 [DeviceB-GigabitEthernet1/0/3] quit

Verifying the configuration

1. Verify the LB function when the CC function detects a link fault:

# Enable LB on Device A to check the status of the link between MEP 1001 and MEP 5001 in service instance 1.

Page 36

[DeviceA] cfd loopback service-instance 1 mep 1001 target-mep 5001 Loopback to 0010-FC05-6515 with the sequence number start from 1001-43404: Reply from 0010-FC05-6515: sequence number=1001-43404 time=5ms Reply from 0010-FC05-6515: sequence number=1001-43405 time=5ms Reply from 0010-FC05-6515: sequence number=1001-43406 time=5ms Reply from 0010-FC05-6515: sequence number=1001-43407 time=5ms Reply from 0010-FC05-6515: sequence number=1001-43408 time=5ms Sent: 5 Received: 5 Lost: 0

2. Verify the LT function after the CC function obtains the status information of the entire network:

# Identify the path between MEP 1001 and MEP 5001 in service instance 1 on Device A.

[DeviceA] cfd linktrace service-instance 1 mep 1001 target-mep 5001 Linktrace to MEP 5001 with the sequence number 1001-43462: MAC Address TTL Last Mac Relay Action 0010-FC05-6515 63 0010-FC02-6512 Hit

3. Verify the LM function after the CC function obtains the status information for the entire network:

# Test the frame loss from MEP 1001 to MEP 4002 in service instance 1 on Device A.

[DeviceA] cfd slm service-instance 1 mep 1001 target-mep 4002 Reply from 0010-fc00-6514 Far-end frame loss: 10 Near-end frame loss: 20 Reply from 0010-fc00-6514 Far-end frame loss: 40 Near-end frame loss: 40 Reply from 0010-fc00-6514 Far-end frame loss: 0 Near-end frame loss: 10 Reply from 0010-fc00-6514 Far-end frame loss: 30 Near-end frame loss: 30

Average Far-end frame loss: 20 Near-end frame loss: 25 Far-end frame loss rate: 25.00% Near-end frame loss rate: 32.00% Sent LMMs: 5 Received: 5 Lost: 0

4. Verify the one-way DM function after the CC function obtains the status information for the entire

network:

# Test the one-way frame delay from MEP 1001 to MEP 4002 in service instance 1 on Device A.

[DeviceA] cfd dm one-way service-instance 1 mep 1001 target-mep 4002 5 1DMs have been sent. Please check the result on the remote device.

# Display the one-way DM result on MEP 4002 in service instance 1 on Device D.

[DeviceD] display cfd dm one-way history service-instance 1 mep 4002 Service instance: 1 MEP ID: 4002 Sent 1DM total number: 0 Received 1DM total number: 5 Frame delay: 10ms 9ms 11ms 5ms 5ms Delay average: 8ms Delay variation: 5ms 4ms 6ms 0ms 0ms Variation average: 3ms

5. Verify the two-way DM function after the CC function obtains the status information for the entire

network:

Page 37

# Test the two-way frame delay from MEP 1001 to MEP 4002 in service instance 1 on Device A.

[DeviceA] cfd dm two-way service-instance 1 mep 1001 target-mep 4002 Frame delay: Reply from 0010-fc00-6514: 10ms Reply from 0010-fc00-6514: 9ms Reply from 0010-fc00-6514: 11ms Reply from 0010-fc00-6514: 5ms Reply from 0010-fc00-6514: 5ms Average: 8ms Sent DMMs: 5 Received: 5 Lost: 0

Frame delay variation: 5ms 4ms 6ms 0ms 0ms Average: 3ms

6. Verify the TST function after the CC function obtains the status information for the entire network:

# Test the bit errors on the link from MEP 1001 to MEP 4002 in service instance 1 on Device A.

[DeviceA] cfd tst service-instance 1 mep 1001 target-mep 4002 5 TSTs have been sent. Please check the result on the remote device.

# Display the TST result on MEP 4002 in service instance 1 on Device D.

[DeviceD] display cfd tst service-instance 1 mep 4002 Service instance: 1 MEP ID: 4002 Sent TST total number: 0 Received TST total number: 5 Received from 0010-fc00-6511, Bit True, sequence number 0 Received from 0010-fc00-6511, Bit True, sequence number 1 Received from 0010-fc00-6511, Bit True, sequence number 2 Received from 0010-fc00-6511, Bit True, sequence number 3 Received from 0010-fc00-6511, Bit True, sequence number 4

Page 38

Configuring DLDP

Overview

Unidirectional links occur when one end of a link can receive packets from the other end, but the other end cannot receive packets sent by the first end.

Unidirectional fiber links occur in the following cases:

• Fibers are cross-connected.

• A fiber is not connected at one end or one fiber of a fiber pair is broken.

Figure 6 sho

Figure 6 Correct and incorrect fiber connections

ws a correct fiber connection and the two types of unidirectional fiber connections.

Physical layer detection mechanisms, such as auto-negotiation, can detect physical signals and faults. They cannot detect communication failures for unidirectional links where the physical layer state is connected.

As a data link layer protocol, the Device Link Detection Protocol (DLDP) detects whether the fiber link or twisted-pair link is correctly connected at the link layer, and whether the two ends can exchange packets correctly. When DLDP detects unidirectional links, it can automatically shut down the faulty port to avoid network problems. Alternatively, a user can manually shut down the faulty port. DLDP cooperates with physical layer protocols to monitor link status and avoid physical and logical unidirectional links.

Page 39

Basic concepts

DLDP neighbor states

If port A and B are on the same link and port A can receive link-layer packets from port B, port B is a DLDP neighbor of port A. Two ports that can exchange packets are neighbors.

Table 6 DLDP neighbor states

DLDP timer Descri

Confirmed The link to a DLDP neighbor is bidirectional.

Unconfirmed The state of the link to a newly discovered neighbor is not determined.

DLDP port states

A DLDP-enabled port is called a DLDP port. A DLDP port can have multiple neighbors, and its state depends on the DLDP neighbor state.

Table 7 DLDP port states

State Descri

Initial DLDP is enabled on the port, but is disabled globally.

Inactive DLDP is enabled on the port and globally, and the link is physically down.

Bidirectional

Unidirectional

DLDP timers

tion

DLDP is enabled on the port and globally, and at least one neighbor in Confirmed state exists.

DLDP is enabled on the port and globally, and no neighbor in Confirmed state exists. In this state, a port does not send or receive packets other than DLDP packets any more.

Table 8 DLDP timers

DLDP timer Descri

Advertisement timer

Probe timer Probe packet sending interval. This timer is set to 1 second.

Echo timer

Entry timer

Enhanced timer

Advertisement packet sending interval (the default is 5 seconds and is configurable).

The Echo timer is triggered when a probe is launched for a new neighbor. This timer is set to 10 seconds.

When a new neighbor joins, a neighbor entry is created and the corresponding entry timer is triggered if the neighbor is in Confirmed state. When an Advertisement is received, the device updates the corresponding neighbor entry and the Entry timer.

The setting of an Entry timer is three times that of the Advertisement timer.

The Enhanced timer is triggered, together with the Echo timer, when the Entry timer expires. Enhanced timer is set to 1 second.

tion

Page 40

DLDP timer Description

DelayDown timer

RecoverProbe timer

DLDP authentication mode

You can use DLDP authentication to prevent network attacks and illegal detecting.

Table 9 DLDP authentication mode

If a port is physically down, the device triggers the DelayDown timer (the default is 1 second and is configurable), rather than removing the corresponding neighbor entry.

When the DelayDown timer expires, the device removes the corresponding DLDP neighbor information if the port is down, and does not perform any operation if the port is up.

This timer is set to 2 seconds. A port in the Unidirectional state regularly sends RecoverProbe packets to detect whether a unidirectional link has been restored to bidirectional.

Authentication mode

Non-authentication

Plaintext authentication

MD5 authentication

How DLDP works

Detecting one neighbor

When two devices are connected through an optical fiber or network cable, enable DLDP to detect unidirectional links to the neighbor. The following illustrates the unidirectional link detection process in two cases:

• Unidirectional links occur before you enable DLDP.

Figure 7 Cross-connected fibers

Processing at the DLDP packet sending side

The sending side sets the Authentication field of DLDP packets to 0.

The sending side sets the Authentication field to the password configured in plain text.

The sending side encrypts the user configured password using MD5 algorithm, assigns the digest to the Authentication field.

Processing at the DLDP

acket receiving side

The receiving side checks the authentication information of received DLDP packets and drops packets where the authentication information conflicts with the local configuration.

As shown in Figure 7, before you enable DLDP, the optical fibers between Device A and Device B are cross-connected. After you enable DLDP, the four ports are all up and in Unidirectional state, and they send RecoverProbe packets. Take Port 1 as an example to illustrate the unidirectional link detection process:

Page 41

a. Port 1 receives the RecoverProbe packet from Port 4, and returns a RecoverEcho packet. b. Port 4 cannot receive any RecoverEcho packet from Port 1, so Port 4 cannot become the

neighbor of Port 1.

c. Port 3 can receive the RecoverEcho packet from Port 1, but Port 3 is not the intended

destination, so Port 3 cannot become the neighbor of Port 1.

The same process occurs on the other three ports. The four ports are all in Unidirectional state.

• Unidirectional links occur after you enable DLDP.

Figure 8 Broken fiber

Device A Device B

Correct fiber

connection

Device A Device B

One fiber is

broken

Port 1 Port 2

Ethernet fiber port

Tx end Rx end

Fiber link

Broken fiber

As shown in Figure 8, Device and Device B are connected through an optical fiber. After you enable DLDP, Port 1 and Port 2 establish the bidirectional neighborship in the following way:

a. Port 1 that is physically up enters the Unidirectional state and sends a RecoverProbe packet. b. After receiving the RecoverProbe packet, Port 2 returns a RecoverEcho packet. c. After Port 1 receives the RecoverEcho packet and detects that the neighbor information in the

packet matches the local information, Port 1 establishes the neighborship with Port 2 and transits to the Bidirectional state. Port 1 then starts the Entry timer and periodically sends Advertisement packets.

d. After Port 2 receives the Advertisement packet, it establishes the Unconfirmed neighborship

with Port 1. Port 2 then starts the Echo timer and Probe timer, and periodically sends Probe packets.

e. After receiving the Probe packet, Port 1 returns an Echo packet. f. After Port 2 receives the Echo packet and detects that the neighbor information in the packet

matches the local information, the neighbor state of Port 1 becomes Confirmed. Port 2 then transits to the Bidirectional state, starts the Entry timer, and periodically sends Advertisement packets.

The bidirectional neighborship between Port 1 and Port 2 is now established.

After that, when Port 2's Rx end fails to receive signals, Port 2 is physically down and enters the Inactive state. Because Port 2's Tx end can still send signals to Port 1, Port 1 stays up. After the Entry timer for Port 2 expires, Port 1 starts the Enhanced timer and Echo timer, and sends a probe pack et to Port 2 . Bec ause Port 1 's Tx line is br oken, Port 1 cannot receive the Echo packet from Port 2 after the Echo timer expires. Port 1 then enters the Unidirectional state, and sends a Disable

Page 42

packet to Port 2. At the same time, Port 1 deletes the neighborship with Port 2, and starts the RecoverProbe timer. Port 2 stays in Inactive state during this process.

When an interface is physically down, but the Tx end of the interface is still operating, DLDP sends a LinkDown packet to inform the peer to delete the relevant neighbor entry.

Detecting multiple neighbors

When multiple devices are connected through a hub, enable DLDP on all interfaces connected to the hub to detect unidirectional links among the neighbors. When no Confirmed neighbor exists, an interface enters the Unidirectional state.

Figure 9 Network diagram

As shown in Figure 9, Device A through Device D are connected through a hub, and enabled with DLDP. When Port 1, Port 2, and Port 3 detect that the link to Port 4 fails, they deletes the neighborship with Port 4, but stay in Bidirectional state.

Configuration restrictions and guidelines

When you configure DLDP, follow these configuration restrictions and guidelines:

• For DLDP to operate correctly, enable DLDP on both sides and make sure these settings are

consistent: the interval to send Advertisement packets, DLDP authentication mode, and password.

• For DLDP to operate correctly, configure the full duplex mode for the ports at the two ends of the link,

and configure the same speed for the two ports.

DLDP configuration task list

Tasks at a glance

(Required.) Enabling DLDP

(Optional.) Setting the interval to send advertisement packets

(Optional.) Setting the DelayDown timer

(Optional.) Setting the port shutdown mode

(Optional.) Configuring DLDP authentication

Page 43

Enabling DLDP

To correctly configure DLDP on the device, you must enable DLDP globally and on each port.

To enable DLDP:

Step Command

1. Enter system view.

2. Enable DLDP globally.

3. Enter Layer 2 Ethernet

interface view.

4. Enable DLDP.

system-view N/A

dldp global enable

interface interface-type interface-number

dldp enable

Remarks

By default, DLDP is globally disabled.

N/A

By default, DLDP is disabled on an interface.

Setting the interval to send advertisement packets

To make sure DLDP can detect unidirectional links before network performance deteriorates, set the advertisement interval appropriate for your network environment. (HP recommends that you use the default interval.)

To set the Advertisement packet sending interval:

Step Command

1. Enter system view.

2. Set the interval to send

Advertisement packets.

system-view N/A

dldp interval time The default is 5 seconds.

Remarks

Setting the DelayDown timer

On some ports, when the Tx line fails, the port goes down and then comes up again, causing optical signal jitters on the Rx line. To avoid this problem, when a port goes down due to a Tx failure, the device triggers the DelayDown timer to prevent the corresponding neighbor entries from being removed. If the port remains down when the timer expires, the device removes the DLDP neighbor information. If the port goes up, the device takes no action.

To set the DelayDown timer:

Step Command

1. Enter system view.

2. Set the DelayDown timer.

system-view N/A

dldp delaydown-timer time

Remarks

The default is 1 second.

The DelayDown timer setting applies to all DLDP-enabled ports.

Page 44

Setting the port shutdown mode

On detecting a unidirectional link, the ports can be shut down in one of the following modes:

• Auto mode—When a unidirectional link is detected, DLDP changes the DLDP port state to

Unidirectional. The unidirectional port periodically sends RecoverProbe packets. When a correct RecoverEcho packet is received, the link is restored to a bidirectional link, and the port state changes from Unidirectional to Bidirectional. This process is called link auto-recovery mechanism.

• Manual mode—When a unidirectional link is detected, DLDP does not shut down the port, and you

need to manually shut it down. When the link state is restored to Bidirectional, you must manually bring up the port. If the network performance is low, the device is busy, or the CPU usage is high, use this mode to prevent normal links from being shut down because of false unidirectional link reports.

On a port with both remote OAM loopback and DLDP enabled, if the port shutdown mode is auto mode, the port will be shut down by DLDP when it receives a packet sent by itself. This causes remote OAM loopback failure. To prevent this, set the port shutdown mode to manual mode. For more information about Ethernet OAM, see "Configuring Ethernet OAM."

To set port shutdown mode:

Step Command

1. Enter system view.

2. Set port shutdown mode.

system-view N/A

dldp unidirectional-shutdown

{ auto | manual }

Configuring DLDP authentication

You can guard your network against attacks and malicious probes by configuring an appropriate DLDP authentication mode, which can be plain text authentication or MD5 authentication. If your network is safe, you can choose not to authenticate.

To configure DLDP authentication:

Step Command

1. Enter system view.

2. Configure a DLDP

authentication mode.

3. Configure the password for

DLDP authentication.

system-view N/A

dldp authentication-mode { md5 | none | simple }

dldp authentication-password { cipher cipher | simple simple }

Remarks

The default mode is auto.

Remarks

The default authentication mode is none.

By default, no password is configured for DLDP authentication.

If you do not configure the authentication password after you configure the authentication mode, the authentication mode is none no matter which authentication mode you configure.

Page 45

Displaying and maintaining DLDP

Execute display commands in any view and the reset command in user view.

Task Command

Display the DLDP configuration globally and of a port.

Display the statistics on DLDP packets passing through a port.

Clear the statistics on DLDP packets passing through a port.

display dldp [ interface interface-type interface-number ]

display dldp statistics [ interface interface-type interface-number ]

reset dldp statistics [ interface interface-type interface-number ]

DLDP configuration examples

Automatically shutting down unidirectional links

Network requirements

As shown in Figure 10, Device A and Device B are connected with two fiber pairs.

Configure DLDP to automatically shut down the faulty port upon detecting a unidirectional link, and automatically bring up the port after you clear the fault.

Figure 10 Network diagram

Configuration procedure

1. Configure Device A:

# Enable DLDP globally.

<DeviceA> system-view [DeviceA] dldp global enable

# Configure GigabitEthernet 1/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.

[DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] duplex full [DeviceA-GigabitEthernet1/0/1] speed 1000 [DeviceA-GigabitEthernet1/0/1] dldp enable [DeviceA-GigabitEthernet1/0/1] quit

Page 46

# Configure GigabitEthernet 1/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.

[DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] duplex full [DeviceA-GigabitEthernet1/0/2] speed 1000 [DeviceA-GigabitEthernet1/0/2] dldp enable [DeviceA-GigabitEthernet1/0/2] quit

# Set the port shutdown mode to auto.

[DeviceA] dldp unidirectional-shutdown auto

2. Configure Device B:

# Enable DLDP globally.

<DeviceB> system-view [DeviceB] dldp global enable

# Configure GigabitEthernet 1/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.

[DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] duplex full [DeviceB-GigabitEthernet1/0/1] speed 1000 [DeviceB-GigabitEthernet1/0/1] dldp enable [DeviceB-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.

[DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] duplex full [DeviceB-GigabitEthernet1/0/2] speed 1000 [DeviceB-GigabitEthernet1/0/2] dldp enable [DeviceB-GigabitEthernet1/0/2] quit

# Set the port shutdown mode to auto.

[DeviceB] dldp unidirectional-shutdown auto

3. Verify the configuration:

After the configurations are complete, you can use the display dldp command to display the DLDP configuration globally and on ports.

# Display the DLDP configuration globally and on all the DLDP-enabled ports of Device A.

[DeviceA] display dldp DLDP global status: Enabled DLDP advertisement interval: 5s DLDP authentication-mode: None DLDP unidirectional-shutdown mode: Auto DLDP delaydown-timer value: 1s Number of enabled ports: 2

Interface GigabitEthernet1/0/1 DLDP port state: Bidirectional Number of the port’s neighbors: 1 Neighbor MAC address: 0023-8956-3600 Neighbor port index: 1 Neighbor state: Confirmed

Page 47

Neighbor aged time: 11s

Interface GigabitEthernet1/0/2 DLDP port state: Bidirectional Number of the port’s neighbors: 1 Neighbor MAC address: 0023-8956-3600 Neighbor port index: 2 Neighbor state: Confirmed Neighbor aged time: 12s

The output shows that both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are in Bidirectional state, which means both links are bidirectional.

# Enable the monitoring of logs on the current terminal on Device A, and set the lowest level of the logs that can be output to the current terminal to 6.

[DeviceA] quit <DeviceA> terminal monitor <DeviceA> terminal logging level 6

The following log information is displayed on Device A:

<DeviceA>%Jul 11 17:40:31:089 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is DOWN.

%Jul 11 17:40:31:091 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is DOWN.

%Jul 11 17:40:31:677 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is DOWN.

%Jul 11 17:40:31:678 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is DOWN.

%Jul 11 17:40:38:544 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is UP.

%Jul 11 17:40:38:836 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is UP.

The output shows that the port status of both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 is down and then up. The link status of both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 is always down.

# Display the DLDP configuration globally and of all the DLDP-enabled ports.

<DeviceA> display dldp DLDP global status: Enabled DLDP advertisement interval: 5s DLDP authentication-mode: None DLDP unidirectional-shutdown mode: Auto DLDP delaydown-timer value: 1s Number of enabled ports: 2

Interface GigabitEthernet1/0/1 DLDP port state: Unidirectional Number of the port’s neighbors: 0 (Maximum number ever detected: 1)

Interface GigabitEthernet1/0/2 DLDP port state: Unidirectional Number of the port’s neighbors: 0 (Maximum number ever detected: 1)

Page 48

The output shows that the DLDP port status of both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 is unidirectional, which indicates that DLDP detects unidirectional links on them and automatically shuts down the two ports.

The unidirectional links are caused by cross-connected fibers. Correct the fiber connections. As a result, the ports shut down by DLDP automatically recover, and Device A displays the following log information:

<DeviceA>%Jul 11 17:42:57:709 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is DOWN.

%Jul 11 17:42:58:603 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is DOWN.

%Jul 11 17:43:02:342 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is UP.

%Jul 11 17:43:02:343 2014 DeviceA DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface GigabitEthernet1/0/1. The neighbor's system MAC is 0023-8956-3600, and the port index is 1.

%Jul 11 17:43:02:344 2014 DeviceA DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface GigabitEthernet1/0/1.

%Jul 11 17:43:02:353 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is UP.

%Jul 11 17:43:02:357 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is UP.

%Jul 11 17:43:02:362 2014 DeviceA DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface GigabitEthernet1/0/2. The neighbor's system MAC is 0023-8956-3600, and the port index is 2.

%Jul 11 17:43:02:362 2014 DeviceA DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface GigabitEthernet1/0/2.

%Jul 11 17:43:02:368 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is UP.

The output shows that the port status and link status of both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are now up and their DLDP neighbors are determined.

Manually shutting down unidirectional links

Network requirements

As shown in Figure 11, Device A and Device B are connected with two fiber pairs.

Configure DLDP to detect unidirectional links. When a unidirectional link is detected, the administrator must manually shut down the port.

Figure 11 Network diagram

Page 49

Configuration procedure

1. Configure Device A:

# Enable DLDP globally.

<DeviceA> system-view [DeviceA] dldp enable

# Configure GigabitEthernet 1/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.

# Configure GigabitEthernet 1/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on the port.

# Set the port shutdown mode to manual.

[DeviceA] dldp unidirectional-shutdown manual

2. Configure Device B:

# Enable DLDP globally.

<DeviceB> system-view [DeviceB] dldp global enable

# Configure GigabitEthernet 1/0/1 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.

# Configure GigabitEthernet 1/0/2 to operate in full duplex mode and at 1000 Mbps, and enable DLDP on it.

# Set the port shutdown mode to manual.

[DeviceB] dldp unidirectional-shutdown manual

3. Verify the configuration:

After the configurations are complete, you can use the display dldp command to display the DLDP configuration globally and on ports.

# Display the DLDP configuration globally and on all the DLDP-enabled ports of Device A.

[DeviceA] display dldp

Page 50

DLDP global status: Enabled DLDP advertisement interval: 5s DLDP authentication-mode: None DLDP unidirectional-shutdown mode: Manual DLDP delaydown-timer value: 1s Number of enabled ports: 2

Interface GigabitEthernet1/0/1 DLDP port state: Bidirectional Number of the port’s neighbors: 1 Neighbor MAC address: 0023-8956-3600 Neighbor port index: 1 Neighbor state: Confirmed Neighbor aged time: 11s

The output shows that both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are in Bidirectional state, which means both links are bidirectional.

# Enable the monitoring of logs on the current terminal on Device A, and set the lowest level of the logs that can be output to the current terminal to 6.

[DeviceA] quit <DeviceA> terminal monitor <DeviceA> terminal logging level 6

The following log information is displayed on Device A:

<DeviceA>%Jul 12 08:29:17:786 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is DOWN.

%Jul 12 08:29:17:787 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is DOWN.

%Jul 12 08:29:17:800 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is DOWN.

%Jul 12 08:29:17:800 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is DOWN.

%Jul 12 08:29:25:004 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is UP.

%Jul 12 08:29:25:005 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is UP.

%Jul 12 08:29:25:893 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is UP.

%Jul 12 08:29:25:894 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is UP.

The output shows that the port status and link status of both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are down and then up.

# Display the DLDP configuration globally and of all the DLDP-enabled ports.

Page 51

<DeviceA> display dldp DLDP global status: Enabled DLDP advertisement interval: 5s DLDP authentication-mode: None DLDP unidirectional-shutdown mode: Manual DLDP delaydown-timer value: 1s Number of enabled ports: 2

Interface GigabitEthernet1/0/1 DLDP port state: Unidirectional Number of the port’s neighbors: 0 (Maximum number ever detected: 1)

Interface GigabitEthernet1/0/2 DLDP port state: Unidirectional Number of the port’s neighbors: 0 (Maximum number ever detected: 1)

The unidirectional links are caused by cross-connected fibers. Manually shut down the two ports:

# Shut down GigabitEthernet 1/0/1.

<DeviceA> system-view [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] shutdown

The following log information is displayed on Device A:

[DeviceA-GigabitEthernet1/0/1]%Jul 12 08:34:23:717 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is DOWN.

%Jul 12 08:34:23:718 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is DOWN.

%Jul 12 08:34:23:778 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is DOWN.

%Jul 12 08:34:23:779 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is DOWN.

The output shows that the port status and link status of both GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are now down.

# Shut down GigabitEthernet 1/0/2.

[DeviceA-GigabitEthernet1/0/1] quit [DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] shutdown

Correct the fiber connections and bring up the two ports:

# Bring up GigabitEthernet 1/0/2.

[DeviceA-GigabitEthernet1/0/2] undo shutdown

The following log information is displayed on Device A:

[DeviceA-GigabitEthernet1/0/2]%Jul 12 08:46:17:677 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/2 link status is UP.

%Jul 12 08:46:17:678 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/2 is UP.

Page 52

%Jul 12 08:46:17:959 2014 DeviceA DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface GigabitEthernet1/0/2. The neighbor's system MAC is 0023-8956-3600, and the port index is 2.

%Jul 12 08:46:17:959 2014 DeviceA DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface GigabitEthernet1/0/2.

The output shows that the port status and link status of GigabitEthernet 1/0/2 are now up and its DLDP neighbors are determined.

# Bring up GigabitEthernet 1/0/1.

[DeviceA-GigabitEthernet1/0/2] quit [DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] undo shutdown

The following log information is displayed on Device A:

[DeviceA-GigabitEthernet1/0/1]%Jul 12 08:48:25:952 2014 DeviceA IFNET/3/PHY_UPDOWN: GigabitEthernet1/0/1 link status is UP.

%Jul 12 08:48:25:952 2014 DeviceA DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface GigabitEthernet1/0/1. The neighbor's system MAC is 0023-8956-3600, and the port index is 1.

%Jul 12 08:48:25:953 2014 DeviceA IFNET/5/LINK_UPDOWN: Line protocol on the interface GigabitEthernet1/0/1 is UP.

%Jul 12 08:48:25:953 2014 DeviceA DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface GigabitEthernet1/0/1.

The output shows that the port status and link status of GigabitEthernet 1/0/1 are now up and its DLDP neighbors are determined.

Page 53

Configuring RRPP

For the HP 5130 EI Switch Series, RRPP is supported only by Release 3108P01 and later versions. The support for RRPP varies by device model.

• HP 5130-24G-SFP-4SFP+ EI Switch (JG933A)—All interfaces support RRPP.

• HP 5130-24G-4SFP+ EI Switch (JG932A), HP 5130-24G-4SFP+ EI Brazil Switch (JG975A), HP

5130-24G-PoE+-4SFP+ (370W) EI Switch (JG936A) and HP 5130-24G-PoE+-4SFP+ (370W) EI Brazil Switch (JG977A)—Only the following interfaces support RRPP:

{ Interfaces numbered from 1 to 8.

{ Interfaces numbered from 25 to 28.

• HP 5130-48G-4SFP+ EI Switch (JG934A), HP 5130-48G-4SFP+ EI Brazil Switch (JG976A), HP

5130-48G-PoE+-4SFP+ (370W) EI Switch (JG937A) and HP 5130-48G-PoE+-4SFP+ (370W) EI Brazil Switch (JG978A)—Only the following interfaces support RRPP:

{ Interfaces numbered from 1 to 8.

{ Interfaces numbered from 25 to 32.

{ Interfaces numbered from 49 to 52.

• HP 5130-24G-2SFP+-2XGT EI Switch (JG938A) and HP 5130-24G-PoE+-2SFP+-2XGT (370W) EI

Switch (JG940A)—Only the following interfaces support RRPP:

{ Interfaces numbered from 1 to 8.

{ Interfaces numbered 25 and 26.

• HP 5130-48G-2SFP+-2XGT EI Switch (JG939A) and HP 5130-48G-PoE+-2SFP+-2XGT (370W) EI

Switch (JG941A)—Only the following interfaces support RRPP:

{ Interfaces numbered from 1 to 16.

{ Interfaces numbered 49 and 50.

Overview

Metropolitan area networks (MANs) and enterprise networks typically use the ring topology to improve reliability. However, services will be interrupted if any node in the ring network fails. A ring network typically uses RPR or Ethernet rings. RPR is high in cost because it needs dedicated hardware. In contrast, the Ethernet ring technology is more mature and economical, so it is more and more popular in MANs and enterprise networks.

The Rapid Ring Protection Protocol (RRPP) is a link layer protocol designed for Ethernet rings. RRPP can prevent broadcast storms caused by data loops when an Ethernet ring is healthy. RRPP can also rapidly restore the communication paths between the nodes when a link is disconnected on the ring. The convergence time of RRPP is independent of the number of nodes in the Ethernet ring. RRPP is applicable to large-diameter networks.

Page 54

Basic RRPP concepts

Figure 12 shows a typical RRPP network with two Ethernet rings and multiple nodes. RRPP detects ring

status and sends topology change information by exchanging Rapid Ring Protection Protocol Data Units (RRPPDUs) among the nodes.

Figure 12 RRPP networking diagram

RRPP domain

An RR PP do main is u niqu ely id enti fied by a do main ID. Th e in tercon nect ed d evices wi th the sa me d omai n ID and control VLANs constitute an RRPP domain. An RRPP domain contains the following elements:

• Primary ring and subring.

• Control VLAN.

• Master node, transit node, edge node, and assistant edge node.

• Primary port, secondary port, common port, and edge port.

As shown in Figure 12, Dom the nodes on the two RRPP rings belong to the RRPP domain.

RRPP ring

A ring-shaped Ethernet topology is called an RRPP ring. RRPP rings include primary rings and subrings. You can configure a ring as either the primary ring or a subring by specifying its ring level. The primary ring is of level 0, and a subring is of level 1. An RRPP domain contains one or multiple RRPP rings, one serving as the primary ring and the others serving as subrings. A ring can be in one of the following states:

• Health state—All physical links on the Ethernet ring are connected.

• Disconnect state—Some physical links on the Ethernet ring are not connected.

As shown in Figure 12, 1 and 1 for Ring 2. Ring 1 is configured as the primary ring, and Ring 2 is configured as a subring.

ain 1 is an RRPP domain, containing two RRPP rings: Ring 1 and Ring 2. All

Domai n 1 contain s two RRPP rings : Ring 1 and Ring 2. The level is set to 0 for Ring

Control VLAN and data VLAN

1. Control VLAN

Page 55

Node

In an RRPP domain, a control VLAN is dedicated to transferring RRPPDUs. On a device, the ports accessing an RRPP ring belong to the control VLANs of the ring, and only these ports can join the control VLANs.

An RRPP domain is configured with the following control VLANs:

{ One primary control VLAN, which is the control VLAN for the primary ring.

{ One secondary control VLAN, which is the control VLAN for subrings.

After you specify a VLAN as the primary control VLAN, the system automatically configures the secondary control VLAN. The VLAN ID is the primary control VLAN ID plus one. All subrings in the same RRPP domain share the same secondary control VLAN. IP address configuration is prohibited on the control VLAN interfaces.

2. Data VLAN

A data VLAN is dedicated to transferring data packets. Both RRPP ports and non-RRPP ports can be assigned to a data VLAN.

Each device on an RRPP ring is a node. The role of a node is configurable. RRPP has the following node roles:

• Master node—Each ring has only one master node. The master node initiates the polling

mechanism and determines the operations to be performed after a topology change.

• Transit node—On the primary ring, transit nodes refer to all nodes except the master node. On the

subring, transit nodes refer to all nodes except the master node and the nodes where the primary ring intersects with the subring. A transit node monitors the state of its directly connected RRPP links and notifies the master node of the link state changes, if any. Based on the link state changes, the master node determines the operations to be performed.

Port

• Edge node—A special node residing on both the primary ring and a subring at the same time. An

edge node acts as a master node or transit node on the primary ring and as an edge node on the subring.

• Assistant edge node—A special node residing on both the primary ring and a subring at the same

time. An assistant edge node acts as a master node or transit node on the primary ring and as an assistant edge node on the subring. This node works in conjunction with the edge node to detect the integrity of the primary ring and to perform loop guard.

As shown in Figure 12, R

ing 1 is the primary ring and Ring 2 is a subring. Device A is the master node of Ring 1. Device B, Device C, and Device D are the transit nodes of Ring 1. Device E is the master node of Ring 2, Device B is the edge node of Ring 2, and Device C is the assistant edge node of Ring 2.

1. Primary port and secondary port

Each master node or transit node has two ports connected to an RRPP ring, a primary port and a secondary port. You can determine the role of a port.

In terms of functionality, the primary port and the secondary port of a master node have the following differences:

{ The primary port and the secondary port are designed to play the role of sending and receiving

Hello packets, respectively.

{ When an RRPP ring is in Health state, the secondary port logically denies data VLANs and

permits only the packets from the control VLANs.

Page 56

{ When an RRPP ring is in Disconnect state, the secondary port forwards packets from data

VLANs.

In terms of functionality, the primary port and the secondary port of a transit node are the same. Both are designed for transferring protocol packets and data packets over an RRPP ring.

As shown in Figure 12, Devic port and the secondary port of the master node on Ring 1, respectively. Device B, Device C, and Device D are the transit nodes of Ring 1. Their Port 1 and Port 2 are the primary port and the secondary port on Ring 1, respectively.

2. Common port and edge port

The ports connecting the edge node and assistant edge node to the primary ring are common ports. The ports connecting the edge node and assistant edge node only to the subrings are edge ports. You can determine the role of a port.

As shown in Figure 12, Devic Port 2 and Device C's Port 1 and Port 2 access the primary ring, so they are common ports. Device B's Port 3 and Device C's Port 3 access only the subring, so they are edge ports.

RRPP ring group

To reduce Edge-Hello traffic, you can configure a group of subrings on the edge node or assistant edge node. You must configure a device as the edge node of these subrings, and another device as the assistant edge node of these subrings. Additionally, the subrings of the edge node and assistant edge node must connect to the same subring packet tunnels in major ring (SRPTs). Edge-Hello packets of the edge node of these subrings travel to the assistant edge node of these subrings over the same link.

An RRPP ring group configured on the edge node is an edge node RRPP ring group. An RRPP ring group configured on an assistant edge node is an assistant edge node RRPP ring group. Only one subring in an edge node RRPP ring group is allowed to send Edge-Hello packets.

e A is the master node of Ring 1. Port 1 and Port 2 are the primary

e B and Device C reside on Ring 1 and Ring 2. Device B's Port 1 and

RRPPDUs

RRPPDUs of subrings are transmitted as data packets in the primary ring, and RRPPDUs of the primary ring can only be transmitted within the primary ring.

Table 10 RRPPDU types and their functions

e Description

Hello

Link-Down

Common-Flush-FDB

Complete-Flush-FDB

The master node initiates Hello packets (also known as Health packets) to detect the integrity of a ring in a network.

When a port on the transit node, edge node, or assistant edge node fails, the node initiates Link-Down packets to notify the master node of the disconnection of the ring.

When an RRPP ring transits to Disconnect state, the master node initiates Common-Flush-FDB (FDB stands for Forwarding Database) packets. It uses the packets to instruct the transit nodes, edge nodes, and assistant edge nodes to update their own MAC address entries and ARP/ND entries.

When an RRPP ring transits to Health state, the master node initiates Complete-Flush-FDB packets for the following purposes:

• Instruct the transit nodes, edge nodes, and assistant edge nodes to update their

MAC address entries and ARP/ND entries.

• Instruct the transit nodes to release temporarily blocked ports.

Page 57

Type Description

Edge-Hello

Major-Fault

RRPP timers

When RRPP determines the link state of an Ethernet ring, it uses the following timers:

• Hello timer—Specifies the interval at which the master node sends Hello packets out of the primary

port.

• Fail timer—Specifies the maximum delay of Hello packets sent from the primary port to the

secondary port of the master node. If the secondary port receives the Hello packets sent by the local master node before the Fail timer expires, the ring is in Health state. Otherwise, the ring transits to Disconnect state.

In an RRPP domain, a transit node learns the Fail timer value on the master node through the received Hello packets. This ensures that all nodes in the ring network have consistent Fail timer settings.

How RRPP works

The edge node initiates Edge-Hello packets to examine the SRPTs between the edge node and the assistant edge node.

The assistant edge node initiates Major-Fault packets to notify the edge node of SRPT failure when an SRPT between assistant edge node and edge node is disconnected.

Polling mechanism

The polling mechanism is used by the master node of an RRPP ring to examine the Health state of the ring network.

The master node sends Hello packets out of its primary port at the Hello interval. These Hello packets travel through each transit node on the ring in turn.

• If the ring is complete, the secondary port of the master node receives Hello packets before the Fail

timer expires. The master node keeps the secondary port blocked.

• If the ring is disconnected, the secondary port of the master node fails to receive Hello packets

before the Fail timer expires. The master node releases the secondary port from blocking data VLANs. It sends Common-Flush-FDB packets to instruct all transit nodes to update their own MAC address entries and ARP/ND entries.

Load balancing

In a ring network, traffic from multiple VL ANs might be transmitted at the same time. RRPP can implement load balancing by transmitting traffic from different VLANs along different paths.

You can configure multiple RRPP domains for a ring network. Each RRPP domain transmits the traffic from the specified VLANs (protected VLANs). Traffic from different VLANs can be transmitted according to different topologies in the ring network for load balancing.

As shown in Figure 17, configured with different protected VLANs. Device A is the master node of Ring 1 in Domain 1. Device B is the master node of Ring 1 in Domain 2. With such configurations, traffic from different VLANs can be transmitted on different links for load balancing in the single-ring network.

Ring 1 is configured as the primary ring of Domain 1 and Domain 2, which are

Page 58

Link down alarm mechanism

In an RRPP domain, when the transit node, edge node, or assistant edge node finds that any of its ports is down, it immediately sends Link-Down packets to the master node. When the master node receives a Link-Down packet, it takes the following actions:

• Releases the secondary port from blocking data VLANs.

• Sends Common-Flush-FDB packets to instruct all the transit nodes, edge nodes, and assistant edge

nodes to update their MAC address entries and ARP/ND entries.

After each node updates its own entries, traffic is switched to the normal link.

Ring recovery

When the ports in an RRPP domain on the transit nodes, edge nodes, or assistant edge nodes come up again, the ring is recovered. However, the master node might detect the ring recovery after a period of time. A temporary loop might arise in the data VLAN during this period. As a result, a broadcast storm occurs.

To prevent such cases, non-master nodes block the ports immediately when they find the ports accessing the ring are brought up again. The nodes block only the packets from the protected VLAN, and they permit only the packets from the control VLAN to pass through. The blocked ports are activated only when the nodes determine that no loop will be generated by these ports.

Broadcast storm suppression mechanism in case of SRPT failure in a multi-homed subring

As shown in Figure 16, Ring 1 is the primary ring, and Ring 2 and Ring 3 are subrings. When the two SRPTs between the edge node and the assistant edge node are down, the master nodes of Ring 2 and Ring 3 will open their secondary ports. A loop is generated among Device B, Device C, Device E, and Device F, causing a broadcast storm.

To avoid generating a loop, the edge node will temporarily block the edge port. The blocked edge port is activated only when the edge node determines that no loop will be generated when the edge port is activated.

RRPP ring group

In an edge node RRPP ring group, only the activated subring with the smallest domain ID and ring ID can send Edge-Hello packets. In an assistant edge node RRPP ring group, any activated subring that has received Edge-Hello packets will forward these packets to the other activated subrings. When an edge node RRPP ring group and an assistant edge node RRPP ring group are configured, the CPU workload is reduced because of the following reasons:

• Only one subring sends Edge-Hello packets on the edge node.

• Only one subring receives Edge-Hello packets on the assistant edge node.

As shown in Figure 16, node of Ring 2 and Ring 3. Device B and Device C need to sen d or receive Edge-H ello packets freque ntly. If more subrings are configured or more domains are configured for load balancing, Device B and Device C will send or receive a large number of Edge-Hello packets.

To reduce Edge-Hello traffic, perform the following tasks:

• Assign Ring 2 and Ring 3 to an RRPP ring group configured on the edge node Device B.

• Assign Ring 2 and Ring 3 to an RRPP ring group configured on the assistant edge node Device C.

If all rings are activated, only Ring 2 on Device B sends Edge-Hello packets.

Device B is the edge node of Ring 2 and Ring 3. Device C is the assistant edge

Page 59

Typical RRPP networking

Single ring

As shown in Figure 13, only a single ring exists in the network topology. You need only define an RRPP domain.

Figure 13 Schematic diagram for a single-ring network

Tangent rings

As shown in Figure 14, two or more rings exist in the network topology and only one common node exists between rings. You must define an RRPP domain for each ring.

Figure 14 Schematic diagram for a tangent-ring network

Intersecting rings

As shown in Figure 15, two or more rings exist in the network topology and two common nodes exist between rings. You need only define an RRPP domain and configure one ring as the primary ring and the other rings as subrings.

Page 60

Figure 15 Schematic diagram for an intersecting-ring network

Dual-homed rings

As shown in Figure 16, two or more rings exist in the network topology and two similar common nodes exist between rings. You need only define an RRPP domain and configure one ring as the primary ring and the other rings as subrings.

Figure 16 Schematic diagram for a dual-homed-ring network

Single-ring load balancing

In a single-ring network, you can achieve load balancing by configuring multiple domains.

As shown in Figure 17:

• R

ing 1 is configured as the primary ring of both Domain 1 and Domain 2.

• Domain 1 and Domain 2 are configured with different protected VLANs.

• In Domain 1, Device A is configured as the master node of Ring 1.

• In Domain 2, Device B is configured as the master node of Ring 1.

Such configurations enable the ring to block different links based on VLANs and achieve single-ring load balancing.

Page 61

Figure 17 Schematic diagram for a single-ring load balancing network

Intersecting-ring load balancing

In an intersecting-ring network, you can also achieve load balancing by configuring multiple domains.

As shown in Figure 18:

• R

ing 1 is the primary ring and Ring 2 is the subring in both Domain 1 and Domain 2.

• Domain 1 and Domain 2 are configured with different protected VLANs.

• Device A is configured as the master node of Ring 1 in Domain 1.

• Device D is configured as the master node of Ring 1 in Domain 2.

• Device E is configured as the master node of Ring 2 in both Domain 1 and Domain 2. However,

different ports on Device E are blocked in Domain 1 and Domain 2.

With the configurations, you can enable traffic from different VLANs to travel over different paths in the subring and primary ring, achieving intersecting-ring load balancing.

Figure 18 Schematic diagram for an intersecting-ring load balancing network

Protocols and standards

RFC 3619, Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1.

Page 62

RRPP configuration task list

You can configure RRPP in the following order:

• Create RRPP domains based on service planning.

• Specify control VLANs and data VLANs for each RRPP domain.

• Determine the ring roles and node roles based on the traffic paths in each RRPP domain.

RRPP does not have an auto election mechanism. You must configure each node in the ring network correctly for RRPP to monitor and protect the ring network.

Before you configure RRPP, you must physically construct a ring-shaped Ethernet topology.

To configure RRPP, perform the following tasks:

Tasks at a glance

(Required.) Creating an RRPP domain Perform this task on all nodes in the RRPP domain.

(Required.) Configuring control VLANs Perform this task on all nodes in the RRPP domain.

(Required.) Configuring protected VLANs Perform this task on all nodes in the RRPP domain.

(Required.) Configuring RRPP rings:

• Configuring RRPP ports

• Configuring RRPP nodes

(Required.) Activating an RRPP domain Perform this task on all nodes in the RRPP domain.

(Optional.) Configuring RRPP timers Perform this task on the master node in the RRPP domain.

(Optional.) Configuring an RRPP ring group

Creating an RRPP domain

When you create an RRPP domain, specify a domain ID to uniquely identify the RRPP domain. All devices in the same RRPP domain must be configured with the same domain ID.

Perform this task on devices you want to configure as nodes in the RRPP domain.

Remarks

Perform this task on all nodes in the RRPP domain.

Perform this task on the edge node and assistant edge node in the RRPP domain.

To create an RRPP domain:

Step Command

1. Enter system view.

2. Create an RRPP domain and

enter RRPP domain view.

system-view N/A

rrpp domain domain-id

Remarks

By default, no RRPP domain is created.

Configuring control VLANs

Before you configure RRPP rings in an RRPP domain, configure the same control VLANs for all nodes in the RRPP domain first. You need only configure the primary control VLAN for an RRPP domain. The system automatically configures the secondary control VLAN. It uses the primary control VLAN ID plus 1 as the

Page 63

secondary control VLAN ID. For the control VLAN configuration to succeed, make sure the IDs of the two

control VLANs are consecutive and have not been previously assigned.

Follow these guidelines when you configure control VLANs:

• Do not configure the default VLAN of a port accessing an RRPP ring as the control VLAN, and do

not enable QinQ or VLAN mapping on control VLANs. If you do, RRPPDUs cannot be correctly forwarded.

• After you configure RRPP rings for an RRPP domain, you cannot delete or modify the primary control

VLAN of the domain. You can only use the undo control-vlan command to delete a primary control VLAN.

• To transparently transmit RRPPDUs on a device not configured with RRPP, make sure only the two

ports accessing the RRPP ring permit packets from the control VLANs. Otherwise, the packets from other VLANs might enter the control VLANs in transparent transmission mode and strike the RRPP ring.

Perform this task on all nodes in the RRPP domain to be configured.

To configure control VLANs:

Step Command

1. Enter system view.

2. Enter RRPP domain view.

3. Configure the primary control

VLAN for the RRPP domain.

system-view N/A

rrpp domain domain-id

control-vlan vlan-id

Configuring protected VLANs

Before you configure RRPP rings in an RRPP domain, configure the same protected VLANs for all nodes in the RRPP domain. All VLANs to which the RRPP ports are assigned must be protected by the RRPP domains.

Protected VLANs are configured by referencing Multiple Spanning Tree Instances (MSTIs). The protected VLAN configuration method varies by the spanning tree mode:

• In STP, RSTP, or MSTP mode, you must manually configure the mappings between VLANs and

MSTIs.

• In PVST mode, the device automatically maps each VLAN to an MSTI. When the spanning tree

protocol is disabled globally, all VLANs are automatically mapped to MSTI 0.

For more information about spanning tree, see Layer 2—LAN Switching Configuration Guide.

Remarks

N/A

By default, no control VLAN exists in the RRPP domain.

IMPORTANT:

hen you configure load balancing, you must configure different protected VLANs for different RRPP

domains.

Perform this task on all nodes in the RRPP domain to be configured.

To configure protected VLANs:

Page 64

Step Command

1. Enter system view.

2. Enter MST region view.

system-view N/A

stp region-configuration

• Method 1:

3. Configure the

VLAN-to-instance mapping table.

4. Activate MST region

configuration.

instance instance-id vlan vlan-id-list

• Method 2:

vlan-mapping modulo modulo

active region-configuration

Remarks

Not required if the device is operating in PVST mode.

For more information about the command, see Layer 2—LAN Switching Command Reference.

Use either method.

By default, all VLANs in an MST region are mapped to MSTI 0 (the CIST).

Not required if the device is operating in PVST mode.

For more information about the commands, see Layer 2—LAN Switching Command Reference.

Not required if the device is operating in PVST mode.

For more information about the command, see Layer 2—LAN Switching Command Reference.

5. (Optional.) Display the

currently activated configuration information of the MST region.

6. Return to system view.

7. Enter RRPP domain view.

8. Configure protected VLANs

for the RRPP domain.

display stp region-configuration

quit

rrpp domain domain-id N/A

protected-vlan reference-instance instance-id-list

Configuring RRPP rings

When you configure an RRPP ring, you must configure the ports connecting each node to the RRPP ring before configuring the nodes.

Configuring RRPP ports

Available in any view.

The output of the command includes VLAN-to-instance mappings.

For more information about the command, see Layer 2—LAN Switching Command Reference.

Not required if the device is operating in PVST mode.

By default, no protected VLAN is configured for an RRPP domain.

Follow these guidelines when you configure RRPP ports:

• Do not enable the OAM remote loopback function on an RRPP port. Otherwise, temporary

broadcast storms might occur.

Page 65

• To accelerate topology convergence, HP recommends that you use the link-delay command to

enable link status rapid report function on an RRPP port. Use this command (or the undo link-delay command, depending on the device model) to set the physical state change suppression interval to 0 seconds. For more information about the link-delay command (or the undo link-delay command), see Layer 2—LAN Switching Command Reference.

Perform this task on each node's ports intended for accessing RRPP rings.

To configure RRPP ports:

Step Command

1. Enter system view.

2. Enter Layer 2 Ethernet

interface view or Layer 2 aggregate interface view.

3. Configure the link type of the

interface as trunk.

4. Assign the trunk port to the

protected VLANs of the RRPP domain.

5. Disable the spanning tree

feature.

system-view N/A

interface interface-type interface-number

port link-type trunk

port trunk permit vlan { vlan-id-list | all }

undo stp enable

Remarks

N/A

By default, the link type of an interface is access.

For more information about the command, see Layer 2—LAN Switching Command Reference.

By default, a trunk port allows only packets from VLAN 1 to pass through.

RRPP ports always allow packets from the control VLANs to pass through.

For more information about the command, see Layer 2—LAN Switching Command Reference.

By default, the spanning tree feature is enabled.

For more information about the command, see Layer 2—LAN Switching Command Reference.

Configuring RRPP nodes

The maximum number of rings that can be configured on a device in all RRPP domains is 16.

If a device carries multiple RRPP rings in an RRPP domain, it can only be an edge node or an assistant edge node on a subring.

Specifying a master node

Step Command

1. Enter system view.

2. Enter RRPP domain view.

3. Specify the current

device as the master node of the ring, and specify the primary port and the secondary port.

system-view N/A

rrpp domain domain-id N/A

ring ring-id node-mode master

[ primary-port interface-type interface-number ] [ secondary-port interface-type interface-number ] level level-value

Remarks

By default, the device is not a node of the RRPP ring.

Page 66

Specifying a transit node

Step Command

1. Enter system view.

2. Enter RRPP domain view.

3. Specify the current

device as a transit node of the ring, and specify the primary port and the secondary port.

Specifying an edge node

When you configure an edge node, you must configure the primary ring before configuring the subrings.

To specify an edge node:

Step Command

1. Enter system view.

2. Enter RRPP domain view.

3. Specify the current

device as a master node or transit node of the primary ring, and specify the primary port and the secondary port.

4. Specify the current

device as the edge node of a subring, and specify the edge port.

Remarks

system-view N/A

rrpp domain domain-id N/A

ring ring-id node-mode transit

[ primary-port interface-type interface-number ] [ secondary-port interface-type interface-number ] level level-value

By default, the device is not a node of the RRPP ring.

Remarks

system-view

rrpp domain domain-id N/A

ring ring-id node-mode { master | transit } [ primary-port interface-type

interface-number ] [ secondary-port interface-type interface-number ] level level-value

ring ring-id node-mode edge [ edge-port interface-type interface-number ]

N/A

By default, the device is not a node of the RRPP ring.

Specifying an assistant edge node

When you configure an assistant edge node, you must configure the primary ring before configuring the subrings.

To specify an assistant edge node:

Step Command

1. Enter system view.

2. Enter RRPP domain view.

3. Specify the current device

as a master node or transit node of the primary ring, and specify the primary port and the secondary port.

Remarks

system-view N/A

rrpp domain domain-id N/A

ring ring-id node-mode { master | transit } [ primary-port interface-type

interface-number ] [ secondary-port interface-type interface-number ] level level-value

By default, the device is not a node of the RRPP ring.

Page 67

Step Command

4. Specify the current device

as the assistant edge node of the subring, and specify an edge port.

ring ring-id node-mode assistant-edge [ edge-port interface-type interface-number ]

Activating an RRPP domain

Before you activate an RRPP domain on the current device, enable the RRPP protocol and RRPP rings for the RRPP domain on the current device.

Follow these guidelines when you activate an RRPP domain:

• Before you enable subrings on a device, you must enable the primary ring. Before you disable the

primary ring on the device, you must disable all subrings. Otherwise, the system displays error prompts.

• To prevent Hello packets of subrings from being looped on the primary ring, enable the primary

ring on its master node first. Then enable the subrings on their separate master nodes.

Perform this task on all nodes in the RRPP domain.

To activate an RRPP domain:

Remarks

By default, the device is not a node of the RRPP ring.

Step Command

1. Enter system view.

2. Enable RRPP.

3. Enter RRPP domain view.

4. Enable the specified RRPP

ring.

system-view N/A

rrpp enable By default, RRPP is disabled.

rrpp domain domain-id N/A

ring ring-id enable

Configuring RRPP timers

The Fail timer must be greater than or equal to three times the Hello timer.

In a dual-homed-ring network, make sure the difference between the Fail timer values on the master node of the subring and the master node of the primary ring is greater than twice the Hello timer value on the master node of the subring. Otherwise, temporary loops might occur when the primary ring fails.

Perform this task on the master node of an RRPP domain.

To configure RRPP timers:

Step Command

1. Enter system view.

system-view N/A

Remarks

By default, an RRPP ring is disabled.

Remarks

2. Enter RRPP domain view.

3. Configure the Hello timer

and Fail timer for the RRPP domain.

rrpp domain domain-id N/A

timer hello-timer hello-value fail-timer fail-value

By default, the Hello timer value is 1 second and the Fail timer value is 3 seconds.

Page 68

Configuring an RRPP ring group

To reduce Edge-Hello traffic, assign subrings with the same edge node and assistant edge node to an RRPP ring group. An RRPP ring group must be configured on both the edge node and the assistant edge node. It can only be configured on these two types of nodes.

Follow these guidelines when you configure an RRPP ring group:

• You can assign a subring to only one RRPP ring group. The RRPP ring groups configured on the edge

node and the assistant edge node must contain the same subrings. Otherwise, the RRPP ring group cannot operate correctly.

• The subrings in an RRPP ring group must share the same edge node and assistant edge node. The

edge node and the assistant edge node must have the same SRPTs.

• Make sure a device is either the edge node or the assistant edge node on the subrings in an RRPP

ring group.

• Make sure the RRPP ring groups on the edge node and the assistant edge node have the same

configurations and activation status.

• Make sure all subrings in an RRPP ring group have the same SRPTs. If the SRPTs of these subrings are

different, the RRPP ring group cannot operate correctly.

Perform this task on both the edge node and the assistant edge node in an RRPP domain.

To configure an RRPP ring group:

Step Command

1. Enter system view.

2. Create an RRPP ring group

and enter RRPP ring group view.

3. Assign the specified subrings

to the RRPP ring group.

system-view N/A

rrpp ring-group ring-group-id

domain domain-id ring ring-id-list

Displaying and maintaining RRPP

Execute display commands in any view and reset commands in user view.

Task Command

Display brief RRPP information.

Display RRPP group configuration information. display rrpp ring-group [ ring-group-id ]

Display RRPPDU statistics. display rrpp statistics domain domain-id [ ring ring-id ]

Display detailed RRPP information. display rrpp verbose domain domain-id [ ring ring-id ]

Clear RRPPDU statistics. reset rrpp statistics domain domain-id [ ring ring-id ]

display rrpp brief

Remarks

By default, no RRPP ring group is created.

By default, no subrings are assigned to an RRPP ring group.

Page 69

RRPP configuration examples

Single ring configuration example

Network requirements

As shown in Figure 19:

• Device A, D evice B, Device C, and Devi ce D f orm R RPP d omai n 1. Sp ecif y th e pri mar y con trol VLA N

of RRPP domain 1 as VLAN 4092. Specify the protected VLANs of RRPP domain 1 as VLANs 1 through 30.

• Device A, Device B, Device C, and Device D form primary ring 1.

• Specify Device A as the master node of primary ring 1, GigabitEthernet 1/0/1 as the primary port,

and GigabitEthernet 1/0/2 as the secondary port.

• Specify Device B, Device C, and Device D as the transit nodes of primary ring 1. Specify

GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port on Device B, Device C, and Device D.

Figure 19 Network diagram

Configuration procedure

1. Configure Device A:

# Create VLANs 1 through 30.

<DeviceA> system-view [DeviceA] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] link-delay 0

Page 70

# Disable the spanning tree feature on the port.

[DeviceA-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceA-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] link-delay 0 [DeviceA-GigabitEthernet1/0/2] undo stp enable [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceA] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceA-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceA-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceA-rrpp-domain1] ring 1 enable [DeviceA-rrpp-domain1] quit

# Enable RRPP.

[DeviceA] rrpp enable

2. Configure Device B:

# Create VLANs 1 through 30.

<DeviceB> system-view [DeviceB] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceB-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceB-GigabitEthernet1/0/1] port link-type trunk

Page 71

# Assign the port to VLANs 1 through 30.

[DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] link-delay 0 [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceB] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceB-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceB-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device B as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceB-rrpp-domain1] ring 1 enable [DeviceB-rrpp-domain1] quit

# Enable RRPP.

[DeviceB] rrpp enable

3. Configure Device C:

Configure Device C in the same way Device B is configured.

4. Configure Device D:

Configure Device D in the same way Device B is configured.

Verifying the configuration

# Use the display commands to view RRPP configuration and operational information on each device.

Intersecting ring configuration example

Network requirements

As shown in Figure 20:

• Device A, Device B, Device C, Device D, and Device E form RRPP domain 1. VLAN 4092 is the

primary control VLAN of RRPP domain 1. RRPP domain 1 protects VLANs 1 through 30.

• Device A, Device B, Device C, and Device D form primary ring 1. Device B, Device C, and Device

E form subring 2.

• Device A is the master node of primar y ri ng 1, with GigabitEthernet 1/0/1 as the primary port and

GigabitEthernet 1/0/2 the secondary port.

• Device E is the master node of subring 2, with GigabitEthernet 1/0/1 as the primary port and

GigabitEthernet 1/0/2 the secondary port.

Page 72

• Device B is the transit node of primary ring 1 and the edge node of subring 2, with GigabitEthernet

1/0/3 as the edge port.

• Device C is the transit node of primary ring 1 and the assistant edge node of subring 1, with

GigabitEthernet 1/0/3 as the edge port.

• Device D is the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and

GigabitEthernet 1/0/2 the secondary port.

Figure 20 Network diagram

Domain 1

Device A

Master node

Device D

Transit node

Configuration procedure

1. Configure Device A:

# Create VLANs 1 through 30.

<DeviceA> system-view [DeviceA] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceA-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceA-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] link-delay 0

GE1/0/1

GE1/0/2

GE1/0/1

Ring 1

GE1/0/2

GE1/0/1

GE1/0/2

GE1/0/1

Device B

Edge node

GE1/0/3

Ring 2

GE1/0/3

Device C

Assistant edge node

GE1/0/1

Device E

Master node

GE1/0/2

Page 73

[DeviceA-GigabitEthernet1/0/2] undo stp enable [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceA] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceA-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceA-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceA-rrpp-domain1] ring 1 enable [DeviceA-rrpp-domain1] quit

# Enable RRPP.

[DeviceA] rrpp enable

2. Configure Device B:

# Create VLANs 1 through 30.

<DeviceB> system-view [DeviceB] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceB-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceB-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

Page 74

# Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceB] interface gigabitethernet 1/0/3 [DeviceB-GigabitEthernet1/0/3] link-delay 0 [DeviceB-GigabitEthernet1/0/3] undo stp enable [DeviceB-GigabitEthernet1/0/3] port link-type trunk [DeviceB-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/3] quit

# Create RRPP domain 1.

[DeviceB] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceB-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceB-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device B as a transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceB-rrpp-domain1] ring 1 enable

# Configure Device B as the edge node of subring 2, with GigabitEthernet 1/0/3 as the edge port. Enable ring 2.

[DeviceB-rrpp-domain1] ring 2 node-mode edge edge-port gigabitethernet 1/0/3 [DeviceB-rrpp-domain1] ring 2 enable [DeviceB-rrpp-domain1] quit

# Enable RRPP.

[DeviceB] rrpp enable

3. Configure Device C:

# Create VLANs 1 through 30.

<DeviceC> system-view [DeviceC] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceC-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceC-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceC-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/1] quit

Page 75

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] link-delay 0 [DeviceC-GigabitEthernet1/0/2] undo stp enable [DeviceC-GigabitEthernet1/0/2] port link-type trunk [DeviceC-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/2] quit

# Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceC] interface gigabitethernet 1/0/3 [DeviceC-GigabitEthernet1/0/3] link-delay 0 [DeviceC-GigabitEthernet1/0/3] undo stp enable [DeviceC-GigabitEthernet1/0/3] port link-type trunk [DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/3] quit

# Create RRPP domain 1.

[DeviceC] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceC-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceC-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device C as a transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceC-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceC-rrpp-domain1] ring 1 enable

# Configure Device C as the assistant edge node of subring 2, with GigabitEthernet 1/0/3 as the edge port. Enable ring 2.

[DeviceC-rrpp-domain1] ring 2 node-mode assistant-edge edge-port gigabitethernet 1/0/3

[DeviceC-rrpp-domain1] ring 2 enable [DeviceC-rrpp-domain1] quit

# Enable RRPP.

[DeviceC] rrpp enable

4. Configure Device D:

# Create VLANs 1 through 30.

<DeviceD> system-view [DeviceD] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceD] stp region-configuration [DeviceD-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceD-mst-region] active region-configuration [DeviceD-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] link-delay 0

Page 76

# Disable the spanning tree feature on the port.

[DeviceD-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceD-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] link-delay 0 [DeviceD-GigabitEthernet1/0/2] undo stp enable [DeviceD-GigabitEthernet1/0/2] port link-type trunk [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceD] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceD-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceD-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device D as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceD-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceD-rrpp-domain1] ring 1 enable [DeviceD-rrpp-domain1] quit

# Enable RRPP.

[DeviceD] rrpp enable

5. Configure Device E:

# Create VLANs 1 through 30.

<DeviceE> system-view [DeviceE] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceE] stp region-configuration [DeviceE-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceE-mst-region] active region-configuration [DeviceE-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceE] interface gigabitethernet 1/0/1 [DeviceE-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceE-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceE-GigabitEthernet1/0/1] port link-type trunk

Page 77

# Assign the port to VLANs 1 through 30.

[DeviceE-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceE-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceE] interface gigabitethernet 1/0/2 [DeviceE-GigabitEthernet1/0/2] link-delay 0 [DeviceE-GigabitEthernet1/0/2] undo stp enable [DeviceE-GigabitEthernet1/0/2] port link-type trunk [DeviceE-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceE-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceE] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceE-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceE-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device E as the master node of subring 2, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 2.

[DeviceE-rrpp-domain1] ring 2 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 1

[DeviceE-rrpp-domain1] ring 2 enable [DeviceE-rrpp-domain1] quit

# Enable RRPP.

[DeviceE] rrpp enable

Verifying the configuration

# Use the display commands to view RRPP configuration and operational information on each device.

Dual-homed rings configuration example

Network requirements

As shown in Figure 21:

• Device A through D evice H form RRPP domain 1. Specify th e prim ary control VLA N of RRPP domain

1 as VLAN 4092. Specify the protected VLANs of RRPP domain 1 as VLANs 1 through 30.

• Device A through Device D form primary ring 1. Device A, Device B, and Device E form subring 2.

Device A, Device B, and Device F form subring 3. Device C, Device D, and Device G form subring

4. Device C, Device D, and Device H form subring 5.

• Specify Device A, Device E, Device F, Device G, and Device H as the master nodes of Ring 1, Ring

2, Ring 3, Ring 4, and Ring 5, respectively. Specify GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port on the rings.

• Specify Device A as the edge node of the connected subrings, its GigabitEthernet 1/0/3 and

GigabitEthernet 1/0/4 as the edge ports. Specify Device D as the transit node of the primary ring and edge node of the connected subrings, its GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 as the edge ports. Specify Device B and Device C as the transit node of the primary ring and assistant edge nodes of the connected subrings, their GigabitEthernet 1/0/3 and GigabitEthernet 1/0/4 as the edge ports.

Page 78

IMPORTANT:

Configure the primary and secondary ports on the master nodes correctly to make sure other protocols still operate correctly when data VLANs are denied by the secondary ports.

Figure 21 Network diagram

GE1/0/2

0/1

GE1/

Configuration procedure

1. Configure Device A:

# Create VLANs 1 through 30.

<DeviceA> system-view [DeviceA] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceA-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceA-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

GE1/0

GE1/0/4

GE1/0/3

E1/

GE1/0/1

Page 79

# Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceA] interface gigabitethernet 1/0/3 [DeviceA-GigabitEthernet1/0/3] link-delay 0 [DeviceA-GigabitEthernet1/0/3] undo stp enable [DeviceA-GigabitEthernet1/0/3] port link-type trunk [DeviceA-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/3] quit

# Configure GigabitEthernet 1/0/4 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceA] interface gigabitethernet 1/0/4 [DeviceA-GigabitEthernet1/0/4] link-delay 0 [DeviceA-GigabitEthernet1/0/4] undo stp enable [DeviceA-GigabitEthernet1/0/4] port link-type trunk [DeviceA-GigabitEthernet1/0/4] port trunk permit vlan 1 to 30 [DeviceA-GigabitEthernet1/0/4] quit

# Create RRPP domain 1.

[DeviceA] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceA-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceA-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceA-rrpp-domain1] ring 1 enable

# Configure Device A as the edge node of subring 2, with GigabitEthernet 1/0/4 as the edge port. Enable subring 2.

[DeviceA-rrpp-domain1] ring 2 node-mode edge edge-port gigabitethernet 1/0/4 [DeviceA-rrpp-domain1] ring 2 enable

# Configure Device A as the edge node of subring 3, with GigabitEthernet 1/0/3 as the edge port. Enable subring 3.

[DeviceA-rrpp-domain1] ring 3 node-mode edge edge-port gigabitethernet 1/0/3 [DeviceA-rrpp-domain1] ring 3 enable [DeviceA-rrpp-domain1] quit

# Enable RRPP.

[DeviceA] rrpp enable

2. Configure Device B:

# Create VLANs 1 through 30.

<DeviceB> system-view [DeviceB] vlan 1 to 30

Page 80

# Map these VLANs to MSTI 1.

[DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceB-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceB-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

# Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured.

# Configure GigabitEthernet 1/0/4 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceB] interface gigabitethernet 1/0/4 [DeviceB-GigabitEthernet1/0/4] link-delay 0 [DeviceB-GigabitEthernet1/0/4] undo stp enable [DeviceB-GigabitEthernet1/0/4] port link-type trunk [DeviceB-GigabitEthernet1/0/4] port trunk permit vlan 1 to 30 [DeviceB-GigabitEthernet1/0/4] quit

# Create RRPP domain 1.

[DeviceB] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceB-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceB-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device B as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

Page 81

[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceB-rrpp-domain1] ring 1 enable

# Configure Device B as the assistant edge node of subring 2, with GigabitEthernet 1/0/4 as the edge port. Enable subring 2.

[DeviceB-rrpp-domain1] ring 2 node-mode assistant-edge edge-port gigabitethernet 1/0/4

[DeviceB-rrpp-domain1] ring 2 enable

# Configure Device B as the assistant edge node of subring 3, with GigabitEthernet 1/0/3 as the edge port. Enable subring 3.

[DeviceB-rrpp-domain1] ring 3 node-mode assistant-edge edge-port gigabitethernet 1/0/3

[DeviceB-rrpp-domain1] ring 3 enable [DeviceB-rrpp-domain1] quit

# Enable RRPP.

[DeviceB] rrpp enable

3. Configure Device C:

# Create VLANs 1 through 30.

<DeviceC> system-view [DeviceC] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceC-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceC-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceC-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

# Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceC] interface gigabitethernet 1/0/3 [DeviceC-GigabitEthernet1/0/3] link-delay 0

Page 82

[DeviceC-GigabitEthernet1/0/3] undo stp enable [DeviceC-GigabitEthernet1/0/3] port link-type trunk [DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/3] quit

# Configure GigabitEthernet 1/0/4 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceC] interface gigabitethernet 1/0/4 [DeviceC-GigabitEthernet1/0/4] link-delay 0 [DeviceC-GigabitEthernet1/0/4] undo stp enable [DeviceC-GigabitEthernet1/0/4] port link-type trunk [DeviceC-GigabitEthernet1/0/4] port trunk permit vlan 1 to 30 [DeviceC-GigabitEthernet1/0/4] quit

# Create RRPP domain 1.

[DeviceC] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceC-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceC-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device C as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceC-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceC-rrpp-domain1] ring 1 enable

# Configure Device C as the assistant edge node of subring 4, with GigabitEthernet 1/0/3 as the edge port. Enable subring 4.

[DeviceC-rrpp-domain1] ring 4 node-mode assistant-edge edge-port gigabitethernet 1/0/3

[DeviceC-rrpp-domain1] ring 4 enable

# Configure Device C as the assistant edge node of subring 5, with GigabitEthernet 1/0/4 as the edge port. Enable subring 5.

[DeviceC-rrpp-domain1] ring 5 node-mode assistant-edge edge-port gigabitethernet 1/0/4

[DeviceC-rrpp-domain1] ring 5 enable [DeviceC-rrpp-domain1] quit

# Enable RRPP.

[DeviceC] rrpp enable

4. Configure Device D:

# Create VLANs 1 through 30.

<DeviceD> system-view [DeviceD] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceD] stp region-configuration [DeviceD-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceD-mst-region] active region-configuration [DeviceD-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

Page 83

[DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceD-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceD-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

# Configure GigabitEthernet 1/0/3 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceD] interface gigabitethernet 1/0/3 [DeviceD-GigabitEthernet1/0/3] link-delay 0 [DeviceD-GigabitEthernet1/0/3] undo stp enable [DeviceD-GigabitEthernet1/0/3] port link-type trunk [DeviceD-GigabitEthernet1/0/3] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/3] quit

# Configure GigabitEthernet 1/0/4 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceD] interface gigabitethernet 1/0/4 [DeviceD-GigabitEthernet1/0/4] link-delay 0 [DeviceD-GigabitEthernet1/0/4] undo stp enable [DeviceD-GigabitEthernet1/0/4] port link-type trunk [DeviceD-GigabitEthernet1/0/4] port trunk permit vlan 1 to 30 [DeviceD-GigabitEthernet1/0/4] quit

# Create RRPP domain 1.

[DeviceD] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceD-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceD-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device D as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceD-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceD-rrpp-domain1] ring 1 enable

# Configure Device D as the edge node of subring 4, with GigabitEthernet 1/0/3 as the edge port. Enable subring 4.

[DeviceD-rrpp-domain1] ring 4 node-mode edge edge-port gigabitethernet 1/0/3 [DeviceD-rrpp-domain1] ring 4 enable

Page 84

# Configure Device D as the edge node of subring 5, with GigabitEthernet 1/0/4 as the edge port. Enable subring 5.

[DeviceD-rrpp-domain1] ring 5 node-mode edge edge-port gigabitethernet 1/0/4 [DeviceD-rrpp-domain1] ring 5 enable [DeviceD-rrpp-domain1] quit

# Enable RRPP.

[DeviceD] rrpp enable

5. Configure Device E:

# Create VLANs 1 through 30.

<DeviceE> system-view [DeviceE] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceE] stp region-configuration [DeviceE-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceE-mst-region] active region-configuration [DeviceE-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceE] interface gigabitethernet 1/0/1 [DeviceE-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceE-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceE-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceE-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceE-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

# Create RRPP domain 1.

[DeviceE] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceE-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceE-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device E as the master node of subring 2, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable subring 2.

[DeviceE-rrpp-domain1] ring 2 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 1

[DeviceE-rrpp-domain1] ring 2 enable

Page 85

[DeviceE-rrpp-domain1] quit

# Enable RRPP.

[DeviceE] rrpp enable

6. Configure Device F:

# Create VLANs 1 through 30.

<DeviceF> system-view [DeviceF] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceF-mst-region] active region-configuration [DeviceF-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceF] interface gigabitethernet 1/0/1 [DeviceF-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceF-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceF-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceF-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceF-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceF] interface gigabitethernet 1/0/2 [DeviceF-GigabitEthernet1/0/2] link-delay 0 [DeviceF-GigabitEthernet1/0/2] undo stp enable [DeviceF-GigabitEthernet1/0/2] port link-type trunk [DeviceF-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceF-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceF] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceF-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceF-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device F as the master node of subring 3, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable subring 3.

[DeviceF-rrpp-domain1] ring 3 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 1

[DeviceF-rrpp-domain1] ring 3 enable [DeviceF-rrpp-domain1] quit

# Enable RRPP.

[DeviceF] rrpp enable

7. Configure Device G:

Page 86

# Create VLANs 1 through 30.

<DeviceG> system-view [DeviceG] vlan 1 to 30

# Map these VLANs to MSTI 1.

[DeviceG] stp region-configuration [DeviceG-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceG-mst-region] active region-configuration [DeviceG-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceG] interface gigabitethernet 1/0/1 [DeviceG-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceG-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceG-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceG-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceG-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceG] interface gigabitethernet 1/0/2 [DeviceG-GigabitEthernet1/0/2] link-delay 0 [DeviceG-GigabitEthernet1/0/2] undo stp enable [DeviceG-GigabitEthernet1/0/2] port link-type trunk [DeviceG-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceG-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceG] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceG-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceG-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device G as the master node of subring 4, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable subring 4.

[DeviceG-rrpp-domain1] ring 4 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 1

[DeviceG-rrpp-domain1] ring 4 enable [DeviceG-rrpp-domain1] quit

# Enable RRPP.

[DeviceG] rrpp enable

8. Configure Device H:

# Create VLANs 1 through 30.

<DeviceH> system-view [DeviceH] vlan 1 to 30

# Map these VLANs to MSTI 1.

Page 87

[DeviceH] stp region-configuration [DeviceH-mst-region] instance 1 vlan 1 to 30

# Activate the MST region configuration.

[DeviceH-mst-region] active region-configuration [DeviceH-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceH] interface gigabitethernet 1/0/1 [DeviceH-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceH-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceH-GigabitEthernet1/0/1] port link-type trunk

# Assign the port to VLANs 1 through 30.

[DeviceH-GigabitEthernet1/0/1] port trunk permit vlan 1 to 30 [DeviceH-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceH] interface gigabitethernet 1/0/2 [DeviceH-GigabitEthernet1/0/2] link-delay 0 [DeviceH-GigabitEthernet1/0/2] undo stp enable [DeviceH-GigabitEthernet1/0/2] port link-type trunk [DeviceH-GigabitEthernet1/0/2] port trunk permit vlan 1 to 30 [DeviceH-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceH] rrpp domain 1

# Configure VLAN 4092 as the primary control VLAN of RRPP domain 1.

[DeviceH-rrpp-domain1] control-vlan 4092

# Configure the VLANs mapped to MSTI 1 as the protected VLANs of RRPP domain 1.

[DeviceH-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device H as the master node of subring 5, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable subring 5.

[DeviceH-rrpp-domain1] ring 5 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 1

[DeviceH-rrpp-domain1] ring 5 enable [DeviceH-rrpp-domain1] quit

# Enable RRPP.

[DeviceH] rrpp enable

Verifying the configuration

# Use the display commands to view RRPP configuration and operational information on each device.

Load-balanced intersecting-ring configuration example

Network requirements

As shown in Figure 22:

Page 88

• Device A, Device B, Device C, Device D, and Device F form RRPP domain 1. VLAN 100 is the

primary control VLAN of the RRPP domain. Device A is the master node of the primary ring, Ring 1. Device D is the transit node of Ring 1. Device F is the master node of the subring Ring 3. Device C is the edge node of the subring Ring 3. Device B is the assistant edge node of the subring Ring 3.

• Device A, Device B, Device C, Device D, and Device E form RRPP domain 2. VLAN 105 is the

primary control VLAN of the RRPP domain. Device A is the master node of the primary ring, Ring 1. Device D is the transit node of Ring 1. Device E is the master node of the subring Ring 2. Device C is the edge node of the subring Ring 2. Device B is the assistant edge node of the subring Ring 2.

• Specify VLAN 11 as the protected VLAN of domain 1, and VLAN 12 the protected VLAN of domain

2. You can implement VLAN-based load balancing on Ring 1.

• Ring 2 and Ring 3 have the same edge node and assistant edge node, and the two subrings have

the same SRPTs. You can add Ring 2 and Ring 3 to an RRPP ring group to reduce Edge-Hello traffic.

Figure 22 Network diagram

Configuration procedure

1. Configure Device A:

# Create VLANs 11 and 12.

<DeviceA> system-view [DeviceA] vlan 11 to 12

# Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2.

[DeviceA] stp region-configuration [DeviceA-mst-region] instance 1 vlan 11 [DeviceA-mst-region] instance 2 vlan 12

# Activate the MST region configuration.

[DeviceA-mst-region] active region-configuration [DeviceA-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] link-delay 0

Page 89

# Disable the spanning tree feature on the port.

[DeviceA-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceA-GigabitEthernet1/0/1] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLANs 11 and 12.

[DeviceA-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceA-GigabitEthernet1/0/1] port trunk permit vlan 11 12

# Configure VLAN 11 as the default VLAN.

[DeviceA-GigabitEthernet1/0/1] port trunk pvid vlan 11 [DeviceA-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceA] interface gigabitethernet 1/0/2 [DeviceA-GigabitEthernet1/0/2] link-delay 0 [DeviceA-GigabitEthernet1/0/2] undo stp enable [DeviceA-GigabitEthernet1/0/2] port link-type trunk [DeviceA-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceA-GigabitEthernet1/0/2] port trunk permit vlan 11 12 [DeviceA-GigabitEthernet1/0/2] port trunk pvid vlan 11 [DeviceA-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceA] rrpp domain 1

# Configure VLAN 100 as the primary control VLAN of RRPP domain 1.

[DeviceA-rrpp-domain1] control-vlan 100

# Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.

[DeviceA-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceA-rrpp-domain1] ring 1 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceA-rrpp-domain1] ring 1 enable [DeviceA-rrpp-domain1] quit

# Create RRPP domain 2.

[DeviceA] rrpp domain 2

# Configure VLAN 105 as the primary control VLAN of RRPP domain 2.

[DeviceA-rrpp-domain2] control-vlan 105

# Configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2.

[DeviceA-rrpp-domain2] protected-vlan reference-instance 2

# Configure Device A as the master node of primary ring 1, with GigabitEthernet 1/0/2 as the master port and GigabitEthernet 1/0/1 as the secondary port. Enable ring 1.

[DeviceA-rrpp-domain2] ring 1 node-mode master primary-port gigabitethernet 1/0/2 secondary-port gigabitethernet 1/0/1 level 0

[DeviceA-rrpp-domain2] ring 1 enable [DeviceA-rrpp-domain2] quit

# Enable RRPP.

[DeviceA] rrpp enable

2. Configure Device B:

Page 90

# Create VLANs 11 and 12.

<DeviceB> system-view [DeviceB] vlan 11 to 12

# Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2.

[DeviceB] stp region-configuration [DeviceB-mst-region] instance 1 vlan 11 [DeviceB-mst-region] instance 2 vlan 12

# Activate the MST region configuration.

[DeviceB-mst-region] active region-configuration [DeviceB-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceB] interface gigabitethernet 1/0/1 [DeviceB-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceB-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceB-GigabitEthernet1/0/1] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLANs 11 and 12.

[DeviceB-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceB-GigabitEthernet1/0/1] port trunk permit vlan 11 12

# Configure VLAN 11 as the default VLAN.

[DeviceB-GigabitEthernet1/0/1] port trunk pvid vlan 11 [DeviceB-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceB] interface gigabitethernet 1/0/2 [DeviceB-GigabitEthernet1/0/2] link-delay 0 [DeviceB-GigabitEthernet1/0/2] undo stp enable [DeviceB-GigabitEthernet1/0/2] port link-type trunk [DeviceB-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceB-GigabitEthernet1/0/2] port trunk permit vlan 11 12 [DeviceB-GigabitEthernet1/0/2] port trunk pvid vlan 11 [DeviceB-GigabitEthernet1/0/2] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/3.

[DeviceB] interface gigabitethernet 1/0/3 [DeviceB-GigabitEthernet1/0/3] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceB-GigabitEthernet1/0/3] undo stp enable

# Configure the port as a trunk port.

[DeviceB-GigabitEthernet1/0/3] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLAN 12.

[DeviceB-GigabitEthernet1/0/3] undo port trunk permit vlan 1 [DeviceB-GigabitEthernet1/0/3] port trunk permit vlan 12

# Configure VLAN 12 as the default VLAN.

[DeviceB-GigabitEthernet1/0/3] port trunk pvid vlan 12 [DeviceB-GigabitEthernet1/0/3] quit

Page 91

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/4.

[DeviceB] interface gigabitethernet 1/0/4 [DeviceB-GigabitEthernet1/0/4] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceB-GigabitEthernet1/0/4] undo stp enable

# Configure the port as a trunk port.

[DeviceB-GigabitEthernet1/0/4] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLAN 11.

[DeviceB-GigabitEthernet1/0/4] undo port trunk permit vlan 1 [DeviceB-GigabitEthernet1/0/4] port trunk permit vlan 11

# Configure VLAN 11 as the default VLAN.

[DeviceB-GigabitEthernet1/0/4] port trunk pvid vlan 11 [DeviceB-GigabitEthernet1/0/4] quit

# Create RRPP domain 1.

[DeviceB] rrpp domain 1

# Configure VLAN 100 as the primary control VLAN of RRPP domain 1.

[DeviceB-rrpp-domain1] control-vlan 100

# Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.

[DeviceB-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device B as a transit node of primary ring 1 in RRPP domain 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceB-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceB-rrpp-domain1] ring 1 enable

# Configure Device B as the assistant edge node of subring 3 in RRPP domain 1, with GigabitEthernet 1/0/4 as the edge port. Enable subring 3.

[DeviceB-rrpp-domain1] ring 3 node-mode assistant-edge edge-port gigabitethernet 1/0/4

[DeviceB-rrpp-domain1] ring 3 enable [DeviceB-rrpp-domain1] quit

# Create RRPP domain 2.

[DeviceB] rrpp domain 2

# Configure VLAN 105 as the primary control VLAN of RRPP domain 2.

[DeviceB-rrpp-domain2] control-vlan 105

# Configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2.

[DeviceB-rrpp-domain2] protected-vlan reference-instance 2

# Configure Device B as the transit node of primary ring 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceB-rrpp-domain2] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceB-rrpp-domain2] ring 1 enable

# Configure Device B as the assistant edge node of subring 2 in RRPP domain 2, with GigabitEthernet 1/0/3 as the edge port. Enable subring 2.

[DeviceB-rrpp-domain2] ring 2 node-mode assistant-edge edge-port gigabitethernet 1/0/3

[DeviceB-rrpp-domain2] ring 2 enable

Page 92

[DeviceC-rrpp-domain2] quit

# Enable RRPP.

[DeviceB] rrpp enable

3. Configure Device C:

# Create VLANs 11 and 12.

<DeviceC> system-view [DeviceC] vlan 11 to 12

# Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2.

[DeviceC] stp region-configuration [DeviceC-mst-region] instance 1 vlan 11 [DeviceC-mst-region] instance 2 vlan 12

# Activate the MST region configuration.

[DeviceC-mst-region] active region-configuration [DeviceC-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceC] interface gigabitethernet 1/0/1 [DeviceC-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceC-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceC-GigabitEthernet1/0/1] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLANs 11 and 12.

[DeviceC-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceC-GigabitEthernet1/0/1] port trunk permit vlan 11 12

# Configure VLAN 11 as the default VLAN.

[DeviceC-GigabitEthernet1/0/1] port trunk pvid vlan 11 [DeviceC-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceC] interface gigabitethernet 1/0/2 [DeviceC-GigabitEthernet1/0/2] link-delay 0 [DeviceC-GigabitEthernet1/0/2] undo stp enable [DeviceC-GigabitEthernet1/0/2] port link-type trunk [DeviceC-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceC-GigabitEthernet1/0/2] port trunk permit vlan 11 12 [DeviceC-GigabitEthernet1/0/2] port trunk pvid vlan 11 [DeviceC-GigabitEthernet1/0/2] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/3.

[DeviceC] interface gigabitethernet 1/0/3 [DeviceC-GigabitEthernet1/0/3] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceC-GigabitEthernet1/0/3] undo stp enable

# Configure the port as a trunk port.

[DeviceC-GigabitEthernet1/0/3] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLAN 12.

[DeviceC-GigabitEthernet1/0/3] undo port trunk permit vlan 1

Page 93

[DeviceC-GigabitEthernet1/0/3] port trunk permit vlan 12

# Configure VLAN 12 as the default VLAN.

[DeviceC-GigabitEthernet1/0/3] port trunk pvid vlan 12 [DeviceC-GigabitEthernet1/0/3] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/4.

[DeviceC] interface gigabitethernet 1/0/4 [DeviceC-GigabitEthernet1/0/4] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceC-GigabitEthernet1/0/4] undo stp enable

# Configure the port as a trunk port.

[DeviceC-GigabitEthernet1/0/4] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLAN 11.

[DeviceC-GigabitEthernet1/0/4] undo port trunk permit vlan 1 [DeviceC-GigabitEthernet1/0/4] port trunk permit vlan 11

# Configure VLAN 11 as the default VLAN.

[DeviceC-GigabitEthernet1/0/4] port trunk pvid vlan 11 [DeviceC-GigabitEthernet1/0/4] quit

# Create RRPP domain 1.

[DeviceC] rrpp domain 1

# Configure VLAN 100 as the primary control VLAN of RRPP domain 1.

[DeviceC-rrpp-domain1] control-vlan 100

# Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.

[DeviceC-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device C as the transit node of primary ring 1 in RRPP domain 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceC-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceC-rrpp-domain1] ring 1 enable

# Configure Device C as the edge node of subring 3 in RRPP domain 1, with GigabitEthernet 1/0/4 as the edge port. Enable subring 3.

[DeviceC-rrpp-domain1] ring 3 node-mode edge edge-port gigabitethernet 1/0/4 [DeviceC-rrpp-domain1] ring 3 enable [DeviceC-rrpp-domain1] quit

# Create RRPP domain 2.

[DeviceC] rrpp domain 2

# Configure VLAN 105 as the primary control VLAN of RRPP domain 2.

[DeviceC-rrpp-domain2] control-vlan 105

# Configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2.

[DeviceC-rrpp-domain2] protected-vlan reference-instance 2

# Configure Device C as the transit node of primary ring 1 in RRPP domain 2, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceC-rrpp-domain2] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceC-rrpp-domain2] ring 1 enable

Page 94

# Configure Device C as the edge node of subring 2 in RRPP domain 2, with GigabitEthernet 1/0/3 as the edge port. Enable subring 2.

[DeviceC-rrpp-domain2] ring 2 node-mode edge edge-port gigabitethernet 1/0/3 [DeviceC-rrpp-domain2] ring 2 enable [DeviceC-rrpp-domain2] quit

# Enable RRPP.

[DeviceC] rrpp enable

4. Configure Device D:

# Create VLANs 11 and 12.

<DeviceD> system-view [DeviceD] vlan 11 to 12

# Map VLAN 11 to MSTI 1 and VLAN 12 to MSTI 2.

[DeviceD] stp region-configuration [DeviceD-mst-region] instance 1 vlan 11 [DeviceD-mst-region] instance 2 vlan 12

# Activate the MST region configuration.

[DeviceD-mst-region] active region-configuration [DeviceD-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceD] interface gigabitethernet 1/0/1 [DeviceD-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceD-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceD-GigabitEthernet1/0/1] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLANs 11 and 12.

[DeviceD-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceD-GigabitEthernet1/0/1] port trunk permit vlan 11 12

# Configure VLAN 11 as the default VLAN.

[DeviceD-GigabitEthernet1/0/1] port trunk pvid vlan 11 [DeviceD-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceD] interface gigabitethernet 1/0/2 [DeviceD-GigabitEthernet1/0/2] link-delay 0 [DeviceD-GigabitEthernet1/0/2] undo stp enable [DeviceD-GigabitEthernet1/0/2] port link-type trunk [DeviceD-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceD-GigabitEthernet1/0/2] port trunk permit vlan 11 12 [DeviceD-GigabitEthernet1/0/2] port trunk pvid vlan 11 [DeviceD-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceD] rrpp domain 1

# Configure VLAN 100 as the primary control VLAN of RRPP domain 1.

[DeviceD-rrpp-domain1] control-vlan 100

# Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.

Page 95

[DeviceD-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device D as the transit node of primary ring 1 in RRPP domain 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceD-rrpp-domain1] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceD-rrpp-domain1] ring 1 enable [DeviceD-rrpp-domain1] quit

# Create RRPP domain 2.

[DeviceD] rrpp domain 2

# Configure VLAN 105 as the primary control VLAN of RRPP domain 2.

[DeviceD-rrpp-domain2] control-vlan 105

# Configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2.

[DeviceD-rrpp-domain2] protected-vlan reference-instance 2

# Configure Device D as the transit node of primary ring 1 in RRPP domain 2, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable ring 1.

[DeviceD-rrpp-domain2] ring 1 node-mode transit primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 0

[DeviceD-rrpp-domain2] ring 1 enable [DeviceD-rrpp-domain2] quit

# Enable RRPP.

[DeviceD] rrpp enable

5. Configure Device E:

# Create VLAN 12.

<DeviceE> system-view [DeviceE] vlan 12

# Map VLAN 12 to MSTI 2.

[DeviceE-vlan12] quit [DeviceE] stp region-configuration [DeviceE-mst-region] instance 2 vlan 12

# Activate the MST region configuration.

[DeviceE-mst-region] active region-configuration [DeviceE-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceE] interface gigabitethernet 1/0/1 [DeviceE-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceE-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceE-GigabitEthernet1/0/1] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLAN 12.

[DeviceE-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceE-GigabitEthernet1/0/1] port trunk permit vlan 12

# Configure VLAN 12 as the default VLAN.

[DeviceE-GigabitEthernet1/0/1] port trunk pvid vlan 12 [DeviceE-GigabitEthernet1/0/1] quit

Page 96

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceE] interface gigabitethernet 1/0/2 [DeviceE-GigabitEthernet1/0/2] link-delay 0 [DeviceE-GigabitEthernet1/0/2] undo stp enable [DeviceE-GigabitEthernet1/0/2] port link-type trunk [DeviceE-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceE-GigabitEthernet1/0/2] port trunk permit vlan 12 [DeviceE-GigabitEthernet1/0/2] port trunk pvid vlan 12 [DeviceE-GigabitEthernet1/0/2] quit

# Create RRPP domain 2.

[DeviceE] rrpp domain 2

# Configure VLAN 105 as the primary control VLAN of RRPP domain 2.

[DeviceE-rrpp-domain2] control-vlan 105

# Configure the VLAN mapped to MSTI 2 as the protected VLAN of RRPP domain 2.

[DeviceE-rrpp-domain2] protected-vlan reference-instance 2

# Configure Device E as the master mode of subring 2 in RRPP domain 2, with GigabitEthernet 1/0/2 as the primary port and GigabitEthernet 1/0/1 as the secondary port. Enable ring 2.

[DeviceE-rrpp-domain2] ring 2 node-mode master primary-port gigabitethernet 1/0/2 secondary-port gigabitethernet 1/0/1 level 1

[DeviceE-rrpp-domain2] ring 2 enable [DeviceE-rrpp-domain2] quit

# Enable RRPP.

[DeviceE] rrpp enable

6. Configure Device F:

# Create VLAN 11.

<DeviceF> system-view [DeviceF] vlan 11 [DeviceF-vlan11] quit

# Map VLAN 11 to MSTI 1.

[DeviceF] stp region-configuration [DeviceF-mst-region] instance 1 vlan 11

# Activate the MST region configuration.

[DeviceF-mst-region] active region-configuration [DeviceF-mst-region] quit

# Set the physical state change suppression interval to 0 seconds on GigabitEthernet 1/0/1.

[DeviceF] interface gigabitethernet 1/0/1 [DeviceF-GigabitEthernet1/0/1] link-delay 0

# Disable the spanning tree feature on the port.

[DeviceF-GigabitEthernet1/0/1] undo stp enable

# Configure the port as a trunk port.

[DeviceF-GigabitEthernet1/0/1] port link-type trunk

# Remove the port from VLAN 1, and assign it to VLAN 11.

[DeviceF-GigabitEthernet1/0/1] undo port trunk permit vlan 1 [DeviceF-GigabitEthernet1/0/1] port trunk permit vlan 11

# Configure VLAN 11 as the default VLAN.

Page 97

[DeviceF-GigabitEthernet1/0/1] port trunk pvid vlan 11 [DeviceF-GigabitEthernet1/0/1] quit

# Configure GigabitEthernet 1/0/2 in the same way GigabitEthernet 1/0/1 is configured.

[DeviceF] interface gigabitethernet 1/0/2 [DeviceF-GigabitEthernet1/0/2] link-delay 0 [DeviceF-GigabitEthernet1/0/2] undo stp enable [DeviceF-GigabitEthernet1/0/2] port link-type trunk [DeviceF-GigabitEthernet1/0/2] undo port trunk permit vlan 1 [DeviceF-GigabitEthernet1/0/2] port trunk permit vlan 11 [DeviceF-GigabitEthernet1/0/2] port trunk pvid vlan 11 [DeviceF-GigabitEthernet1/0/2] quit

# Create RRPP domain 1.

[DeviceF] rrpp domain 1

# Configure VLAN 100 as the primary control VLAN of RRPP domain 1.

[DeviceF-rrpp-domain1] control-vlan 100

# Configure the VLAN mapped to MSTI 1 as the protected VLAN of RRPP domain 1.

[DeviceF-rrpp-domain1] protected-vlan reference-instance 1

# Configure Device F as the master node of subring 3 in RRPP domain 1, with GigabitEthernet 1/0/1 as the primary port and GigabitEthernet 1/0/2 as the secondary port. Enable subring 3.

[DeviceF-rrpp-domain1] ring 3 node-mode master primary-port gigabitethernet 1/0/1 secondary-port gigabitethernet 1/0/2 level 1

[DeviceF-rrpp-domain1] ring 3 enable [DeviceF-rrpp-domain1] quit

# Enable RRPP.

[DeviceF] rrpp enable

7. Configure RRPP ring group settings on Device B and Device C:

# Create RRPP ring group 1 on Device B, and add subrings 2 and 3 to the RRPP ring group.

[DeviceB] rrpp ring-group 1 [DeviceB-rrpp-ring-group1] domain 2 ring 2 [DeviceB-rrpp-ring-group1] domain 1 ring 3

# Create RRPP ring group 1 on Device C, and add subrings 2 and 3 to the RRPP ring group.

[DeviceC] rrpp ring-group 1 [DeviceC-rrpp-ring-group1] domain 2 ring 2 [DeviceC-rrpp-ring-group1] domain 1 ring 3

Verifying the configuration

# Use the display commands to view RRPP configuration and operational information on each device.

Troubleshooting RRPP

Symptom

When the link state is normal, the master node cannot receive Hello packets, and it unblocks the secondary port.

Analysis

This symptom is probably caused by the following reasons:

Page 98

Solution

• RRPP is not enabled on some nodes in the RRPP ring.

• The domain ID or primary control VLAN ID is not the same on the nodes in the RRPP ring.

• Some ports are abnormal.

• Use the display rrpp brief command to determine whether RRPP is enabled for all nodes. If it is not,

use the rrpp enable command and the ring enable command to enable RRPP and RRPP rings for all nodes.

• Use the display rrpp brief command to determine whether the domain ID and primary control

VLAN ID are the same for all nodes. If they are not, set the same domain ID and primary control VLAN ID for the nodes.

• Use the display rrpp verbose command to examine the link state of each port in each ring.

• Use the debugging rrpp command on each node to determine whether a port receives or transmits

Hello packets. If it does not, Hello packets are lost.

Page 99

Configuring Smart Link

Overview

To avoid single-point failures and guarantee network reliability, downstream devices are typically dual-homed to upstream devices, as shown in Figure 23.

Figure 23 Dual uplink network diagr

To remove network loops on a dual-homed network, you can use a spanning tree protocol. However, convergence time is long with spanning tree protocols, which makes it unsuitable for users who have high demand on convergence speed.

For more information about spanning tree protocols, see Layer 2—LAN Switching Configuration Guide.

Smart Link is a feature developed to address the slow convergence issue with STP. It provides link redundancy as well as fast convergence in a dual uplink network, allowing the backup link to take over quickly when the primary link fails. Smart Link features subsecond convergence time.

A Smart Link device is configured with a smart link group and a transmit control VLAN to transmit flush messages. For example, Device C and Device D in Figure 23 ar

An associated device supports Smart Link, and receives flush messages sent from the specified control VLAN. For example, Device A, Device B, and Device E in Figure 23 ar

e Smart Link devices.

e associated devices.

Page 100

Terminology

Smart link group

A smart link group consists of only two member ports: the primary and the secondary ports. Only one port is active for forwarding at a time, and the other port is blocked and in standby state. When link failure occurs on the active port due to port shutdown or the presence of unidirectional link, the standby port becomes active and takes over, and the original active port transits to the blocked state.

As shown in Figure 23, P another, with Port 1 being active and Port 2 being standby.

Primary/secondary port

Primary port and secondary port are two port types in a smart link group. When both ports in a smart link group are up, the primary port preferentially transits to the forwarding state, and the secondary port stays in standby state. Once the primary port fails, the secondary port takes over to forward traffic. As shown in Figure 23, y 2 of Device C and that of Device D secondary ports.

Primary/secondary link

The link that connects the primary port in a smart link group is the primary link; the link that connects the secondary port is the secondary link.

Flush message

Flush messages are used by a smart link group to notify other devices to refresh their MAC address forwarding entries and ARP/ND entries when link switchover occurs in the smart link group. Flush messages are common multicast data packets, and will be dropped by a blocked receiving port.

Protected VLAN

A smart link group controls the forwarding state of protected VLANs. Each smart link group on a port controls a different protected VLAN. The state of the port in a protected VLAN is determined by the state of the port in the smart link group.

ort 1 and Port 2 of Device C form a smart link group and those of Device D form

ou can configure Port 1 of Device C and that of Device D as primary ports, and Port

Transmit control VLAN

The transmit control VLAN is used for transmitting flush messages. When link switchover occurs, the devices (such as Device C and Device D in Figure 23) VLAN.

Receive control VLAN

The receive control VLAN is used for receiving and processing flush messages. When link switchover occurs, the devices (such as Device A, Device B, and Device E in Figure 23) r messages in the receive control VLAN and refresh their MAC address forwarding entries and ARP/ND entries.

How Smart Link works

Link backup

As shown in Figure 23, the link on Port 1 of Device C is the primary link. The link on Port 2 of Device C is the secondary link. Typically, Port 1 is in forwarding state, and Port 2 is in standby state. When the primary link fails, Port 2 takes over to forward traffic and Port 1 is blocked and placed in standby state.

send flush messages within the transmit control

eceive and process flush

HP 5130 EI Configuration Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Configuring Ethernet OAM

Overview

Major functions of Ethernet OAM

Ethernet OAMPDUs

How Ethernet OAM works

Ethernet OAM connection establishment

Link monitoring

Remote fault detection

Remote loopback

Protocols and standards

Ethernet OAM configuration task list

Configuring basic Ethernet OAM functions

Configuring the Ethernet OAM connection detection timers

Configuring link monitoring

Configuring errored symbol event detection

Configuring errored frame event detection

Configuring errored frame period event detection

Configuring errored frame seconds event detection

Configuring the action a port takes after it receives an Ethernet OAM event from the remote end

Configuring Ethernet OAM remote loopback

Configuration guidelines

Enabling Ethernet OAM remote loopback on a specific port

Enabling Ethernet OAM remote loopback on the port

Rejecting the Ethernet OAM remote loopback request from a remote port

Displaying and maintaining Ethernet OAM

Ethernet OAM configuration example

Network requirements

Configuration procedure

Configuring CFD

Overview

Basic CFD concepts

Maintenance domain

Maintenance association

Maintenance point

MEP list

CFD functions

Continuity check

Loopback

Linktrace

EAIS

Protocols and standards

CFD configuration task list

Configuring basic CFD settings

Enabling CFD

Configuring service instances

Configuring MEPs

Configuring MIP auto-generation rules

Configuring CFD functions

Configuration prerequisites

Configuring CC on MEPs

Configuring LB on MEPs

Configuring LT on MEPs

Configuring AIS

Configuring LM

Configuring one-way DM

Configuring two-way DM

Configuring TST

Configuring EAIS

Displaying and maintaining CFD

CFD configuration example

Network requirements

Configuration procedure

Verifying the configuration

Configuring DLDP

Overview

Basic concepts

DLDP neighbor states

DLDP port states

DLDP timers

DLDP authentication mode

How DLDP works

Detecting one neighbor

Detecting multiple neighbors

Configuration restrictions and guidelines

DLDP configuration task list