HPE 3100 v2 Series User manual

HPE 3100 v2 Switch Series
High Availability
Configuration Guide
Part number: 5998-5997s
Software version: Release 5213 and Release 5213P02
Document version: 6W101-20160506

© 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
High availability overview················································································1
Availability requirements····································································································································1
Availability evaluation·········································································································································1
High availability technologies·····························································································································2
Fault detection technologies ······················································································································2
Protection switchover technologies············································································································2
Configuring Ethernet OAM··············································································4
Ethernet OAM overview·····································································································································4
Major functions of Ethernet OAM···············································································································4
Ethernet OAMPDUs···································································································································4
How Ethernet OAM works··························································································································5
Standards and protocols····························································································································7
Ethernet OAM configuration task list··················································································································7
Configuring basic Ethernet OAM functions········································································································8
Configuring the Ethernet OAM connection detection timers··············································································8
Configuring link monitoring ································································································································9
Configuring errored symbol event detection ······························································································9
Configuring errored frame event detection·································································································9
Configuring errored frame period event detection······················································································9
Configuring errored frame seconds event detection··················································································9
Configuring Ethernet OAM remote loopback ···································································································10
Enabling Ethernet OAM remote loopback································································································10
Rejecting the Ethernet OAM remote loopback request from a remote port·············································11
Displaying and maintaining Ethernet OAM configuration·················································································11
Ethernet OAM configuration example··············································································································12
Configuring CFD (available only on the HPE 3100 v2 EI)·····························15
Overview··························································································································································15
Basic CFD concepts·································································································································15
CFD functions ··········································································································································17
Protocols and standards ··························································································································18
CFD configuration task list·······························································································································19
Configuring basic CFD settings ·······················································································································19
Enabling CFD···········································································································································20
Configuring the CFD protocol version······································································································20
Configuring service instances··················································································································20
Configuring MEPs····································································································································21
Configuring MIP generation rules·············································································································21
Configuring CFD functions·······························································································································22
Configuration prerequisites······················································································································22
Configuring CC on MEPs·························································································································22
Configuring LB on MEPs··························································································································23
Configuring LT on MEPs··························································································································23
Configuring AIS········································································································································24
Configuring LM·········································································································································24
Configuring one-way DM··························································································································24
Configuring two-way DM··························································································································25
Configuring TST·······································································································································25
Displaying and maintaining CFD······················································································································26
CFD configuration example ·····························································································································27
Configuring DLDP·························································································33
DLDP overview ················································································································································33
Background··············································································································································33
How DLDP works·····································································································································34
DLDP configuration task list·····························································································································40

ii
Configuring the duplex mode and speed of an Ethernet interface···································································40
Enabling DLDP ················································································································································40
Setting DLDP mode ·········································································································································41
Setting the interval to send advertisement packets ·························································································41
Setting the delaydown timer·····························································································································42
Setting the port shutdown mode ······················································································································42
Configuring DLDP authentication·····················································································································43
Resetting DLDP state ······································································································································43
Displaying and maintaining DLDP ···················································································································44
DLDP configuration examples ·························································································································44
Automatically shutting down unidirectional links······················································································44
Manually shutting down unidirectional links·····························································································48
Troubleshooting DLDP·····································································································································51
Configuring RRPP·························································································52
RRPP overview················································································································································52
Background··············································································································································52
Basic concepts in RRPP··························································································································52
RRPPDUS················································································································································54
RRPP timers ············································································································································55
How RRPP works·····································································································································55
Typical RRPP networking ························································································································56
Protocols and standards ··························································································································59
RRPP configuration task list ····························································································································60
Creating an RRPP domain·······························································································································60
Configuring control VLANs·······························································································································61
Configuration guidelines···························································································································61
Configuration procedure···························································································································61
Configuring protected VLANs ··························································································································61
Configuring RRPP rings···································································································································62
Configuring RRPP ports···························································································································63
Configuring RRPP nodes·························································································································63
Activating an RRPP domain·····························································································································64
Configuring an RRPP ring group ·····················································································································65
Configuration restrictions and guidelines·································································································65
Configuration procedure···························································································································65
Displaying and maintaining RRPP···················································································································66
RRPP configuration examples·························································································································66
Single ring configuration example············································································································66
Intersecting ring configuration example ···································································································69
Dual homed rings configuration example·································································································74
Intersecting-ring load balancing configuration example···········································································83
Troubleshooting ···············································································································································91
Configuring Smart Link (available only on the HPE 3100 v2 EI)···················93
Smart Link overview·········································································································································93
Background··············································································································································93
Terminology ·············································································································································94
How Smart Link works ·····························································································································94
Smart Link collaboration mechanisms ·····································································································95
Smart Link configuration task list ·····················································································································95
Configuring a Smart Link device······················································································································96
Configuration prerequisites······················································································································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
Configuring an associated device····················································································································99
Configuration prerequisites······················································································································99
Enabling the receiving of flush messages································································································99
Displaying and maintaining Smart Link············································································································99
Smart Link configuration examples················································································································100

