HPE FlexNetwork HSR6800 series User manual

HPE FlexNetwork HSR6800 Routers
High Availability Configuration Guide
Part number: 5998-4497R
Software version: HSR6800-CMW520-R3303P25
Document version: 6W105-20151231

© Copyright 2015 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············································································································3
Configuring active and standby switchover·····················································5
Configuring active and standby switchover········································································································5
Active and standby switchover configuration task list························································································5
Ignoring version check of the standby MPU ······································································································5
Restarting the standby MPU······························································································································6
Manually performing an active and standby switchover ····················································································6
Displaying and maintaining active and standby switchover···············································································6
Configuring Ethernet OAM··············································································7
Overview····························································································································································7
Major functions of Ethernet OAM···············································································································7
Ethernet OAMPDUs···································································································································7
How Ethernet OAM works··························································································································8
Standards and protocols··························································································································10
Ethernet OAM configuration task list················································································································10
Configuring basic Ethernet OAM functions······································································································11
Configuring the Ethernet OAM connection detection timers············································································11
Configuring link monitoring ······························································································································12
Configuring errored symbol event detection ····························································································12
Configuring errored frame event detection·······························································································12
Configuring errored frame period event detection····················································································12
Configuring errored frame seconds event detection················································································13
Configuring Ethernet OAM remote loopback ···································································································13
Configuration guidelines···························································································································13
Enabling Ethernet OAM remote loopback in user view············································································14
Enabling Ethernet OAM remote loopback in system view ·······································································14
Enabling Ethernet OAM remote loopback in Ethernet port view······························································14
Rejecting the Ethernet OAM remote loopback request from a remote port·············································14
Displaying and maintaining Ethernet OAM configuration·················································································15
Ethernet OAM configuration example··············································································································15
Network requirements······························································································································15
Configuration procedure···························································································································16
Configuring CFD···························································································18
Overview··························································································································································18
Basic CFD concepts·································································································································18
CFD functions ··········································································································································20
Protocols and standards ··························································································································21
CFD configuration task list·······························································································································21
Configuring basic CFD settings ·······················································································································22
Enabling CFD···········································································································································22
Configuring the CFD protocol version······································································································22
Configuring service instances··················································································································22
Configuring MEPs····································································································································23
Configuring MIP generation rules·············································································································24
Configuring CFD functions·······························································································································24
Configuration prerequisites······················································································································24
Configuring CC on MEPs·························································································································24
Configuring LB on MEPs··························································································································25
Configuring LT on MEPs··························································································································25

ii
Displaying and maintaining CFD······················································································································26
CFD configuration example ·····························································································································27
Configuring DLDP·························································································31
Overview··························································································································································31
Configuring DLDP············································································································································32
DLDP configuration task list·····························································································································38
Configuring the duplex mode and speed of an Ethernet interface···································································38
Enabling DLDP ················································································································································39
Setting DLDP mode ·········································································································································39
Setting the interval to send advertisement packets ·························································································39
Setting the DelayDown timer ···························································································································40
Setting the port shutdown mode ······················································································································40
Configuring DLDP authentication·····················································································································41
Resetting DLDP state ······································································································································41
Displaying and maintaining DLDP ···················································································································42
DLDP configuration examples ·························································································································42
Automatically shutting down unidirectional links······················································································42
Manually shutting down unidirectional links·····························································································46
Troubleshooting DLDP·····································································································································49
Configuring RPR···························································································50
RPR overview ··················································································································································50
Ring structure of RPR······························································································································50
Data operations on RPR··························································································································51
Topology discovery··································································································································52
Fault response methods···························································································································53
Centralized RPR and distributed RPR·····································································································55
RPR interface···········································································································································55
Protocols and standards ··························································································································56
RPR configuration task list·······························································································································56
Configuring basic RPR functions ·····················································································································57
Configuring an RPR physical port············································································································57
Creating and configuring an RPR logical interface ··················································································57
Binding an RPR logical interface with RPR physical ports·······································································58
Enabling RPR mate port smart connection······························································································58
Configuring the RPR station name···········································································································59
Configuring RPR protection ·····························································································································59
Configuring the RPR protection mode ·····································································································59
Configuring RPR protection reversion mode····························································································59
Manually sending a protection request ····································································································60
Configuring the ringlet selection table··············································································································60
Adding a static ringlet selection entry·······································································································60
Configuring default ringlet selection·········································································································61
Configure the RPR fairness algorithm ·············································································································61
Configuring reserved bandwidth or rate limiting·······················································································61
Configuring station weight························································································································62
Configuring RPR timers ···································································································································62
Configuring the ATD timer························································································································62
Configuring the hold off timer···················································································································63
Configuring the keepalive timer················································································································63
Configuring the topology stability timer····································································································63
Configuring the TC timers························································································································63
Configuring the TP timers ························································································································64
Configuring the WTR timer·······················································································································64
Testing connectivity between RPR stations·····································································································64
Displaying and maintaining RPR ·····················································································································65
RPR configuration examples ···························································································································66
RPR interface binding configuration example··························································································66
RPR protection mode/static ringlet selection configuration example·······················································68

