Alcatel-Lucent 7210 SAS M - Configuring ETH-CFM Parameters

Services
7210 SAS M Services Guide Page 79
Configuring ETH-CFM Parameters
Configuring ETH-CFM requires commands at two different hierarchy levels of the CLI.
A sample of the global ETH-CFM configuration which defines the domains, associations, linkage
o the service id or function, and the globally applicable CCM parameters including the interval
and building of the remote MEPs database is shown below.
The following example displays a sample configuration.
*A:ALU-7_A>config>eth-cfm# info
----------------------------------------------
domain 1 name "1" level 1
association 2 name "1345"
bridge-identifier 100
exit
ccm-interval 60
remote-mepid 2
remote-mepid 3
exit
exit
----------------------------------------------
*A:ALU-7_A>config>eth-cfm#
Defining the MEP and configuring service specific ETH-CFM parameters is performed within the
service on the specific SAP or SDP binding. The example using the service VPLS 100 shows this
configuration on the SAP.
#*A:ALU-7_A>config>service# info
----------------------------------------------
vpls 100 customer 1 create
description "VPLS service 100 - Used for MEP configuration example"
sap 2/2/1:20 create
description "2/2/1:20"
eth-cfm
mep 1 domain 1 association 1 direction down
no shutdown
exit
exit
exit
exit
no shutdown
exit
customer 1 create
description "Default customer"
exit
exit
----------------------------------------------
*A:ALU-7_A>config>service#
All of the examples shown above were based on IEEE 802.1ag. They are not capable of running
Y.1731 functions. To build a Y.1731 context the domain format must be none.