Ethernet OAM Licensing Requirements and Configuration Precautions

When you associate 802.1ag with the UNI, you must configured the same association mode on both ends.

None.

NA

When a Layer 2 GE interface has an EVC sub-interface with the type of Port Default Vlan, default, or untag.

Plan the MEP properly.

The OAM status is Down in PORT MEP scenarios.

When the MEP is bound to a QinQ interface, the interface supports only four types of QinQ protocols:0x8100, 0x9100, 0x88a8, and 0x9200.

Configure a proper QinQ protocol type.

The MEP status is abnormal.

When an MEP is bound to a VLL/VSI main interface, CCM packets do not carry VLAN IDs, and priority configuration is not supported.

This MEP does not support priority performance monitoring.

Do not configure priority-based statistics collection.

Priority configuration is not supported.

When a MEP is bound to a VLL or VSI interface, Y.1731 packets do not carry VLAN information and priority-based statistics are not supported. The following message is displayed:

This MEP does not support priority performance monitoring.

Do not configure priority-based packet loss statistics when a MEP is bound to a VLL or VSI interface.

No statistics results are available.

An outward-facing MEP that detects VLL or VSI services on a trunk interface cannot be configured together with a port MEP that detects the trunk interface's member interface.

Plan MAs and MEPs properly.

802.1ag goes Down if they are configured together.

The PORT MEP status is falsely detected as Down when a trunk main interface has the Port Default Vlan configuration and its member interfaces are bound to the PORT MEP.

Plan the MEP properly.

The OAM status is Down in PORT MEP scenarios.

Y.1731 single- or dual-end packet loss measurement does not support load balancing and Eth-Trunk on public networks.

Do not configure Y.1731 single- or dual-end packet loss measurement for public-network load balancing and Eth-Trunk scenarios.

The measurement result is inaccurate.

Y.1731 single-end packet loss rate measurement and Y.1731 dual-end packet loss rate measurement are mutually exclusive.

Error:Dual-ended loss-measure and single-ended loss-measure can not be configured at the same time.

Configure either Y.1731 single-end packet loss rate measurement or Y.1731 dual-end packet loss rate measurement at a time.

Y.1731 single-end packet loss rate measurement and Y.1731 dual-end packet loss rate measurement cannot be configured together.

Y.1731 single-end delay measurement must be used together with 1588v2 clock synchronization.

Ensure clock synchronization when configuring Y.1731 single-end delay measurement.

The measurement result is inaccurate when clocks are not synchronized.

Y.1731 single- or dual-end packet loss measurement does not support load balancing on public networks.

Do not configure Y.1731 single- or dual-end delay measurement for public-network load balancing scenarios.

The measurement result is inaccurate.

Priority-based Y.1731 continuous statistics collection and non priority-based Y.1731 continuous statistics collection are mutually exclusive.

Error:The single-ended loss measurement function is already enabled in test-id 1.

Configure either priority-based Y.1731 continuous statistics collection or non priority-based Y.1731 continuous statistics collection at a time.

Priority-based Y.1731 continuous statistics collection and non priority-based Y.1731 continuous statistics collection cannot be configured together.

Y.1731 does not support packet loss detection in a non-single trunk member interface scenario.

Do not configure Y.1731 packet loss detection in a load balancing scenario.

Packet loss data detected by Y.1731 is inaccurate in a load balancing scenario.

Association between 802.1ag and interface status is not supported in local CCC inward scenarios.

None

Association between 802.1ag and interface status cannot be configured in local CCC inward scenarios.

For Layer 2 interfaces with the port link type of access or hybrid, when the VLAN associated with the MEP is the default VLAN, DM/SLM packets do not carry VLAN IDs, and priority-based DM/SLM measurement is not supported.

None

Priority-based DM/SLM measurement is not supported.

When a Layer 3 physical main interface is configured with CFM connectivity detection, the interface will interface the detection each time it joins in or leaves the Eth-Trunk interface. The detection is automatically recovered.

Avoid adding a Layer 3 physical interface to or removing it from the Eth-Trunk interface bound to the MEP during CFM connectivity detection.

The EOAM falsely reports an alarm or is falsely associated with other services.

For a physical interface, an outward-facing MEP that detects VLL or VSI services cannot be configured together with a port MEP. For a trunk interface, an outward-facing MEP that detects VLL and VSI services cannot be configured together with a port MEP that detects the trunk interface's member interface.

Plan MAs and MEPs properly.

802.1ag goes Down if they are configured together.

A virtual cluster does not support Y.1731 packet loss detection.

None

The measurement result is inaccurate.

An ETH-Test test case supports the collection of traffic from a maximum of five different source MAC addresses. If traffic is received from more than five source MAC addresses, traffic from the additional source MAC addresses is not counted.

Configure traffic to be sent to the ETH-Test test case to come from at most five different source MAC addresses.

After traffic is received from more than five source MAC addresses, traffic from the additional source MAC addresses is not counted.

In VPLS and VLAN scenarios, Y.1731 measurement fails when the system MAC mode is used, which must be switched to the interface MAC mode.

Use the interface MAC mode in VPLS and VLAN scenarios.

Y.1731 measurement fails.