Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 00-S12500_CFD_Configuration_Examples | 157.01 KB |
Introduction
This document provides Connectivity Fault Detection (CFD) configuration examples.
CFD conforms to IEEE 802.1ag Connectivity Fault Management (CFM). It is an end-to-end per-VLAN link layer Operations, Administration and Maintenance (OAM) mechanism used for link connectivity detection, fault verification, and fault location.
Prerequisites
The configuration examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.
This document assumes that you have basic knowledge of H3C CFD.
Example: Configuring CFD
Network requirements
As shown in Figure 1, enable CFD on Device A, Device B, and Device C to detect link connectivity through Device A. When a link fault is detected, use the LB and LT functions to locate the fault.
Software version used
This configuration example was created and verified on S12500-CMW520-R1825P01.
Configuration restrictions and guidelines
The ports that are configured as inward-facing MEPs can be down, but the ports that are configured as outward-facing MEPs must be up.
Configuration procedures
1. Add all interfaces of Device A, Device B, and Device C to VLAN 10.
Except GE3/0/1 of Device A, all other interfaces shown in Figure 1 must be up.
2. Configure the same MD MD_TEST and MA MA_TEST on Device A, Device B, and Device C. Specify the MD level as 7, specify VLAN 10 for the MA, and create service instance 10 for the MA. Specify the MEP ID of GE3/0/1 on Device A as 1 and that of Device C as 3. Take Device A as an example to illustrate the configuration process.
<Device A> system-view
[Device A] cfd md MD_TEST level 7
[Device A] cfd ma MA_TEST md MD_TEST vlan 10
[Device A] cfd service-instance 10 md MD_TEST ma MA_TEST
[Device A] cfd meplist 1 3 service-instance 10
3. Configure GE3/0/1 of Device A as an inward-facing MEP (that sends CFD packets to other ports on the device) and that of Device C as an outward-facing MEP (that sends CFD packets to its host port). Enable MEP and CCM for the two interfaces. Configure the MIP generation rule on Device B as default.
# Configure Device A.
[Device A] interface GigabitEthernet 3/0/1
[Device A-GigabitEthernet3/0/1] cfd mep 1 service-instance 10 inbound
Please Wait...Done.
[Device A-GigabitEthernet3/0/1] cfd mep service-instance 10 mep 1 enable
[Device A-GigabitEthernet3/0/1] cfd cc service-instance 10 mep 1 enable
# Configure Device C.
[Device C] interface GigabitEthernet 3/0/1
[Device C-GigabitEthernet3/0/1] cfd mep 3 service-instance 10 outbound
Please Wait...Done.
[Device C-GigabitEthernet3/0/1] cfd mep service-instance 10 mep 3 enable
[Device C-GigabitEthernet3/0/1] cfd cc service-instance 10 mep 3 enable
# Configure Device B.
[Device B] cfd mip-rule default service-instance 10
4. Enable CFD globally on Device A, Device B, and Device C. Take Device A as an example to illustrate the configuration process.
[Device A] cfd enable
Please Wait...Done.
Verifying the configuration
1. After the whole network status is obtained with the CC function, display the status of other MEPs from the source MEP in the MA:
# Display information about remote MEP 1 in service instance 10.
[Device A] display cfd remote-mep service-instance 10 mep 1
MEP ID MAC Address State Time MAC Status
3 0001-000C-0000 OK 2011/12/06 11:37:14 UP
# After you shut down GE3/0/1 on Device B, you can see that MEP 3 is in abnormal state on Device A.
%Dec 6 15:19:00:596 2011 Device A CFD/4/CFD_LOST_CCM: MEP 1 in SI 10 failed to re
ceive CCMs from RMEP 3.
#Dec 6 15:19:00:707 2011 Device A CFD/1/FaultAlarm: -Slot=3;
Trap 1.3.111.2.802.1.1.8.0.1<dot1agCfmFaultAlarm>: MD 1(dot1agCfmMdIndex) MA 1(d
ot1agCfmMaIndex)'s MEP 1(dot1agCfmMepIdentifier) has detected the fault 3.
# Display information about remote MEP 1 in service instance 10.
[Device A] display cfd remote-mep service-instance 10 mep 1
MEP ID MAC Address State Time MAC Status
3 0001-000C-0000 FAILED 2011/12/06 15:22:14 DOWN
2. When the CC function detects a link fault, use the LB function to locate the fault:
# Enable LB on Device A to check the status of the link between MEP 1 and MEP 3 in service instance 10.
[Device A] cfd loopback service-instance 10 mep 1 target-mep 3
Loopback to 0001-000C-0000 with the sequence number start from 1-58:
Reply from 0001-000C-0000: sequence number=1-58 time=2ms
Reply from 0001-000C-0000: sequence number=1-59 time=2ms
Reply from 0001-000C-0000: sequence number=1-60 time=2ms
Reply from 0001-000C-0000: sequence number=1-61 time=3ms
Reply from 0001-000C-0000: sequence number=1-62 time=3ms
Send: 5 Received: 5 Lost: 0
# After you shut down GE3/0/1 on Device B, enable LB on Device A to check the status of the link between MEP 1 and MEP 3 in service instance 10. You can see that the link between MEP 1 and MEP 3 has failed. Use LT or a lower-level MD to further locate the fault.
[Device C] cfd loopback service-instance 10 mep 1 target-mep 3
Loopback to 0001-000C-0000 with the sequence number start from 3-0:
sequence number=3-0: Request timed out
sequence number=3-1: Request timed out
sequence number=3-2: Request timed out
sequence number=3-3: Request timed out
sequence number=3-4: Request timed out
Send: 5 Received: 0 Lost: 5
3. After the whole network status is obtained with the CC function, use the LT function to identify the paths between source and target MEPs or locate faults:
# Identify the path between MEP 1 and MEP 3 in service instance 10 on Device A.
[Device A] cfd linktrace service-instance 10 mep 1 target-mep 3
Linktrace to 0001-000C-0000 with the sequence number 1-63:
MAC Address TTL Last MAC Relay Action
000F-E212-3200 63 00E0-1A1A-0000 MPDB
0001-000C-0000 62 000F-E212-3200 Hit
# After you shut down GE3/0/1 on Device B, identify the path between MEP 1 and MEP 3 in service instance 10 on Device A. A reply is received from only the MIP configured on Device B, which means the link between Device B and Device C has failed.
[Device A] cfd linktrace service-instance 10 mep 1 target-mep 3
Linktrace to 0001-000C-0000 with the sequence number 1-63:
MAC Address TTL Last MAC Relay Action
000F-E212-3200 63 00E0-1A1A-0000 MPDB
Configuration files
· Device A
#
cfd enable
cfd md MD_TEST level 7
cfd ma MA_TEST md MD_TEST vlan 10
cfd service-instance 10 md MD_TEST ma MA_TEST
cfd meplist 1 3 service-instance 10
#
vlan 1
#
vlan 10
#
stp enable
#
interface GigabitEthernet3/0/1
port link-mode bridge
port access vlan 10
cfd mep 1 service-instance 10 inbound
cfd mep service-instance 10 mep 1 enable
cfd cc service-instance 10 mep 1 enable
#
return
· Device B
#
cfd enable
cfd md MD_TEST level 7
cfd ma MA_TEST md MD_TEST vlan 10
cfd service-instance 10 md MD_TEST ma MA_TEST
cfd mip-rule default service-instance 10
cfd meplist 1 3 service-instance 10
#
vlan 1
#
vlan 10
#
stp enable
#
interface GigabitEthernet3/0/1
port link-mode bridge
port access vlan 10
#
interface GigabitEthernet3/0/3
port link-mode bridge
port access vlan 10
#
return
· Device C
#
cfd enable
cfd md MD_TEST level 7
cfd ma MA_TEST md MD_TEST vlan 10
cfd service-instance 10 md MD_TEST ma MA_TEST
cfd meplist 1 3 service-instance 10
#
vlan 1
#
vlan 10
#
stp enable
#
interface GigabitEthernet3/0/1
port link-mode bridge
port access vlan 10
cfd mep 3 service-instance 10 outbound
cfd mep service-instance 10 mep 3 enable
cfd cc service-instance 10 mep 3 enable
#
return
Related documentation
· H3C S12500 Routing Switch Series High Availability Configuration Guide
· H3C S12500 Routing Switch Series High Availability Command Reference
