HPE FlexFabric 5700 Series User manual

HPE FlexFabric 5700 Switch Series
High Availability Configuration Guide
Part number: 5998-5593R
Software version: Release 2422P01 and later
Document version: 6W100-20160331

© Copyright 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise 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. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® andAcrobat® are trademarks ofAdobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.

i
Contents
Configuring Ethernet OAM··············································································1
Overview····························································································································································1
Major functions of Ethernet OAM···············································································································1
Ethernet OAMPDUs···································································································································1
How Ethernet OAM works··························································································································1
Protocols and standards ····························································································································3
Ethernet OAM configuration task list··················································································································3
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······················································································6
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 ·····································································································8
Configuration guidelines·····························································································································8
Enabling Ethernet OAM remote loopback on a specific port······································································9
Enabling Ethernet OAM remote loopback on the port················································································9
Rejecting the Ethernet OAM remote loopback request from a remote port···············································9
Displaying and maintaining Ethernet OAM ······································································································10
Ethernet OAM configuration example··············································································································10
Network requirements······························································································································10
Configuration procedure···························································································································10
Configuring CFD···························································································12
Overview··························································································································································12
Basic CFD concepts·································································································································12
CFD functions ··········································································································································14
EAIS·························································································································································16
Protocols and standards ··························································································································16
CFD configuration task list·······························································································································16
Configuring basic CFD settings ·······················································································································17
Enabling CFD···········································································································································17
Configuring service instances··················································································································17
Configuring MEPs····································································································································18
Configuring MIP auto-generation rules ····································································································18
Configuring CFD functions·······························································································································19
Configuration prerequisites······················································································································19
Configuring CC·········································································································································19
Configuring LB ·········································································································································20
Configuring LT··········································································································································20
Configuring AIS········································································································································21
Configuring LM·········································································································································21
Configuring one-way DM··························································································································22
Configuring two-way DM··························································································································22
Configuring TST·······································································································································22
Configuring EAIS ·············································································································································23
Displaying and maintaining CFD······················································································································23
CFD configuration example ·····························································································································24
Configuring DLDP·························································································30
Overview··························································································································································30
Basic concepts·········································································································································31
How DLDP works·····································································································································32
Configuration restrictions and guidelines·········································································································34
DLDP configuration task list·····························································································································34

ii
Enabling DLDP ················································································································································34
Setting the interval to send advertisement packets ·························································································35
Setting the DelayDown timer ···························································································································35
Setting the port shutdown mode ······················································································································35
Configuring DLDP authentication·····················································································································36
Displaying and maintaining DLDP ···················································································································36
DLDP configuration examples ·························································································································37
Automatically shutting down unidirectional links······················································································37
Manually shutting down unidirectional links·····························································································40
Configuring RRPP·························································································44
Overview··························································································································································44
Basic RRPP concepts······························································································································44
RRPPDUs················································································································································46
RRPP timers ············································································································································47
How RRPP works·····································································································································47
Typical RRPP networking ························································································································48
Protocols and standards ··························································································································51
RRPP configuration task list ····························································································································52
Creating an RRPP domain·······························································································································52
Configuring control VLANs·······························································································································52
Configuring protected VLANs ··························································································································53
Configuring RRPP rings···································································································································54
Configuring RRPP ports···························································································································54
Configuring RRPP nodes·························································································································55
Activating an RRPP domain·····························································································································56
Configuring RRPP timers·································································································································57
Configuring an RRPP ring group ·····················································································································57
Displaying and maintaining RRPP···················································································································58
RRPP configuration examples·························································································································58
Single ring configuration example············································································································58
Intersecting ring configuration example ···································································································61
Dual-homed rings configuration example·································································································67
Load-balanced intersecting-ring configuration example···········································································77
Troubleshooting RRPP ····································································································································87
Configuring Smart Link ·················································································89
Overview··························································································································································89
Terminology ·············································································································································90
How Smart Link works ·····························································································································90
Smart Link collaboration mechanisms ·····································································································91
Smart Link configuration task list ·····················································································································92
Configuring a Smart Link device······················································································································92
Configuration prerequisites······················································································································92
Configuring protected VLANs for a smart link group················································································92
Configuring member ports for a smart link group·····················································································93
Configuring a preemption mode for a smart link group············································································94
Enabling the sending of flush messages··································································································94
Configuring collaboration between Smart Link and Track········································································94
Configuring an associated device····················································································································95
Configuration prerequisites······················································································································95
Enabling the receiving of flush messages································································································95
Displaying and maintaining Smart Link············································································································95
Smart Link configuration examples··················································································································96
Single smart link group configuration example ························································································96
Multiple smart link groups load sharing configuration example······························································100
Smart Link and Track collaboration configuration example ···································································104
Configuring Monitor Link·············································································110
Overview························································································································································110
Configuration restrictions and guidelines·······································································································111
Monitor Link configuration task list·················································································································111

