The MPLS OAM auto protocol is a Huawei proprietary protocol.
On the NetEngine 8000 F, the OAM auto protocol can address the following problems,
which occur because of drawbacks of ITU-T Recommendations Y.1710 and
A dLOCV defect occurs if the OAM function is enabled on the
ingress on an LSP later than that on the egress or if OAM is enabled
on the egress and disabled on the ingress.
The dLOCV defect also occurs when OAM is disabled. OAM must
be disabled on the ingress and egress before the OAM detection packet
type or the interval at which detection packets are sent can be changed.
OAM parameters, including a detection packet type and an interval
at which detection packets are sent must be set on both the ingress
and egress. This is likely to cause a parameter inconsistency.
The OAM auto protocol enabled on the egress provides the following
- 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.
- If the OAM function-enabled sink node does not receive CV or FFD
packets within a specified period of time, the sink node generates
a BDI packet and notifies the NMS of the BDI defect.
- 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.