A service instance is indicated by an integer to represent an MA in an MD. The MD and MA define the
level and VLAN attribute of the messages handled by the MPs in a service instance.
Service instances fall into these types:
Service instance with the MD name, which takes effect in any version of CFD
•
Service instance without the MD name, which takes effect in only CFD IEEE 802.1ag
•
You can create either type of service instance as needed.
Creating a service instance with the MD name
To create a service instance with the MD name, create the MD and MA for the service instance first.
To configure a service instance with the MD name:
To do...
•
Enter system view
•
Create an MD
•
Create an MA
•
Create a service instance with
the MD name
You must create the MD, MA, and service instance by strictly following the order stated in the table.
Creating a service instance without the MD name
When you create a service instance without the MD name, the system automatically creates the MA and
MD for the service instance.
To create a service instance without the MD name:
To do...
•
Enter system view
•
Create a service instance
without the MD name
Configuring MEPs
CFD is implemented through various operations on MEPs. As a MEP is configured on a service instance,
the MD level and VLAN attribute of the service instance become the attribute of the MEP.
Before creating MEPs, configure the MEP list. An MEP list is a collection of local MEPs allowed to be
configured in an MA and the remote MEPs to be monitored.
To configure a MEP:
To do...
•
Enter system view
Use the command...
system-view
cfd md md-name level level-value
cfd ma ma-name md md-name
vlan vlan-id
cfd service-instance instance-id md
md-name ma ma-name
Use the command...
system-view
cfd service-instance instance-id
maid format { string ma-name }
level level-value vlan vlan-id
Use the command...
system-view
26
Remarks
—
Required
Not created by default
Required
Not created by default
Required
Not created by default
Remarks
—
Required
Not created by default
Remarks
—