HPE JL585A Configuration Guide

HPE FlexFabric 5710 Switch Series

High Availability Configuration Guide

Software version: Release 671x and later

Document version: 6W100-20230822

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 either registered trademarks or trademarks of Microsoft Corporation in the

United States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

i

Contents

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

About Ethernet OAM ·········································································································································· 1

Major functions of Ethernet OAM ··············································································································· 1

Ethernet OAMPDUs ··································································································································· 1

How Ethernet OAM works ·························································································································· 1

Protocols and standards ···························································································································· 3

Restrictions and guidelines: Ethernet OAM configuration ·················································································· 3

Ethernet OAM tasks at a glance ························································································································ 4

Configuring basic Ethernet OAM functions ········································································································ 4

Configuring the Ethernet OAM connection detection timers ·············································································· 5

About the Ethernet OAM connection detection timers ··············································································· 5

Restrictions and guidelines for configuring Ethernet OAM connection detection timers ···························· 5

Configuring the Ethernet OAM connection detection timers globally ························································· 5

Configuring the Ethernet OAM connection detection timers on a port ······················································· 5

Configuring errored symbol event detection ······································································································ 6

Restrictions and guidelines for configuring errored symbol event detection ·············································· 6

Configuring errored symbol event detection globally ················································································· 6

Configuring errored symbol event detection on a port ··············································································· 6

Configuring errored frame event detection········································································································· 7

Restrictions and guidelines for configuring errored frame event detection ················································ 7

Configuring errored frame event detection globally ··················································································· 7

Configuring errored frame event detection on a port ················································································· 7

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

Restrictions and guidelines for configuring errored frame period event detection ····································· 7

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

Configuring errored frame period event detection on a port ······································································ 8

Configuring errored frame seconds event detection ·························································································· 8

Restrictions and guidelines for configuring errored frame seconds event detection ·································· 8

Configuring errored frame seconds event detection globally ····································································· 8

Configuring errored frame seconds event detection on a port ··································································· 9

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

Enabling Ethernet OAM remote loopback for a port ·························································································· 9

About Ethernet OAM remote loopback ······································································································ 9

Restrictions and guidelines for enabling Ethernet OAM remote loopback ··············································· 10

Enabling Ethernet OAM remote loopback for a port in system view ························································ 10

Enabling Ethernet OAM remote loopback for a port in interface view ······················································ 10

Rejecting the Ethernet OAM remote loopback request from a remote port ····················································· 11

Display and maintenance commands for Ethernet OAM ················································································· 11

Ethernet OAM configuration examples ············································································································ 12

Example: Configuring Ethernet OAM ······································································································· 12

Configuring CFD ·························································································· 14

About CFD ······················································································································································· 14

Basic CFD concepts ································································································································· 14

CFD levels ················································································································································ 14

Packet processing of MPs ························································································································ 17

CFD functions ·········································································································································· 17

EAIS ························································································································································· 18

Port collaboration ····································································································································· 18

Collaboration between CFD and Track ···································································································· 19

Protocols and standards ·························································································································· 19

Restrictions and guidelines: CFD configuration ······························································································· 19

CFD tasks at a glance ······································································································································ 20

Prerequisites for CFD······································································································································· 20

Configuring basic CFD settings ······················································································································· 21

Enabling CFD ··········································································································································· 21

Configuring service instances ·················································································································· 21

ii

Configuring MEPs ···································································································································· 21

Configuring MIP auto-generation rules ···································································································· 22

Configuring CFD functions ······························································································································· 22

Configuring CC ········································································································································· 22

Configuring LB ········································································································································· 24

Configuring LT ·········································································································································· 24

Configuring AIS ········································································································································ 24

Configuring LM ········································································································································· 25

Configuring one-way DM ·························································································································· 25

Configuring two-way DM ·························································································································· 26

Configuring TST ······································································································································· 26

Configuring EAIS·············································································································································· 26

Configuring port collaboration ·························································································································· 27

Display and maintenance commands for CFD ································································································ 27

CFD configuration examples ···························································································································· 28

Example: Configuring CFD ······················································································································ 28

Configuring DLDP ························································································ 34

About DLDP ····················································································································································· 34

Application scenario ································································································································· 34

Basic concepts ········································································································································· 35

How DLDP works ····································································································································· 36

Restrictions and guidelines: DLDP configuration ····························································································· 38

DLDP tasks at a glance···································································································································· 39