iii
Configuring RRPP·························································································70
RRPP overview················································································································································70
Basic RRPP concepts······························································································································70
RRPPDUs················································································································································72
RRPP timers ············································································································································73
How RRPP works·····································································································································73
Typical RRPP networking ························································································································74
Protocols and standards ··························································································································77
RRPP configuration task list ····························································································································78
Creating an RRPP domain·······························································································································78
Configuring control VLANs·······························································································································79
Configuring protected VLANs ··························································································································79
Configuring RRPP rings···································································································································80
Configuring RRPP ports···························································································································80
Configuring RRPP nodes·························································································································81
Activating an RRPP domain·····························································································································82
Configuring RRPP timers·································································································································83
Configuring an RRPP ring group ·····················································································································83
Displaying and maintaining RRPP···················································································································84
RRPP configuration examples·························································································································84
Single ring configuration example············································································································84
Intersecting ring configuration example ···································································································87
Dual homed rings configuration example·································································································92
Load balanced intersecting-ring configuration example·········································································101
Troubleshooting ·············································································································································110
Configuring Smart Link ···············································································111
Smart Link overview·······································································································································111
Background············································································································································111
Terminology ···········································································································································112
How Smart Link works ···························································································································112
Smart Link collaboration mechanisms ···································································································113
Smart Link configuration task list ···················································································································114
Configuring a Smart Link device····················································································································114
Configuration prerequisites····················································································································114
Configuring protected VLANs for a smart link group··············································································114
Configuring member ports for a smart link group···················································································115
Configuring role preemption for a smart link group················································································116
Enabling the sending of flush messages································································································116
Configuring the collaboration between Smart Link and CC of CFD·······················································117
Configuring an associated device··················································································································117
Configuration prerequisites····················································································································117
Enabling the receiving of flush messages······························································································117
Displaying and maintaining Smart Link··········································································································118
Smart Link configuration examples················································································································118
Single smart link group configuration example ······················································································118
Multiple smart link groups load sharing configuration example······························································123
Smart Link and CFD collaboration configuration example·····································································127
Configuring VRRP·······················································································132
VRRP overview··············································································································································132
VRRP standard mode····························································································································133
VRRP load balancing mode···················································································································138
Configuring the IPv4/IPv6 VRRP version·······································································································142
Configuring VRRP for IPv4 ····························································································································143
VRRP for IPv4 configuration task list·····································································································143
Configuring a VRRP working mode ·······································································································143
Specifying the type of MAC addresses mapped to virtual IP addresses················································144
Specifying the VRRP control VLAN ·······································································································144
Creating a VRRP group and configuring virtual IP address···································································146
Configuring router priority, preemptive mode and tracking function·······················································147

