H3C Technologies H3C S7500E Series Switches - Manual (Page 47)

5-12
To do... Use the command... Remarks
Display MA configuration
information
display cfd ma [ [ ma-name ] md
md-name ]
Available in any view
Display service instance
configuration information
display cfd service-instance
[ instance-id ]
Available in any view
Display MEP list in a service
instance
display cfd meplist
[ service-instance instance-id ]
Available in any view
Display MP information
display cfd mp [ interface
interface-type interface-number ]
Available in any view
Display the attribute and running
information of the MEPs
display cfd mep mep-id
service-instance instance-id
Available in any view
Display LTR information received
by a MEP
display cfd linktrace-reply
[ service-instance instance-id
[ mep mep-id ] ]
Available in any view
Display the information of a remote
MEP
display cfd remote-mep
service-instance instance-id mep
mep-id
Available in any view
Display the content of the LTR that
responds to LTM messages
display cfd linktrace-reply
auto-detection [ size size-value ]
Available in any view
CFD Configuration Example
Network requirements
As shown in Figure 5-6 :
z The network comprises five devices and is divided into two MDs: MD_A (level 5) and MD_B (level
3). Ports GigabitEthernet2/0/1 through GigabitEthernet2/0/4 of every device belong to VLAN 100,
and the MAs in the two MDs all serve VLAN 100.
z In MD_A, there are three edge ports: GigabitEthernet2/0/1 on Device A, GigabitEthernet2/0/3 on
Device D, and GigabitEthernet2/0/4 on Device E; configure inward-facing MEPs on these ports
respectively. In MD_B, there are two edge ports: GigabitEthernet2/0/3 on Device B and
GigabitEthernet2/0/1 on Device D; configure outward-facing MEPs on the two ports respectively.
z In MD_A, Device B is designed to have MIPs when its port is configured with low level MEPs. In
this case, port GigabitEthernet2/0/3 is configured with MEPs of MD_B, and the MIPs of MD_A can
be configured on this port. Based on the design, you should configure the MIP generation rule of
MD_A as explicit.
z The MIPs of MD_B are designed on Device C, and are configured on all ports. Based on this
design, you should configure the MIP generation rule as default.