HP A5830 Series User manual

HP A5830 Switch Series
High Availability
Configuration Guide
Abstract
This document describes the software features for the HP A Series products and guides you through the
software configuration procedures. These configuration guides also provide configuration examples to
help you apply software features to different network scenarios.
This documentation is intended for network planners, field technical support and servicing engineers,
and network administrators working with the HP A Series products.
Part number: 5998-2068
Software version: Release 1109
Document version: 6W100-20110715

Legal and notice information
© Copyright 2011 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or use
of this material.
The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

iii
Contents
High availability overview··········································································································································· 7
Availability requirements··················································································································································7
Availability evaluation······················································································································································7
High availability technologies ·········································································································································8
Fault detection technologies····································································································································8
Protection switchover technologies·························································································································9
Ethernet OAM configuration ·····································································································································11
Ethernet OAM overview················································································································································ 11
Background···························································································································································· 11
Major functions of Ethernet OAM ······················································································································· 11
Ethernet OAMPDUs··············································································································································· 11
How Ethernet OAM works ··································································································································· 12
Standards and protocols ······································································································································ 15
Ethernet OAM configuration task list ··························································································································· 15
Configuring basic Ethernet OAM functions ················································································································ 15
Configuring the Ethernet OAM connection detection timers····················································································· 15
Configuring link monitoring ·········································································································································· 16
Configuring errored symbol event detection ······································································································ 16
Configuring errored frame event detection ········································································································ 16
Configuring errored frame period event detection···························································································· 17
Configuring errored frame seconds event detection ························································································· 17
Displaying and maintaining Ethernet OAM configuration························································································ 17
Ethernet OAM configuration example························································································································· 18
CFD configuration······················································································································································21
CFD overview ································································································································································· 21
Basic concepts in CFD ·········································································································································· 21
CFD functions························································································································································· 23
Protocols and standards ······································································································································· 24
CFD configuration task list ············································································································································ 24
Configuring basic CFD settings···································································································································· 25
Enabling CFD························································································································································· 25
Configuring the CFD protocol version ················································································································ 25
Configuring service instances ······························································································································ 25
Configuring MEPs·················································································································································· 26
Configuring MIP generation rules························································································································ 27
Configuring CFD functions············································································································································ 28
Configuration prerequisites ·································································································································· 28
Configuring CC on MEPs ····································································································································· 28
Configuring LB on MEPs ······································································································································· 29
Configuring LT on MEPs ······································································································································· 29
Displaying and maintaining CFD································································································································· 29
CFD configuration example ·········································································································································· 30
DLDP configuration·····················································································································································35
DLDP overview································································································································································ 35
Background···························································································································································· 35
How DLDP works ··················································································································································· 36
DLDP configuration task list··········································································································································· 42
Configuring the duplex mode and speed of an Ethernet interface··········································································· 42
Enabling DLDP································································································································································ 43

iv
Setting DLDP mode························································································································································· 43
Setting the interval to send advertisement packets ····································································································· 43
Setting the delaydown timer ········································································································································· 44
Setting the port shutdown mode··································································································································· 44
Configuring DLDP authentication ································································································································· 45
Resetting DLDP state······················································································································································· 45
Displaying and maintaining DLDP································································································································ 46
DLDP configuration examples ······································································································································· 46
Automatically shutting down unidirectional links······························································································· 46
Manually shutting down unidirectional links ······································································································ 50
Troubleshooting DLDP···················································································································································· 53
RRPP configuration ·····················································································································································54
Background···························································································································································· 54
Basic concepts in RRPP ········································································································································· 54
RRPPDUS ································································································································································ 56
RRPP timers····························································································································································· 57
How RRPP works···················································································································································· 57
Typical RRPP networking ······································································································································ 59
Protocols and standards ······································································································································· 62
RRPP configuration task list ··········································································································································· 62
Creating an RRPP domain············································································································································· 63
Configuring control VLANs ··········································································································································· 63
Configuring protected VLANs······································································································································· 64
Configuring RRPP rings·················································································································································· 65
Configuring RRPP ports········································································································································· 65
Configuring RRPP nodes ······································································································································· 65
Activating an RRPP domain··········································································································································· 67
Configuring RRPP timers ················································································································································ 67
Configuring an RRPP ring group ·································································································································· 68
Displaying and maintaining RRPP ································································································································ 68
RRPP configuration examples········································································································································ 69
Single ring configuration example ······················································································································ 69
Intersecting ring configuration example·············································································································· 71
Dual homed rings configuration example ·········································································································· 77
Intersecting-ring load balancing configuration example··················································································· 86
Troubleshooting······························································································································································ 94
Smart Link configuration············································································································································95
Smart Link overview ······················································································································································· 95
Background···························································································································································· 95
Terminology ··························································································································································· 96
How Smart Link works ·········································································································································· 97
Smart Link collaboration mechanisms ················································································································· 97
Smart Link configuration task list ·································································································································· 98
Configuring a Smart Link device ·································································································································· 98
Configuration prerequisites ·································································································································· 98
Configuring protected VLANs for a smart link group························································································ 98
Configuring member ports for a smart link group ····························································································· 99
Configuring role preemption for a smart link group ·······················································································100
Enabling the sending of flush messages ···········································································································100
Configuring an associated device ·····························································································································101
Configuration prerequisites ································································································································101
Enabling the receiving of flush messages·········································································································101
Displaying and maintaining Smart Link·····················································································································101
Smart Link configuration examples ····························································································································102
Single smart link group configuration example ·······························································································102