Enabling DLDP················································································································································· 39

Setting the interval to send advertisement packets ························································································· 39

Setting the DelayDown timer···························································································································· 40

Setting the port shutdown mode ······················································································································ 40

Configuring DLDP authentication ····················································································································· 41

Display and maintenance commands for DLDP ······························································································ 41

DLDP configuration examples ························································································································· 42

Example: Configuring the auto port shutdown mode ··············································································· 42

Example: Configuring the manual port shutdown mode ·········································································· 45

Example: Configuring the hybrid port shutdown mode ············································································ 49

Configuring RRPP ······················································································· 54

About RRPP ····················································································································································· 54

RRPP networking ····································································································································· 54

RRPPDUs ················································································································································ 56

RRPP timers ············································································································································ 57

How RRPP works ····································································································································· 58

Typical RRPP networking ························································································································ 60

Protocols and standards ·························································································································· 64

Restrictions and guidelines: RRPP configuration····························································································· 64

RRPP tasks at a glance ··································································································································· 64

Prerequisites for RRPP ···································································································································· 65

Creating an RRPP domain ······························································································································· 65

Configuring control VLANs ······························································································································· 65

Configuring protected VLANs ·························································································································· 66

Configuring RRPP rings ··································································································································· 66

Prerequisites ············································································································································ 66

Configuring RRPP ports ··························································································································· 66

Configuring RRPP nodes ························································································································· 67

Activating an RRPP domain ····························································································································· 68

Configuring RRPP timers ································································································································· 69

Restrictions and guidelines for RRPP timer configuration ······································································· 69

Configuring the Hello timer and Fail timer ································································································ 69

Configuring the link-up delay timer ··········································································································· 69

Configuring RRPP fast detection ····················································································································· 70

Enabling fast detection ····························································································································· 70

Configuring fast detection timers ·············································································································· 70

Configuring an RRPP ring group······················································································································ 71

iii

Enabling SNMP notifications for RRPP············································································································ 72

Display and maintenance commands for RRPP ······························································································ 72

RRPP configuration examples ························································································································· 72

Example: Configuring a single ring ·········································································································· 72

Example: Configuring intersecting rings··································································································· 75

Example: Configuring load-balanced intersecting rings ··········································································· 81

Example: Configuring fast detection ········································································································ 92

Troubleshooting RRPP ···································································································································· 95

The primary node cannot receive Hello packets when the link state is normal········································ 95

Configuring ERPS························································································ 97

About ERPS ····················································································································································· 97

ERPS structure ········································································································································ 97

Instances ·················································································································································· 98

ERPS protocol packets ···························································································································· 98

ERPS node states ···································································································································· 99

ERPS timers ············································································································································· 99

ERPS operation mechanism ·················································································································· 100

ERPS network diagrams ························································································································ 102

Protocols and standards ························································································································ 105

Restrictions and guidelines: ERPS configuration ··························································································· 105

ERPS tasks at a glance ································································································································· 105

Prerequisites ·················································································································································· 106

Enabling ERPS globally ································································································································· 106

Configuring an ERPS ring ······························································································································ 106

Creating an ERPS ring ··························································································································· 106

Configuring ERPS ring member ports ···································································································· 107

Configuring control VLANs ····················································································································· 108

Configuring protected VLANs················································································································· 108

Configuring the node role ······················································································································· 109

Enabling ERPS for an instance ······················································································································ 109

Enabling R-APS packets to carry the ring ID in the destination MAC address ·············································· 110

Configuring R-APS packet levels ··················································································································· 110

Setting ERPS timers ······································································································································ 111

Setting the non-revertive mode ······················································································································ 111

Setting a switchover mode ····························································································································· 111

Associating a ring with a subring···················································································································· 112

Enabling flush packet transparent transmission ···························································································· 112

Associating an ERPS ring member port with a track entry ············································································ 113

Removing the MS mode and FS mode settings for an ERPS ring································································· 113

Displaying and maintaining ERPS ················································································································· 113

ERPS configuration examples ······················································································································· 114

Example: Configuring one ring ··············································································································· 114

Example: Configuring one subring ········································································································· 122

Example: Configuring one-ring multi-instance load balancing ······························································· 136

Troubleshooting ERPS··································································································································· 146

The owner node cannot receive SF packets from a faulty node when the link state is normal·············· 146

Configuring Smart Link ·············································································· 148

