HP FlexNetwork 5130 HI High Availability Configuration Guide
HPE FlexNetwork 5130 HI Switch Series
High Availability
Configuration Guide
Part number: 5200-3603
Software version: Release 13xx
Document version: 6W100-20170315
© Copyright 2015, 2017 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements acco mpanying such
products and services. Nothing herein should be construe d as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions co ntained herein.
Confidential computer software. V alid 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 T e chnical 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 In corporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Contents
Configuring CFD ·············································································· 1
Overview ·································································································································· 1
Basic CFD concepts ············································································································ 1
CFD functions ····················································································································· 3
EAIS ································································································································· 5
Protocols and standards ······································································································· 5
CFD configuration task list ··········································································································· 5
Configuring basic CFD settings ····································································································· 6
Enabling CFD ····················································································································· 6
Configuring Ethernet service instances ···················································································· 6
Configuring MEPs ··············································································································· 7
Configuring MIP auto-generation rules ····················································································· 7
Configuring CFD functions ··········································································································· 8
Configuration prerequisites ···································································································· 8
Configuring CC ··················································································································· 8
Configuring LB ···················································································································· 9
Configuring LT ···················································································································· 9
Configuring AIS ··················································································································· 9
Configuring LM ················································································································· 10
Configuring one-way DM ····································································································· 10
Configuring two-way DM ····································································································· 11
Configuring TST ················································································································ 11
Configuring EAIS ····················································································································· 11
Displaying and maintaining CFD ································································································· 12
CFD configuration example ········································································································ 13
Configuring DLDP ·········································································· 18
Overview ································································································································ 18
Basic concepts ················································································································· 19
How DLDP works ·············································································································· 20
Configuration restrictions and guidelines ······················································································· 22
DLDP configuration task list ······································································································· 22
Enabling DLDP ························································································································ 22
Setting the interval to send advertisement packets ·········································································· 23
Setting the DelayDown timer ······································································································ 23
Setting the port shutdown mode ·································································································· 23
Configuring DLDP authentication ································································································· 24
Displaying and maintaining DLDP ································································································ 24
DLDP configuration examples ····································································································· 25
Configuring the auto port shutdown mode ··············································································· 25
Configuring the manual port shutdown mode ··········································································· 28
Configuring the hybrid port shutdown mode ············································································ 31
Configuring RRPP ·········································································· 36
Overview ································································································································ 36
Basic RRPP concepts ········································································································ 36
RRPPDUs ······················································································································· 38
RRPP timers ···················································································································· 39
How RRPP works ·············································································································· 39
Typical RRPP networking ···································································································· 40
Protocols and standards ····································································································· 43
RRPP configuration task list ······································································································· 44
Creating an RRPP domain ········································································································· 44
Configuring control VLANs ········································································································· 44
Configuring protected VLANs ····································································································· 45
Configuring RRPP rings ············································································································ 46
Configuring RRPP ports ······································································································ 46
i
Configuring RRPP nodes ···································································································· 47
Activating an RRPP domain ······································································································· 48
Configuring RRPP timers ··········································································································· 49
Configuring an RRPP ring group ································································································· 49
Enabling SNMP notifications for RRPP ························································································· 50
Displaying and maintaining RRPP ······························································································· 50
RRPP configuration examples ···································································································· 50
Single ring configuration example ························································································· 50
Intersecting ring configuration example ·················································································· 53
Dual-homed rings configuration example ················································································ 59
Load-balanced intersecting-ring configuration example ······························································ 69
Troubleshooting RRPP ·············································································································· 79
Configuring ERPS ·········································································· 80
Overview ································································································································ 80
ERPS structure ················································································································· 80
ERPS protocol packets ······································································································· 81
ERPS node states ············································································································· 82
ERPS timers ···················································································································· 82
ERPS operation mechanism ································································································ 83
ERPS network diagrams ····································································································· 85
Protocols and standards ····································································································· 87
ERPS configuration task list ······································································································· 87
Configuration prerequisites ········································································································ 88
Enabling ERPS globally ············································································································· 88
Enabling flush packet transparent transmission ·············································································· 89
Configuring an ERPS ring ·········································································································· 89
Enabling R-APS packets to carry the ring ID in the destination MAC address ········································ 89
Configuring ERPS ring member ports ··························································································· 89
Configuring ERPS ring member port attributes ········································································· 90
Configuring an ERPS ring member port ·················································································· 90
Configuring control VLANs ········································································································· 90
Configuring protected VLANs ····································································································· 91
Configuring the node role ··········································································································· 92
Enabling ERPS for an instance ··································································································· 92
Configuring R-APS packet levels ································································································· 93
Setting ERPS timers ················································································································· 93
Setting the non-revertive mode ··································································································· 93
Setting the MS mode ················································································································ 94
Setting the FS mode ················································································································· 94
Associating a ring with a subring ································································································· 94
Associating an ERPS ring member port with a track entry ································································· 94
Removing the MS mode and FS mode settings for an ERPS ring ······················································· 95
Displaying and maintaining ERPS ······························································································· 95
ERPS configuration examples ···································································································· 95
One-ring configuration example ···························································································· 95
One-subring configuration example ····················································································· 104
One-ring multi-instance load balancing configuration example ·················································· 117
Troubleshooting ERPS ············································································································ 127
Configuring Smart Link ·································································· 129
Overview ······························································································································ 129
Terminology ··················································································································· 130
How Smart Link works ······································································································ 130
Smart Link collaboration mechanisms ·················································································· 131
Smart Link configuration task list ······························································································· 132
Configuring a Smart Link device ································································································ 132
Configuration prerequisites ································································································ 132
Configuring protected VLANs for a smart link group ································································ 132
Configuring member ports for a smart link group ···································································· 133
Configuring a preemption mode for a smart link group ····························································· 134
Enabling the sending of flush messages ··············································································· 134
ii
Configuring collaboration between Smart Link and Track ························································· 134
Configuring an associated device ······························································································ 135
Configuration prerequisites ································································································ 135
Enabling the receiving of flush messages ············································································· 135
Displaying and maintaining Smart Link ······················································································· 136
Smart Link configuration examples ···························································································· 136
Single smart link group configuration example ······································································· 136
Multiple smart link groups load sharing configuration example ·················································· 141
Smart Link and Track collaboration configuration example ······················································· 145
Configuring Monitor Link ································································ 151
Overview ······························································································································ 151
Configuration restrictions and guidelines ····················································································· 152
Monitor Link configuration task list ····························································································· 152
Enabling Monitor Link globally ·································································································· 152
Creating a monitor link group ···································································································· 152
Configuring monitor link group member interfaces ········································································· 153
Configuring the uplink interface threshold for triggering monitor link group state switchover ··················· 153
Configuring the switchover delay for the downlink interfaces in a monitor link group ····························· 154
Displaying and maintaining Monitor Link ····················································································· 154
Monitor Link configuration example ···························································································· 154
Configuring BFD ·········································································· 159
Overview ······························································································································ 159
BFD session establishment and termination ·········································································· 159
BFD session modes and operating modes ············································································ 159
Supported features ·········································································································· 160
Protocols and standards ··································································································· 160
Configuring BFD basic functions ······························································································· 160
Configuring echo packet mode ··························································································· 161
Configuring control packet mode ························································································ 161
Configuring a BFD template ····································································································· 163
Enabling SNMP notifications for BFD ························································································· 164
Displaying and maintaining BFD ································································································ 164
Configuring Track ········································································· 165
Overview ······························································································································ 165
Collaboration fundamentals ······························································································· 165
Collaboration application example ······················································································· 166
Track configuration task list ······································································································ 166
Associating the Track module with a detection module ··································································· 167
Associating Track with NQA ······························································································ 167
Associating Track with BFD ······························································································· 167
Associating Track with CFD ······························································································· 168
Associating Track with interface management ······································································· 168
Associating Track with route management ············································································ 169
Associating Track with LLDP ····························································································· 169
Associating the Track module with an application module ······························································· 170
Associating Track with static routing ···················································································· 170
Associating Track with PBR ······························································································· 171
Associating Track with Smart Link ······················································································· 172
Associating Track with EAA ······························································································· 172
Associating Track with ERPS ····························································································· 173
Displaying and maintaining track entries ····················································································· 174
Track configuration examples ··································································································· 174
Static routing-Track-NQA collaboration configuration example ·················································· 174
Static routing-Track-BFD collaboration configuration example ··················································· 178
Static routing-Track-LLDP collaboration configuration example ················································· 182
Smart Link-Track-CFD collaboration configuration example ······················································ 185
Configuring process placement ······················································· 186
Overview ······························································································································ 186
iii
Process ························································································································· 186
1:N process redundancy ··································································································· 186
Process placement policy and optimization ··········································································· 186
Configuration restrictions and guidelines ····················································································· 187
Process placement configuration task list ···················································································· 187
Configuring process placement policy ························································································ 188
Configuring a location affinity ····························································································· 188
Configuring a location type affinity ······················································································· 188
Configuring a process affinity ····························································································· 189
Configuring a self affinity ··································································································· 189
Optimizing process placement ·································································································· 189
Displaying process placement ·································································································· 190
Document conventions and icons ···················································· 191
Conventions ························································································································· 191
Network topology icons ··········································································································· 192
Support and other resources ·························································· 193
Accessing Hewlett Packard Enterprise Support ············································································ 193
Accessing updates ················································································································· 193
Websites ······················································································································· 194
Customer self repair ········································································································· 194
Remote support ·············································································································· 194
Documentation feedback ·································································································· 194
Index ························································································· 196
iv
Configuring CFD
Overview
Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault
Management (CFM) and ITU-T Y.1731, is an end-to-end per-VLAN link layer OAM mechanism. CFD
is used for link connectivity detection, fault verification, and fault location.
Basic CFD concepts
Maintenance domain
A maintenance domain (M D) 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 domai n
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 1, 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 1 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.
An MA serves the specified VLAN or no VLAN. An MA that serves a VLAN is considered to be
carrying VLAN attribute. An MA that serves no VLAN is considered to be carryin g 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.
1
Maintenance point
An MP is configured on a port and bel on gs to an MA. MPs in clude 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, but 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 the following 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 2 to cre
ate or not to create MIPs at the current level.
Figure 2 Procedure of creating MIPs
Figure 3 demonstrates a grading example of the CFD module. Four levels of MDs (0, 2, 3, and 5) are
designed. The bigger the number, the higher the level and the larger the area covered. MPs are
configured on the ports of Device A through Device F. Port 1 of Device B is configured with the
following MPs:
2
• A level 5 MIP.
• A level 3 inward-facing MEP.
• A level 2 inward-facing MEP.
• A level 0 outward-facing MEP.
Figure 3 CFD grading example
Device A Device B Device C Device D Device E Device F
Port 1
5 5
5 5
MEP list
3
2 2 2 2
0 0 0 0 0 0
3
Inward-facing MEP (number is MD level)
5
Outward-facing MEP (number is MD level)
5
MIP (number is MD level)
2 2 2 2
3 3
Interface
Maintenance association
Logical path of CFD PDUs
3
A MEP list is a collection of local MEPs allowed to be configured and the remote MEPs to be
monitored in the same MA. It lists all the MEPs configured on different devices in the same MA . The
MEPs all have unique MEP IDs. When a MEP receives from a remote device a continuity check
message (CCM) carrying a MEP ID not in the MEP list of the MA, it drops the message.
The local device must send CCM messages carrying the Remote Defect Indication (RDI) flag bits.
Otherwise, the peer device cannot sense certain failures. When a local MEP has not learned all
remote MEPs in the MEP list, the MEPs in the MA do not carry the RDI flag bits in CCMs.
CFD functions
CFD functions, which are implemented through the MPs, include:
• Continuity check (CC)
• Loopback (LB)
• Linktrace (LT)
• Alarm indication signal (AIS)
• Loss measurement (LM)
• Delay measurement (DM)
• Test (TST)
Continuity check
Connectivity faults are usually caused by device faults or configuration errors. Continuity check
examines the connectivity between MEPs. This function is implemented through periodic sending of
3
CCMs by the MEPs. A CCM sent by one MEP is intended to be received by all the other MEPs in the
same MA. If a MEP fails to receive the CCMs within 3.5 times the sending interval, the link is
considered as faulty and a log is generated. When multiple MEPs send CCMs at the same ti me, the
multipoint-to-multipoint link check is achieved. CCM frames are multicast frames.
Loopback
Similar to ping at the IP layer, loopback verifies the connectivity between a source device and a
target device. To implement this function, the source MEP sends loopback messages (LBMs) to the
target MEP. Depending on whether the source MEP can receive a loopback reply message (LBR)
from the target MEP, the link state between the two can be verified.
LBM frames are multicast and unicast frames. The switch supports sending and receiving unicast
LBM frames and receiving multicast LBM frames. HPE devices do not support sending multicast
LBM frames. LBR frames are unicast frames.
Linktrace
Linktrace is similar to traceroute. It identifies the path between the source MEP and the target MP.
The source MEP sends the linktrace messages (LTMs) to the target MP. After receiving the
messages, the target MP and the MIPs that the LTM frames pass send back linktrace reply
messages (L TRs) to the source MEP. Based on the reply messages, the source MEP can identify the
path to the target MP. LTM frames are multicast frames and LTRs are unicast frames.
AIS
The AIS function suppresses the number of erro r alar ms reported by MEPs. If a local MEP do es not
receive any CCM frames from its peer MEP within 3.5 times the CCM transmission interval, it
immediately starts sending AIS frames. The AIS frames are sent periodically in the opposite direction
of CCM frames. When the peer MEP receives the AIS frames, it suppresses th e error alarms lo cally,
and continues to send the AIS frames. If the local MEP receives CCM frames within 3.5 times the
CCM transmission interval, it stops sending AIS frames and restores the error alarm function. AIS
frames are multicast frames.
LM
DM
The LM function measures the frame loss in a certain direction between a pair of MEPs. The source
MEP sends loss measurement messages (LMMs) to the target ME P. The target MEP responds with
loss measurement replies (LMRs). The source MEP calculates the numbe r of lost frames a cco rding
to the counter values of the two consecutive LMRs (the current LMR and the previous LMR). LMMs
and LMRs are unicast frames.
The DM function measures frame delays between two MEPs, including the following types:
• One-way frame delay measurement
The source MEP sends a one-way delay measurement (1DM) frame, which carries the
transmission time, to the target MEP. When the target MEP receives the 1DM frame, it does the
following:
{ Records the reception time.
{ Calculates and records the link transmission delay and jitter (delay variation) according to
the transmission time and reception time.
1DM frames are unicast frames.
• Two-way frame delay measurement
The source MEP sends a delay measurement message (DMM), which carries the transmi ssion
time, to the target MEP. When the target MEP receives the DMM, it responds with a delay
measurement reply (DMR). The DMR carries the reception time and transmission time of the
DMM and the transmission time of the DMR. When the source MEP receives the DMR, it does
the following:
{ Records the DMR reception time.
4
{ Calculates the link transmission delay and jitter according to the DMR reception time and
DMM transmission time.
DMM frames and DMR frames are unicast frames.
TST
The TST function tests the bit errors between two MEPs. The source MEP sends a TST frame, whi ch
carries the test pattern, such as pseudo random bit sequence (PRBS) or all-zero, to the target MEP.
When the target MEP receives the TST frame, it determines the bit errors by calculating and
comparing the content of the TST frame. TST frames are unicast frames.
EAIS
Ethernet Alarm Indication S ignal (EAIS ) enables collaboratio n between the Et hernet port status and
the AIS function. When a port on the device (not necessarily an MP) goes down, it immediately starts
to send EAIS frames periodically to suppress the error alarms. When the port goes up again, it
immediately stops sending EAIS frames. When the MEP receives the EAIS frames, it suppresses
the error alarms locally, and continues to send the EAIS frames. If a MEP receives no EAIS frames
within 3.5 times the EAIS frame transmission interval, the fault is considered cleared. The port stops
sending EAIS frames and restores the error alarm function. EAIS frames are multicast frames.
Protocols and standards
• IEEE 802.1ag, Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault
Management
• ITU-T Y.1731, OAM functions and mechanisms for Ethernet based networks
CFD configuration task list
For CFD to work correctly, design the network by performing the following tasks:
• Grade the MDs in the entire network, and define the boundary of each MD.
• Assign a name for each MD. Make sure that the devices in the same MD use the same MD
name.
• Define the MA in each MD according to the VLAN you want to monitor.
• Assign a name for each MA. Make sure that the devices in the same MA in the same MD use
the same MA name.
• Determine the MEP list of each MA in each MD. Make sure that devices in the same MA
maintain the same MEP list.
• At the edges of MD and MA, MEPs must be designed at the device port. MIPs can be designed
on devices or ports that are not at the edges.
To configure CFD, perform the following tasks:
Tasks at a glance
Configuring basic CFD settings:
• (Required.) Enabling CFD
• (Req
• (Req
• (Req
uired.) Configuring Ethernet service instances
uired.) Configuring MEPs
uired.) Configuring MIP auto-generation rules
Configuring CFD functions:
5
Tasks at a glance
• (Required.) Configuring CC
• (Optional.) Configuring LB
• (Optional.) Configuring LT
• (Optional.) Configuring AIS
• (Optional.) Configuring LM
• (Optional.) Configuring one-way DM
• (Optional.) Configuring two-way DM
• (Optional.) Configuring TST
(Optional.) Configuring EAIS
Typically, a port blocked by the spanning tree feature cannot receive or send CFD messages except
in the following cases:
• The port is configured as an outward-facing MEP.
• The port is configured as a MIP or inward-facing MEP, which can still receive and send CFD
messages except CCM messages.
For more information about the spanning tree feature, see Layer 2—LAN Switching Configuration
Guide.
Configuring basic CFD settings
Enabling CFD
Step Command Remarks
1. Enter system view.
2. Enable CFD.
system-view
cfd enable
Configuring Ethernet service instances
Before configuring the MEPs and MIPs, you must first configure Ethernet service instances. An
Ethernet service instance is a set of service access points (SAPs), and belongs to an MA in an MD.
The MD and MA define the level attribute and VLAN attribute of the messages ha ndled by the MPs in
an Ethernet service instance. The MPs of the MA that carri es no VLAN attribute do not belong to any
VLAN.
To configure an Ethernet service instance with the MD name:
Step Command Remarks
1. Enter system view.
2. Create an MD.
system-view
cfd md
md-name [
index-value ]
level
index
level-value
N/A
By default, CFD is disabled.
N/A
By default, no MDs exist.
3. Create an Ethernet service
instance.
cfd service-instance
ma-id
integer
ma-name |
[
md-name [
icc-based
{
ma-num |
ma-index
ma-name |
string
vlan-based
index-value ] md
vlan
vlan-id ]
6
instance-id
[ vlan-id ] }
By default, no Ethernet service
instance exists.
Configuring MEPs
CFD is implemented through various operations on MEPs. As a MEP is configured on an Ethernet
service instance, the MD level and VLAN attribute of the Ethernet service instance become the
attribute of the MEP.
Before creating MEPs, configure the MEP list. A MEP list is a collection of local MEPs that can be
configured in an MA and the remote MEPs to be monitored. You cannot create a MEP if the MEP ID
is not included in the MEP list of the Ethernet service instance.
You can specify an interface as the MEP for only one of the non-VLAN-specific MAs at the same
level. In addition, the MEP must be outward facing.
If a MEP in a non-VLAN-specific MA does not re ceive a CCM message within 3.5 CCM intervals fro m
a remote MEP, the local MEP sets its interface to link down state. This behavior of the local MEP
facilitates fast switchover for RRPP or Smart Link.
To configure a MEP:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Configure a MEP list.
3. Enter Layer 2 Ethernet
interface view or Layer 2
aggregate interface view.
4. Create a MEP.
cfd meplist
service-instance
interface
interface-number
cfd mep
service-instance
inbound
{
mep-list
interface-type
mep-id
outbound
|
instance-id
instance-id
}
Configuring MIP auto-generation rules
As functional entities in an Ethernet service instance, MIPs respond to various CFD frames, such as
LTM and LBM frames. You can configure MIP auto-generation rules for the system to automatically
create MIPs.
Any of the following events can cause MIPs to be created or deleted after you have configured the
cfd mip-rule command:
• Enabling or disabling CFD.
• Creating or deleting MEPs on a port.
• Changes occur to the VLAN attribute of a port.
• The rule specified in the cfd mip-rule command changes.
An MA carrying no VLAN attribute is typically used to detect direct link status. The system cannot
generate MIPs for such MAs.
By default, no MEP list is
configured.
N/A
By default, no MEPs are
configured.
For an MA carrying VLAN attribute, the system does not generate MIPs if the same or a higher level
MEP exists on the interface.
To configure the rules for generating MIPs:
Step Command Remarks
1. Enter system view.
2. Configure MIP
auto-generation rules.
system-view
cfd mip-rule { default | explicit }
service-instance
7
instance-id
N/A
By default, no rules for generating
MIPs are configured, and the
system does not automatically
Step Command Remarks
Configuring CFD functions
Configuration prerequisites
Complete basic CFD settings.
Configuring CC
Configure CC before you use the MEP ID of the remote MEP to configure other CFD fun ctions. This
restriction does not apply when you use the MAC address of the remote MEP to configure other CF D
functions.
After the CC function is configured, MEPs in an MA can periodically send CCM frames to maintain
connectivity. When the lifetime of a CCM frame expires, the link to the sending MEP is considered
disconnected. When setting the CCM interval, use the settings described in Table 1.
create any MIP.
Table 1
CCM interval field encoding
CCM interval field Transmission interval Maximum CCM lifetime
3 100 milliseconds 350 milliseconds
4 1 second 3.5 seconds
5 10 seconds 35 seconds
6 60 seconds 210 seconds
7 600 seconds 2100 seconds
NOTE:
• The value range for the interval field value is 3 to 7.
• The CCM messages with an interval field value of 1 to 3 are short-interval CCM messages. The
CCM messages with an interval field value of 4 to 7 are long-interval CCM messages.
Follow these guidelines when you configure CC on a MEP:
• Configure the same CCM interval field value for all MEPs in the same MA.
• After the CCM interval field is modified, the MEP must wait for another CCM interval before
sending CCMs.
To configure CC on a MEP:
Step Command Remarks
1. Enter system view.
2. (Optional.) Set the CCM
interval field.
3. Enter Layer 2 Ethernet
interface view or Layer 2
aggregate interface view.
4. Enable CCM sending on a
MEP.
system-view
cfd cc interval
service-instance
interface
interface-number
cfd cc service-instance
instance-id
interval-value
instance-id
interface-type
mep
mep-id
8
enable
N/A
By default, the interval field value
is 4.
N/A
By default, CCM sending is
disabled on a MEP.
Configuring LB
The LB function can verify the link state between the local MEP and the remote MEP or MIP.
To configure LB on a MEP:
Task Command Remarks
Enable LB.
Configuring LT
LT can trace the path between source and target MEPs, and can locate link faults by automatically
sending LT messages. The two functions are implemented in the following way:
• Tracing path—The source MEP first sends LTM messages to the target MEP. Based on the
L TR messages in response to the LTM messages, the path between the two MEPs is identified.
• LT messages automatic sending—If the source MEP fails to receive CCM frames from the
target MEP within 3.5 times the transmission interval, it considers the link faulty. The source
MEP then sends LTM frames, with the TTL field set to the maximum value 255, to the target
MEP. Based on the returned L TRs, the fault source is located.
cfd loopback service-instance
instance-id
target-mac
{
target-mep
number
[
mep
mac-address |
target-mep-id }
number ]
mep-id
Available in any view.
IMPORTANT:
Before you configure LT on a MEP in an MA carrying VLAN attribute, create the VLAN to which the
MA belongs.
To configure LT on MEPs:
Step Command Remarks
1. Identify the path between a
source MEP and a target
MEP.
2. Enter system view.
3. Enable LT messages
automatic sending.
Configuring AIS
The AIS function suppresses the number of error alarms reported by MEPs.
To make a MEP in the Ethernet service instance send AIS frames, set the AIS frame transmission
level to be higher than the MD level of the MEP.
cfd linktrace service-instance
instance-id
mac-address |
target-mep-id } [
hw-only
[
system-view
cfd linktrace auto-detection [ size
size-value ]
mep
target-mep
]
mep-id {
ttl
target-mac
ttl-value ]
Available in any view.
N/A
By default, LT messages
automatic sending is disabled.
Enable AIS and configure a correct AIS frame transmission level on the target MEP, so the target
MEP can do the following:
• Suppress the error alarms.
9
• Send the AIS frame to the MD of a higher level.
If you enable AIS but do not configure a correct AIS frame transmission level, the target MEP can
suppress the error alarms, but cannot send the AIS frames.
To configure AIS:
Step Command Remarks
1. Enter system view.
2. Enable AIS.
system-view
cfd ais enable
N/A
By default, AIS is disabled.
3. Configure the AIS frame
transmission level.
4. Configure the AIS frame
transmission interval.
Configuring LM
The LM function measures frame loss between MEPs. Frame loss statistics include the number of
lost frames, the frame loss ratio, and the average number of lost frames for the source and target
MEPs.
To configure LM:
Task Command Remarks
cfd slm service-instance
target-mac
Configure LM.
mep-id {
target-mep
dot1p-value ] [
interval ]
Configuring one-way DM
cfd ais level
service-instance
cfd ais period
service-instance
target-mep-id } [
number
level-value
period-value
instance-id
mac-address |
number ] [
instance-id
instance-id
mep
dot1p
interval
By default, the AIS frame
transmission level is not
configured.
By default, the AIS frame
transmission interval is 1 second.
Available in any view.
The one-way DM function measures the one-way frame delay between two MEPs, and monitors and
manages the link transmission performance.
One-way DM requires that the time setting at the transmitting MEP and the receiving MEP be the
same. For the purpose of frame delay variation measurement, the requirement can be relaxed.
To view the test result, use the display cfd dm one-way history command on the target MEP.
To configure one-way DM:
Task Command Remarks
cfd dm one-way
Configure one-way DM.
service-instance
mep
mep-id {
mac-address |
target-mep-id } [
target-mac
target-mep
number
10
instance-id
Available in any view.
number ]
Configuring two-way DM
The two-way DM function measures the two-way frame delay, average two-way frame delay, and
two-way frame delay variation between two MEPs. It also monitors and manages the link
transmission performance.
To configure two-way DM:
Task Command Remarks
Configure two-way DM.
Configuring TST
The TST function detects bit errors on a link, and monitors and manages the link transmission
performance.
To view the test result, use the display cfd tst command on the target MEP.
To configure TST:
cfd dm two-way
service-instance
mep
mep-id {
mac-address |
target-mep-id }
dot1p-value ] [
interval
[
target-mac
target-mep
dot1p
number
interval ]
instance-id
number ]
Available in any view.
Task Command Remarks
Configure TST.
Configuring EAIS
You can configure EAIS on a device that does not support or is not configured with CFD. However,
EAIS must collaborate with the CFD function in the network, so you must configure CFD in the
network.
To make a port send the EAIS frames, configure port status-AIS collaboration, and configure the
correct EAIS frame transmission level and interval. If you only enable port status-EAIS collaboration,
but do not configure the EAIS frame transmission level and interval, the port cannot send EAIS
frames.
If you do not specify the VLANs where the EAIS frames can be transmitted, the EAIS frames will be
transmitted in the default VLAN of the current port. Otherwise, the EAIS frames will be transmitted in
the intersection of the following VLANs:
• Specified VLANs where the EAIS frames can be transmitted.
• VLANs to which the port belongs.
cfd tst service-instance
instance-id
target-mac
{
target-mep
number
[
length-of-test
[
pattern-of-test { all-zero
[
with-crc
[
mep
mep-id
mac-address |
target-mep-id }
number ]
length ]
] ]
|
prbs
Available in any view.
}
The EAIS configuration on a member port of an aggregation group takes effect only after the
member port leaves the aggregation group.
11
If the intersection of the configured VLANs where the EAIS frames can be transmitted and the
VLANs to which the port belongs is empty, no EAIS frame is sent. If the intersection contains more
than 70 VLANs and the EAIS frame transmission interval is 1 second, the CPU u sage will be too high.
As a best practice, set the EAIS frame transmission interval to 60 seconds in this case.
To configure EAIS:
Step Command Remarks
1. Enter system view.
2. Enable port status-AIS
collaboration.
3. Enter Layer 2 Ethernet
interface view or Layer 2
aggregate interface view.
system-view
cfd ais-track link-status global
interface
interface-number
interface-type
N/A
By default, port status-AIS
collaboration is disabled.
N/A
4. Configure the EAIS frame
transmission level.
5. Configure the EAIS frame
transmission interval.
6. Specify the VLANs where
the EAIS frames can be
transmitted.
cfd ais-track link-status level
level-value
cfd ais-track link-status period
period-value
cfd ais-track link-status vlan
vlan-list
Displaying and maintaining CFD
Execute display commands in any view and reset commands in user view.
Task Command
Display the AIS configuration and information on the
specified MEP.
Display the AIS configuration and information
associated with the status of the specified port.
Display the one-way DM result on the specified
MEP.
display cfd ais
mep
[
mep-id ] ]
display cfd ais-track link-status
interface-type interface-number ]
display cfd dm one-way history
service-instance
[
By default, the EAIS frame
transmission level is not
configured.
By default, the EAIS frame
transmission interval is not
configured.
By default, the EAIS frames can
only be transmitted within the
default VLAN of the port.
service-instance
[
instance-id [
instance-id
interface
[
mep
mep-id ] ]
Display LTR information received by a MEP.
Display the content of the LTR messages received
as responses to the automatically sent LTMs.
Display MD configuration information.
Display the attribute and running information of the
MEPs.
Display MEP list in an Ethernet service instance.
Display MP information.
Display information about a remote MEP.
Display Ethernet service instance configuration
information.
12
display cfd linktrace-reply
instance-id [
display cfd linktrace-reply auto-detection [ size
size-value ]
display cfd md
display cfd mep
instance-id
display cfd meplist [ service-instance
display cfd mp [ interface
interface-number ]
display cfd remote-mep service-instance
instance-id
display cfd service-instance
mep
mep
mep-id ] ]
mep-id
mep-id
service-instance
[
service-instance
interface-type
[ instance-id ]
instance-id ]
Task Command
Display CFD status.
display cfd status
Display the TST result on the specified MEP.
Clear the one-way DM result on the specified MEP.
Clear the TST result on the specified MEP.
CFD configuration example
Network requirements
As shown in Figure 4:
• The network comprises five devices and is divided into two MDs: MD_A (level 5) and MD_B
(level 3). All ports belong to VLAN 100, and the MAs in the two MDs all serve VLAN 100.
Assume that the MAC addresses of Device A through Device E are 0010-FC01-6511,
0010-FC02-6512, 0010-FC03-6513, 0010-FC04-6514, and 0010-FC05-6515, respectively.
• MD_A has three edge ports: GigabitEthernet 1/0/1 on Device A, GigabitEthernet 1/0/3 on
Device D, and GigabitEthernet 1/0/4 on Device E. They are all inward-facing MEPs. MD_B ha s
two edge ports: GigabitEthernet 1/0/3 on Device B and GigabitEthernet 1/0/1 on Device D.
They are both outward-facing MEPs.
• In MD_A, Device B is designed to have MIPs when its port is configured with low level MEPs.
Port GigabitEthernet 1/0/3 is configured with MEPs of MD_B, and the MIPs of MD_A can be
configured on this port. You must configure the MIP generation rule of MD_A as explicit.
• The MIPs of MD_B are designed on Device C, and are configured on all ports. You must
configure the MIP generation rule as default.
• Configure CC to monitor the connectivity among all the MEPs in MD_A and MD_B. Configure
LB to locate link faults, and use the AIS and EAIS functions to suppress the error alarms that
are reported.
• After the status information of the entire network is obtained, use L T, LM, one-way DM, two-way
DM, and TST to detect link faults.
display cfd tst
mep-id ] ]
reset cfd dm one-way history
instance-id [
reset cfd tst
mep-id ] ]
service-instance
[
mep
mep-id ] ]
service-instance
[
instance-id [
service-instance
[
instance-id [
mep
mep
Figure 4 Network diagram
13
Configuration procedure
1. Configure a VLAN and assign ports to it:
On each device shown in Figure 4, cre
through GigabitEthernet 1/0/4 to VLAN 100.
2. Enable CFD:
# Enable CFD on Device A.
<DeviceA> system-view
[DeviceA] cfd enable
# Configure Device B through Device E in the same way Device A is configured. (Details not
shown.)
3. Configure Ethernet service instances:
# Create MD_A (level 5) on Device A, and create Ethernet service instance 1 (in whi ch the MA
is identified by a VLAN and serves VLAN 100).
[DeviceA] cfd md MD_A level 5
[DeviceA] cfd service-instance 1 ma-id vlan-based md MD_A vlan 100
# Configure Device E in the same way Device A is configured. (Details not shown.)
# Create MD_A (level 5) on Device B, and create Ethernet service instance 1 (in whi ch the MA
is identified by a VLAN and serves VLAN 100).
[DeviceB] cfd md MD_A level 5
[DeviceB] cfd service-instance 1 ma-id vlan-based md MD_A vlan 100
# Create MD_B (level 3), and create Ethernet service instance 2 (in which the MA is identified
by a VLAN and serves VLAN 100).
[DeviceB] cfd md MD_B level 3
[DeviceB] cfd service-instance 2 ma-id vlan-based md MD_B vlan 100
# Configure Device D in the same way Device B is configured. (Details not shown.)
# Create MD_B (level 3) on Device C, and create Ethernet service instance 2 (in which the MA
is identified by a VLAN and serves VLAN 100).
[DeviceC] cfd md MD_B level 3
[DeviceC] cfd service-instance 2 ma-id vlan-based md MD_B vlan 100
4. Configure MEPs:
# On Device A, configure a MEP list in Ethernet service instance 1, and create inward-facing
MEP 1001 in Ethernet service instance 1 on GigabitEthernet 1/0/1.
[DeviceA] cfd meplist 1001 4002 5001 service-instance 1
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] cfd mep 1001 service-instance 1 inbound
[DeviceA-GigabitEthernet1/0/1] quit
# On Device B, configure a MEP list in Ethernet service instances 1 and 2.
[DeviceB] cfd meplist 1001 4002 5001 service-instance 1
[DeviceB] cfd meplist 2001 4001 service-instance 2
# Create outward-facing MEP 2001 in Ethernet service instance 2 on GigabitEthernet 1/0/3.
[DeviceB] interface gigabitethernet 1/0/3
[DeviceB-GigabitEthernet1/0/3] cfd mep 2001 service-instance 2 outbound
[DeviceB-GigabitEthernet1/0/3] quit
# On Device D, configure a MEP list in Ethernet service instances 1 and 2.
[DeviceD] cfd meplist 1001 4002 5001 service-instance 1
[DeviceD] cfd meplist 2001 4001 service-instance 2
# Create outward-facing MEP 4001 in Ethernet service instance 2 on GigabitEthernet 1/0/1.
[DeviceD] interface gigabitethernet 1/0/1
ate VLAN 100 and assign ports GigabitEthernet 1/0/1
14
[DeviceD-GigabitEthernet1/0/1] cfd mep 4001 service-instance 2 outbound
[DeviceD-GigabitEthernet1/0/1] quit
# Create inward-facing MEP 4002 in Ethernet service instance 1 on GigabitEthernet 1/0/3.
[DeviceD] interface gigabitethernet 1/0/3
[DeviceD-GigabitEthernet1/0/3] cfd mep 4002 service-instance 1 inbound
[DeviceD-GigabitEthernet1/0/3] quit
# On Device E, configure a MEP list in Ethernet service instance 1.
[DeviceE] cfd meplist 1001 4002 5001 service-instance 1
# Create inward-facing MEP 5001 in Ethernet service instance 1 on GigabitEthernet 1/0/4.
[DeviceE] interface gigabitethernet 1/0/4
[DeviceE-GigabitEthernet1/0/4] cfd mep 5001 service-instance 1 inbound
[DeviceE-GigabitEthernet1/0/4] quit
5. Configure MIPs:
# Configure the MIP generation rule in Ethernet service instance 1 on Device B as explicit.
[DeviceB] cfd mip-rule explicit service-instance 1
# Configure the MIP generation rule in Ethernet service instance 2 on Device C as default.
[DeviceC] cfd mip-rule default service-instance 2
6. Configure CC:
# On Device A, enable the sending of CCM frames for MEP 1001 in Ethernet service instance 1
on GigabitEthernet 1/0/1.
[DeviceA] interface gigabitethernet 1/0/1
[DeviceA-GigabitEthernet1/0/1] cfd cc service-instance 1 mep 1001 enable
[DeviceA-GigabitEthernet1/0/1] quit
# On Device B, enable the sending of CCM frames for MEP 2001 in Ethernet service instance 2
on GigabitEthernet 1/0/3.
[DeviceB] interface gigabitethernet 1/0/3
[DeviceB-GigabitEthernet1/0/3] cfd cc service-instance 2 mep 2001 enable
[DeviceB-GigabitEthernet1/0/3] quit
# On Device D, enable the sending of CCM frames for MEP 4001 in Ethernet se rvice instance 2
on GigabitEthernet 1/0/1.
[DeviceD] interface gigabitethernet 1/0/1
[DeviceD-GigabitEthernet1/0/1] cfd cc service-instance 2 mep 4001 enable
[DeviceD-GigabitEthernet1/0/1] quit
# Enable the sending of CCM frames for MEP 4002 in Ethernet service instance 1 on
GigabitEthernet 1/0/3.
[DeviceD] interface gigabitethernet 1/0/3
[DeviceD-GigabitEthernet1/0/3] cfd cc service-instance 1 mep 4002 enable
[DeviceD-GigabitEthernet1/0/3] quit
# On Device E, enable the sending of CCM frames for MEP 5001 in Ethernet service instance 1
on GigabitEthernet 1/0/4.
[DeviceE] interface gigabitethernet 1/0/4
[DeviceE-GigabitEthernet1/0/4] cfd cc service-instance 1 mep 5001 enable
[DeviceE-GigabitEthernet1/0/4] quit
7. Configure AIS:
# Enable AIS on Device B. Configure the AIS frame transmission level as 5 and AIS frame
transmission interval as 1 second in Ethernet service instance 2.
[DeviceB] cfd ais enable
[DeviceB] cfd ais level 5 service-instance 2
15
[DeviceB] cfd ais period 1 service-instance 2
8. Configure EAIS:
# Enable port status-AIS collaboration on Device B.
[DeviceB] cfd ais-track link-status global
# On GigabitEthernet 1/0/3 of Device B, configure the EAIS frame transmission level as 5 and
the EAIS frame transmission interval as 60 seconds. Specify the VLANs where the EAIS frames
can be transmitted as VLAN 100.
[DeviceB] interface gigabitethernet 1/0/3
[DeviceB-GigabitEthernet1/0/3] cfd ais-track link-status level 5
[DeviceB-GigabitEthernet1/0/3] cfd ais-track link-status period 60
[DeviceB-GigabitEthernet1/0/3] cfd ais-track link-status vlan 100
Verifying the configuration
1. Verify the LB function when the CC function detects a link fault:
# Enable LB on Device A to check the status of the link between MEP 1001 and MEP 5001 in
Ethernet service instance 1.
[DeviceA] cfd loopback service-instance 1 mep 1001 target-mep 5001
Loopback to MEP 5001 with the sequence number start from 1001-43404:
Reply from 0010-fc05-6515: sequence number=1001-43404 time=5ms
Reply from 0010-fc05-6515: sequence number=1001-43405 time=5ms
Reply from 0010-fc05-6515: sequence number=1001-43406 time=5ms
Reply from 0010-fc05-6515: sequence number=1001-43407 time=5ms
Reply from 0010-fc05-6515: sequence number=1001-43408 time=5ms
Sent: 5 Received: 5 Lost: 0
2. Verify the LT function after the CC function obtains the status information of the entire network:
# Identify the path between MEP 1001 and MEP 5001 in Ethernet service instance 1 on Device
A.
[DeviceA] cfd linktrace service-instance 1 mep 1001 target-mep 5001
Linktrace to MEP 5001 with the sequence number 1001-43462:
MAC address TTL Last MAC Relay action
0010-fc05-6515 63 0010-fc02-6512 Hit
3. Verify the LM function after the CC function obtains the status information of the entire network:
# Test the frame loss from MEP 1001 to MEP 4002 in Ethernet service instance 1 on Device A.
[DeviceA] cfd slm service-instance 1 mep 1001 target-mep 4002
Reply from 0010-fc04-6514
Far-end frame loss: 10 Near-end frame loss: 20
Reply from 0010-fc04-6514
Far-end frame loss: 40 Near-end frame loss: 40
Reply from 0010-fc04-6514
Far-end frame loss: 0 Near-end frame loss: 10
Reply from 0010-fc04-6514
Far-end frame loss: 30 Near-end frame loss: 30
Average
Far-end frame loss: 20 Near-end frame loss: 25
Far-end frame loss rate: 25.00% Near-end frame loss rate: 32.00%
Send LMMs: 5 Received: 5 Lost: 0
4. Verify the one-way DM function after the CC function obtains the status information of the entire
network:
16
# Test the one-way frame delay from MEP 1001 to MEP 4002 in Ethernet service instance 1 on
Device A.
[DeviceA] cfd dm one-way service-instance 1 mep 1001 target-mep 4002
5 1DMs have been sent. Please check the result on the remote device.
# Display the one-way DM result on MEP 4002 in Ethernet service instance 1 on Device D.
[DeviceD] display cfd dm one-way history service-instance 1 mep 4002
Service instance: 1
MEP ID: 4002
Sent 1DM total number: 0
Received 1DM total number: 5
Frame delay: 10ms 9ms 11ms 5ms 5ms
Delay average: 8ms
Delay variation: 5ms 4ms 6ms 0ms 0ms
Variation average: 3ms
5. Verify the two-way DM function after the CC function obtains the status information of the entire
network:
# Test the two-way frame delay from MEP 1001 to MEP 4002 in Ethernet service instance 1 on
Device A.
[DeviceA] cfd dm two-way service-instance 1 mep 1001 target-mep 4002
Frame delay:
Reply from 0010-fc04-6514: 2406us
Reply from 0010-fc04-6514: 2215us
Reply from 0010-fc04-6514: 2112us
Reply from 0010-fc04-6514: 1812us
Reply from 0010-fc04-6514: 2249us
Average: 2158us
Sent DMMs: 5 Received: 5 Lost: 0
Frame delay variation: 191us 103us 300us 437us
Average: 257us
6. Verify the TST function after the CC function obtains the status information of the entire
network:
# Test the bit errors on the link from MEP 1001 to MEP 4002 in Ethernet service instance 1 on
Device A.
[DeviceA] cfd tst service-instance 1 mep 1001 target-mep 4002
5 TSTs have been sent. Please check the result on the remote device.
# Display the TST result on MEP 4002 in Ethernet service instance 1 on Device D.
[DeviceD] display cfd tst service-instance 1 mep 4002
Service instance: 1
MEP ID: 4002
Sent TST total number: 0
Received TST total number: 5
Received from 0010-fc01-6511, Bit True, sequence number 0
Received from 0010-fc01-6511, Bit True, sequence number 1
Received from 0010-fc01-6511, Bit True, sequence number 2
Received from 0010-fc01-6511, Bit True, sequence number 3
Received from 0010-fc01-6511, Bit True, sequence number 4
17
Configuring DLDP
Overview
A link becomes unidi rectio nal when only one end of the link can receive packets from the other end.
Unidirectional fiber links occur in the following cases:
• Fibers are cross-connected.
• A fiber is not con ne cted at one en d or one fiber of a fiber pair is broken.
Figure 5 sh
Figure 5 Correct and incorrect fiber connections
ows a correct fiber connection and two types of unidirectional fiber connections.
Physical layer detection mechanisms, such as auto-negotiation, can detect physical signals and
faults. However, they cannot detect communication failures for unidirectional links where the
physical layer is in connected state.
As a data link layer protocol, the Device Link Detection Protocol (DLDP) detects the following:
• Whether the fiber link or twisted-pair link is correctly connected at the link layer.
• Whether the two ends of the link can exchange packets correctly.
When DLDP detects unidirectional links, it can automatically shut down the faulty port to avoid
network problems. Alternatively, a user can manually shut down the faulty port. DLDP cooperates
with physical layer protocols to monitor link status and avoid physical and logical unidirectional links.
18
Basic concepts
DLDP neighbor states
If port A can receive link-layer packets from port B on the same link, port B is a DLDP neighbor of port
A. Two ports that can exchange packets are neighbors.
Table 2 DLDP neighbor states
DLDP timer Description
Confirmed The link to a DLDP neighbor is bidirectional.
Unconfirmed The state of the link to a newly discovered neighbor is not determined.
DLDP port states
A DLDP-enab led port is call ed a DLDP port. A DLDP port can have multiple neighbors, and its state
varies by the DLDP neighbor state.
Table 3 DLDP port states
State Description
Initial DLDP is enabled on the port, but is disabled globally.
Inactive DLDP is enabled on the port and globally, and the link is physically down.
Bidirectional
Unidirectional
DLDP timers
Table 4 DLDP timers
DLDP timer Description
Advertisement timer
Probe timer Probe packet sending interval. This timer is set to 1 second.
Echo timer
Entry timer
Enhanced timer
DLDP is enabled on the port and globally, and at least one neighbor in
Confirmed state exists.
DLDP is enabled on the port and globally, and no neighbor in Confirmed s tate
exists. In this state, a port does not send or receive packets other than DLDP
packets any more.
Advertisement packet sending interval (the default is 5 seconds and is
configurable).
The Echo timer is triggered when a probe is launched for a new neighbor. This
timer is set to 10 seconds.
When a new neighbor joins, a neighbor entry is created and the corresponding
entry timer is triggered if the neighbor is in Confirmed state. When an
Advertisement is received, the device updates the corresponding neighbor entry
and the Entry timer.
The setting of an Entry timer is three times that of the Advertisement timer.
The Enhanced timer is triggered, together with the Echo timer, when the Entry
timer expires. The Enhanced timer is set to 1 second.
DelayDown timer
RecoverProbe timer
If a port is physically down, the device triggers the DelayDown timer, rather than
removing the corresponding neighbor entry. The default DelayDown timer is 1
second and is configurable.
When the DelayDown timer expires, the device removes the corresponding
DLDP neighbor information if the port is down, and does not perform any
operation if the port is up.
This timer is set to 2 seconds. A port in unidirectional state regularly sends
19
DLDP timer Description
DLDP authentication mode
You can use DLDP authentication to prevent network attacks and illegal detecting.
Table 5 DLDP authentication mode
RecoverProbe packets to detect whether a unidirectional link has been restored
to bidirectional.
Authentication
mode
Non-authentication
Plaintext
authentication
MD5
authentication
Processing at the DLDP packet sending side
The sending side sets the Authentication field of DLDP
packets to 0.
The sending side sets the Authentication field to the
password configured in plain text.
The sending side encrypts the user configured password
by using MD5 algorithm, and assigns the digest to the
Authentication field.
How DLDP works
Detecting one neighbor
When two devices are connected through an optical fiber or a net work cable, enable DLDP to detect
unidirectional links to the neighbor. The following illustrates the unidirectional link detection process
in two cases:
• Unidirectional links occur before you enable DLDP.
Figure 6 Cross-connected fibers
Processing at the
DLDP packet
receiving side
The receiving side
examines the
authentication
information of received
DLDP packets and
drops packets where the
authentication
information conflicts with
the local configuration.
As shown in Figure 6, before you enable DLDP, the optical fibers between Device A and Device
B are cross-connected. After you enable DLDP, the four ports are all up and in unidirectional
state, and they send RecoverProbe packets. Take Port 1 as an example to illustrate the
unidirectional link detection process.
a. Port 1 receives the RecoverProbe packet from Port 4, and returns a RecoverEcho packet.
b. Port 4 cannot receive any RecoverEcho packet from Port 1, so Port 4 cannot become the
neighbor of Port 1.
c. Port 3 can receive the RecoverEcho packet from Port 1, but Port 3 is not the intended
destination, so Port 3 cannot become the neighbor of Port 1.
The same process occurs on the other three ports. The four ports are all in uni directional state.
• Unidirectional links occur after you enable DLDP.
20
Figure 7 Broken fiber
Correct fiber
connection
One fiber is
broken
Device A Device B
Port 1 Port 2
Device A Device B
Port 1 Port 2
Ethernet
fiber port
Tx end Rx end
Fiber link
Broken fiber
As shown in Figure 7, Device A and Device B are connected through an optical fiber. After you
enable DLDP, Port 1 and Port 2 establish the bidirectional neighborship in the following way:
a. Port 1 that is physically up enters the unidirectional state and sends a RecoverProbe
packet.
b. After receiving the RecoverProb e packet, Port 2 returns a RecoverEcho packet.
c. After Port 1 receives the RecoverEcho packet, it examines the neighbor information in the
packet. If the neighbor information matches the local information, Port 1 establishes the
neighborship with Port 2 and transits to bidirectional state. Port 1 then starts the Entry timer
and periodically sends Advertisement packets.
d. After Port 2 receives the Advertisem ent packet, it establishes the Unconfirmed neighborship
with Port 1. Port 2 then starts the Echo timer and Probe timer, and periodically sends Probe
packets.
e. After receiving the Probe packet, Port 1 returns an Echo packet.
f. After Port 2 receives the Echo packet, it examines the neighbor information in the packet. If
the neighbor information matches the local information, the neighbor state of Port 1
becomes Confirmed. Port 2 then transits to bidirectional state, starts the Entry timer, and
periodically sends Advertisement packets.
The bidirectional neighborship between Port 1 and Port 2 is now established.
After that, when Port 2's Rx end fails to receive signals, Port 2 is physically down a nd enters the
Inactive state. Because Port 2's Tx end can still send signals to Port 1, Port 1 stays up. After the
Entry timer for Port 2 expires, Port 1 starts the Enhanced timer and Echo timer, and sends a
probe packet to Port 2. Because Port 1's Tx line is broken, Port 1 cannot receive the Echo
packet from Port 2 after the Echo timer expires. Port 1 then enters the unidirectional state, an d
sends a Disable packet to Port 2. At the same time, Port 1 deletes the nei ghborship with Port 2,
and starts the RecoverProbe timer. Port 2 stays in Inactive state during this process.
When an interface is physically down, but the Tx end of the interface is still operating, DLDP
sends a LinkDown packet to inform the peer to delete the relevant neighbor entry.
Detecting multiple neighbors
When multiple devices are connected through a hub, enable DLDP on all interfaces conne cted to the
hub to detect unidirectional links among the neighbors. When no Confirmed neighbor exists, an
interface enters the unidirectional state.
21
Figure 8 Network diagram
As shown in Figure 8, Device A through Device D are connected through a hub, and enabled with
DLDP. When Ports 1, 2, and 3 detect that the link to Port 4 fails, they delete the neighborship with
Port 4, but stay in bidirectional state.
Configuration restrictions and guidelines
When you configure DLDP, follow these configuration restrictions and guidelines:
• For DLDP to operate correctly , enable DLDP on both sides and make sure the following settings
are consistent:
{ Interval to send Advertisement packets.
{ DLDP authentication mode.
{ Password.
• For DLDP to operate correctly , configure the full duplex mode for the ports at the two ends of the
link, and configure the same speed for the two ports.
DLDP configuration task list
Tasks at a glance
(Required.) Enabling DLDP
(Optional.) Setting the interval to send advertisement packets
(Optional.) Setting the DelayDown timer
(Optional.) Setting the port shutdown mode
(Optional.) Configuring DLDP authentication
Enabling DLDP
To correctly configure DLDP on the device, you must enable DLDP globally and on each port.
To enable DLDP:
22
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Enable DLDP globally.
3. Enter Ethernet interface
view.
4. Enable DLDP.
dldp global enable
interface
interface-number
dldp enable
interface-type
By default, DLDP is globally
disabled.
N/A
By default, DLDP is disabled on
an interface.
Setting the interval to send advertisement packets
To make sure DLDP can detect unidirectional links before network performance deteriorate s, set the
advertisement interval appropriate for your network environment. As a best practice, use the default
interval.
To set the Advertisement packet sending interval:
Step Command Remarks
1. Enter system view.
2. Set the interval to send
Advertisement packets.
system-view
dldp interval
interval
N/A
By default, the interval is 5
seconds.
Setting the DelayDown timer
When the Tx line fails, some ports might go down and then come up again, causing optical signal
jitters on the Rx line. To prevent the device from removing neighbor entries in such cases, set the
DelayDown timer for the device. The device starts the DelayDown timer when a port goes down due
to a Tx line failure. If the port remains down when the timer expires, the device removes the DLDP
neighbor information. If the port comes up, the device takes no action.
To set the DelayDown timer:
Step Command Remarks
1. Enter system view.
2. Set the DelayDown timer.
system-view
dldp delaydown-timer
time
Setting the port shutdown mode
On detecting a unidirectional link, DLDP shuts down the ports in on e of the following modes:
• Auto mode—When DLDP detects a unidirectional link, it shuts down the unidirectional port.
When the link becomes bidirectional, DLDP brings up the port that was shut down.
• Hybrid mode—When DLDP detects a unidirectional link, it shuts down the unidirectional port
and stops link detection. T o verify the link status, use the undo shut down command to bring up
the port. If the link becomes bidirectional, the port becomes bidirectional.
N/A
The default is 1 second.
The DelayDown timer setting
applies to all DLDP-enabled ports.
23
• Manual mode—When DLDP detects a unidirectional link, it does not shut down the port. You
must manually shut it down. When the link becomes bidirectional, you must manually bring up
the port. Use this mode to prevent normal links from being shut down because of false
unidirectional link reports in the following ca ses:
{ The network performance is low.
{ The device is busy.
{ The CPU usage is high.
To set port shutdown mode:
Step Command Remarks
1. Enter system view.
system-view
N/A
2. Set port shutdown mode.
dldp unidirectional-shutdown
auto
{
hybrid
|
manual
|
}
Configuring DLDP authentication
You can guard your network against attacks and malicious probes by configuring an appropriate
DLDP authentication mode, which can be plain text authentication or MD5 authentication. If your
network is safe, you can choose not to authenticate.
To configure DLDP authentication:
Step Command Remarks
1. Enter system view.
2. Configure a DLDP
authentication mode.
3. Configure the password for
DLDP authentication.
system-view
dldp authentication-mode
md5
none
simple
|
simple
|
}
} string
{
|
dldp authentication-password
cipher
{
The default mode is
N/A
The default authentication mode
none
is
By default, no password is
configured for DLDP
authentication.
If you do not configure the
authentication password after you
configure the authentication
mode, the authentication mode is
none
authentication mode you
configure.
.
no matter which
auto
.
Displaying and maintaining DLDP
Execute display commands in any view and the reset command in user view.
Task Command
Display the DLDP configuration globally and of a
port.
Display the statistics on DLDP packets passing
through a port.
Clear the statistics on DLDP packets passing
through a port.
24
display dldp
interface-number ]
display dldp statistics
interface-number ]
reset dldp statistics [ interface
interface-number ]
[
interface
interface-type
interface
[
interface-type
interface-type
Loading...