cc enable

MPLS-TP OAM provides proactive monitoring. To enable proactive monitoring, run the cc enable command.

MPLS-TP OAM is configured for a maintenance entity (ME). An ME consists of two maintenance entity group end points (MEPs) on both ends of a transport path. MPLS-TP OAM detects faults in the MEP. The mpls-tp meg command must be run to create a MEG before the cc enable command is run to implement MPLS-TP OAM.

The OAM auto protocol enabled on the egress provides the following functions:

• Triggers OAM. If the sink node does not support OAM CC and CC parameters (including the detection packet type and interval at which packets are sent), upon the receipt of the first CV or FFD packet, the sink node automatically records the packet type and interval at which the packet is sent and uses these parameters in CC detection that starts.
• Dynamically stops running the OAM. If the detection packet type or interval at which detection packets are sent is to be changed on the source node, the source node sends an FDI packet to instruct the sink node to stop the OAM state machine. If an OAM function is to be disabled on the source node, the source node also sends an FDI packet to instruct the sink node to stop the OAM state machine.

To prevent unnecessary alarms, run the cc enable and undo cc enable commands in the following sequence:

• Run the cc send enable command on the ingress and then the cc receive enable command on the egress. Run the cc receive enable command on the egress and then the cc send enable command on the ingress.
• Run the undo cc receive enable command on the egress and then the undo cc send enable command on the ingress. Run the undo cc receive enable command on the ingress and then the undo cc send enable command on the egress.
  Running the cc enable command enables both CC and CV.
  If MPLS-TP OAM is already associated with an APS tunnel protection group, the device cannot be disabled from sending or receiving CCMs.