Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring Y.1731 Functionality for VPLS to Support Delay and Delay Variation

For VPLS, you can configure the Ethernet frame delay measurement (ETH-DM) functionality to trigger two-way ETH-DM and allow concurrent ETH-DM CLI sessions from the same local maintenance association end point (MEP). The feature also provides the option to perform ETH-DM for a given 802.1q priority, to set the size of the data type, length, and value (TLV), to disable the session-id-tlv option, and to generate XML output.

This feature complements the ITU-T Y.1731 Ethernet service OAM feature. On-demand delay measurement for VPLS is supported on MX Series routers installed with Rev-B DPCs. Only the two-way delay measurement feature is supported for VPLS connections.

MX Series routers with modular port concentrators (MPCs) and 10-Gigabit Ethernet MPCs with SFP+ support ITU-T Y.1731 functionality on VPLS for frame-delay and delay-variation.

This feature is currently supported only for up MEPs. Set the MEP direction to up by configuring the up option for the direction statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-association ma-name mep mep-id] hierarchy level.

This feature also provides support for an optional configuration where you can delegate the server-side processing (for two-way delay measurement) to the Packet Forwarding Engine (PFE) to prevent overloading on the Routing Engine. To enable this feature, include the delegate-server-processing statement at the [edit protocols oam ethernet connectivity-fault-management performance-monitoring] hierarchy level. By default, the server-side processing is done by the Routing Engine.

The following commands enable you to monitor and maintain the Y.1731 feature for VPLS:

  • To display the delay measurement values across a VPLS connection, use the monitor ethernet delay-measurement two-way (remote-mac-address | mep mep-id) maintenance-domain name maintenance-association name count count wait time priority 802.1p-value size no-session-id-tlv xml command.

  • The feature also provides support for enhanced continuity measurement by using an existing continuity check protocol. The continuity for every remote MEP is measured as the percentage of time that a remote MEP was operationally up over the total administratively enabled time.

    To display the continuity measurement information, use the show oam ethernet connectivity-fault-management mep-database maintenance-domain name maintenance-association name local-mep identifier remote-mep identifier command.

  • You can restart the continuity measurement by clearing the currently measured operational uptime and administrative enabled time. To clear the existing continuity measurement and restart counting the operational uptime, use the clear oam ethernet connectivity-fault-management continuity-measurement maintenance-domain name maintenance-association name local-mep identifier remote-mep identifier command.

  • To clear the delay statistics, issue a clear oam ethernet connectivity-fault-management statistics command or a clear oam ethernet connectivity-fault-management delay-statistics two-way maintenance-domain md-name maintenance-association ma-name command.