v
Multiple smart link groups load sharing configuration example····································································106
Monitor Link configuration······································································································································ 111
Monitor Link overview ·················································································································································111
Terminology ·························································································································································111
How Monitor Link works·····································································································································112
Configuring Monitor Link ············································································································································112
Configuration prerequisites ································································································································112
Creating a monitor link group ···························································································································112
Configuring monitor link group member ports·································································································112
Displaying and maintaining Monitor Link ·················································································································113
Monitor Link configuration example ··························································································································113
VRRP configuration·················································································································································· 117
VRRP overview······························································································································································117
VRRP standard protocol mode····································································································································118
Introduction to VRRP group·································································································································118
VRRP timers ··························································································································································119
Packet format ·······················································································································································120
Principles of VRRP················································································································································121
VRRP tracking·······················································································································································121
VRRP application (taking IPv4-based VRRP for example)················································································122
Configuring VRRP for IPv4 ··········································································································································123
VRRP for IPv4 configuration task list··················································································································123
Specifying the type of MAC addresses mapped to virtual IP addresses·······················································124
Creating a VRRP group and configuring virtual IP address············································································124
Configuring router priority, preemptive mode and tracking function····························································125
Configuring VRRP packet attributes···················································································································126
Enabling the trap function for VRRP ··················································································································127
Displaying and maintaining VRRP for IPv4·······································································································128
Configuring VRRP for IPv6 ··········································································································································128
VRRP for IPv6 configuration task list··················································································································128
Specifying the type of MAC addresses mapped to virtual IPv6 addresses ··················································128
Creating a VRRP group and configuring a virtual IPv6 address ····································································129
Configuring router priority, preemptive mode and tracking function····························································130
Configuring VRRP packet attributes···················································································································131
Displaying and maintaining VRRP for IPv6·······································································································132
IPv4-based VRRP configuration examples ·················································································································132
Single VRRP group configuration example·······································································································132
VRRP interface tracking configuration example ·······························································································135
VRRP with multiple VLANs configuration example ··························································································138
IPv6-based VRRP configuration examples ·················································································································141
Single VRRP group configuration example·······································································································141
VRRP interface tracking configuration example ·······························································································145
VRRP with multiple VLANs configuration example ··························································································148
Troubleshooting VRRP··················································································································································152
BFD configuration···················································································································································· 153
BFD overview································································································································································153
How BFD works···················································································································································153
BFD packet format···············································································································································155
Supported features ··············································································································································157
Protocols and standards ·····································································································································157
Configuring BFD basic functions ································································································································158
Configuration prerequisites ································································································································158
Configuration procedure ····································································································································158
Displaying and maintaining BFD································································································································159