iii
Single smart link group configuration example ······················································································100
Multiple smart link groups load sharing configuration example······························································104
Configuring Monitor Link (available only on the HPE 3100 v2 EI) ··············109
Monitor Link overview ····································································································································109
Terminology ···········································································································································109
How Monitor Link works·························································································································110
Configuring Monitor Link································································································································110
Configuration prerequisites····················································································································110
Creating a monitor link group·················································································································110
Configuring monitor link group member ports························································································110
Displaying and maintaining Monitor Link ·······································································································111
Monitor Link configuration example ···············································································································111
Document conventions and icons·······························································115
Conventions···················································································································································115
Network topology icons··································································································································116
Support and other resources ······································································117
Accessing Hewlett Packard Enterprise Support ····························································································117
Accessing updates·········································································································································117
Websites ················································································································································118
Customer self repair·······························································································································118
Remote support······································································································································118
Documentation feedback ·······················································································································118
Index···········································································································120

1
High availability overview
Communication interruptions can seriously affect widely-deployed value-added services such as
IPTV and video conference. Therefore, the basic network infrastructures must be able to provide
high availability.
The following are the effective ways to improve availability:
•Increasing fault tolerance
•Speeding up fault recovery
•Reducing impact of faults on services
Availability requirements
Availability requirements fall into three levels based on purpose and implementation.
Table 1 Availability requirements
Level Requirement Solution
1 Decrease system software and
hardware faults
•Hardware—Simplifying circuit design, enhancing
production techniques, and performing reliability
tests.
•Software—Reliability design and test
2 Protect system functions from being
affected if faults occur Device and link redundancy and deployment of switchover strategies
3 Enable the system to recover as fast
as possible Performing fault detection, diagnosis, isolation, and recovery technologies
The level 1 availability requirement should be considered during the design and production process
of network devices. Level 2 should be considered during network design. Level 3 should be
considered during network deployment, according to the network infrastructure and service
characteristics.
Availability evaluation
Mean Time Between Failures (MTBF) and Mean Time to Repair (MTTR) are used to evaluate the
availability of a network.
MTBF
MTBF is the predicted elapsed time between inherent failures of a system during operation. It is
typically in the unit of hours. A higher MTBF means a high availability.
MTTR
MTTR is the average time required to repair a failed system. MTTR in a broad sense also involves
spare parts management and customer services.
MTTR = fault detection time + hardware replacement time + system initialization time + link recovery
time + routing time + forwarding recovery time.Asmaller value of each item means a smaller MTTR
and a higher availability.

2
High availability technologies
Increasing MTBF or decreasing MTTR can enhance the availability of a network. The high
availability technologies described in this section meet the level 2 and level 3 high availability
requirements by decreasing MTTR.
High availability technologies can be classified as fault detection technologies or protection
switchover technologies.
Fault detection technologies
Fault detection technologies enable detection and diagnosis of network faults. CFD, DLDP, and
Ethernet OAM are data link layer fault detection technologies. NQA is used for diagnosis and
evaluation of network quality. Monitor Link works along with other high availability technologies to
detect faults through a collaboration mechanism.
Table 2 Fault detection technologies
Technology Introduction Reference
CFD (available only
on the HPE 3100
v2 EI)
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 Operations,
Administration and Maintenance (OAM) mechanism used for
link connectivity detection, fault verification, and fault
location.
"Configuring CFD" in
High Availability
Configuration Guide
DLDP
The Device link detection protocol (DLDP) deals with
unidirectional links that may occur in a network. Upon
detecting a unidirectional link, DLDP, as configured, can
shut down the related port automatically or prompt users to
take actions to avoid network problems.
"Configuring DLDP"
in High Availability
Configuration Guide
Ethernet OAM
As a tool monitoring Layer 2 link status, Ethernet OAM is
mainly used to address common link-related issues on the
"last mile". You can monitor the status of the point-to-point
link between two directly connected devices by enabling
Ethernet OAM on them.
"Configuring Ethernet
OAM" in High
Availability
Configuration Guide
NQA
Network Quality Analyzer (NQA) analyzes network
performance, services and service quality through sending
test packets, and provides you with network performance
and service quality parameters such as jitter, TCP
connection delay, FTP connection delay and file transfer
rate.
"Configuring NQA" in
Network
Management and
Monitoring
Configuration Guide
Monitor Link
(available only on
the HPE 3100 v2
EI)
Monitor Link works together with Layer 2 topology protocols
to adapt the up/down state of a downlink port to the state of
an uplink port. This feature enables fast link switchover on a
downstream device in response to the uplink state change
on its upstream device.
"Configuring Monitor
Link" in High
Availability
Configuration Guide
Protection switchover technologies
Protection switchover technologies aim at recovering network faults. They back up hardware, link,
routing, and service information for switchover in case of network faults, to ensure continuity of
network services.

