HP 5900 User manual
HP 5920 & 5900 Switch Series
High Availability
Configuration Guide
Part number: 5998-5303a
Software version: Release 23xx
Document version: 6W101-20150320
Legal and notice information
© Copyright 2015 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.
i
Contents
Configuring Ethernet OAM ········································································································································· 1
Overview············································································································································································1
Major functions of Ethernet OAM ··························································································································1
Ethernet OAMPDUs··················································································································································1
How Ethernet OAM works ······································································································································1
Protocols and standards ··········································································································································3
Ethernet OAM configuration task list ······························································································································4
Configuring basic Ethernet OAM functions····················································································································4
Configuring the Ethernet OAM connection detection timers························································································4
Configuring link monitoring ·············································································································································5
Configuring errored symbol event detection ·········································································································5
Configuring errored frame event detection ···········································································································6
Configuring errored frame period event detection·······························································································7
Configuring errored frame seconds event detection ····························································································7
Configuring the action a port takes after it receives an Ethernet OAM event from the remote end························8
Configuring Ethernet OAM remote loopback················································································································9
Configuration guidelines ·········································································································································9
Enabling Ethernet OAM remote loopback on a specific port ·············································································9
Enabling Ethernet OAM remote loopback on the port······················································································ 10
Rejecting the Ethernet OAM remote loopback request from a remote port···················································· 10
Displaying and maintaining Ethernet OAM················································································································ 10
Ethernet OAM configuration example ························································································································· 11
Network requirements··········································································································································· 11
Configuration procedure ······································································································································ 11
Configuring CFD ························································································································································13
Overview········································································································································································· 13
Basic CFD concepts··············································································································································· 13
CFD functions························································································································································· 16
Protocols and standards ······································································································································· 16
CFD configuration task list ············································································································································ 16
Configuring basic CFD settings ···································································································································· 17
Enabling CFD························································································································································· 17
Configuring service instances ······························································································································ 17
Configuring MEPs·················································································································································· 18
Configuring MIP auto-generation rules ··············································································································· 18
Configuring CFD functions············································································································································ 19
Configuration prerequisites ·································································································································· 19
Configuring CC on MEPs ····································································································································· 19
Configuring LB on MEPs ······································································································································· 20
Configuring LT on MEPs········································································································································ 20
Displaying and maintaining CFD ································································································································· 21
CFD configuration example ·········································································································································· 21
Configuring DLDP·······················································································································································25
Overview········································································································································································· 25
Basic concepts ······················································································································································· 26
How DLDP works ··················································································································································· 27
Configuration restrictions and guidelines···················································································································· 29
DLDP configuration task list··········································································································································· 29
ii
Enabling DLDP ································································································································································ 30
Setting the interval to send advertisement packets ····································································································· 30
Setting the DelayDown timer ········································································································································ 30
Setting the port shutdown mode ··································································································································· 31
Configuring DLDP authentication·································································································································· 31
Displaying and maintaining DLDP································································································································ 32
DLDP configuration examples ······································································································································· 32
Automatically shutting down unidirectional links······························································································· 32
Manually shutting down unidirectional links ······································································································ 35
Configuring Smart Link ··············································································································································40
Smart Link overview ······················································································································································· 40
Terminology ··························································································································································· 41
How Smart Link works ·········································································································································· 41
Smart Link collaboration mechanisms ················································································································· 42
Smart Link configuration task list ·································································································································· 43
Configuring a Smart Link device ·································································································································· 43
Configuration prerequisites ·································································································································· 43
Configuring protected VLANs for a smart link group························································································ 43
Configuring member ports for a smart link group ····························································································· 44
Configuring role preemption for a smart link group·························································································· 45
Enabling the sending of flush messages ············································································································· 45
Configuring the collaboration between Smart Link and Track ········································································· 46
Configuring an associated device ······························································································································· 46
Configuration prerequisites ·································································································································· 46
Enabling the receiving of flush messages ··········································································································· 46
Displaying and maintaining Smart Link ······················································································································· 47
Smart Link configuration examples ······························································································································ 47
Single smart link group configuration example ································································································· 47
Multiple smart link groups load sharing configuration example······································································ 52
Smart Link and Track collaboration configuration example ············································································· 56
Configuring Monitor Link···········································································································································62
Overview········································································································································································· 62
Configuring Monitor Link ·············································································································································· 63
Creating a monitor link group ····························································································································· 63
Configuring monitor link group member interfaces··························································································· 63
Configuring the switchover delay for a monitor link group·············································································· 64
Displaying and maintaining Monitor Link ··················································································································· 64
Monitor Link configuration example ···························································································································· 65
Configuring VRRP·······················································································································································69
Overview········································································································································································· 69
VRRP standard mode ····················································································································································· 70
Router priority in a VRRP group ··························································································································· 70
Preemption ····························································································································································· 70
Authentication method ·········································································································································· 71
VRRP timers ···························································································································································· 71
Master election ······················································································································································ 72
VRRP tracking························································································································································· 72
VRRP application ··················································································································································· 72
VRRP load balancing mode ·········································································································································· 74
Virtual MAC address assignment ························································································································ 74
Virtual forwarder ··················································································································································· 76
Protocols and standards ················································································································································ 78
Configuring IPv4 VRRP ·················································································································································· 78
iii
IPv4 VRRP configuration task list·························································································································· 78
Specifying an IPv4 VRRP operating mode·········································································································· 79
Specifying the IPv4 VRRP version ························································································································ 79
Creating a VRRP group and assigning a virtual IP address ············································································· 79
Configuring the router priority, preemptive mode, and tracking function ······················································ 80
Configuring IPv4 VRRP packet attributes ············································································································ 81
Configuring VF tracking········································································································································ 82
Enabling SNMP notifications for VRRP················································································································ 83
Disabling an IPv4 VRRP group····························································································································· 83
Displaying and maintaining IPv4 VRRP··············································································································· 84
Configuring IPv6 VRRP ·················································································································································· 84
IPv6 VRRP configuration task list·························································································································· 84
Specifying an IPv6 VRRP operating mode·········································································································· 84
Creating a VRRP group and assigning a virtual IPv6 address ········································································· 85
Configuring the router priority, preemptive mode, and tracking function ······················································ 86
Configuring VF tracking········································································································································ 87
Configuring IPv6 VRRP packet attributes ············································································································ 87
Disabling an IPv6 VRRP group····························································································································· 88
Displaying and maintaining IPv6 VRRP··············································································································· 88
IPv4 VRRP configuration examples······························································································································· 89
Single VRRP group configuration example········································································································· 89
Multiple VRRP groups configuration example ···································································································· 92
VRRP load balancing configuration example····································································································· 94
IPv6 VRRP configuration examples·····························································································································102
Single VRRP group configuration example·······································································································102
Multiple VRRP groups configuration example ··································································································105
VRRP load balancing configuration example···································································································109
Troubleshooting VRRP··················································································································································117
An error prompt is displayed ·····························································································································117
Multiple masters appear in a VRRP group········································································································118
Fast VRRP state flapping ·····································································································································118
Configuring BFD······················································································································································ 119
Introduction to BFD·······················································································································································119
BFD session establishment ··································································································································119
BFD session modes and operating modes········································································································120
Supported features ··············································································································································120
Protocols and standards ·····································································································································121
Configuring BFD basic functions ································································································································121
Configuring echo packet mode ·························································································································121
Configuring control packet mode······················································································································122
Displaying and maintaining BFD································································································································123
Configuring Track ··················································································································································· 125
Overview·······································································································································································125
Collaboration fundamentals·······························································································································125
Collaboration application example···················································································································126
Track configuration task list·········································································································································126
Associating the Track module with a detection module···························································································127
Associating Track with NQA ·····························································································································127
Associating Track with BFD································································································································128
Associating Track with CFD ·······························································································································128
Associating Track with interface management·································································································129
Associating the Track module with an application module·····················································································129
Associating Track with VRRP······························································································································129
iv
Associating Track with static routing·················································································································131
Associating Track with PBR ································································································································132
Associating Track with Smart Link ·····················································································································133
Displaying and maintaining track entries··················································································································133
Track configuration examples·····································································································································134
VRRP-Track-NQA collaboration configuration example··················································································134
Configuring BFD for a VRRP backup to monitor the master············································································137
Configuring BFD for the VRRP master to monitor the uplinks··········································································140
Static routing-Track-NQA collaboration configuration example ····································································144
Static routing-Track-BFD collaboration configuration example·······································································148
VRRP-Track-interface management collaboration configuration example ·····················································151
Smart Link-Track-CFD collaboration configuration example ···········································································154
Configuring process placement ····························································································································· 155
Overview·······································································································································································155
Process··································································································································································155
1:N process redundancy····································································································································155
Process placement policy and optimization ·····································································································155
Configuration restrictions and guidelines··················································································································156
Process placement configuration task list ··················································································································156
Configuring process placement policy ······················································································································157
Configuring a location affinity ···························································································································157
Configuring a location type affinity···················································································································157
Configuring a process affinity····························································································································158
Configuring a self affinity···································································································································158
Optimizing process placement ···································································································································158
Displaying process placement ····································································································································159
Support and other resources ·································································································································· 160
Contacting HP ······························································································································································160
Subscription service ············································································································································160
Related information······················································································································································160
Documents····························································································································································160
Websites·······························································································································································160
Conventions ··································································································································································161
Index ········································································································································································ 163
1
Configuring Ethernet OAM
Overview
Ethernet Operation, Administration and Maintenance (OAM) is a tool that monitors Layer 2 link status
and addresses common link-related issues on the "last mile." Ethernet OAM improves Ethernet
management and maintainability. You can use it to monitor the status of the point-to-point link between
two directly connected devices.
Major functions of Ethernet OAM
Ethernet OAM provides the following functions:
•Link performance monitoring—Monitors the performance indices of a link, including packet loss,
delay, and jitter, and collects traffic statistics of various types.
•Fault detection and alarm—Checks the connectivity of a link by sending OAM protocol data units
(OAMPDUs) and reports to the network administrators when a link error occurs.
•Remote loopback—Checks link quality and locates link errors by looping back OAMPDUs.
Ethernet OAMPDUs
Ethernet OAM operates on the data link layer. Ethernet OAM reports the link status by periodically
exchanging OAMPDUs between devices, so that the administrator can effectively manage the network.
Ethernet OAMPDUs include the following types shown in Table 1.
Table 1 Functions of different types of OAMPDUs
OAMPDU 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.
NOTE:
Throughout this document, an Ethernet OAM-enabled port is called an "Ethernet OAM entity" or an
"OAM entity."
How Ethernet OAM works
This section describes the working procedures of Ethernet OAM.
2
Ethernet OAM connection establishment
Ethernet OAM connection is the basis of all the other Ethernet OAM functions. OAM connection
establishment is also known as the "Discovery phase," where an Ethernet OAM entity discovers the
remote OAM entity to establish a session.
In this phase, two connected OAM entities exchange Information OAMPDUs to advertise their OAM
configuration and capabilities to each other for a comparison. If their Loopback, link detection, and link
event settings match, the OAM entities establish an OAM connection.
An OAM entity operates in active mode or passive mode. OAM entities in active mode initiate OAM
connections, and OAM entities in passive mode wait and respond to the OAM connection requests. To
set up an OAM connection between two OAM entities, you must set at least one entity to operate in
active mode.
Table 2 shows the actions that a device can perform in different modes.
Table 2 Active Ethernet OAM mode and passive Ethernet OAM mode
Item Active Ethernet OAM mode
Passive Ethernet OAM mode
Initiating OAM Discovery Available Unavailable
Responding to OAM Discovery Available Available
Transmitting Information
OAMPDUs Available Available
Transmitting Event Notification
OAMPDUs Available Available
Transmitting Information
OAMPDUs without any TLV Available Available
Transmitting Loopback Control
OAMPDUs Available Unavailable
Responding to Loopback Control
OAMPDUs
Available when both sides are
operating in active OAM mode Available
After an Ethernet OAM connection is established, the Ethernet OAM entities exchange Information
OAMPDUs at the handshake packet transmission interval to detect the availability of the Ethernet OAM
connection. If an Ethernet OAM entity receives no Information OAMPDU within the Ethernet OAM
connection timeout time, the Ethernet OAM connection is considered disconnected.
Link monitoring
Error detection in an Ethernet is difficult, especially when the physical connection in the network is not
disconnected, but network performance is degrading gradually.
Link monitoring detects link faults in various environments. Ethernet OAM entities monitor link status by
exchanging Event Notification OAMPDUs. When detecting one of the link error events listed in Table 3,
an OAM entity sends an Event Notification OAMPDU to its peer OAM entity. The network administrator
can keep track of network status changes by retrieving the log.
Table 3 Ethernet OAM link error events
Ethernet OAM link events Descri
p
tion
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.
3
Ethernet OAM link events Descri
p
tion
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.
Errored frame seconds event
An errored frame seconds event occurs when the number of errored frame
seconds (the second in which an errored frame appears is called an
"errored frame second") detected on a port in the detection window
(specified detection interval) reaches the predefined threshold.
Remote fault detection
Information OAMPDUs are exchanged periodically among Ethernet OAM entities across established
OAM connections. In a network where traffic is interrupted due to device failures or unavailability, the
flag field defined in Information OAMPDUs allows an Ethernet OAM entity to send error information (any
critical link event type shown in Table 4) to its peer. You can use the log information to track ongoing link
status and troubleshoot problems promptly.
Table 4 Critical link events
T
yp
e Descri
p
tion OAMPDU transmission fre
q
uencies
Link Fault Peer link signal is lost. Once per second.
Dying Gasp An unexpected fault, such as power failure,
occurred. Non-stop.
Critical Event An undetermined critical event happened. Non-stop.
The switch is able to receive Information OAMPDUs carrying the critical link events listed in Table 4.
The switch is able to send Information OAMPDUs carrying Link Fault events.
The switch is able to send Information OAMPDUs carrying Dying Gasp events when the switch is
rebooted or relevant ports are manually shut down. Physical IRF ports, however, are unable to send this
type of OAMPDUs.
The switch is unable to send Information OAMPDUs carrying Critical Events.
Remote loopback
Remote loopback is available only after the Ethernet OAM connection is established. With remote
loopback enabled, the Ethernet OAM entity in active mode sends non-OAMPDUs to its peer. After
receiving these frames, the peer does not forward them according to their destination addresses. Instead,
it returns them to the sender along the original path.
Remote loopback enables you to check the link status and locate link failures. Performing remote
loopback periodically helps to detect network faults promptly. Furthermore, performing remote loopback
by network segments helps to locate network faults.
Protocols and standards
IEEE 802.3ah, Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and
Physical Layer Specifications
4
Ethernet OAM configuration task list
Tasks at a
g
lance
(Required.) Configuring basic Ethernet OAM functions
(Optional.) Configuring the Ethernet OAM connection detection timers
(Optional.) Configuring link monitoring
•Configuring errored symbol event detection
•Configuring errored frame event detection
•Configuring errored frame period event detection
•Configuring errored frame seconds event detection
(Optional.) Configuring the action a port takes after it receives an Ethernet OAM event from the remote end
(Optional.) Configuring Ethernet OAM remote loopback
•Enabling Ethernet OAM remote loopback on a specific port
•Enabling Ethernet OAM remote loopback on the port
•Rejecting the Ethernet OAM remote loopback request from a remote port
Configuring basic Ethernet OAM functions
To set up an Ethernet OAM connection between two Ethernet OAM entities, you must set at least one
entity to operate in active mode. An Ethernet OAM entity can initiate OAM connection only in active
mode.
To change the Ethernet OAM mode on an Ethernet OAM-enabled port, first disable Ethernet OAM on the
port.
To configure basic Ethernet OAM functions:
Ste
p
Command
Remarks
1. Enter system view. System-view N/A
2. Enter Layer 2 Ethernet port
view.
interface interface-type
interface-number N/A
3. Set the Ethernet OAM mode. oam mode { active | passive } The default is active Ethernet OAM
mode.
4. Enable Ethernet OAM. oam enable Ethernet OAM is disabled by
default.
Configuring the Ethernet OAM connection
detection timers
After an Ethernet OAM connection is established, the Ethernet OAM entities exchange Information
OAMPDUs at the handshake packet transmission interval to detect the availability of the Ethernet OAM
5
connection. If an Ethernet OAM entity receives no Information OAMPDU within the Ethernet OAM
connection timeout time, the Ethernet OAM connection is considered disconnected.
By adjusting the handshake packet transmission interval and the connection timeout timer, you can
change the detection time resolution for Ethernet OAM connections.
You can configure this command in system view or port view. The configuration in system view takes effect
on all ports, and the configuration in port view takes effect on the specified port. For a port, the
configuration in port view takes precedence.
After the timeout timer of an Ethernet OAM connection expires, the local OAM entity ages out its
connection with the peer OAM entity, causing the OAM connection to disconnect. To keep the Ethernet
OAM connections stable, HP recommends that you set the connection timeout timer to be at least five
times the handshake packet transmission interval.
To configure the Ethernet OAM connection detection timers globally:
Ste
p
Command
Remarks
1. Enter system view. System-view N/A
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.
To configure the Ethernet OAM connection detection timers on a port:
Ste
p
Command
Remarks
1. Enter system view. System-view N/A
2. Enter Layer 2/Layer 3 Ethernet
port view.
interface interface-type
interface-number N/A
3. Configure the Ethernet OAM
handshake packet
transmission interval.
oam timer hello interval By default, an interface uses the
value configured globally.
4. Configure the Ethernet OAM
connection timeout timer. oam timer keepalive interval By default, an interface uses the
value configured globally.
Configuring link monitoring
After Ethernet OAM connections are established, the link monitoring periods and thresholds configured
in this section automatically take effect on all Ethernet ports.
Configuring errored symbol event detection
An errored symbol event occurs when the number of detected symbol errors in the detection window
(specified number of received symbols) exceeds the predefined threshold.
You can configure this command in system view or port view. The configuration in system view takes effect
on all ports, and the configuration in port view takes effect on the specified port. For a port, the
configuration in port view takes precedence.
6
To configure errored symbol event detection globally:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Configure the errored symbol
event detection window. oam global errored-symbol-period
window window-value
By default, the errored symbol
event detection window is
100000000.
3. Configure the errored symbol
event triggering threshold. oam global errored-symbol-period
threshold threshold-value
By default, the errored symbol
event triggering threshold is 1.
To configure errored symbol event detection on a port:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3 Ethernet
port view.
interface interface-type
interface-number N/A
3. Configure the errored symbol
event detection window. oam errored-symbol-period
window window-value
By default, an interface uses the
value configured globally.
4. Configure the errored symbol
event triggering threshold. oam errored-symbol-period
threshold threshold-value
By default, an interface uses the
value configured globally.
Configuring errored frame event detection
An errored frame event occurs when the number of times that error frames in the detection window
(specified detection interval) are detected exceeds the predefined threshold.
You can configure this command in system view or port view. The configuration in system view takes effect
on all ports, and the configuration in port view takes effect on the specified port. For a port, the
configuration in port view takes precedence.
To configure errored frame event detection globally:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Configure the errored frame
event detection window. oam global errored-frame window
window-value
By default, the errored frame event
detection window is 1000
milliseconds.
3. Configure the errored frame
event triggering threshold. oam global errored-frame
threshold threshold-value
By default, the errored frame event
triggering threshold is 1.
To configure errored frame event detection on a port:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3 Ethernet
port view.
interface interface-type
interface-number N/A
7
Ste
p
Command
Remarks
3. Configure the errored frame
event detection window. oam errored-frame window
window-value
By default, an interface uses the
value configured globally.
4. Configure the errored frame
event triggering threshold. oam errored-frame threshold
threshold-value
By default, an interface uses the
value configured globally.
Configuring errored frame period event detection
An errored frame period event occurs when the number of times that frame errors in the detection window
(specified number of received frames) are detected exceeds the predefined threshold.
You can configure this command in system view or port view. The configuration in system view takes effect
on all ports, and the configuration in port view takes effect on the specified port. For a port, the
configuration in port view takes precedence.
To configure errored frame period event detection globally:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Configure the errored frame
period event detection
window.
oam global errored-frame-period
window window-value
By default, the errored frame
period event detection window is
10000000.
3. Configure the errored frame
period event triggering
threshold.
oam global errored-frame-period
threshold threshold-value
By default, the errored frame
period event triggering threshold is
1.
To configure errored frame period event detection on a port:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3 Ethernet
port view.
interface interface-type
interface-number N/A
3. Configure the errored frame
period event detection
window.
oam errored-frame-period
window window-value
By default, an interface uses the
value configured globally.
4. Configure the errored frame
period event triggering
threshold.
oam errored-frame-period
threshold threshold-value
By default, an interface uses the
value configured globally.
Configuring errored frame seconds event detection
CAUTION:
Make sure the errored frame seconds tri
gg
erin
g
threshold is less than the errored frame seconds detection
w
indow. Otherwise, no errored frame seconds event can be generated.
8
An errored frame seconds event occurs when the number of times that errored frame seconds are
detected on a port in the detection window (specified detection interval) exceeds the predefined
threshold.
You can configure this command in system view or port view. The configuration in system view takes effect
on all ports, and the configuration in port view takes effect on the specified port. For a port, the
configuration in port view takes precedence.
To configure errored frame seconds event detection globally:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Configure the errored frame
seconds event detection
window.
oam global errored-frame-seconds
window window-value
By default, the errored frame
seconds event detection window
is 60000 milliseconds.
3. Configure the errored frame
seconds event triggering
threshold.
oam global errored-frame-seconds
threshold threshold-value
By default, the errored frame
seconds event triggering
threshold is 1.
To configure errored frame seconds event detection on a port:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3 Ethernet
port view.
interface interface-type
interface-number N/A
3. Configure the errored frame
seconds event detection
window.
oam errored-frame-seconds
window window-value
By default, an interface uses the
value configured globally.
4. Configure the errored frame
seconds event triggering
threshold.
oam errored-frame-seconds
threshold threshold-value
By default, an interface uses the
value configured globally.
Configuring the action a port takes after it receives
an Ethernet OAM event from the remote end
This feature enables a port to log events and automatically terminate the OAM connection and set the
link state to down.
To configure the action the port takes after it receives an Ethernet OAM event from the remote end:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3 Ethernet
port view.
interface interface-type
interface-number N/A
9
Ste
p
Command
Remarks
3. Configure the action the port
takes after it receives an
Ethernet OAM event from the
remote end.
oam remote-failure
{ connection-expired |
critical-event | dying-gasp |
link-fault } action error-link-down
By default, the port only logs the
Ethernet OAM event it receives
from the remote end.
Configuring Ethernet OAM remote loopback
CAUTION:
Use this function with caution, because enabling Ethernet OAM remote loopback impacts other services.
When you enable Ethernet OAM remote loopback on a port, the port sends Loopback Control
OAMPDUs to a remote port, and the remote port enters the loopback state. The port then sends test
frames to the remote port. By observing how many of these test frames return, you can calculate the
packet loss ratio on the link and evaluate the link performance.
You can enable Ethernet OAM remote loopback on a specific port in user view, system view, or Layer 2
Ethernet port view. The configuration effects are the same.
Configuration guidelines
•Ethernet OAM remote loopback is available only after the Ethernet OAM connection is established,
and can be performed only by Ethernet OAM entities operating in active Ethernet OAM mode.
•Remote loopback is available only on full-duplex links that support remote loopback at both ends.
•Ethernet OAM remote loopback must be supported by both the remote port and the sending port.
•Enabling Ethernet OAM remote loopback interrupts data communications. After Ethernet OAM
remote loopback is disabled, all the ports involved will shut down and then come up. Ethernet OAM
remote loopback can be disabled by any of the following events: disabling Ethernet OAM,
disabling Ethernet OAM remote loopback, and Ethernet OAM connection timing out.
•Enabling internal loopback test on a port in remote loopback test can terminate the remote
loopback test. For more information about loopback test, see Layer 2—LAN Switching
Configuration Guide.
Enabling Ethernet OAM remote loopback on a specific port
Ste
p
Command
Remarks
1. (Optional.) Enter system view. system-view N/A
2. Enable Ethernet OAM remote
loopback on a specific port.
oam remote-loopback start
interface interface-type
interface-number
By default, Ethernet OAM remote
loopback is disabled.
This command can be executed in
user view or system view.
10
Enabling Ethernet OAM remote loopback on the port
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2/Layer 3
Ethernet port view.
interface interface-type
interface-number N/A
3. Enable Ethernet OAM remote
loopback on the port. oam remote-loopback start By default, Ethernet OAM remote
loopback is disabled.
Rejecting the Ethernet OAM remote loopback request from a
remote port
The Ethernet OAM remote loopback function impacts other services. To solve this problem, you can
disable a port from being controlled by the Loopback Control OAMPDUs sent by a remote port. The local
port then rejects the Ethernet OAM remote loopback request from the remote port.
To reject the Ethernet OAM remote loopback request from a remote port:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter Layer 2 Ethernet port
view.
interface interface-type
interface-number N/A
3. Reject the Ethernet OAM
remote loopback request from
a remote port.
oam remote-loopback
reject-request
By default, a port does not reject
the Ethernet OAM remote
loopback request from a remote
port.
This setting does not affect the
loopback test that has been
performed on the port. It takes
effect when the next loopback
starts on the port.
Displaying and maintaining Ethernet OAM
Execute display commands in any view and reset commands in user view:
Pur
p
ose 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 ]
11
Pur
p
ose Command
Display the statistics on Ethernet OAM link error
events after an Ethernet OAM connection is
established.
display oam link-event { local |remote } [ interface
interface-type interface-number ]
Clear statistics on Ethernet OAM packets and Ethernet
OAM link error events. reset oam [interface interface-type interface-number ]
Ethernet OAM configuration example
Network requirements
On the network shown in Figure 1, perform the following operations:
•Enable Ethernet OAM on Device A and Device B to auto-detect link errors between the two devices
•Determine the performance of the link between Device A and Device B by collecting statistics about
the error frames received by Device A
Figure 1 Network diagram
Configuration procedure
1. Configure Device A:
# Configure Ten-GigabitEthernet 1/0/1 to operate in active Ethernet OAM mode, and enable
Ethernet OAM for it.
<DeviceA> system-view
[DeviceA] interface ten-gigabitethernet 1/0/1
[DeviceA-Ten-GigabitEthernet1/0/1] oam mode active
[DeviceA-Ten-GigabitEthernet1/0/1] oam enable
# Set the errored frame event detection window to 20000 milliseconds, and set the errored frame
event triggering threshold to 10.
[DeviceA] oam errored-frame period 200
[DeviceA] oam errored-frame threshold 10
[DeviceA-Ten-GigabitEthernet1/0/1] quit
2. Configure Device B:
# Configure Ten-GigabitEthernet 1/0/1 to operate in passive Ethernet OAM mode (the default),
and enable Ethernet OAM for it.
<DeviceB> system-view
[DeviceB] interface ten-gigabitethernet 1/0/1
[DeviceB-Ten-GigabitEthernet1/0/1] oam mode passive
[DeviceB-Ten-GigabitEthernet1/0/1] oam enable
[DeviceB-Ten-GigabitEthernet1/0/1] quit
3. Verify the configuration:
12
Use the display oam critical-event command to display the statistics of Ethernet OAM critical link
events. For example:
# Display the statistics of Ethernet OAM critical link events on all the ports of Device A.
[DeviceA] display oam critical-event
-----------[Ten-GigabitEthernet1/0/1] -----------
Local link status : UP
Event statistics
Link fault : Not occurred
Dying gasp : Not occurred
Critical event : Not occurred
The output shows that no critical link event occurred on the link between Device A and Device B.
Use the display oam link-event command to display the statistics of Ethernet OAM link events. For
example:
# Display Ethernet OAM link event statistics of the local end of Device A.
[DeviceA] display oam link-event local
------------ [Ten-GigabitEthernet1/0/1] -----------
Link status: UP
OAM local errored frame event
Event time stamp : 5789 x 100 milliseconds
Errored frame window : 200 x 100 milliseconds
Errored frame threshold : 10 error frames
Errored frame : 13 error frames
Error running total : 350 error frames
Event running total : 17 events
The output shows that 350 errors occurred after Ethernet OAM is enabled on Device A, 17 of
which were caused by error frames. The link is instable.
13
Configuring CFD
Overview
Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault Management
(CFM), is an end-to -end per-VL AN link layer OAM mechanism. CFD is used for link connectivity detection,
fault verification, and fault location.
Basic CFD concepts
Maintenance domain
A maintenance domain (MD) defines the network or part of the network where CFD plays its role. An MD
is identified by its MD name.
To accurately locate faults, CFD introduces eight levels (from 0 to 7) to MDs. The bigger the number, the
higher the level and the larger the area covered. Domains can touch or nest (if the outer domain has a
higher level than the nested one) but cannot intersect or overlap.
MD levels facilitate fault location and make fault location more accurate. As shown in Figure 2, MD_A in
light blue nests MD_B in dark blue. If a connectivity fault is detected at the boundary of MD_A, any of
the devices in MD_A, including Device A through Device E, might fail. If a connectivity fault is also
detected at the boundary of MD_B, the failure points can be any of Device B through Device D. If the
devices in MD_B can operate correctly, at least Device C is operational.
Figure 2 Two nested MDs
CFD exchanges messages and performs operations on a per-domain basis. By planning MDs correctly
in a network, you can use CFD to rapidly locate failure points.
Maintenance association
A maintenance association (MA) is a part of an MD. You can configure multiple MAs in an MD as
needed. An MA is identified by the "MD name + MA name".
14
An MA serves the specified VLAN or no VLAN. An MA that serves a VLAN is considered carrying VLAN
attribute. An MA that serves no VLAN is considered having no VLAN attribute. An MP can receive
packets sent by other MPs in the same MA. The level of an MA equals the level of the MD that the MA
belongs to.
Maintenance point
An MP is configured on a port and belongs to an MA. MPs include the following types: maintenance
association end points (MEPs) and maintenance association intermediate points (MIPs).
•MEP
MEPs define the boundary of the MA. Each MEP is identified by a MEP ID.
The MA to which a MEP belongs defines the VLAN of packets sent by the MEP. The level of a MEP
equals the level of the MD to which the MEP belongs. The level of packets sent by a MEP equals the
level of the MEP.
The level of a MEP determines the levels of packets that the MEP can process. A MEP forwards
packets at a higher level and processes packet of its level or lower. The processing procedure is
specific to packets in the same VLAN. Packets of different VLANs are independent.
MEPs include inward-facing MEPs and outward-facing MEPs:
{An outward-facing MEP sends packets to its host port.
{An inward-facing MEP does not send packets to its host port. Rather, it sends packets to other
ports on the device.
•MIP
A MIP is internal to an MA. It cannot send CFD packets actively; however, it can handle and
respond to CFD packets. By cooperating with MEPs, a MIP can perform a function similar to ping
and traceroute. A MIP forwards packets of a different level without any processing and only
processes packet of its level.
The MA to which a MIP belongs defines the VLAN of packets that the MIP can receive. The level
of a MIP is defined by its generation rule and the MD to which the MIP belongs. MIPs are
generated on each port automatically according to related MIP generation rules:
{Default rule—If no lower-level MIP exists on an interface, a MIP is created on the current level.
A MIP can be created even if no MEP is configured on the interface.
{Explicit rule—If no lower-level MIP exists and a lower-level MEP exists on an interface, a MIP is
created on the current level. A MIP can be created only when a lower-level MEP is created on
the interface.
If a port has no MIP, the system will check the MAs in each MD (from low to high levels), and follow
the procedure as described in Figure 3 to create or not to create MIPs at the current level.
Other manuals for 5900
5
This manual suits for next models
1
Table of contents
Other HP Network Router manuals
HP
HP MSR930 Series Assembly instructions
HP
HP HP ProCurve Series 6600 User manual
HP
HP StorageWorks SR2122 User manual
HP
HP VSR1000 User manual
HP
HP 6602 User instructions
HP
HP MSR930 Series Assembly instructions
HP
HP MSR SERIES User manual
HP
HP ProCurve Networking J8454A User manual
HP
HP MSR SERIES Installation manual
HP
HP MSR954 Series User manual
HP
HP 5920 User manual
HP
HP A5500 EI Switch Series Installation manual
HP
HP R100-Series Instruction Manual
HP
HP 5920 User manual
HP
HP Pavilion a6600 User manual
HP
HP StorageWorks M2402 User manual
HP
HP PS1810-8G User manual
HP
HP ProCurve Secure Router 7203dl J8753A J8753A Assembly instructions
HP
HP A8800 Series User manual
HP
HP StorageWorks SR2122-2 How to use