About Smart Link············································································································································ 148

Application scenario ······························································································································· 148

Terminology ··········································································································································· 149

How Smart Link works ··························································································································· 149

Collaboration between Smart Link and Monitor Link for port status detection ······································· 150

Collaboration between Smart Link and Track for link status detection ·················································· 150

Restrictions and guidelines: Smart Link configuration ··················································································· 151

Smart Link tasks at a glance ·························································································································· 151

Configuring a Smart Link device ···················································································································· 151

Prerequisites for Smart Link device configuration ·················································································· 151

Configuring protected VLANs for a smart link group ·············································································· 151

Configuring member ports for a smart link group ··················································································· 152

Configuring a preemption mode for a smart link group ·········································································· 152

iv

Enabling the sending of flush messages································································································ 153

Configuring collaboration between Smart Link and Track······································································ 153

Enabling an associated device to receive flush messages ············································································ 153

Display and maintenance commands for Smart Link ····················································································· 154

Smart Link configuration examples ················································································································ 154

Example: Configuring a single smart link group ····················································································· 154

Example: Configuring multiple smart link groups load sharing ······························································ 159

Example: Configuring Smart Link and Track collaboration ···································································· 163

Configuring Monitor Link ············································································ 170

About Monitor Link ········································································································································· 170

Restrictions and guidelines: Monitor Link configuration ················································································· 171

Monitor Link tasks at a glance························································································································ 171

Enabling Monitor Link globally ······················································································································· 171

Creating a monitor link group ························································································································· 171

Configuring monitor link group member interfaces ························································································ 172

Restrictions and guidelines ···················································································································· 172

Configuring monitor link group member interfaces in monitor link group view ······································· 172

Configuring monitor link group member interfaces in interface view ······················································ 172

Configuring the uplink interface threshold for triggering monitor link group state switchover ························ 173

Configuring the switchover delay for the downlink interfaces in a monitor link group ···································· 173

Display and maintenance commands for Monitor Link ·················································································· 173

Monitor Link configuration examples·············································································································· 173

Example: Configuring Monitor Link ········································································································ 173

Configuring VRRP ····················································································· 178

About VRRP ··················································································································································· 178

VRRP group ··················································································································································· 178

VRRP standard mode ···································································································································· 179

VRRP networking ··································································································································· 179

Virtual IP address and IP address owner ······························································································· 179

Router priority in a VRRP group ············································································································· 179

Preemption ············································································································································· 180

Authentication method ··························································································································· 180

VRRP timers ·········································································································································· 180

Master election ······································································································································· 181

VRRP tracking ········································································································································ 181

VRRP application ··································································································································· 182

VRRP load balancing mode ··························································································································· 183

Virtual MAC address assignment ··········································································································· 183

Virtual forwarder ····································································································································· 185

Protocols and standards ································································································································ 187

Restrictions: Hardware compatibility with VRRP···························································································· 187

Configuring IPv4 VRRP·································································································································· 187

Restrictions and guidelines: IPv4 VRRP configuration ·········································································· 187

IPv4 VRRP tasks at a glance ················································································································· 188

Specifying an IPv4 VRRP operating mode ···························································································· 188

Specifying the IPv4 VRRP version ········································································································· 188

Configuring an IPv4 VRRP group ·········································································································· 189

Specifying an IPv4 VRRP control VLAN ································································································ 191

Configuring IPv4 VRRP packet attributes ······························································································ 192

Configuring VF tracking ·························································································································· 193

Setting the packet sending mode for IPv4 VRRPv3 ··············································································· 194

Enabling periodic sending of gratuitous ARP packets for IPv4 VRRP ··················································· 194

Configuring a subordinate IPv4 VRRP group to follow a master IPv4 VRRP group ······························ 195

Setting the state transition delay timer for an IPv4 VRRP group ··························································· 196

Enabling SNMP notifications for VRRP ·································································································· 196

Enabling the isolation mode for IPv4 VRRP··························································································· 197

Display and maintenance commands for IPv4 VRRP ············································································ 197

Configuring IPv6 VRRP·································································································································· 197

Restrictions and guidelines: IPv6 VRRP configuration ·········································································· 197

IPv6 VRRP tasks at a glance ················································································································· 198

v

Specifying an IPv6 VRRP operating mode ···························································································· 198

Configuring an IPv6 VRRP group ·········································································································· 198

Specifying an IPv6 VRRP control VLAN ································································································ 200

