Configuring Association Between CFM and EFM
Context
For details on the principle and usage scenarios of association between EFM and CFM, see Fault Information Advertisement Between CFM and Other Modules.
Association between EFM and CFM is bidirectional. When EFM detects a link fault, it will notify CFM of the fault. When CFM detects a link fault, it will notify EFM of the fault.
Pre-configuration Tasks
Perform the task of Configuring Basic EFM Functions.
Perform the task of Configuring Basic Ethernet CFM Functions.
Procedure
- Run system-view
The system view is displayed.
- Run oam-mgr
The OAM management view is displayed.
- Run the following commands as required.
Unidirectional association
Run oam-bind ingress efm interface interface-type interface-number egress cfm md md-name ma ma-name
EFM is configured to report faults to CFM.
Run oam-bind ingress cfm md md-name ma ma-name egress efm interface interface-type interface-number
CFM is configured to report faults to EFM.
Bidirectional association
Run oam-bind cfm md md-name ma ma-name efm interface interface-type interface-number
EFM and CFM are configured to report faults to each other.
The functions of two commands used to configure association functions in opposite directions are the same as those of the command used to configure the bidirectional association function.
If the oam-bind cfm md md-name ma ma-name efm interface interface-type interface-number command is run, oam-bind ingress efm interface interface-type interface-number egress cfm md md-name ma ma-name and oam-bind ingress cfm md md-name ma ma-name egress efm interface interface-type interface-number will be displayed in the configuration file.
After EFM is associated with other functional modules, pay attention to the following points: If EFM is disabled on an interface, association between EFM and other functional modules is deleted. If an MA or MD is deleted, the association between Ethernet CFM and other functional modules is deleted.