iv
Configuring VF tracking··························································································································148
Enabling ARP entry backup···················································································································149
Configuring VRRP packet attributes ······································································································150
Enabling the trap function for VRRP······································································································151
Displaying and maintaining VRRP for IPv4····························································································151
Configuring VRRP for IPv6 ····························································································································151
VRRP for IPv6 configuration task list·····································································································151
Specifying the type of MAC addresses mapped to virtual IPv6 addresses············································152
Creating a VRRP group and configuring a virtual IPv6 address····························································153
Configuring router priority, preemptive mode and tracking function·······················································154
Configuring VF tracking··························································································································155
Configuring VRRP packet attributes ······································································································156
Displaying and maintaining VRRP for IPv6····························································································156
IPv4-based VRRP configuration examples····································································································157
Single VRRP group configuration example····························································································157
VRRP interface tracking configuration example·····················································································159
Multiple VRRP groups configuration example························································································162
VRRP load balancing mode configuration example···············································································165
IPv6-based VRRP configuration examples····································································································174
Single VRRP group configuration example····························································································174
VRRP interface tracking configuration example·····················································································177
Multiple VRRP groups configuration example························································································181
VRRP load balancing mode configuration example···············································································183
Troubleshooting VRRP ··································································································································192
The screen frequently displays error prompts························································································192
Multiple masters are present in the same VRRP group·········································································192
Frequent VRRP state transition ·············································································································192
Configuring BFD ·························································································194
Introduction to BFD········································································································································194
How BFD works ·····································································································································194
BFD packet format·································································································································196
Supported features·································································································································198
Protocols and standards ························································································································198
Configuring BFD basic functions····················································································································198
Configuration prerequisites····················································································································198
Configuration procedure·························································································································199
Enabling trap··················································································································································200
Displaying and maintaining BFD····················································································································200
Configuring Track························································································202
Overview························································································································································202
Collaboration fundamentals ···················································································································202
Collaboration application example·········································································································203
Track configuration task list ···························································································································203
Associating the Track module with a detection module·················································································204
Associating Track with NQA···················································································································204
Associating Track with BFD···················································································································204
Associating Track with interface management·······················································································205
Associating the Track module with an application module ············································································206
Associating Track with VRRP ················································································································206
Associating Track with static routing······································································································207
Associating Track with PBR···················································································································208
Displaying and maintaining track entries ·······································································································210
Track configuration examples························································································································210
VRRP-Track -NQA collaboration configuration example ·······································································210
Configuring BFD for a VRRP backup to monitor the master··································································214
Configuring BFD for the VRRP master to monitor the uplink·································································217
Static routing-Track-NQA collaboration configuration example ·····························································220
Static routing-Track-BFD collaboration configuration example······························································225
VRRP-track-interface management collaboration configuration example··············································228

v
Document conventions and icons·······························································232
Conventions···················································································································································232
Network topology icons··································································································································233
Support and other resources ······································································234
Accessing Hewlett Packard Enterprise Support ····························································································234
Accessing updates·········································································································································234
Websites ················································································································································235
Customer self repair·······························································································································235
Remote support······································································································································235
Documentation feedback ·······················································································································235
Index···········································································································237