Configuring VF tracking ·························································································································· 202

Configuring IPv6 VRRP packet attributes ······························································································ 202

Enabling periodic sending of ND packets for IPv6 VRRP ······································································ 203

Configuring a subordinate IPv6 VRRP group to follow a master IPv6 VRRP group ······························ 203

Setting the state transition delay timer for an IPv6 VRRP group ··························································· 204

Enabling the isolation mode for IPv6 VRRP··························································································· 205

Display and maintenance commands for IPv6 VRRP ············································································ 205

IPv4 VRRP configuration examples ··············································································································· 206

Example: Configuring a single VRRP group ·························································································· 206

Example: Configuring multiple VRRP groups ························································································ 209

Example: Configuring VRRP load balancing·························································································· 211

IPv6 VRRP configuration examples ··············································································································· 220

Example: Configuring a single VRRP group ·························································································· 220

Example: Configuring multiple VRRP groups ························································································ 223

Example: Configuring VRRP load balancing·························································································· 226

Troubleshooting VRRP ·································································································································· 234

An error prompt is displayed ·················································································································· 234

Multiple masters appear in a VRRP group ····························································································· 235

Fast VRRP state flapping ······················································································································· 235

Configuring BFD ························································································ 236

About BFD······················································································································································ 236

Mechanism ····················································································································································· 236

Single-hop detection and multihop detection ························································································· 237

BFD session modes ······························································································································· 237

Hardware BFD ······································································································································· 238

Supported features ································································································································· 238

Protocols and standards ························································································································ 239

Restrictions and guidelines: BFD configuration ····························································································· 239

BFD tasks at a glance ···································································································································· 239

Configuring BFD sessions in echo packet mode ··························································································· 240

About BFD session creation methods ···································································································· 240

Restrictions and guidelines ···················································································································· 240

Creating a static BFD session ················································································································ 240

Configuring detection time settings ········································································································ 242

Configuring BFD sessions in control packet mode ························································································ 242

About BFD session creation methods ···································································································· 242

Restrictions and guidelines ···················································································································· 243

Configuring the session establishment mode ························································································ 243

Configuring the detection mode ············································································································· 243

Creating a static BFD session ················································································································ 244

Configuring detection time settings ········································································································ 245

Configuring the authentication mode ····································································································· 246

Configuring the destination port number for multihop BFD control packets ··········································· 247

Configuring the notification delay timer for session establishment failures ············································ 247

Enabling the echo function ····················································································································· 248

Associating the interface state with BFD ································································································ 248

Configuring the TTL value for BFD packets ··························································································· 249

Configuring BFD session flapping suppression ····························································································· 250

Configuring a BFD template ··························································································································· 251

Enabling SNMP notifications for BFD ············································································································ 251

Display and maintenance commands for BFD ······························································································· 251

Configuring Track ······················································································ 253

About Track ···················································································································································· 253

Collaboration mechanism ······················································································································· 253

Supported detection modules ················································································································ 254

Supported application modules ·············································································································· 254

Restrictions and guidelines: Track configuration···························································································· 254

vi

Collaboration application example ················································································································· 255

Track tasks at a glance ·································································································································· 255

Associating the Track module with a detection module ················································································· 256

Associating Track with NQA ··················································································································· 256

Associating Track with BFD ··················································································································· 256

Associating Track with CFD ··················································································································· 257

Associating Track with interface management······················································································· 258

Associating Track with route management ···························································································· 259

Associating Track with LLDP ················································································································· 259

Associating Track with DRNI MAD state ································································································ 260

Associating Track with a tracked list ·············································································································· 260

Associating Track with a Boolean list ····································································································· 260

Associating Track with a percentage threshold list ················································································ 261

Associating Track with a weight threshold list ························································································ 261

Associating the Track module with an application module············································································· 262

Prerequisites for associating the Track module with an application module ····································· 262

Associating Track with VRRP ················································································································ 262

Associating Track with static routing ······································································································ 264

Associating Track with PBR ··················································································································· 265

Associating Track with Smart Link ········································································································· 267

Associating Track with VXLAN ··············································································································· 268

Associating Track with EAA ··················································································································· 268

Associating Track with ERPS ················································································································· 269

Display and maintenance commands for Track ····························································································· 269

Track configuration examples ························································································································ 270

Example: Configuring VRRP-Track-NQA collaboration ········································································· 270