iii
Enabling Monitor Link globally ·······················································································································111
Creating a monitor link group·························································································································111
Configuring monitor link group member interfaces ························································································111
In monitor link group view ······················································································································112
In interface view·····································································································································112
Configuring the switchover delay for the downlink interfaces in a monitor link group····································112
Displaying and maintaining Monitor Link ·······································································································113
Monitor Link configuration example ···············································································································113
Configuring VRRP·······················································································117
Overview························································································································································117
VRRP standard mode····································································································································118
Router priority in a VRRP group·············································································································118
Preemption·············································································································································118
Authentication method ···························································································································119
VRRP timers ··········································································································································119
Master election·······································································································································119
VRRP tracking········································································································································120
VRRP application···································································································································120
VRRP load balancing mode···························································································································122
Virtual MAC address assignment···········································································································122
Virtual forwarder·····································································································································123
Protocols and standards ································································································································125
Configuring IPv4 VRRP ·································································································································126
IPv4 VRRP configuration task list ··········································································································126
Specifying an IPv4 VRRP operating mode ····························································································126
Specifying the IPv4 VRRP version·········································································································126
Creating a VRRP group and assigning a virtual IP address ··································································127
Configuring the router priority, preemptive mode, and tracking function················································127
Configuring IPv4 VRRP packet attributes······························································································128
Configuring VF tracking··························································································································129
Enabling SNMP notifications for VRRP··································································································130
Disabling an IPv4 VRRP group··············································································································130
Displaying and maintaining IPv4 VRRP·································································································130
Configuring IPv6 VRRP ·································································································································131
IPv6 VRRP configuration task list ··········································································································131
Specifying an IPv6 VRRP operating mode ····························································································131
Creating a VRRP group and assigning a virtual IPv6 address·······························································132
Configuring the router priority, preemptive mode, and tracking function················································132
Configuring VF tracking··························································································································133
Configuring IPv6 VRRP packet attributes······························································································134
Disabling an IPv6 VRRP group··············································································································135
Displaying and maintaining IPv6 VRRP·································································································135
IPv4 VRRP configuration examples···············································································································135
Single VRRP group configuration example····························································································135
Multiple VRRP groups configuration example························································································138
VRRP load balancing configuration example·························································································141
IPv6 VRRP configuration examples···············································································································149
Single VRRP group configuration example····························································································149
Multiple VRRP groups configuration example························································································151
VRRP load balancing configuration example·························································································155
Troubleshooting VRRP ··································································································································163
An error prompt is displayed··················································································································163
Multiple masters appear in a VRRP group·····························································································163
Fast VRRP state flapping·······················································································································164
Configuring BFD ·························································································165
Overview························································································································································165
BFD session establishment····················································································································165
BFD session modes and operating modes····························································································166
Supported features·································································································································166
Protocols and standards ························································································································167

