This fault is commonly caused by one of the following:
The interface with a MEP configured is Down.
The MD levels on the local and remote ends are different.
The MEPs configured on the local and remote ends belong to different MAs.
The MAs on the local and remote ends are associated with different VLANs.
The number of unexpected-MEP alarms saved on the local device has reached the maximum value.
Run the display interface interface-type interface-number command is any view to check the status of the interface.
If the interface is in Down state, run the display this command in the interface view to check whether the interface has been shut down.
If the command output displays shutdown, run the undo shutdown command in the interface view.
If shutdown is not displayed, go to step 3.
If the interface is in Up state, go to step 4.
Run the display cfm md command in any view on both ends to check whether the Level field values on both ends are the same.
If the MD levels are different, set the same MD level for both ends.
If the MD levels are the same, go to step 3.
Run the display cfm ma command in any view to check the MA name on both ends.
If the MA names are different, configure the same MA for both ends.
If the MA names are the same, go to step 4.
Run the display cfm ma command in any view to check the VLANs associated with the MAs on both ends.
If the MAs are associated with different VLANs, associate the MAs with the same VLAN.
If the MAs are associated with the same VLAN, go to step 5.
Run the display cfm error-info error-type unexpected-mep [ md md-name ma ma-name mep-id mep-id ] command in any view to check the number of unexpected-MEP alarms. If the number of unexpected-MEP alarms has reached the maximum value, no Unexpected-MEP alarm can be generated.