Example: Configuring an echo-mode BFD session for a VRRP backup to monitor the master············· 273

Example: Configuring a control-mode BFD session for a VRRP backup to monitor the master············ 276

Example: Configuring an echo-mode BFD session for the VRRP master to monitor the uplink ············ 279

Example: Configuring a control-mode BFD session for the VRRP master to monitor the uplink ··········· 283

Example: Configuring static routing-Track-NQA collaboration ······························································· 286

Example: Configuring static routing-Track-BFD (echo mode) collaboration ·········································· 291

Example: Configuring static routing-Track-BFD (control mode) collaboration ······································· 294

Example: Configuring VRRP-Track-interface management collaboration ············································· 298

Example: Configuring VRRP-Track-route management collaboration ··················································· 300

Example: Configuring static routing-Track-LLDP collaboration······························································ 303

Example: Configuring Smart Link-Track-CFD collaboration ·································································· 307

Configuring process placement ································································· 308

About process placement······························································································································· 308

Process ·················································································································································· 308

Node ······················································································································································· 308

Process redundancy ······························································································································ 308

Process placement ································································································································· 308

Default process placement policy ·········································································································· 308

Process placement affinities ·················································································································· 309

Process placement optimization ············································································································ 309

Restrictions and guidelines: process placement configuration ······································································ 309

Process placement tasks at a glance············································································································· 310

Configuring process placement policy ··········································································································· 310

Configuring a location affinity ················································································································· 310

Configuring a location type affinity ········································································································· 310

Configuring a process affinity ················································································································· 311

Configuring a self affinity ························································································································ 311

Optimizing process placement ······················································································································· 312

Display and maintenance commands for process placement ········································································ 312

Document conventions and icons ······························································ 313

Conventions ··················································································································································· 313

Network topology icons ·································································································································· 314

vii

Support and other resources ····································································· 315

Accessing Hewlett Packard Enterprise Support····························································································· 315

Accessing updates ········································································································································· 315

Websites ················································································································································ 316

Customer self repair ······························································································································· 316

Remote support ······································································································································ 316

Documentation feedback ······················································································································· 316

Index ·········································································································· 318

1

Configuring Ethernet OAM

About Ethernet OAM

Ethernet Operation, Administration, and Maintenance (OAM) is a tool that monitors Layer 2 link

status and addresses common link-related issues on the "last mile." Ethernet OAM improves

Ethernet management and maintainability. You can use it to monitor the status of the point-to-point

link between two directly connected devices.

Major functions of Ethernet OAM

Ethernet OAM provides the following functions:

•

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

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

•

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

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

•

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

Ethernet OAMPDUs

Ethernet OAM operates on the data link layer. Ethernet OAM reports the link status by periodically

exchanging OAMPDUs between devices, so that the administrator can effectively manage the

network.

Ethernet OAMPDUs include the following types shown in Table 1.

Table 1 Functions of different types of OAMPDUs

OAMPDU type

Function

Information OAMPDU

Used for transmitting state information of an Ethernet OAM entity, including the

information about the local device and remote devices, and customized

information, to the remote Ethernet OAM entity, and maintaining OAM

connections.

Event Notification

OAMPDU Used by link monitoring to notify the remote OAM entity when it detects problems

on the link in between.

Loopback Control

OAMPDU

Used for remote loopback control. By inserting the information used to

enable/disable loopback to a loopback control OAMPDU, you can enable/disable

loopback on a remote OAM entity.

NOTE:

Throughout this document, an Ethernet OAM

-enabled port is called an Ethernet OAM entity or an

OAM entity.

How Ethernet OAM works

This section describes the working procedures of Ethernet OAM.

Ethernet OAM connection establishment

OAM connection establishment is also known as the Discovery phase, where an Ethernet OAM

entity discovers the remote OAM entity to establish a session.

2

In this phase, two connected OAM entities exchange Information OAMPDUs to advertise their OAM

configuration and capabilities to each other for a comparison. If their Loopback, link detection, and

link event settings match, the OAM entities establish an OAM connection.

An OAM entity operates in active mode or passive mode. OAM entities in active mode initiate OAM

connections, and OAM entities in passive mode wait and respond to the OAM connection requests.

To set up an OAM connection between two OAM entities, you must set at least one entity to operate

in active mode.

Table 2 shows the actions that a device can perform in different modes.

Table 2 Active Ethernet OAM mode and passive Ethernet OAM mode