3
Table 3 Protection switchover technologies
Technology Introduction Reference
Ethernet Link
Aggregation
Ethernet link aggregation, most often simply called link
aggregation, aggregates multiple physical Ethernet links into
one logical link to increase link bandwidth beyond the limits
of any one single link. This logical link is an aggregate link. It
allows for link redundancy because the member physical
links can dynamically back up one another.
"Configuring Ethernet
ink aggregation" in
Layer 2
— LAN
Switching
Configuration Guide
Smart Link
(available only on
the HPE 3100 v2
EI)
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.
"Configuring Smart
Link" in High
Availability
Configuration Guide
MSTP
As a Layer 2 management protocol, the Multiple Spanning
Tree Protocol (MSTP) eliminates Layer 2 loops by
selectively blocking redundant links in a network, and in the
mean time, allows for link redundancy.
"Configuring
spanning tree" in
Layer 2—LAN
Switching
Configuration Guide
RRPP
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, and rapidly restore the communication paths
between the nodes in the event that a link is disconnected on
the ring.
"Configuring RRPP"
in High Availability
Configuration Guide
A single availability technology cannot solve all problems. Therefore, a combination of availability
technologies, chosen on the basis of detailed analysis of network environments and user
requirements, should be used to enhance network availability. For example, access-layer devices
should be connected to distribution-layer devices over redundant links, and core-layer devices
should be fully meshed. Also, network availability should be considered during planning prior to
building a network.

4
Configuring Ethernet OAM
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." 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 works 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 fall into the following types: Information, Event Notification, and Loopback
Control.
Figure 1 Formats of different types of Ethernet OAMPDUs
Table 4 Fields in an OAMPDU
Field Description
Dest addr Destination MAC address of the Ethernet OAMPDU
It is a slow protocol multicast address, 0180c2000002. Bridges cannot forward
slow protocol packets, so Ethernet OAMPDUs cannot be forwarded.
Source addr Source MAC address of the Ethernet OAMPDU
It is the bridge MAC address of the sending side and is a unicast MAC address.
Type Type of the encapsulated protocol in the Ethernet OAMPDU
The value is 0x8809.

5
Field Description
Subtype The specific protocol being encapsulated in the Ethernet OAMPDU
The value is 0x03.
Flags Status information of an Ethernet OAM entity
Code Type of the Ethernet OAMPDU
NOTE:
Throughout this document, a port with Ethernet OAM enabled is an Ethernet OAM entity or an OAM
entity.
Table 5 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.
How Ethernet OAM works
This section describes the working procedures of Ethernet OAM.
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
remote OAM entities and establishes sessions with them.
In this phase, interconnected OAM entities determine whether Ethernet OAM connections can be
established, by exchanging Information OAMPDUs to notify the peer of their OAM configuration
information and the OAM capabilities of the local nodes. An Ethernet OAM connection can be
established between entities that have matching Loopback, link detecting, and link event settings.
After an Ethernet OAM connection is established, Ethernet OAM takes effect on both sides.
For Ethernet OAM connection establishment, a device can operate in active Ethernet OAM mode or
passive Ethernet OAM mode, but a switch role will be somewhat different depending on the mode.
Table 6 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