iv
Configuring BFD basic functions····················································································································167
Configuring echo packet mode ··············································································································167
Configuring control packet mode ···········································································································168
Configuring a BFD template···················································································································169
Displaying and maintaining BFD····················································································································169
Configuring Track························································································171
Overview························································································································································171
Collaboration fundamentals ···················································································································171
Collaboration application example·········································································································172
Track configuration task list ···························································································································172
Associating the Track module with a detection module·················································································173
Associating Track with NQA···················································································································173
Associating Track with BFD···················································································································173
Associating Track with CFD···················································································································174
Associating Track with interface management·······················································································174
Associating the Track module with an application module ············································································175
Associating Track with VRRP ················································································································175
Associating Track with static routing······································································································176
Associating Track with Smart Link·········································································································177
Displaying and maintaining track entries ·······································································································177
Track configuration examples························································································································178
VRRP-Track-NQA collaboration configuration example ········································································178
Configuring BFD for a VRRP backup to monitor the master··································································181
Configuring BFD for the VRRP master to monitor the uplinks·······························································184
Static routing-Track-NQA collaboration configuration example ·····························································188
Static routing-Track-BFD collaboration configuration example······························································192
VRRP-Track-interface management collaboration configuration example ············································195
Smart Link-Track-CFD collaboration configuration example··································································198
Configuring process placement ··································································199
Overview························································································································································199
Process··················································································································································199
1:N process redundancy························································································································199
Process placement policy and optimization···························································································199
Configuration restrictions and guidelines·······································································································200
Process placement configuration task list······································································································200
Configuring process placement policy ···········································································································201
Configuring a location affinity·················································································································201
Configuring a location type affinity·········································································································201
Configuring a process affinity·················································································································202
Configuring a self affinity························································································································202
Optimizing process placement·······················································································································202
Displaying process placement ·······················································································································203
Document conventions and icons·······························································204
Conventions···················································································································································204
Network topology icons··································································································································205
Support and other resources ······································································206
Accessing Hewlett Packard Enterprise Support ····························································································206
Accessing updates·········································································································································206
Websites ················································································································································207
Customer self repair·······························································································································207
Remote support······································································································································207
Documentation feedback ·······················································································································207
Index···········································································································209

1
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 different types of OAMPDUs
OAMPDU type Function
Information OAMPDU
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.
Event Notification
OAMPDU Used by link monitoring to notify the remote OAM entity when it detects problems on the link in between.
Loopback Control
OAMPDU
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.
NOTE:
Throughout this document, an Ethernet OAM-enabled port is called an Ethernet OAM entity or an
OAM entity.
How Ethernet OAM works
This section describes the working procedures of Ethernet OAM.

2
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 shows 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 Passive Ethernet OAM
mode
Initiating OAM Discovery Available Unavailable
Responding to OAM Discovery Available Available
Transmitting Information
OAMPDUs Available Available
Transmitting Event Notification
OAMPDUs Available Available
Transmitting Information
OAMPDUs without any TLV Available Available
Transmitting Loopback Control
OAMPDUs Available Unavailable
Responding to Loopback Control
OAMPDUs Available when both sides are operating in active 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 OAM 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 Description
Errored symbol event 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.
Errored frame event An errored frame event occurs when the number of detected error frames in the detection window (specified detection interval) exceeds the
predefined threshold.

3
Ethernet OAM link events Description
Errored frame period event 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.
Errored frame seconds event
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.
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. You can use the log information to track
ongoing link status and troubleshoot problems promptly.
Table 4 Critical link events
Type Description OAMPDU transmission
frequencies
Link Fault Peer link signal is lost. Once per second.
Dying Gasp An unexpected fault, such as power failure,
occurred. Non-stop.
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.
Protocols and standards
IEEE 802.3ah, Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method
and Physical Layer Specifications
Ethernet OAM configuration task list
Tasks at a glance
(Required.) Configuring basic Ethernet OAM functions