1
High availability overview
Because communication interruptions can seriously affect widely-deployed value-added services
such as IPTV and video conference, 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
Table 1 describes a typical availability model that divides availability requirements into different
levels.
Table 1 Availability requirements
Level Requirement Solution
1 Decrease system software and
hardware faults
•Hardware—Simplified circuit design, enhanced
production techniques, and reliability tests.
•Software—Reliability design and test.
2 Protect system functions from being
affected if faults occur Device and link redundancy and switchover.
3 Enable the system to recover as fast
as possible Performing fault detection, diagnosis, isolation, and recovery technologies.
Consider level 1 availability requirements during the design and production processes of network
devices.
Consider level 2 availability requirements during network design.
Consider level 3 availability requirements 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 in the aspect of 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.
•BFD is a generic fault detection technology that can be used at any layer.
•NQA is used for diagnosis and evaluation of network quality.
•Track works along with other high availability technologies to detect faults through a
collaboration mechanism.
Table 2 Fault detection technologies
Technology Introduction Reference
CFD CFD, which conforms to IEEE 802.1ag CFM and ITU-T Y.1731, is
an end-to-end per-VLAN link layer OAM mechanism used for link
connectivity detection, fault verification, and fault location. "Configuring CFD"
DLDP
DLDP deals with unidirectional links that might occur in a network.
When 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"
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 the two devices.
"Configuring
Ethernet OAM"
BFD
BFD provides a single mechanism to quickly detect and monitor the
connectivity of links or IP forwarding in networks. To improve
network performance, devices must quickly detect communication
failures to restore communication through backup paths as soon as
possible.
"Configuring BFD"
NQA
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.
Network
Management and
Monitoring
Configuration
Guide
Track
The Track module implements collaboration between different
modules. The collaboration involves three sets of modules:
application, Track, and detection. These modules collaborate with
one another through collaboration entries. The detection modules
trigger the application modules to perform certain operations
through the Track module. The detection modules probe such items
as link status and network performance, and inform the application
modules of the detection result through the Track module. Once
notified of network status changes, the application modules use the
changes to avoid communication interruption and network
performance degradation.
"Configuring
Track"

3
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.
A single availability technology cannot solve all problems. You should use a combination of
availability technologies, chosen on the basis of detailed analysis of network environments and user
requirements, 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. Network availability should be considered during the planning stage.
Table 3 Protection switchover technologies
Technology Introduction Reference
Active and
standby
switchover
Devices supporting active and standby switchover are typically
equipped with two main boards, with one being the active MPU,
and the other being the standby MPU. The configurations on the
standby MPU are the same as those on the active MPU. When
the active MPU fails or is removed, the standby MPU
automatically becomes the active MPU to ensure non-stop
operating of the devices.
"Configuring active
and standby
switchover"
Ethernet link
aggregation
Ethernet link aggregation, or 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.
Layer 2—LAN
Switching
Configuration Guide
Smart Link
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"
MSTP As a Layer 2 management protocol, MSTP eliminates Layer 2 loops by selectively blocking redundant links in a network, and in
the meantime, allows for link redundancy.
Layer 2—LAN
Switching
Configuration Guide
RPR
RPR is a new MAC layer protocol designed for transferring mass
data services over MANs. It can operate on SONET/SDH,
DWDM and Ethernet to provide flexible and efficient networking
schemes for broadband IP MANs carriers.
"Configuring RPR"
RRPP
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"
FRR
FRR provides a quick per-link or per-node protection on an LSP.
Once a link or node fails on a path, FRR reroutes the path to a
new link or node to bypass the failed link or node. This can
happen as fast as 50 milliseconds minimizing data loss.
Protocols such as RIP, OSPF, IS-IS, static routing, and RSVP-TE
support this technology.
Layer 3—IP Routing
Configuration Guide,
MPLS Configuration
Guide, and
configuration guide
of the corresponding
protocols
GR
GR ensures the continuity of packet forwarding when a protocol,
such as BGP, IS-IS, OSPF, LDP, or RSVP-TE, restarts, or during
an active/standby switchover process. It needs other devices to
implement routing information backup and recovery.
Related chapters in
Layer 3—IP Routing
Configuration Guide
and MPLS
Configuration Guide