Item Active Ethernet OAM mode Passive Ethernet OAM

mode

Initiating OAM Discovery Available Unavailable

Responding to OAM Discovery Available Available

Transmitting Information

OAMPDUs Available Available

Transmitting Event Notification

OAMPDUs Available Available

Transmitting Information

OAMPDUs without any TLV Available Available

Transmitting Loopback Control

OAMPDUs Available Unavailable

Responding to Loopback Control

OAMPDUs Available Available

After an Ethernet OAM connection is established, the Ethernet OAM entities exchange Information

OAMPDUs at the handshake packet transmission interval to detect the availability of the Ethernet

OAM connection. If an Ethernet OAM entity receives no Information OAMPDU within the Ethernet

OAM connection timeout time, the Ethernet OAM connection is considered disconnected.

Link monitoring

Error detection in an Ethernet is difficult, especially when the physical connection in the network is

not disconnected, but network performance is degrading gradually.

Link monitoring detects link faults in various environments. Ethernet OAM entities monitor link status

by exchanging Event Notification OAMPDUs. When detecting one of the link error events listed in

Table 3, an OAM entity sends an Event Notification OAMPDU to its peer OAM entity. The network

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

Table 3 Ethernet OAM link error events

Ethernet OAM link events

Description

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

errors in the detection window (specified number of received symbols)

exceeds the predefined threshold.

Errored frame event An errored frame event occurs when the number of detected error frames

in the detection window (specified detection interval) exceeds the

predefined threshold.

Errored frame period event An errored frame period event occurs when the number of frame errors in

the detection window (specified number of received frames) exceeds the

predefined threshold.

3

Ethernet OAM link events

Description

Errored frame seconds event

An errored frame seconds event occurs when the number of errored

frame seconds (the second in which an errored frame appears is called an

errored frame second) detected on a port in the detection window

(specified detection interval) reaches the predefined threshold.

Remote fault detection

Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established

OAM connections. When traffic is interrupted due to device failure or unavailability, the Ethernet

OAM entity at the faulty end sends error information to its peer. The Ethernet OAM entity uses the

flag field in Information OAMPDUs to indicate the error information (any critical link event type as

shown in Table 4). You can use the log information to track ongoing link status and troubleshoot

problems promptly.

Table 4 Critical link events

Type Description OAMPDU transmission

frequencies

Link Fault IPL 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.

Remote loopback

Remote loopback is available only after the Ethernet OAM connection is established. With remote

loopback enabled, the Ethernet OAM entity in active mode sends non-OAMPDUs to its peer. After

receiving these frames, the peer does not forward them according to their destination addresses.

Instead, it returns them to the sender along the original path.

Remote loopback enables you to check the link status and locate link failures. Performing remote

loopback periodically helps to detect network faults promptly. Furthermore, performing remote

loopback by network segments helps to locate network faults.

Protocols and standards

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

and Physical Layer Specifications

Restrictions and guidelines: Ethernet OAM

configuration

The device's support for sending and receiving Information OAMPDUs carrying critical link events is

as follows:

•

Can receive Information OAMPDUs carrying the critical link events listed in Table 4.

•

Cannot send Information OAMPDUs carrying Link Fault events.

•

Can send Information OAMPDUs carrying Dying Gasp events when the device is rebooted or

relevant ports are manually shut down. Physical IRF ports, however, are unable to send this

type of OAMPDUs.

•

Cannot send Information OAMPDUs carrying Critical Events.

4

Ethernet OAM tasks at a glance

To configure Ethernet OAM, perform the following tasks:

1. Configuring basic Ethernet OAM functions

2. (Optional.) Configuring the Ethernet OAM connection detection timers

3. (Optional.) Configuring link event detection

 Configuring errored symbol event detection

 Configuring errored frame event detection

 Configuring errored frame period event detection

 Configuring errored frame seconds event detection

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

remote end

5. (Optional.) Configuring Ethernet OAM remote loopback

 Enabling Ethernet OAM remote loopback for a port

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

Configuring basic Ethernet OAM functions

About this task

To set up an Ethernet OAM connection between two Ethernet OAM entities, you must set at least

one entity to operate in active mode. An Ethernet OAM entity can initiate OAM connection only in

active mode.

Restrictions and guidelines

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

the port.

Procedure

1. Enter system view.

System-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Set the Ethernet OAM mode.

oam mode { active | passive }