vi
Track configuration ················································································································································· 160
Track overview ·····························································································································································160
Introduction to collaboration ······························································································································160
Collaboration fundamentals·······························································································································160
Collaboration application example···················································································································161
Track configuration task list ········································································································································161
Associating the track module with a detection module ···························································································162
Associating track with NQA ······························································································································162
Associating track with BFD·································································································································162
Associating track with interface management ·································································································163
Associating the track module with an application module······················································································164
Associating track with VRRP·······························································································································164
Associating track with static routing··················································································································165
Associating track with PBR ·································································································································166
Displaying and maintaining track entries··················································································································167
Track configuration examples·····································································································································167
VRRP-track-NQA collaboration configuration example (the master monitors the uplink) ····························167
Configuring BFD for a VRRP backup to monitor the master ···········································································170
Configuring BFD for the VRRP master to monitor the uplinks··········································································173
Static routing-track-NQA collaboration configuration example ·····································································177
Static routing-Track-BFD collaboration configuration example·······································································182
VRRP-track-interface management collaboration configuration example (the master monitors the uplink
interface) ······························································································································································185
Support and other resources ·································································································································· 189
Contacting HP ······························································································································································189
Subscription service ············································································································································189
Related information······················································································································································189
Documents····························································································································································189
Websites ······························································································································································189
Conventions ··································································································································································190
Index ········································································································································································ 192

7
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 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, as shown in Table
1.
Table 1 Availability requirements
Level Re
q
uirement 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
You should consider the Level 1 availability requirement during the design and production process of
network devices. Consider Level 2 during network design. Finally, consider Level 3 during network
deployment, according to the network infrastructure and service characteristics.
Availability evaluation
MTBF and 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. A smaller value of each item means a smaller MTTR and
a higher availability.

8
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 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. BFD is a generic fault detection technology that
can be used at any layer. NQA is used for diagnosis and evaluation of network quality. Monitor Link
and Track work along with other high availability technologies to detect faults through a collaboration
mechanism.
Table 2 Fault detection technologies
Technolo
gy
Introduction Reference
CFD
CFD, which conforms to IEEE 802.1ag CFM, is an end-to-end per-
VLAN link layer OAM mechanism used for link connectivity
detection, fault verification, and fault location.
CFD configuration in
High Availability
Configuration Guide
DLDP
The 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.
DLDP configuration 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.
Ethernet OAM
configuration in High
Availability
Configuration Guide
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.
BFD configuration in
High Availability
Configuration Guide
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.
NQA configuration
in Network
Management and
Monitoring
Configuration Guide
Monitor Link
Monitor link is a port collaboration function. It is usually used in
conjunction with Layer 2 topology protocols. The idea is to
monitor the states of uplink ports and adapt the up/down state of
downlink ports to the up/down state of uplink ports, triggering
link switchover on the downstream device in time.
Monitor link
configuration in High
Availability
Configuration Guide

9
Technolo
gy
Introduction Reference
Track
The track module is used to implement collaboration between
different modules. The collaboration here involves three parts: the
application modules, the track module, and the detection
modules. These modules collaborate with one another through
collaboration entries. That is, the detection modules trigger the
application modules to perform certain operations through the
track module. More specifically, the detection modules probe the
link status, network performance and so on, and inform the
application modules of the detection result through the track
module. Once notified of network status changes, the application
modules deal with the changes to avoid communication
interruption and network performance degradation.
Track configuration
in High Availability
Configuration Guide
Protection switchover technologies
Protection switchover technologies aim at recovering network faults. To ensure continuity of network
services, they back up hardware, link, routing, and service information for switchover in case of network
faults.
Table 3 Protection switchover technologies
Technolo
gy
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.
Ethernet link
aggregation
configuration in 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.
Smart link
configuration in High
Availability
Configuration Guide
MSTP
As a Layer 2 management protocol, the MSTP eliminates Layer 2
loops by selectively blocking redundant links in a network, and in
the meantime, allows for link redundancy.
Spanning tree
configuration in Layer
2—LAN Switching
Configuration Guide
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. It can also rapidly restore the
communication paths between the nodes in the event that a link is
disconnected on the ring.
RRPP configuration in
High Availability
Configuration Guide
FRR
FRR provides a quick per-link or per-node protection on an LSP. In
this approach, once a link or node fails on a path, FRR comes up
to reroute the path to a new link or node to bypass the failed link
or node. This can happen in as fast as 50 milliseconds,
minimizing data loss. Protocols such as RIP, OSPF, IS-IS, and
static routing support this technology.
Layer 3—IP Routing
Configuration
Guide/Configuration
Guide of the
corresponding
protocols