4
Technology Introduction Reference
NSR
NSR ensures non-stop data transmission during an
active/standby switchover by backing up IP/MPLS forwarding
information from the active MPU to the standby MPU. Upon an
active/standby switchover, NSR can complete link state recovery
and route re-generation without requiring the cooperation of other
devices. IS-IS supports this feature.
Layer 3—IP Routing
Configuration Guide
Stateful failover
Two devices back up the services of each other to ensure that the
services on them are consistent. If one device fails, the other
device can take over the services by using VRRP or dynamic
routing protocols. Because the other device has already backed
up the services, service traffic can pass through the other device,
avoiding service interruption.
"Configuring stateful
failover"
VRRP VRRP is an error-tolerant protocol, which provides highly reliable
default links on multicast and broadcast LANs such as Ethernet,
avoiding network interruption due to failure of a single link. "Configuring VRRP"

5
Configuring active and standby
switchover
If a device has two MPUs, the MPU that forwards and processes packets is called the active MPU,
and the MPU that is in the standby state is called the standby MPU. The system uses the MPU with
a smaller slot number as the active MPU, and the other MPU as the standby MPU. The standby MPU
keeps its configuration the same as the active MPU through the synchronization function. When the
active MPU fails, the standby MPU becomes the active MPU to process services to ensure the
normal operation of the device. This switchover process is called an active and standby switchover.
Active and standby switchover functions in the following ways:
•Automatic active and standby switchover. If the active MPU fails or is removed, the system
automatically performs an active and standby switchover to enable the standby MPU to function
as the active MPU.
•Manual active and standby switchover, which is an active and standby switchover performed at
the command line interface.
Configuring active and standby switchover
•The tasks in this chapter can be performed only when the device is operating in standalone
mode. In IRF mode, only the display switchover state command takes effect. For more
information about IRF, see IRF Configuration Guide.
•Active/standby switchover configuration tasks must be performed at the CLI of the active MPU.
The system can automatically propagate the configuration to the standby MPU.
Active and standby switchover configuration task
list
Task Remarks
Ignoring version check of the standby MPU Optional
Restarting the standby MPU Optional
Manually performing an active and standby switchover Optional
Ignoring version check of the standby MPU
When the standby MPU attempts to start up, the system by default examines its software version
against the software version on the active MPU for inconsistency. If the versions of the active MPU
and standby MPU are not consistent, the standby MPU cannot be started.
To disable the system from examining the software version of the standby MPU:
Step Command Remarks
1. Enter system view. system-view N/A
2. Ignore version check of the
standby MPU. ha slave-ignore-version-check By default, version check of the
standby MPU is enabled.

6
Restarting the standby MPU
After the standby MPU has restarted, the active MPU will perform initial synchronization on the
standby MPU. During this process, the system does not respond to your input. After the initial
synchronization is completed, you can execute all the configuration commands on the active MPU
and the active MPU and standby MPU will keep a real-time synchronization process. Your
configuration on the active MPU will be copied to the standby MPU to ensure the consistency of the
current configuration of the active MPU and standby MPU.
To restart the standby MPU:
Step Command
3. Enter system view. system-view
4. Manually restart the standby MPU. slave restart
Manually performing an active and standby
switchover
An automatic active and standby switchover might cause configuration and data loss. Before you
unplug the active MPU to start an active and standby switchover, perform a manual switchover so
that the standby MPU can synchronize latest configurations from the active MPU.
Before a switchover, make sure the LPUs, active MPU, and standby MPU are operating correctly.
To manually perform an active and standby switchover:
Step Command Remarks
5. Enter system view. system-view N/A
6. Enable manual active and
standby switchover. slave switchover { disable |
enable } Optional.
Enabled by default.
7. Manually perform an active
and standby switchover. slave switchover N/A
Displaying and maintaining active and standby
switchover
Task Command Remarks
Display the switchover state of
MPUs (in standalone mode).
display switchover state [ slot
slot-number ] [ |{ begin | exclude
| include } regular-expression ] Available in any view.
Display the switchover state of
MPUs (in IRF mode)
display switchover state
[ chassis chassis-number slot
slot-number ] [ | { begin | exclude
| include } regular-expression ]
Available in any view.