The default is active Ethernet OAM mode.

4. Enable Ethernet OAM.

oam enable

Ethernet OAM is disabled by default.

5

Configuring the Ethernet OAM connection

detection timers

About 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.

Restrictions and guidelines for configuring Ethernet OAM

connection detection timers

When you configure Ethernet OAM, follow these restrictions and guidelines:

•

You can configure this command in system view or port view. The configuration in system view

takes effect on all ports, and the configuration in port view takes effect on the specified port. For

a port, the configuration in port view takes precedence.

•

After the timeout timer of an Ethernet OAM connection expires, the local OAM entity ages out

and terminates its connection with the peer OAM entity. To keep the Ethernet OAM connections

stable, set the connection timeout timer to be at least five times the handshake packet

transmission interval.

Configuring the Ethernet OAM connection detection timers

globally

1. Enter system view.

System-view

2. Configure the Ethernet OAM handshake packet transmission interval.

oam global timer hello interval

The default is 1000 milliseconds.

3. Configure the Ethernet OAM connection timeout timer.

oam global timer keepalive interval

The default is 5000 milliseconds.

Configuring the Ethernet OAM connection detection timers

on a port

1. Enter system view.

System-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Configure the Ethernet OAM handshake packet transmission interval.

oam timer hello interval

6

By default, an interface uses the value configured globally.

4. Configure the Ethernet OAM connection timeout timer.

oam timer keepalive interval

By default, an interface uses the value configured globally.

Configuring errored symbol event detection

Restrictions and guidelines for configuring errored symbol

event detection

You can configure this function in system view or port view. The configuration in system view takes

effect on all ports, and the configuration in port view takes effect on the specified port. For a port, the

configuration in port view takes precedence.

Configuring errored symbol event detection globally

1. Enter system view.

system-view

2. Configure the errored symbol event detection window.

oam global errored-symbol-period window window-value

By default, the errored symbol event detection window is 100000000.

3. Configure the errored symbol event triggering threshold.

oam global errored-symbol-period threshold threshold-value

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

Configuring errored symbol event detection on a port

1. Enter system view.

system-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Configure the errored symbol event detection window.

oam errored-symbol-period window window-value

By default, an interface uses the value configured globally.

4. Configure the errored symbol event triggering threshold.

oam errored-symbol-period threshold threshold-value

By default, an interface uses the value configured globally.

7

Configuring errored frame event detection

Restrictions and guidelines for configuring errored frame

event detection

You can configure this function in system view or port view. The configuration in system view takes

effect on all ports, and the configuration in port view takes effect on the specified port. For a port, the

configuration in port view takes precedence.

Configuring errored frame event detection globally

1. Enter system view.

system-view

2. Configure the errored frame event detection window.

oam global errored-frame window window-value

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

3. Configure the errored frame event triggering threshold.

oam global errored-frame threshold threshold-value

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

Configuring errored frame event detection on a port

1. Enter system view.

system-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Configure the errored frame event detection window.

oam errored-frame window window-value

By default, an interface uses the value configured globally.

4. Configure the errored frame event triggering threshold.

oam errored-frame threshold threshold-value

By default, an interface uses the value configured globally.

Configuring errored frame period event detection

Restrictions and guidelines for configuring errored frame

period event detection

You can configure this function in system view or port view. The configuration in system view takes

effect on all ports, and the configuration in port view takes effect on the specified port. For a port, the

configuration in port view takes precedence.

Configuring errored frame period event detection globally

1. Enter system view.

8

system-view

2. Configure the errored frame period event detection window.

oam global errored-frame-period window window-value

By default, the errored frame period event detection window is 10000000.

3. Configure the errored frame period event triggering threshold.

oam global errored-frame-period threshold threshold-value

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

Configuring errored frame period event detection on a port

1. Enter system view.

system-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Configure the errored frame period event detection window.

oam errored-frame-period window window-value

By default, an interface uses the value configured globally.

4. Configure the errored frame period event triggering threshold.

oam errored-frame-period threshold threshold-value

By default, an interface uses the value configured globally.

Configuring errored frame seconds event

detection

Restrictions and guidelines for configuring errored frame

seconds event detection

•

You can configure this function in system view or port view. The configuration in system view

takes effect on all ports, and the configuration in port view takes effect on the specified port. For

a port, the configuration in port view takes precedence.

•

Make sure the errored frame seconds triggering threshold is less than the errored frame

