Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 01-CFD configuration | 246.46 KB |
Restrictions and guidelines: CFD configuration
Configuring basic CFD settings
Configuring single-ended synthetic LM
Display and maintenance commands for CFD
Example: Configuring CFD in a Layer 2 VPN (L2VPN networking)
Configuring CFD
About CFD
Connectivity Fault Detection (CFD), which conforms to IEEE 802.1ag Connectivity Fault Management (CFM) and ITU-T Y.1731, is an end-to-end link layer OAM mechanism. CFD is used for link connectivity detection, fault verification, and fault location in MPLS Layer 2 VPNs. For information about MPLS Layer 2 VPNs, see MPLS L2VPN and VPLS in MPLS Configuration Guide.
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.
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.
In an MPLS Layer 2 VPN, an MA can only serve the specified cross-connect or virtual switch instance (VSI).
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). Only MEPs are supported in the current software version.
MEPs define the boundary of the MA. Each MEP is identified by a MEP ID.
In an MPLS Layer 2 VPN, the MA to which a MEP belongs defines the cross-connect or VSI of packets sent by the MEP.
MEPs include inward-facing MEPs and outward-facing MEPs:
· An inward-facing MEP does not send packets to its host port. Rather, it sends packets to other ports on the device. The packets are broadcast in the cross-connect or VSI to which the MEP belongs. Only inward-facing MEPs are supported in the current software version.
· An outward-facing MEP sends packets to its host port.
MEP list
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 might not carry the RDI flag bits in CCMs.
CFD levels
MD levels
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 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.
|
|
NOTE: This section assumes that physical links between devices are in good condition. |
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.
MA and MP levels
The level of an MA equals the level of the MD to which the MA belongs.
The level of a MEP equals the level of the MD to which the MEP belongs.
Packet processing of MPs
A MEP forwards packets at a higher level without any processing and only processes packets of its level or lower.
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 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 time, 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 device can send and receive unicast LBM frames, and can receive multicast LBM frames but cannot send 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 sends back linktrace reply messages (LTRs) 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.
LM
The loss measurement (LM) function measures the frame loss between a pair of MEPs, including the following types:
· One-way LM—The source MEP sends loss measurement messages (LMMs) to the target MEP. The target MEP responds with loss measurement replies (LMRs). The source MEP calculates the number of lost frames according to the counter values of the two consecutive LMRs (the current LMR and the previous LMR). LMMs and LMRs are unicast frames.
The one-way LM function can be implemented in one of the following ways:
¡ Short-period LM—The source MEP sends a configurable number of LMMs at a configurable interval. The test result is printed when the test ends.
¡ Continual LM—The source MEP continually sends LMMs at a configurable interval until continual LM is administratively disabled. To view the test result, use the display cfd slm history command on the target MEP.
¡ Scheduled LM—Performs one-way LM based on the specified duration. The source MEP sends LMMs at a configurable interval until the specified duration timer expires. To view the test result, use the display cfd slm history command on the target MEP.
· Two-way LM—The source MEP sends CCMs to the target MEP. The target MEP responds with CCMs. The source MEP calculates the number of lost frames according to the counter values of the two consecutive CCMs received (the current CCM and the previous CCM).
The two-way LM function is implemented as continual LM. The number of frames received and the number of frames sent are padded in the CCMs sent by the source MEP. After you disable two-way LM, the device no longer pads the number of frames received or sent in the CCMs. To view the test result, use the display cfd dlm history command on the target MEP.
· Single-ended synthetic LM—The source MEP sends single loss measurement messages (SLMs) to the target MEP. The target MEP responds with single loss measurement replies (SLRs). The source MEP calculates the number of lost frames according to the number of sent SLMs and the number of received SLRs. SLMs and SLRs are unicast frames.
The single-ended synthetic LM function can be implemented in one of the following ways:
¡ Short-period LM—The source MEP sends a configurable number of SLMs at a configurable interval. The test result is printed when the test ends.
¡ Continual LM—The source MEP continually sends SLMs at a configurable interval until continual LM is administratively disabled. To view the test result, use the display cfd synthetic-slm history command on the target MEP.
¡ Scheduled LM—Performs single-ended synthetic LM based on the specified duration. The source MEP sends SLMs at a configurable interval until the specified duration timer expires. To view the test result, use the display cfd synthetic-slm history command on the target MEP.
DM
The DM function measures frame delays between two MEPs.
· Two-way frame delay measurement
The source MEP sends a delay measurement message (DMM), which carries the transmission 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.
¡ 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.
The two-way DM function can be implemented in one of the following ways:
¡ Short-period DM—The source MEP sends a configurable number of DMMs at a configurable interval. The test result is printed when the test ends.
¡ Continual DM—The source MEP continually sends DMMs at a configurable interval until continual DM is administratively disabled. To view the test result, use the display cfd dm two-way history command on the target MEP.
¡ Scheduled DM—Performs one-way DM based on the specified duration. The source MEP sends DMMs at a configurable interval until the specified duration timer expires. To view the test result, use the display cfd dm two-way history command on the target MEP.
Threshold alarm
The threshold alarm function monitors the transmission performance of links. The system generates an alarm when the transmission performance metric of a link crosses the specified upper limit or lower limit three times in succession.
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
Restrictions and guidelines: CFD configuration
Configure CC before you use the MEP ID of the remote MEP to configure other CFD functions. This restriction does not apply when you use the MAC address of the remote MEP to configure other CFD functions.
CFD tasks at a glance
To configure CFD, perform the following tasks:
1. Configuring basic CFD settings
a. Enabling CFD
b. Configuring service instances
b. (Optional.) Configuring LB
c. (Optional.) Configuring LT
d. (Optional.) Configuring one-way LM
e. (Optional.) Configuring two-way LM
f. (Optional.) Configuring single-ended synthetic LM
g. (Optional.) Configuring two-way DM
h. (Optional.) Configuring threshold alarm
Prerequisites for CFD
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 the devices in the same MD use the same MD name.
· Define the MA in each MD according to the VLAN, cross-connect, or VSI 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 devices in the same MA maintain the same MEP list.
Configuring basic CFD settings
Enabling CFD
1. Enter system view.
system-view
2. Enable CFD.
cfd enable
By default, CFD is disabled.
Configuring service instances
About this task
Before configuring the MEPs and MIPs, you must first configure service instances. A service instance is a set of service access points (SAPs), and belongs to an MA in an MD.
In an MPLS Layer 2 VPN, for the messages handled by the MEPs in a service instance, the MD and MA define the level attribute and cross-connect or VSI attribute, respectively.
Procedure
1. Enter system view.
system-view
2. Create an MD.
cfd md md-name [ index index-value ] level level-value [ md-id { dns dns-name | mac mac-address subnumber | none } ]
3. Create a service instance.
cfd service-instance instance-id ma-id { icc-based ma-name | integer ma-num | string ma-name } [ ma-index index-value ] md md-name { xconnect-group group-name connection connection-name | vsi vsi-name }
Configuring MEPs
About this task
CFD is implemented through various operations on MEPs. As a MEP is configured on a service instance, the MD level or cross-connect or VSI attribute of the service instance become the attributes of the MEP.
Restrictions and guidelines
In an MPLS Layer 2 VPN:
· You can configure only one inward-facing MEP for a CFD service instance.
· An inward-facing MEP can only be configured on an AC interface to detect PW or AC connectivity.
Prerequisites
Before you configure MEPs, you must configure service instances.
Configuring MEPs in an MPLS Layer 2 VPN
1. Enter system view.
system-view
2. Configure a MEP list.
cfd meplist mep-list service-instance instance-id
The created MEP must be included in the configured MEP list.
3. Enter interface view.
¡ Enter Layer 3 Ethernet interface view.
interface interface-type interface-number
¡ Enter Layer 3 Ethernet subinterface view.
interface interface-type interface-number.subnumber
4. Create a MEP.
cfd mep mep-id service-instance instance-id inbound
Configuring CFD functions
Configuring CC
About this task
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.
Table 1 CCM interval field encoding
|
CCM interval field |
Transmission interval |
Maximum CCM lifetime |
|
1 |
10/3 milliseconds |
35/3 milliseconds |
|
2 |
10 milliseconds |
35 milliseconds |
|
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 1 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. |
Restrictions and guidelines
When you configure the CCM interval, follow these restrictions and guidelines:
· Configure the same CCM interval field value for all MEPs in the same MA.
· If the device cannot process short-interval CCM messages, setting the CCM interval field value to smaller than 4 might cause the CC function to operate unsteadily.
Configuring CC in an MPLS Layer 2 VPN
1. Enter system view.
system-view
2. (Optional.) Set the CCM interval field.
cfd cc interval interval-value service-instance instance-id
By default, the interval field value is 4.
3. Enter interface view.
¡ Enter Layer 3 Ethernet interface view.
interface interface-type interface-number
¡ Enter Layer 3 Ethernet subinterface view.
interface interface-type interface-number.subnumber
4. Enable CCM sending on a MEP.
cfd cc service-instance instance-id mep mep-id enable
By default, CCM sending is enabled on a MEP.
5. Enable hardware CC on for remote MEPs.
cfd hardware-cc service-instance instance-id remote-mep mep-list
By default, hardware CC is disabled for a remote MEP.
Configuring LB
Restrictions and guidelines
This function is not supported in EVPN VPLS and VPLS networks.
Procedure
To verify the link state between the local MEP and the remote MEP, execute the following command in any view:
cfd loopback service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ number number ]
Configuring LT
About this task
LT can trace the path between source and target MEPs, and can locate link faults by automatically sending LT messages. The source MEP first sends LTM messages to the target MEP. Based on the LTR messages in response to the LTM messages, the path between the two MEPs is identified.
Restrictions and guidelines
In an MPLS Layer 2 VPN, before you configure LT on a MEP in an MA, create the cross-connect or VSI to which the MA belongs.
This function is not supported in EVPN VPLS and VPLS networks.
Procedure
1. Identify the path between a source MEP and a target MEP.
cfd linktrace service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ ttl ttl-value ] [ hw-only ]
This command is available in any view.
Configuring one-way LM
About this task
The one-way 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 target MEPs.
Restrictions and guidelines
To configure one-way LM in a Layer 2 VPN, first configure the same frame counting mode on the source MEP and target MEP.
Configuring the frame counting mode
1. Enter system view.
system-view
2. Enter interface view.
¡ Enter Layer 3 Ethernet interface view.
interface interface-type interface-number
¡ Enter Layer 3 Ethernet subinterface view.
interface interface-type interface-number.subnumber
3. Configure the frame counting mode.
cfd frame-count mode { dot1p-based | port-based }
By default, no frame counting mode is configured for LM.
This command takes effect only in Layer 2 VPNs.
Configuring short-period LM
To configure short-period LM, execute the following command in any view:
cfd slm service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ peer ip-address pw-id pw-id ] [ dot1p dot1p-value ] [ number number ] [ interval { interval | msec msec-interval } ]
Configuring continual LM
1. Enter system view.
system-view
2. Configure continual LM
cfd slm continual service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ peer ip-address pw-id pw-id ] [ dot1p dot1p-value ] [ interval { interval | msec msec-interval }][ period period ]
By default, continual LM is not configured.
Configuring scheduled LM
To configure scheduled LM, execute the following command in any view:
cfd slm duration duration-time start service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ peer ip-address pw-id pw-id ] [ dot1p dot1p-value ] [ interval { interval | msec msec-interval }]
Configuring two-way LM
About this task
The two-way LM function measures bidirectional 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.
Restrictions and guidelines
For the two-way LM function to take effect, you must configure it on both the local and peer devices.
The two-way LM detection interval is the CCM interval. Before configuring two-way LM, configure the CCM interval field value to be greater than 2.
To configure two-way LM, first configure the same frame counting mode on the source MEP and target MEP.
Procedure
1. Enter system view.
system-view
2. Enter interface view.
¡ Enter Layer 3 Ethernet interface view.
interface interface-type interface-number
¡ Enter Layer 3 Ethernet subinterface view.
interface interface-type interface-number.subnumber
3. Configure the frame counting mode.
cfd frame-count mode { dot1p-based | port-based }
By default, no frame counting mode is configured.
4. Return to system view.
quit
5. Configure continual LM
cfd dlm continual service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ peer ip-address pw-id pw-id ] [ dot1p dot1p-value ]
By default, continual LM is not configured.
Configuring single-ended synthetic LM
About this task
The single-ended synthetic LM function measures the one-way frame loss between two MEPs, including the number of sent frames, the number of lost frames, average frame loss ratio, maximum. frame loss ratio, and minimum frame loss ratio.
Restrictions and guidelines
This function is supported only in EVPN VPWS and MPLS VPWS networks.
This function does not require the configuration of the frame counting mode.
Configuring short-period LM
To configure short-period LM, execute the following command in any view:
cfd synthetic-slm service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ number number ] [ interval msec-interval ]
Configuring continual LM
1. Enter system view.
system-view
2. Configure continual LM.
cfd synthetic-slm continual service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ number number ] [ interval msec-interval ]
By default, continual LM is not configured.
Configuring scheduled LM
To configure scheduled LM, execute the following command in any view:
cfd synthetic-slm duration duration-time start service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ number number ] [ interval msec-interval ]
Configuring two-way DM
About this task
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.
Configuring short-period DM
To configure short-period DM, execute the following command in any view:
cfd dm two-way service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ peer ip-address pw-id pw-id ] [ dot1p dot1p-value ] [ number number ] [ interval interval ]
Configuring continual DM
1. Enter system view.
system-view
2. Configure continual DM.
cfd dm two-way continual service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ peer ip-address pw-id pw-id ] [ dot1p dot1p-value ] [ interval interval ]
By default, continual DM is not configured.
Configuring scheduled DM
To configure scheduled DM, execute the following command in any view:
cfd dm two-way duration duration-time start service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } [ peer ip-address pw-id pw-id ] [dot1p dot1p-value ] [ interval interval ]
Configuring threshold alarm
About this task
The threshold alarm function allows you to monitor the packet loss ratio, delay, and bit error rate of MEPs and view the monitoring results.
Restrictions and guidelines
The lower limit must be smaller than the upper limit.
Configuring threshold alarm for continual one-way LM
1. Enter system view.
system-view
2. Configure threshold alarm for continual LM.
cfd slm { far-end | near-end } threshold service-instance instance-id mep mep-id { lower-limit lower-limit | upper-limit upper-limit }
This command takes effect only after you configure continual one-way LM.
Configuring threshold alarm for continual two-way LM
1. Enter system view.
system-view
2. Configure threshold alarm for continual two-way LM.
cfd dlm { far-end | near-end } threshold service-instance instance-id mep mep-id { lower-limit lower-limit | upper-limit upper-limit }
This command takes effect only after you configure continual two-way LM.
Configuring threshold alarm for single-ended synthetic LM
1. Enter system view.
system-view
2. Configure threshold alarm for single-ended synthetic LM.
cfd synthetic-slm { far-end | near-end } threshold service-instance instance-id mep mep-id { target-mac mac-address | target-mep target-mep-id } { lower-limit lower-limit | upper-limit upper-limit }
This command takes effect only after you configure single-ended synthetic LM.
Configuring threshold alarm for continual two-way DM
1. Enter system view.
system-view
2. Configure threshold alarm for continual two-way DM.
cfd dm two-way threshold service-instance instance-id mep mep-id { lower-limit lower-limit | upper-limit upper-limit }
This command takes effect only after you configure continual two-way DM.
Display and maintenance commands for CFD
Execute display commands in any view and reset commands in user view.
|
Task |
Command |
|
Display the two-way LM result on the specified MEP. |
display cfd dlm history [ service-instance instance-id [ mep mep-id ] ] [ number number ] |
|
Display the one-way DM packet statistics. |
display cfd dm one-way statistics [ service-instance instance-id [ mep mep-id ] ] |
|
Display the two-way DM result on the specified MEP. |
display cfd dm two-way history [ service-instance instance-id [ mep mep-id ] ] [ number number ] |
|
Display the two-way DM packet statistics. |
display cfd dm two-way statistics [ service-instance instance-id [ mep mep-id ] ] |
|
Display LTR information received by a MEP. |
display cfd linktrace-reply [ service-instance instance-id [ mep mep-id ] ] |
|
Display MD configuration information. |
display cfd md |
|
Display the attribute and running information of the MEPs. |
display cfd mep mep-id service-instance instance-id |
|
Display MEP lists in a service instance. |
display cfd meplist [ service-instance instance-id ] |
|
Display MP information. |
display cfd mp [ interface interface-type interface-number ] |
|
Display information about a remote MEP. |
display cfd remote-mep service-instance instance-id mep mep-id |
|
Display service instance configuration information. |
display cfd service-instance [ instance-id ] |
|
Display the one-way LM result on the specified MEP. |
display cfd slm history [ service-instance instance-id [ mep mep-id ] ] [ number number ] |
|
Display the one-way LM packet statistics. |
display cfd slm statistics [ service-instance instance-id [ mep mep-id ] ] |
|
Display CFD status. |
display cfd status |
|
Display the single-ended synthetic LM result on the specified MEP. |
display cfd synthetic-slm history [ service-instance instance-id [ mep mep-id [ target-mac mac-address | target-mep target-mep-id ] ] ] [ number number ] |
|
Clear the two-way LM result on the specified MEP. |
reset cfd dlm history [ service-instance instance-id [ mep mep-id ] ] |
|
Clear the two-way DM result on the specified MEP. |
reset cfd dm two-way history [ service-instance instance-id [ mep mep-id ] ] |
|
Clear the one-way LM result on the specified MEP. |
reset cfd slm history [ service-instance instance-id [ mep mep-id ] ] |
|
Clear the single-ended synthetic LM result on the specified MEP. |
reset cfd synthetic-slm history [ service-instance instance-id [ mep mep-id [ target-mac mac-address | target-mep target-mep-id ] ] ] |
CFD configuration examples
Example: Configuring CFD in a Layer 2 VPN (L2VPN networking)
Network configuration
As shown in Figure 2:
· Configure a static PW between PE 1 and PE 2 to enable CE 1 and CE 2 to communicate with each other. Assume that the MAC addresses of Device A through Device D are 0010-FC01-6511, 0010-FC02-6512, 0010-FC03-6513, and 0010-FC04-6514, respectively.
· Configure GigabitEthernet 1/0/6.1 on Device A and Device B as AC interfaces, and associate them with cross-connect svc of cross-connect group vpna.
· Assign the network to MD_A (level 5). MD_A has two edge interfaces: GigabitEthernet 1/0/6.1 on Device A and GigabitEthernet 1/0/6.1 on Device B. They are both inward-facing MEPs.
· Configure CC to monitor the connectivity between the inward-facing MEPs. Configure LB to locate link faults.
· After the status information of the entire network is obtained, use LT, LM, and DM to detect link faults.
Procedure
1. Configure a static PW. (Details not shown.)
For information about configuring a static PW, see MPLS L2VPN in MPLS Configuration Guide.
2. Enable CFD:
# Enable CFD on Device A.
<DeviceA> system-view
[DeviceA] cfd enable
# Configure Device B in the same way Device A is configured. (Details not shown.)
3. Configure service instances:
# Create MD_A (level 5) on Device A, and create service instance 1 (in which the MA is identified by vpnma and serves cross-connect svc of cross-connect group vpna).
[DeviceA] cfd md MD_A level 5
[DeviceA] cfd service-instance 1 ma-id string vpnma md MD_A xconnect-group vpna connection svc
# Configure Device B in the same way Device A is configured. (Details not shown.)
4. Configure MEPs:
# On Device A, configure a MEP list in service instance 1, and create inward-facing MEP 1001 in service instance 1 on GigabitEthernet 1/0/6.1.
[DeviceA] cfd meplist 1001 2001 service-instance 1
[DeviceA] interface gigabitethernet 1/0/6.1
[DeviceA-GigabitEthernet1/0/6.1] cfd mep 1001 service-instance 1 inbound
[DeviceA-GigabitEthernet1/0/6.1] quit
# On Device B, configure a MEP list in service instance 1, and create inward-facing MEP 2001 in service instance 1 on GigabitEthernet 1/0/6.1.
[DeviceB] cfd meplist 1001 2001 service-instance 1
[DeviceB] interface gigabitethernet 1/0/6.1
[DeviceB-GigabitEthernet1/0/6.1] cfd mep 2001 service-instance 1 inbound
[DeviceB-GigabitEthernet1/0/6.1] quit
5. Configure CC:
# On Device A, enable the sending of CCM frames for MEP 1001 in service instance 1 on GigabitEthernet2/0/0.1.
[DeviceA] interface gigabitethernet 2/0/0.1
[DeviceA-GigabitEthernet2/0/0.1] cfd cc service-instance 1 mep 1001 enable
[DeviceA-GigabitEthernet2/0/0.1] cfd hardware-cc service-instance 1 remote-mep 2001
[DeviceA-GigabitEthernet2/0/0.1] quit
# On Device B, enable the sending of CCM frames for MEP 2001 in service instance 1 on GigabitEthernet2/0/0.1.
[DeviceB] interface gigabitethernet 2/0/0.1
[DeviceB-GigabitEthernet2/0/0.1] cfd cc service-instance 1 mep 2001 enable
[DeviceB-GigabitEthernet2/0/0.1] cfd hardware-cc service-instance 1 remote-mep 1001
[DeviceB-GigabitEthernet2/0/0.1] quit
6. Configure hardware CC:
# Configure hardware CC on GigabitEthernet 1/0/6.1 of Device A to enable MEP 1001 to receive CCM frames from MEP 2001.
[DeviceA] interface gigabitethernet 1/0/6.1
[DeviceA-GigabitEthernet1/0/6.1] cfd hardware-cc service-instance 1 remote-mep 2001
[DeviceA-GigabitEthernet1/0/6.1] quit
# Configure hardware CC on GigabitEthernet 1/0/6.1 of Device B to enable MEP 2001 to receive CCM frames from MEP 1001.
[DeviceB] interface gigabitethernet 1/0/6.1
[DeviceB-GigabitEthernet1/0/6.1] cfd hardware-cc service-instance 1 remote-mep 1001
[DeviceB-GigabitEthernet1/0/6.1] quit
7. Configure the frame counting mode:
# Configure the frame counting mode as port-based for GigabitEthernet 1/0/6.1 on Device A.
[DeviceA] interface gigabitethernet 1/0/6.1
[DeviceA-GigabitEthernet1/0/6.1] cfd frame-count mode port-based
[DeviceA-GigabitEthernet1/0/6.1] quit
# Configure the frame counting mode as port-based for GigabitEthernet 1/0/6.1 on Device B.
[DeviceB] interface gigabitethernet 1/0/6.1
[DeviceB-GigabitEthernet1/0/6.1] cfd frame-count mode port-based
[DeviceB-GigabitEthernet1/0/6.1] quit
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 2001 in service instance 1.
[DeviceA] cfd loopback service-instance 1 mep 1001 target-mep 2001
Loopback to MEP 2001 with the sequence number start from 1001-43404:
Reply from 0010-fc02-6512: sequence number=1001-43404 time=5ms
Reply from 0010-fc02-6512: sequence number=1001-43405 time=5ms
Reply from 0010-fc02-6512: sequence number=1001-43406 time=5ms
Reply from 0010-fc02-6512: sequence number=1001-43407 time=5ms
Reply from 0010-fc02-6512: 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 2001 in service instance 1 on Device A.
[DeviceA] cfd linktrace service-instance 1 mep 1001 target-mep 2001
Linktrace to MEP 2001 with the sequence number 1001-43462:
MAC address TTL Last MAC Relay action
0010-fc02-6512 63 0010-fc02-6512 Hit
3. Verify the one-way LM function after the CC function obtains the status information of the entire network:
# Use short-period LM to test the frame loss from MEP 1001 to MEP 2001 in service instance 1 on Device A.
[DeviceA] cfd slm service-instance 1 mep 1001 target-mep 2001
Reply from 0010-fc02-6512:
Far-end frame loss : 10 Far-end frame loss rate : 10.00%
Near-end frame loss: 20 Near-end frame loss rate: 20.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 40 Far-end frame loss rate : 40.00%
Near-end frame loss: 40 Near-end frame loss rate: 40.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 0 Far-end frame loss rate : 0.00%
Near-end frame loss: 10 Near-end frame loss rate: 10.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 30 Far-end frame loss rate : 30.00%
Near-end frame loss: 30 Near-end frame loss rate: 30.00%
Average:
Far-end frame loss : 20 Far-end frame loss rate : 20.00%
Near-end frame loss: 25 Near-end frame loss rate: 25.00%
Packet statistics:
Sent LMMs: 5 Received: 5
# Use continual LM to test the frame delay from MEP 1001 to MEP 2001 in service instance 1 on Device A.
[DeviceA] cfd slm continual service-instance 1 mep 1001 target-mep 2001
# Display the one-way LM result on MEP 1001 in service instance 1 on Device A.
[DeviceA] display cfd slm history service-instance 1 mep 1001
Total continual tests: 1
Service instance: 1
MEP ID: 1001
Send status: Testing
Test state: Active
Reply from 0010-fc02-6512:
Far-end frame loss : 10 Far-end frame loss rate : 10.00%
Near-end frame loss: 20 Near-end frame loss rate: 20.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 40 Far-end frame loss rate : 40.00%
Near-end frame loss: 40 Near-end frame loss rate: 40.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 0 Far-end frame loss rate : 0.00%
Near-end frame loss: 10 Near-end frame loss rate: 10.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 30 Far-end frame loss rate : 30.00%
Near-end frame loss: 30 Near-end frame loss rate: 30.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 20 Far-end frame loss rate : 20.00%
Near-end frame loss: 25 Near-end frame loss rate: 25.00%
Average:
Far-end frame loss : 20 Far-end frame loss rate : 20.00%
Near-end frame loss: 25 Near-end frame loss rate: 25.00%
4. Verify the two-way LM function after the CC function obtains the status information of the entire network:
# Use short-period LM to test the frame loss from MEP 1001 to MEP 2001 in service instance 1 on Device A.
[DeviceA] cfd dlm continual service-instance 1 mep 1001 target-mep 2001
# Use continual LM to test the frame loss from MEP 2001 to MEP 1001 in service instance 1 on Device B.
[DeviceB] cfd dlm continual service-instance 1 mep 2001 target-mep 1001
# Display the two-way LM result on MEP 1001 in service instance 1 on Device A.
[DeviceA] display cfd dlm history service-instance 1 mep 1001
Total continual tests: 1
Service instance: 1
MEP ID: 1001
Send status: Testing
Test state: Active
Reply from 0010-fc02-6512:
Far-end frame loss : 10 Far-end frame loss rate : 10.00%
Near-end frame loss: 20 Near-end frame loss rate: 20.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 40 Far-end frame loss rate : 40.00%
Near-end frame loss: 40 Near-end frame loss rate: 40.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 0 Far-end frame loss rate : 0.00%
Near-end frame loss: 10 Near-end frame loss rate: 10.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 30 Far-end frame loss rate : 30.00%
Near-end frame loss: 30 Near-end frame loss rate: 30.00%
Reply from 0010-fc02-6512:
Far-end frame loss : 20 Far-end frame loss rate : 20.00%
Near-end frame loss: 25 Near-end frame loss rate: 25.00%
Average:
Far-end frame loss : 20 Far-end frame loss rate : 20.00%
Near-end frame loss: 25 Near-end frame loss rate: 25.00%
5. Verify the two-way DM function after the CC function obtains the status information of the entire network:
# Use short-period DM to test the two-way frame delay from MEP 1001 to MEP 2001 in service instance 1 on Device A.
[DeviceA] cfd dm two-way service-instance 1 mep 1001 target-mep 2001
Frame delay:
Reply from 0010-fc02-6512: 10us
Reply from 0010-fc02-6512: 9us
Reply from 0010-fc02-6512: 11us
Reply from 0010-fc02-6512: 5us
Reply from 0010-fc02-6512: 5us
Average: 8us
Frame jitter: 1us 2us 6us 0us
Average: 2us
Packet statistics:
Sent DMMs: 5 Received: 5 Lost: 0
# Use continual DM to test the frame delay from MEP 1001 to MEP 2001 in service instance 1 on Device A.
[DeviceA] cfd dm one-way continual service-instance 1 mep 1001 target-mep 2001
# Display the two-way DM result on MEP 1001 in service instance 1 on Device A.
[DeviceA] display cfd dm two-way history service-instance 1 mep 1001
Total continual tests: 1
Service instance: 1
MEP ID: 1001
Send status: Testing
Test state: Active
Frame delay:
Reply from 0010-fc02-6512: 10us
Reply from 0010-fc02-6512: 9us
Reply from 0010-fc02-6512: 11us
Reply from 0010-fc02-6512: 5us
Reply from 0010-fc02-6512: 5us
Average: 8us
Frame jitter: 1us 2us 6us 0us
Average: 2us