10
Technolo
gy
Introduction Reference
GR
GR ensures the continuity of packet forwarding when a protocol,
such as BGP, IS-IS, OSPF, IPv6 BGP, IPv6 IS-IS, or OSPFv3
restarts, or during an active/standby switchover process. It needs
other devices to implement routing information backup and
recovery.
Layer 3—IP Routing
Configuration
Guide/Configuration
Guide of the
corresponding
protocols
NSR
NSR is a new feature used to ensure non-stop data transmission
during an active/standby switchover. Devices that have formed
an IRF fabric support this feature. It backs up IP forwarding
information from the master to the subordinate. Upon an
active/standby switchover, NSR can complete link state recovery
and route re-generation without requiring the cooperation of
other devices. IS-IS and OSPF support this feature.
Layer 3—IP Routing
Configuration Guide
/Configuration
Guide of the
corresponding
protocols
VRRP
VRRP is an error-tolerant protocol that provides highly reliable
default links on multicast and broadcast LANs such as Ethernet,
avoiding network interruption due to failure of a single link.
VRRP configuration in
High Availability
Configuration Guide
A single availability technology cannot solve all problems. Therefore, to enhance network availability,
use a combination of availability technologies, chosen on the basis of detailed analysis of network
environments and user requirements. For example, connect access-layer devices to distribution-layer
devices over redundant links, and fully mesh core-layer devices. Also, consider network availability
during planning before you build a network.

11
Ethernet OAM configuration
Ethernet OAM overview
Throughout this document, a port with Ethernet OAM enabled is an Ethernet OAM entity or an OAM
entity.
Background
With features such as ease of use and low price, Ethernet has gradually become the major underlying
technology for today’s LANs. Recently, with the emergence of Gigabit Ethernet and 10-Gigabit Ethernet,
Ethernet is gaining popularity in MANs and WANs as well.
In the beginning, Ethernet is mainly used in LANs, which have low reliability and stability requirements.
This is why an effective management and maintenance mechanism for Ethernet has been absent all
along, hindering the usage of Ethernet in MANs and WANs. Implementing OAM on Ethernet networks
has now become an urgent matter.
Ethernet OAM is a tool that monitors Layer 2 link status and addresses 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.
Major functions of Ethernet OAM
Ethernet OAM can effectively promote your management and maintenance capabilities over Ethernet
networks, guaranteeing the stability of the networks. 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 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.

12
Figure 1 Formats of different types of Ethernet OAMPDUs
Table 4 The fields in an OAMPDU
Field Descri
p
tion
Dest addr
Destination MAC address of the Ethernet OAMPDU.
It is a slow protocol multicast address, 0180c2000002.
Bridges cannot forward slow protocol packets, which means you cannot forward
Ethernet OAMPDUs.
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.
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.
Table 5 Functions of different types of OAMPDUs
OAMPDU t
yp
e 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.