7
Configuring Ethernet OAM
Ethernet OAM is supported only when the SAP module is operating in bridge mode.
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 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 include 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. Because bridges cannot
forward slow protocol packets, 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.

8
Field Description
Type Type of the encapsulated protocol in the Ethernet OAMPDU.
The value is 0x8809.
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, an Ethernet OAM-enabled port is called an "Ethernet OAM entity" or an
"OAM entity."
Table 5 Functions of different types of OAMPDUs
OAMPDU type Function
Information OAMPDU Transmits 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 maintains 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 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.
IMPORTANT:
To set up an OAM connection between two OAM entities, you must set at least one entity to operate
in active mode.
Table 6 shows the actions that a device can perform in different modes.
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

9
Item Active Ethernet OAM mode Passive Ethernet OAM
mode
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 7, 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 7 Ethernet OAM link error events
Ethernet OAM link events Description
Errored symbol event Occurs when the number of detected symbol errors during a specific
detection interval exceeds the predefined threshold.
Errored frame event Occurs when the number of detected error frames during a specific
interval exceeds the predefined threshold.
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 Occurs when the number of error frame seconds detected on a port
during a specific 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 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:
Maximum number of frames = interface bandwidth (bps) × errored frame period event detection
period (in ms)/(64 × 8 × 1000)
The 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 information

10
(any critical link event type shown in Table 8) 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 An unexpected fault, such as power failure,
occurred. Non-stop.
Critical Event An undetermined critical event happened. Non-stop.
The devices are able to receive Information OAMPDUs carrying the critical link events listed inTable
8.
The devices are able to send Information OAMPDUs carrying Dying Gasp events when the device is
rebooted or relevant ports are manually shut down.
The devices are unable to send Information OAMPDUs carrying Critical Events.
IRF physical ports do not support OAM-related functions.
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.
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 Required
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 in user view Optional
Enabling Ethernet OAM remote loopback in system view Optional
Enabling Ethernet OAM remote loopback in Ethernet port
view Optional

11
Task Remarks
Rejecting the Ethernet OAM remote loopback request from a
remote port Optional
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. Only in active mode can an Ethernet OAM entity initiate OAM
connection.
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 Ethernet port 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 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.
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. Hewlett Packard
Enterprise recommends that you set the connection timeout timer 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 milliseconds by default.
3. Configure the Ethernet OAM
connection timeout timer. oam timer keepalive interval Optional.
5000 milliseconds by default.

12
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 during a specific
detection interval exceeds the predefined threshold.
To configure errored symbol event detection:
Step Command Remarks
1. Enter system view. system-view N/A
2. Configure the errored
symbol event
detection interval.
oam errored-symbol period
period-value
Optional.
1 second by default.
3. Configure the errored
symbol event
triggering threshold.
oam errored-symbol threshold
threshold-value
Optional.
1 by default.
Configuring errored frame event detection
An errored frame event occurs when the number of detected error frames during a specific interval
exceeds the predefined threshold.
To configure 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
An errored frame period event occurs if the number of frame errors in a specific number of received
frames exceeds the predefined threshold.
To configure 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.

13
Configuring errored frame seconds event detection
An errored frame seconds event occurs when the number of error frame seconds detected on a port
during a detection interval exceeds the error threshold.
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.
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 seconds 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
CAUTION:
The Ethernet OAM remote loopback function can impact other services. Use it with caution.
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. It can be performed only by Ethernet OAM entities operating in active Ethernet
OAM mode.
•Remote loopback is available only on full-duplex links that support remote loopback at both
ends.
•Ethernet OAM remote loopback must be supported by both the remote port and the sending
port.
•Enabling Ethernet OAM remote loopback interrupts data communications.After Ethernet OAM
remote loopback is disabled, all the ports involved will shut down and then come up. Ethernet
OAM remote loopback can be disabled by any of the following events: 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, or the Ethernet
OAM connection timing out.