6
Item Active Ethernet OAM mode Passive Ethernet OAM
mode
Transmitting Information
OAMPDUs without any TLV Available Available
Transmitting Loopback Control
OAMPDUs Available Unavailable
Responding to Loopback Control
OAMPDUs Available—if both sides operate in active OAM mode Available
NOTE:
•Only OAM entities operating in active OAM mode can initiate OAM connections. OAM entities
operating in passive mode wait and respond to the connection requests sent by their peers.
•No OAM connection can be established between OAM entities operating in passive OAM mode.
After an Ethernet OAM connection is established,the Ethernet OAM entities onboth sides exchange
Information OAMPDUs at the handshake packet transmission interval to check whether the Ethernet
OAM connection is normal. 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 is used to detect
and indicate link faults in various environments. Ethernet OAM implements link monitoring through
the exchange of Event Notification OAMPDUs. When detecting one of the link error events listed
in Table 7, the local OAM entity sends an Event Notification OAMPDU to notify the remote OAM
entity. With the log information, network administrators can keep track of network status promptly.
Table 7 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 during a specified detection interval exceeds the
predefined threshold.
Errored frame event An errored frame event occurs when the number of detected error frames during a specified interval exceeds the predefined
threshold.
Errored frame period event An errored frame period event occurs if the number of frame errors
in a specific number of received frames exceeds the predefined
threshold.
Errored frame seconds event An errored frame seconds event occurs when the number of error frame seconds detected on a port during a specified detection
interval reaches the error threshold.
The system transforms the period of detecting errored frame period events into the maximum
number of 64-byte frames (excluding the interframe spacing and preamble) that a port can send in
the specified period. The system takes the maximum number of frames sent as the period. The
maximum number of frames sent is calculated using this formula: the maximum number of frames =
interface bandwidth (bps) × errored frame period event detection period (in ms)/(64 × 8 × 1000).
A second in which errored frames appear is called an "errored frame second."
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