seconds detection window. Otherwise, no errored frame seconds event can be generated.

Configuring errored frame seconds event detection globally

1. Enter system view.

system-view

2. Configure the errored frame seconds event detection window.

oam global errored-frame-seconds window window-value

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

3. Configure the errored frame seconds event triggering threshold.

oam global errored-frame-seconds threshold threshold-value

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

9

Configuring errored frame seconds event detection on a port

1. Enter system view.

system-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Configure the errored frame seconds event detection window.

oam errored-frame-seconds window window-value

By default, an interface uses the value configured globally.

4. Configure the errored frame seconds event triggering threshold.

oam errored-frame-seconds threshold threshold-value

By default, an interface uses the value configured globally.

Configuring the action a port takes after it receives

an Ethernet OAM event from the remote end

About this task

This feature enables a port to log events and automatically terminate the OAM connection and set

the link state to down.

Procedure

1. Enter system view.

system-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Configure the action the port takes after it receives an Ethernet OAM event from the remote

end.

oam remote-failure { connection-expired | critical-event | dying-gasp

| link-fault } action error-link-down

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

Enabling Ethernet OAM remote loopback for a

port

CAUTION:

U

se this feature with caution, because enabling Ethernet OAM remote loopback impacts other

services.

About Ethernet OAM remote loopback

When you enable Ethernet OAM remote loopback on a port, the port sends Loopback Control

OAMPDUs to a remote port. After receiving the Loopback Control OAMPDUs, the remote port enters

the loopback state. The remote port then returns any packets sent from the local port except

10

OAMPDUs. By observing how many of these packets return, you can calculate the packet loss ratio

on the link and evaluate the link performance.

Restrictions and guidelines for enabling Ethernet OAM

remote loopback

•

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 go down and then come up. Ethernet

OAM remote loopback can be disabled by any of the following events:

 Disabling Ethernet OAM.

 Disabling Ethernet OAM remote loopback.

 Timeout of the Ethernet OAM connection.

•

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

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

Configuration Guide.

•

For Ethernet OAM remote loopback to work correctly, do not configure link aggregation

management VLANs. For more information about link aggregation management VLANs, see

Layer 2—LAN Switching Configuration Guide.

•

You can enable Ethernet OAM remote loopback on a specific port in user view, system view, or

Ethernet port view. The configuration effects are the same.

Enabling Ethernet OAM remote loopback for a port in system

view

1. (Optional.) Enter system view.

system-view

You can also perform this task in user view.

2. Enable Ethernet OAM remote loopback for a port.

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

By default, Ethernet OAM remote loopback is disabled.

Enabling Ethernet OAM remote loopback for a port in

interface view

1. Enter system view.

system-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Enable Ethernet OAM remote loopback on the port.

oam remote-loopback start

11

By default, Ethernet OAM remote loopback is disabled.

Rejecting the Ethernet OAM remote loopback

request from a remote port

About this task

The Ethernet OAM remote loopback feature impacts other services. To solve this problem, you can

disable a port from being controlled by the Loopback Control OAMPDUs sent by a remote port. The

local port then rejects the Ethernet OAM remote loopback request from the remote port.

Restrictions and guidelines

This feature does not affect the ongoing remote loopback test on the port. It takes effect when the

next remote loopback starts on the port.

Procedure

1. Enter system view.

system-view

2. Enter Layer 2/Layer 3 Ethernet port view.

interface interface-type interface-number

3. Reject the Ethernet OAM remote loopback request from a remote port.

oam remote-loopback reject-request

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

port.

Display and maintenance commands for Ethernet

OAM

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

Task

Command

Display information about an Ethernet OAM

connection.

display oam

{

local

|

remote

}

[ interface interface-type

interface-number

]

Display Ethernet OAM configuration.

display oam configuration

[ interface interface-type

interface-number

]

Display the statistics on critical events after an

Ethernet OAM connection is established.

display oam critical-event

[ interface interface-type

interface-number

]

Display the statistics on Ethernet OAM link error

events after an Ethernet OAM connection is

established.

display oam link-event

{

local

|

remote } [ interface interface-type

interface-number

]

Clear statistics on Ethernet OAM packets and

Ethernet OAM link error events.

reset oam

[

interface

interface-type interface-number

]

Page is loading ...

HPE JL585A Configuration Guide

This manual is also suitable for

HPE JL585A Configuration Guide

Related papers

Other documents