13
Ethernet OAM connection establishment
Ethernet OAM connection is the basis of all 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. You can establish an Ethernet OAM
connection between entities that have matching Loopback, link detecting, and link event settings. After
you establish an Ethernet OAM connection, 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
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 you establish an Ethernet OAM connection, the Ethernet OAM entities on both sides exchange
Information OAMPDUs at a specified interval (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.

14
Table 7 Ethernet OAM link error events
Ethernet OAM link events Descri
p
tion
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 because of device failures or unavailability,
the flag field defined in Information OAMPDUs allows an Ethernet OAM entity to send error
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
T
yp
e Descri
p
tion OAMPDU transmission fre
q
uencies
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.
This Switch Series is unable to support the sending of 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 shut down manually. Physical IRF ports, however, are unable to send this
type of OAMPDU. For more information about physical IRF ports, see IRF Configuration Guide.
This Switch Series is unable to send Information OAMPDUs carrying Critical Events.

15
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 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:
To do… Use the command… Remarks
•Enter system view system-view —
•Enter Layer 2 Ethernet
interface view
interface interface-type interface-
number —
•Set the Ethernet OAM mode oam mode { active | passive }
Optional.
The default is active Ethernet
OAM mode.
•Enable Ethernet OAM on the
current port oam enable
Required.
Ethernet OAM is disabled by
default.
Configuring the Ethernet OAM connection detection
timers
After you establish an Ethernet OAM connection, the Ethernet OAM entities on both sides exchange
Information OAMPDUs at a specified interval—handshake packet transmission interval—to check

16
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.
To configure the Ethernet OAM connection detection timers:
To do… Use the command… Remarks
•Enter system view system-view —
•Configure the Ethernet OAM
handshake packet
transmission interval
oam timer hello interval Optional
1000 millisecond by default.
•Configure the Ethernet OAM
connection timeout timer oam timer keepalive interval Optional
5000 milliseconds by default.
CAUTION:
A
fter the timeout timer of an Ethernet OAM connection expires, the local OAM entity a
g
es out its
connection with the peer OAM entity. This causes the OAM connection to be disconnected. HP
recommends that you set the connection timeout timer to at least five times the handshake packet
transmission interval. This ensures the stability of Ethernet OAM connections.
Configuring link monitoring
After you establish Ethernet OAM connections, the link monitoring periods and thresholds configured in
this section take effect on all Ethernet ports automatically.
Configuring errored symbol event detection
To configure errored symbol event detection:
To do… Use the command… Remarks
•Enter system view system-view —
•Configure the errored
symbol event detection
interval
oam errored-symbol period period-value Optional
1 second by default.
•Configure the errored
symbol event triggering
threshold
oam errored-symbol threshold threshold-
value
Optional
1 by default.
Configuring errored frame event detection
To configure errored frame event detection:
To do… Use the command… Remarks
•Enter system view system-view —

17
To do… Use the command… Remarks
•Configure the errored
frame event detection
interval
oam errored-frame period period-value Optional
1 second by default.
•Configure the errored
frame event triggering
threshold
oam errored-frame threshold threshold-
value
Optional
1 by default.
Configuring errored frame period event detection
To configure errored frame period event detection:
To do… Use the command… Remarks
•Enter system view system-view —
•Configure the errored
frame period event
detection period
oam errored-frame-period period period-
value
Optional
1000 milliseconds by default.
•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
To configure errored frame seconds event detection:
To do… Use the command… Remarks
•Enter system view system-view —
•Configure the errored
frame seconds event
detection interval
oam errored-frame-seconds period
period-value
Optional
60 second by default.
•Configure the errored
frame seconds event
triggering threshold
oam errored-frame-seconds threshold
threshold-value
Optional
1 by default.
CAUTION:
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.
Displaying and maintaining Ethernet OAM
configuration
To do… Use the command… Remarks
•Display global Ethernet OAM
configuration
display oam configuration [ |{ begin |
exclude | include } regular-expression ] Available in any view

18
To do… Use the 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 only
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 Device A and Device B by collecting statistics about
the error frames received by Device A.
Figure 2 Network diagram for Ethernet OAM configuration
Configuration procedure
1. Configure Device A.
# Configure GigabitEthernet 1/0/1 to operate in passive Ethernet OAM mode, and enable Ethernet
OAM for it.
<DeviceA> system-view
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] oam mode passive
[DeviceA-GigabitEthernet1/0/1] oam enable
[DeviceA-GigabitEthernet1/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.
# Configure GigabitEthernet 1/0/1 to operate in active Ethernet OAM mode (the default), and enable
Ethernet OAM for it.

19
<DeviceB> system-view
[DeviceB] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] oam mode active
[DeviceB-GigabitEthernet1/0/1] oam enable
[DeviceB-GigabitEthernet1/0/1] quit
3. Verify the configuration.
Use the display oam configuration command to view 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 other parameters use the default values.
You can use the display oam critical-event command to view statistics of Ethernet OAM critical link
events. For example:
# Display the statistics of Ethernet OAM critical link events on all ports of Device A.
[DeviceA] display oam critical-event
Port : GigabitEthernet1/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 view 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 :GigabitEthernet1/0/1
Link Status :Up
OAMRemoteErrFrameEvent : (ms = milliseconds)
---------------------------------------------------------------------
Event Time Stamp : 5789 Errored FrameWindow : 10(100ms)

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