7
information—the critical link event type—to its peer. You can use the log information to track ongoing
link status and troubleshoot problems promptly.
Table 8 Critical link events
Type Description OAMPDU transmission
frequencies
Link Fault Peer link signal is lost. Once per second
Dying Gasp A power failure or other unexpected error
occurred. Non-stop
Critical Event An undetermined critical event occurred. Non-stop
This Switch Series is able to receive information OAMPDUs carrying the critical link events listed
in Table 8.
Only the Gigabit fiber ports are able to send information OAMPDUs carrying Link Fault events.
This Switch Series is able to send information OAMPDUs carrying Dying Gasp events when the
device is rebooted or relevant ports are manually shut down.
This Switch Series 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 operating in active Ethernet OAM 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.
Standards and protocols
Ethernet OAM is defined in IEEE 802.3ah (Carrier Sense Multiple Access with Collision Detection
(CSMA/CD) Access Method and Physical Layer Specifications.
Ethernet OAM configuration task list
Task Remarks
Configuring basic Ethernet OAM functions Required
Configuring the Ethernet OAM connection detection timers Optional
Configuring link
monitoring
Configuring errored symbol event detection Optional
Configuring errored frame event detection Optional
Configuring errored frame period event detection Optional
Configuring errored frame seconds event
detection Optional
Configuring
Ethernet OAM
remote loopback
Enabling Ethernet OAM remote loopback Optional
Rejecting the Ethernet OAM remote loopback
request from a remote port Optional

8
Configuring basic Ethernet OAM functions
For Ethernet OAM connection establishment, an Ethernet OAM entity operates in active mode or
passive mode. Only an Ethernet OAM entity in active mode can initiate connection establishment.
After Ethernet OAM is enabled on an Ethernet port, according to its Ethernet OAM mode, the
Ethernet port establishes an Ethernet OAM connection with its peer port.
To change the Ethernet OAM mode on an Ethernet OAM-enabled port, you must 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 Ethernet
interface view. interface interface-type
interface-number N/A
3. Set the Ethernet OAM mode. oam mode { active | passive } Optional.
The default is active Ethernet
OAM mode.
4. Enable Ethernet OAM on the
current port. 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 onboth sides exchange
Information OAMPDUs at the handshake packet transmission interval to check whether the Ethernet
OAM connection is normal. 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.
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 be disconnected. Hewlett
Packard Enterprise recommends that you set the connection timeout timer to at least five times the
handshake packet transmission interval, ensuring the stability of Ethernet OAM connections.
To configure the Ethernet OAM connection detection timers:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the Ethernet OAM
handshake packet
transmission interval. oam timer hello interval Optional.
1000 millisecond by default.
3. Configure the Ethernet OAM
connection timeout timer. oam timer keepalive interval Optional.
5000 milliseconds by default.

9
Configuring link monitoring
After Ethernet OAM connections are established, the link monitoring periods and thresholds
configured in this section take effect on all Ethernet ports automatically.
Configuring errored symbol event detection
Step Command Remarks
4. Enter system view. system-view N/A
5. Configure the errored
symbol event
detection interval.
oam errored-symbol period
period-value
Optional.
1 second by default.
6. Configure the errored
symbol event
triggering threshold.
oam errored-symbol threshold
threshold-value
Optional.
1 by default.
Configuring errored frame event detection
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the errored frame
event detection interval. oam errored-frame period
period-value
Optional.
1 second by default.
3. Configure the errored frame
event triggering threshold. oam errored-frame threshold
threshold-value
Optional.
1 by default.
Configuring errored frame period event detection
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the errored
frame period event
detection period.
oam errored-frame-period period
period-value
Optional.
1000 milliseconds by default.
3. Configure the errored
frame period event
triggering threshold.
oam errored-frame-period threshold
threshold-value
Optional.
1 by default.
Configuring errored frame seconds event detection
IMPORTANT:
Make sure the errored frame seconds triggering threshold is less than the errored frame seconds
detection interval. Otherwise, no errored frame seconds event can be generated.

10
To configure errored frame seconds event detection:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the errored frame
seconds event detection
interval.
oam errored-frame-seconds
period period-value
Optional.
60 second by default.
3. Configure the errored frame
seconds event triggering
threshold.
oam errored-frame-seconds
threshold threshold-value
Optional.
1 by default.
Configuring Ethernet OAM remote loopback
Enabling 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 to evaluate the link performance.
You can enable Ethernet OAM remote loopback ona specific port in user view, system view, or Layer
2 Ethernet interface 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 actions: executing the undo
oam enable command to disable Ethernet OAM; executing the undo oam loopback interface
or undo oam loopback command to disable Ethernet OAM remote loopback; and Ethernet
OAM connection timing out.
•Ethernet OAM remote loopback is only applicable to individual links. It is not applicable to link
aggregation member ports. In addition, do not assign ports where Ethernet OAM remote
loopback is being performed to link aggregation groups. For more information about link
aggregation groups, see Layer 2—LAN Switching Configuration Guide.
•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.
Configuration procedure
To enable Ethernet OAM remote loopback in user view:

11
Task Command Remarks
Enable Ethernet OAM remote
loopback on a specific port. oam loopback interface
interface-type interface-number Disabled by default.
To enable Ethernet OAM remote loopback in system view:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable Ethernet OAM
remote loopback on a
specific port. oam loopback interface
interface-type interface-number Disabled by default.
To enable Ethernet OAM remote loopback in Layer 2 Ethernet interface view:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2 Ethernet
interface view. interface interface-type
interface-number N/A
3. Enable Ethernet OAM
remote loopback on the port. oam loopback Disabled by default.
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 Ethernet
interface view. interface interface-type
interface-number N/A
3. Reject the Ethernet OAM
remote loopback request
from a remote port. oam loopback reject-request
By default, a port does not reject
the Ethernet OAM remote
loopback request from a remote
port.
Displaying and maintaining Ethernet OAM
configuration
Task Command Remarks
Display global Ethernet OAM
configuration.
display oam configuration [ |
{ begin | exclude | include }
regular-expression ] Available in any view

12
Task Command Remarks
Display the statistics on critical
events after an Ethernet OAM
connection is established.
display oam critical-event
[interface interface-type
interface-number ] [ |{ begin |
exclude | include }
regular-expression ]
Available in any view
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 ]
[ |{ begin | exclude | include }
regular-expression ]
Available in any view
Display the information about an
Ethernet OAM connection.
display oam {local | remote }
[interface interface-type
interface-number ] [ |{ begin |
exclude | include }
regular-expression ]
Available in any view
Clear statistics on Ethernet OAM
packets and Ethernet OAM link
error events.
reset oam [interface
interface-type interface-number ]Available in user view
Ethernet OAM configuration example
Network requirements
On the network shown in Figure 2, perform the following operations:
•Enable Ethernet OAM on Device A and Device B to auto-detect link errors between the two
devices
•Monitor the performance of the link between DeviceAand Device B by collecting statistics
about the error frames received by DeviceA
Figure 2 Network diagram
Configuration procedure
1. Configure Device A:
# Configure Ethernet 1/0/1 to operate in passive Ethernet OAM mode and enable Ethernet
OAM for it.
<DeviceA> system-view
[DeviceA] interface ethernet 1/0/1
[DeviceA-Ethernet1/0/1] oam mode passive
[DeviceA-Ethernet1/0/1] oam enable
[DeviceA-Ethernet1/0/1] quit
# Set the errored frame detection interval to 20 seconds and set the errored frame event
triggering threshold to 10.
[DeviceA] oam errored-frame period 20
[DeviceA] oam errored-frame threshold 10
2. Configure Device B:

13
# Configure Ethernet 1/0/1 to operate in active Ethernet OAM mode (the default) and enable
Ethernet OAM for it.
<DeviceB> system-view
[DeviceB] interface ethernet 1/0/1
[DeviceA-Ethernet1/0/1] oam mode active
[DeviceB-Ethernet1/0/1] oam enable
[DeviceB-Ethernet1/0/1] quit
3. Verify the configuration:
Use the display oam configuration command to display the Ethernet OAM configuration. For
example:
# Display the Ethernet OAM configuration on Device A.
[DeviceA] display oam configuration
Configuration of the link event window/threshold :
--------------------------------------------------------------------------
Errored-symbol Event period(in seconds) : 1
Errored-symbol Event threshold : 1
Errored-frame Event period(in seconds) : 20
Errored-frame Event threshold : 10
Errored-frame-period Event period(in ms) : 1000
Errored-frame-period Event threshold : 1
Errored-frame-seconds Event period(in seconds) : 60
Errored-frame-seconds Event threshold : 1
Configuration of the timer :
--------------------------------------------------------------------------
Hello timer(in ms) : 1000
Keepalive timer(in ms) : 5000
The output shows that the detection period of errored frame events is 20 seconds, the detection
threshold is 10 seconds, and all the other parameters use the default values.
You can 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
Port : Ethernet1/0/1
Link Status : Up
Event statistic :
-------------------------------------------------------------------------
Link Fault :0 Dying Gasp : 0 Critical Event : 0
The output shows that no critical link event occurred on the link between Device A and Device
B.
You can use the display oam link-event command to display the statistics of Ethernet OAM
link error events. For example:
# Display Ethernet OAM link event statistics of the remote end of Device B.
[DeviceB] display oam link-event remote
Port :Ethernet1/0/1
Link Status :Up
OAMRemoteErrFrameEvent : (ms = milliseconds)
---------------------------------------------------------------------
Event Time Stamp : 5789 Errored FrameWindow : 200(100ms)

14
Errored Frame Threshold : 10 Errored Frame : 13
Error Running Total : 350 Event Running Total : 17
The output shows that 350 errors occurred since Ethernet OAM was enabled on Device A, 17 of
which are caused by error frames. The link is unstable.

15
Configuring CFD (available only on the
HPE 3100 v2 EI)
Overview
Connectivity Fault Detection (CFD) is an end-to-end per-VLAN link layer OAM mechanism used for
link connectivity detection, fault verification, and fault location. It conforms to IEEE 802.1ag CFM and
ITU-T Y.1731.
Basic CFD concepts
This section explains the concepts of CFD.
MD
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 assigns eight levels ranging from 0 to 7 to MDs. The bigger the
number, the higher the level, and the larger the area covered. If the outer domain has a higher level
than the nested one, domains can touch or nest, but they cannot intersect or overlap.
MD levels facilitate fault location and its accuracy. As shown in Figure 3, 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 Device A through Device E, may fail. If a connectivity fault is also detected at the
boundary of MD_B, the failure points may be any of Device B through Device D. If the devices in
MD_B can operate properly, at least Device C is operational.
Figure 3 Two nested MDs
CFD exchanges messages and performs operations on a per-domain basis. By planning MDs
properly in a network, you can use CFD to rapidly locate failure points.
MA
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".
Device A Device B Device C Device D
Device E
MD_A
MD_B
VLAN 100
Port
Port2
Port1 Port3
Port2
Port1 Port3
Port2
Port1 Port3
Port2
Port1 Port3
Port2
Port1 Port3
Port4 Port4 Port4 Port4
Port4