4
Tasks at a glance
(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 Remarks
1. Enter system view. System-view N/A
2. Enter Layer 2/Layer 3
Ethernet port view. interface interface-type
interface-number N/A
3. Set the Ethernet OAM mode. oam mode { active | passive } The default is active Ethernet
OAM mode.
4. Enable Ethernet OAM. oam enable 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 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 can configure this command in system view or port view. The configuration in system view takes
effect 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.

5
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.As a best practice
to keep the Ethernet OAM connections stable, set the connection timeout timer to be a minimum of
five times the handshake packet transmission interval.
To configure the Ethernet OAM connection detection timers globally:
Step Command Remarks
5. Enter system view. System-view N/A
6. Configure the Ethernet OAM
handshake packet
transmission interval. oam global timer hello interval The default is 1000 milliseconds.
7. Configure the Ethernet OAM
connection timeout timer. oam global timer keepalive
interval The default is 5000 milliseconds.
To configure the Ethernet OAM connection detection timers on a port:
Step Command Remarks
1. Enter system view. System-view N/A
2. Enter Layer 2/Layer 3
Ethernet port view. interface interface-type
interface-number N/A
3. Configure the Ethernet OAM
handshake packet
transmission interval. oam timer hello interval By default, an interface uses the
value configured globally.
4. Configure the Ethernet OAM
connection timeout timer. oam timer keepalive interval 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.
You can configure this command in system view or port view. The configuration in system view takes
effect 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.
To configure errored symbol event detection globally:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the errored symbol
event detection window.
oam global
errored-symbol-period window
window-value
By default, the errored symbol
event detection window is
100000000.
3. Configure the errored symbol
event triggering threshold.
oam global
errored-symbol-period
threshold threshold-value
By default, the errored symbol
event triggering threshold is 1.

6
To configure errored symbol event detection on a port:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3
Ethernet port view. interface interface-type
interface-number N/A
3. Configure the errored symbol
event detection window. oam errored-symbol-period
window window-value By default, an interface uses the
value configured globally.
4. Configure the errored symbol
event triggering threshold. oam errored-symbol-period
threshold threshold-value 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.
You can configure this command in system view or port view. The configuration in system view takes
effect 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.
To configure errored frame event detection globally:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the errored frame
event detection window. oam global errored-frame
window window-value
By default, the errored frame
event detection window is 1000
milliseconds.
3. Configure the errored frame
event triggering threshold. oam global errored-frame
threshold threshold-value By default, the errored frame
event triggering threshold is 1.
To configure errored frame event detection on a port:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3
Ethernet port view. interface interface-type
interface-number N/A
3. Configure the errored frame
event detection window. oam errored-frame window
window-value 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.
You can configure this command in system view or port view. The configuration in system view takes
effect 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.
To configure errored frame period event detection globally:

7
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the errored frame
period event detection
window.
oam global
errored-frame-period window
window-value
By default, the errored frame
period event detection window is
10000000.
3. Configure the errored frame
period event triggering
threshold.
oam global
errored-frame-period threshold
threshold-value
By default, the errored frame
period event triggering threshold
is 1.
To configure errored frame period event detection on a port:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3
Ethernet port view. interface interface-type
interface-number N/A
3. Configure the errored frame
period event detection
window.
oam errored-frame-period
window window-value By default, an interface uses the
value configured globally.
4. Configure the errored frame
period event triggering
threshold.
oam errored-frame-period
threshold threshold-value By default, an interface uses the
value configured globally.
Configuring errored frame seconds event detection
CAUTION:
Make sure the errored frame seconds triggering threshold is less than the errored frame seconds
detection window. Otherwise, no errored frame seconds event can be generated.
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.
You can configure this command in system view or port view. The configuration in system view takes
effect 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.
To configure errored frame seconds event detection globally:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the errored frame
seconds event detection
window.
oam global
errored-frame-seconds window
window-value
By default, the errored frame
seconds event detection window
is 60000 milliseconds.
3. Configure the errored frame
seconds event triggering
threshold.
oam global
errored-frame-seconds
threshold threshold-value
By default, the errored frame
seconds event triggering
threshold is 1.
To configure errored frame seconds event detection on a port:
Step Command Remarks
1. Enter system view. system-view N/A

8
Step Command Remarks
2. Enter Layer 2/Layer 3
Ethernet port view. interface interface-type
interface-number N/A
3. Configure the errored frame
seconds event detection
window.
oam errored-frame-seconds
window window-value By default, an interface uses the
value configured globally.
4. Configure the errored frame
seconds event triggering
threshold.
oam errored-frame-seconds
threshold threshold-value 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 Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3
Ethernet port view. interface interface-type
interface-number N/A
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
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 ona 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.

9
•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 Remarks
1. (Optional.) Enter system
view. system-view N/A
2. Enable Ethernet OAM
remote loopback on a
specific port.
oam remote-loopback start
interface interface-type
interface-number
By default, Ethernet OAM remote
loopback is disabled.
This command can be executed
in user view or system view.
Enabling Ethernet OAM remote loopback on the port
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3
Ethernet port view. interface interface-type
interface-number N/A
3. Enable Ethernet OAM
remote loopback on the port. oam remote-loopback start 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 Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer3
Ethernet port view. interface interface-type
interface-number N/A
3. Reject the Ethernet OAM
remote loopback request
from a remote port. oam remote-loopback
reject-request
By default, a port does not reject
the Ethernet OAM remote
loopback request from a remote
port.
This setting does not affect the
loopback test that has been
performed on the port. It takes

10
Step Command Remarks
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 oam { local | remote } [ interface
interface-type interface-number ]
Display Ethernet OAM configuration. display oam configuration [ interface
interface-type interface-number ]
Display the statistics on critical events after an
Ethernet OAM connection is established. display oam critical-event [ interface
interface-type interface-number ]
Display the statistics on Ethernet OAM link error
events after an Ethernet OAM connection is
established.
display oam link-event { local |remote }
[ interface interface-type interface-number ]
Clear statistics on Ethernet OAM packets and
Ethernet OAM link error events. 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 DeviceA
Figure 1 Network diagram
Configuration procedure
1. Configure Device A:
# Configure Ten-GigabitEthernet 1/0/1 to operate in active Ethernet OAM mode, and enable
Ethernet OAM for it.
<DeviceA> system-view
[DeviceA] interface ten-gigabitethernet 1/0/1
[DeviceA-Ten-GigabitEthernet1/0/1] oam mode active
[DeviceA-Ten-GigabitEthernet1/0/1] oam enable

11
# 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-Ten-GigabitEthernet1/0/1] quit
2. Configure Device B:
# Configure Ten-GigabitEthernet 1/0/1 to operate in passive Ethernet OAM mode (the default),
and enable Ethernet OAM for it.
<DeviceB> system-view
[DeviceB] interface ten-gigabitethernet 1/0/1
[DeviceB-Ten-GigabitEthernet1/0/1] oam mode passive
[DeviceB-Ten-GigabitEthernet1/0/1] oam enable
[DeviceB-Ten-GigabitEthernet1/0/1] quit
3. Verify the configuration:
Use the display oam critical-event command to display the statistics for Ethernet OAM critical
link events. For example:
# Display the statistics for Ethernet OAM critical link events on all the ports of Device A.
[DeviceA] display oam critical-event
-----------[Ten-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 for Ethernet OAM link
events. For example:
# Display Ethernet OAM link event statistics for the local end of Device A.
[DeviceA] display oam link-event local
------------ [Ten-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.

12
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
Amaintenance 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
in 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 DeviceAthrough 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.
An MA serves the specified VLAN or no VLAN. An MA that serves a VLAN is considered to be
carrying VLAN attribute. An MAthat serves no VLAN is considered to be carrying no VLAN attribute.
An MP canreceive packets sent by other MPs in thesame MA. The level of an MAequals the level of
the MD that the MA belongs to.

13
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. AMEP 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 the following 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 MIP, the system will check the MAs in each MD (from low to high levels), and
follow the procedure as described in Figure 3 to create or not to create MIPs at the current level.
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

14
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.
Figure 4 CFD grading example
MEP list
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.
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. ACCM 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.