Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring Ethernet Frame Delay Measurement Sessions

 

Use this topic to understand how to configure Ethernet frame delay measurement sessions. You can start either a one-way Ethernet delay measurement session or a two-way Ethernet delay measurement session. Also, use this topic to view the delay measurement statistics and frame counts.

Guidelines for Configuring Routers to Support an ETH-DM Session

Keep the following guidelines in mind when configuring routers to support an Ethernet frame delay measurement (ETH-DM) session:

Configuration Requirements for ETH-DM

You can obtain ETH-DM information for a link that meets the following requirements:

  • The measurements can be performed between peer maintenance association endpoints (MEPs) on two routers.

  • The two MEPs must be configured on two Ethernet physical interfaces or on two Ethernet logical interfaces. For more information, see Configuring a MEP to Generate and Respond to CFM Protocol Messages.

  • The two MEPs must be configured—on their respective routers—under the same maintenance association (MA) identifier. For more information, see Creating a Maintenance Association.

  • On both routers, the MA must be associated with the same maintenance domain (MD) name. For more information, see Creating a Maintenance Domain.

  • On both routers, periodic packet management (PPM) must be running on the Routing Engine and Packet Forwarding Engine, which is the default configuration. You can disable PPM on the Packet Forwarding Engine only. However, the Ethernet frame delay measurement feature requires that distributed PPM remain enabled on the Packet Forwarding Engine of both routers. For more information about ppm, see the Junos OS Routing Protocols Library.

  • If the PPM process (ppm) is disabled on the Packet Forwarding Engine, you must re-enable it. Re-enabling distributed ppm entails restarting the ethernet-connectivity-fault-management process, which causes all connectivity fault management (CFM) sessions to re-establish. For more information about CFM sessions, see Configuring Ethernet Local Management Interface.

Note

The Ethernet frame delay measurement feature is supported only for MEPs configured on Ethernet physical or logical interfaces on DPCs in MX Series routers. The ETH-DM feature is not supported on aggregated Ethernet interfaces or LSI pseudowires.

Configuration Options for ETH-DM

By default, the ETH-DM feature calculates frame delays using software-based timestamping of the ETH-DM PDU frames sent and received by the MEPs in the session. As an option that can increase the accuracy of ETH-DM calculations when the DPC is loaded with heavy traffic in the receive direction, you can enable hardware-assisted timestamping of session frames in the receive direction.

Guidelines for Starting an ETH-DM Session

Keep the following guidelines in mind when preparing to start an Ethernet frame delay measurement (ETH-DM) session:

ETH-DM Session Prerequisites

Before you can start an ETH-DM session, you must configure two MX Series routers to support ETH-DM by defining the two CFM-enabled physical or logical Ethernet interfaces on each router. This entails creating and configuring CFM maintenance domains, maintenance associations, and maintenance association end points on each router. For more information about enabling CFM on an Ethernet interface, see Creating a Maintenance Domain.

Note

The Ethernet frame delay measurement feature is supported only for maintenance association end points configured on Ethernet physical or logical interfaces on DPCs in MX Series routers. The ETH-DM feature is not supported on aggregated Ethernet interfaces or LSI pseudowires.

For specific information about configuring routers to support ETH-DM, seeGuidelines for Configuring Routers to Support an ETH-DM Session and Configuring Routers to Support an ETH-DM Session.

ETH-DM Session Parameters

You can initiate a one-way or two-way ETH-DM session by entering the monitor ethernet delay-measurement operational command at a router that contains one end of the service for which you want to measure frame delay. The command options specify the ETH-DM session in terms of the CFM elements:

  • The type of ETH-DM measurement (one-way or two-way) to be performed.

  • The Ethernet service for which the ETH-DM measurement is to be performed:

    • CFM maintenance domain—Name of the existing maintenance domain (MD) for which you want to measure Ethernet frame delays. For more information, see Creating a Maintenance Domain.

    • CFM maintenance association—Name of an existing maintenance association (MA) within the maintenance domain. For more information, see Creating a Maintenance Association.

    • Remote CFM maintenance association end point—The unicast MAC address or the numeric identifier of the remote maintenance association end point (MEP)—the physical or logical interface on the remote router that resides in the specified MD and is named in the specified MA—with which to perform the ETH-DM session. For more information, see Configuring a MEP to Generate and Respond to CFM Protocol Messages.

  • Optional specifications:

    • Count—You can specify the number of ETH-DM requests to send for this frame delay measurement session. The range is from 1 through 65,535 frames. The default value is 10 frames.

      NOTE: Although you can trigger frame delay collection for up to 65,535 ETH-DM requests at a time, a router stores only the last 100 frame delay statistics per CFM session (pair of peer MEPs).

    • Frame interval—You can specify the number of seconds to elapse between ETH-DM frame transmittals. The default value is 1 second.

For more detailed information about the parameters you can specify to start an ETH-DM session, see the monitor ethernet delay-measurement operational command description in the CLI Explorer.

Restrictions for an ETH-DM Session

The following restrictions apply to an ETH-DM session:

  • You cannot run multiple simultaneous ETH-DM sessions with the same remote MEP or MAC address.

  • For a given ETH-DM session, you can collect frame delay information for a maximum of 65,535 frames.

  • For a given CFM session (pair of peer MEPs), the ETH-DM database stores a maximum of 100 statistics, with the older statistics being “aged out” as newer statistics are collected for that pair of MEPs.

    • For one-way delay measurements collected within the same CFM session, the 100 most recent ETH-DM statistics can be retrieved at any point of time at the router on which the receiver MEP is defined.

    • For two-way delay measurements collected within the same CFM session, the 100 most recent ETH-DM statistics can be retrieved at any point of time at the router on which the initiator MEP is defined.

    Depending on the number of frames exchanged in the individual ETH-DM sessions, the ETH-DM database can contain statistics collected through multiple ETH-DM sessions.

  • If graceful Routing Engine switchover (GRES) occurs, any collected ETH-DM statistics are lost, and ETH-DM frame counts are reset to zeroes. GRES enables a router with dual Routing Engines to switch from a master Routing Engine to a backup Routing Engine without interruption to packet forwarding. For more information, see the High Availability Feature Guide.

  • Accuracy of frame delay data is compromised when the system is changing (such as from reconfiguration). We recommend performing Ethernet frame delay measurements on a stable system.

Guidelines for Managing ETH-DM Statistics and ETH-DM Frame Counts

ETH-DM Statistics

Ethernet frame delay statistics are the frame delay and frame delay variation values determined by the exchange of frames containing ETH-DM protocol data units (PDUs).

  • For a one-way ETH-DM session, statistics are collected in an ETH-DM database at the router that contains the receiver MEP. For a detailed description of one-way Ethernet frame delay measurement, including the exchange of one-way delay PDU frames, see Ethernet Frame Delay Measurements Overview.

  • For a two-way ETH-DM session, statistics are collected in an ETH-DM database at the router that contains the initiator MEP. For a detailed description of two-way Ethernet frame delay measurement, including the exchange of two-way delay PDU frames, see Ethernet Frame Delay Measurements Overview.

A CFM database stores CFM-related statistics and—for Ethernet interfaces that support ETH-DM—the 100 most recently collected ETH-DM statistics for that pair of MEPs. You can view ETH-DM statistics by using the delay-statistics or mep-statistics form of the show oam ethernet connectivity-fault-management command to display the CFM statistics for the MEP that collects the ETH-DM statistics you want to view.

Table 1 describes the ETH-DM statistics calculated in an ETH-DM session.

Table 1: ETH-DM Statistics

Field Name

Field Description

One-way delay (μsec)

For a one-way ETH-DM session, the frame delay, in microseconds, collected at the receiver MEP.

To display frame delay statistics for a given one-way ETH-DM session, use the delay-statistics or mep-statistics form of the show oam ethernet connectivity-fault-management command at the receiver MEP for that session.

Two-way delay (μsec)

For a two-way ETH-DM session, the frame delay, in microseconds, collected at the initiator MEP.

When you start a two-way frame delay measurement, the CLI output displays each DMR frame receipt timestamp and corresponding DMM frame delay and delay variation collected as the session progresses.

To display frame delay statistics for a given two-way ETH-DM session, use the delay-statistics or mep-statistics form of the show oam ethernet connectivity-fault-management command at the initiator MEP for that session.

Average delay

When you start a two-way frame delay measurement, the CLI output includes a runtime display of the average two-way frame delay among the statistics collected for the ETH-DM session only.

When you display ETH-DM statistics using a show command, the Average delay field displays the average one-way and two- frame delays among all ETH-DM statistics collected at the CFM session level.

For example, suppose you start two one-way ETH-DM sessions for 50 counts each, one after the other. If, after both measurement sessions complete, you use a show command to display 100 ETH-DM statistics for that CFM session, the Average delay field displays the average frame delay among all 100 statistics.

Average delay variation

When you start a two-way frame delay measurement, the CLI output includes a runtime display of the average two-way frame delay variation among the statistics collected for the ETH-DM session only.

When you display ETH-DM statistics using a show command, the Average delay variation field displays the average one-way and two- frame delay variations among all ETH-DM statistics collected at the CFM session level.

Best-case delay

When you start a two-way frame delay measurement, the CLI output includes a runtime display of the lowest two-way frame delay value among the statistics collected for the ETH-DM session only.

When you display ETH-DM statistics using a show command, the Best case delay field displays the lowest one-way and two-way frame delays among all ETH-DM statistics collected at the CFM session level.

Worst-case delay

When you start a two-way frame delay measurement, the CLI output includes a runtime display of the highest two-way frame delay value among the statistics collected for the ETH-DM session only.

When you display ETH-DM statistics using a show command, the Worst case delay field displays the highest one-way and two-way frame delays among all statistics collected at the CFM session level.

When you start a one-way frame delay measurement, the CLI output displays NA (“not available”) for this field. One-way ETH-DM statistics are collected at the remote (receiver) MEP. Statistics for a given one-way ETH-DM session are available only by displaying CFM statistics for the receiver MEP.

ETH-DM Statistics Retrieval

At the receiver MEP for a one-way session, or at the initiator MEP for a two-way session, you can display all ETH-DM statistics collected at a CFM session level by using the following operational commands:

  • show oam ethernet connectivity-fault-management delay-statistics maintenance-domain md-name maintenance-association ma-name <local-mep mep-id> <remote-mep mep-id> <count count>

  • show oam ethernet connectivity-fault-management mep-statistics maintenance-domain md-name maintenance-association ma-name <local-mep mep-id> <remote-mep mep-id> <count count>

ETH-DM Frame Counts

The number of ETH-DM PDU frames exchanged in a ETH-DM session are stored in the CFM database on each router.

Table 2 describes the ETH-DM frame counts collected in an ETH-DM session.

Table 2: ETH-DM Frame Counts

Field Name

Field Description

1DMs sent

Number of one-way delay measurement (1DM) PDU frames sent to the peer MEP in this session.

Stored in the CFM database of the MEP initiating a one-way frame delay measurement.

Valid 1DMs received

Number of valid 1DM frames received.

Stored in the CFM database of the MEP receiving a one-way frame delay measurement.

Invalid 1DMs received

Number of invalid 1DM frames received.

Stored in the CFM database of the MEP receiving a one-way frame delay measurement.

DMMs sent

Number of delay measurement message (DMM) PDU frames sent to the peer MEP in this session.

Stored in the CFM database of the MEP initiating a two-way frame delay measurement.

DMRs sent

Number of delay measurement reply (DMR) frames sent (in response to a received DMM).

Stored in the CFM database of the MEP responding to a two-way frame delay measurement.

Valid DMRs received

Number of valid DMR frames received.

Stored in the CFM database of the MEP initiating a two-way frame delay measurement.

Invalid DMRs received

Number of invalid DMR frames received.

Stored in the CFM database of the MEP initiating a two-way frame delay measurement.

ETH-DM Frame Count Retrieval

Each router counts the number of ETH-DM frames sent or received and stores the counts in a CFM database.

Frame Counts Stored in CFM Databases

You can display ETH-DM frame counts for MEPs assigned to specified Ethernet interfaces or for specified MEPs in CFM sessions by using the following operational commands:

  • show oam ethernet connectivity-fault-management interfaces (detail | extensive)

  • show oam ethernet connectivity-fault-management mep-database maintenance-domain md-name maintenance-association ma-name <local-mep mep-id> <remote-mep mep-id>

One-Way ETH-DM Frame Counts

For a one-way ETH-DM session, delay statistics are collected at the receiver MEP only, but frame counts are collected at both MEPs. As indicated in Table 2, one-way ETH-DM frame counts are tallied from the perspective of each router in the session:

  • At the initiator MEP, the router counts the number of 1DM frames sent.

  • At the receiver MEP, the router counts the number of valid 1DM frames received and the number of invalid 1DM frames received.

You can also view one-way ETH-DM frame counts—for a receiver MEP—by using the show oam ethernet connectivity-fault-management mep-statistics command to display one-way statistics and frame counts together.

Two-Way ETH-DM Frame Counts

For a two-way ETH-DM session, delay statistics are collected at the initiator MEP only, but frame counts are collected at both MEPs. As indicated in Table 2, two-way ETH-DM frame counts are tallied from the perspective of each router in the session:

  • At the initiator MEP, the router counts the number of DMM frames sent, valid DMR frames received, and invalid DMR frames received.

  • At the responder MEP, the router counts the number of DMR frames sent.

You can also view two-way ETH-DM frame counts—for an initiator MEP—by using the show oam ethernet connectivity-fault-management mep-statistics command to display two-way statistics and frame counts together.

Configuring Routers to Support an ETH-DM Session

Configuring MEP Interfaces

Before you can start an Ethernet frame delay measurement session across an Ethernet service, you must configure two MX Series routers to support ETH-DM.

To configure an Ethernet interface on a MX Series router to support ETH-DM:

  1. On each router, configure two physical or logical Ethernet interfaces connected by a VLAN. The following configuration is typical for single-tagged logical interfaces:

    Both interfaces will use the same VLAN ID.
  2. On each router, attach peer MEPs to the two interfaces. The following configuration is typical:

Ensuring That Distributed ppm Is Not Disabled

By default, the router’s period packet management process (ppm) runs sessions distributed to the Packet Forwarding Engine in addition to the Routing Engine. This process is responsible for periodic transmission of packets on behalf of its various client processes, such as Bidirectional Forwarding Detection (BFD), and it also receives packets on behalf of client processes.

In addition, ppm handles time-sensitive periodic processing and performs such processes as sending process-specific packets and gathering statistics. With ppm processes running distributed on both the Routing Engine and the Packet Forwarding Engine, you can run such processes as BFD on the Packet Forwarding Engine.

Distributed ppm Required for ETH-DM

Ethernet frame delay measurement requires that ppm remains distributed to the Packet Forwarding Engine. If ppm is not distributed to the Packet Forwarding Engines of both routers, ETH-DM PDU frame timestamps and ETH-DM statistics are not valid.

Before you start ETH-DM, you must verify that the following configuration statement is NOT present:

If distributed ppm processing is disabled (as shown in the stanza above) on either router, you must re-enable it in order to use the ETH-DM feature.

Procedure to Ensure that Distributed ppm is Not Disabled

To ensure that distributed ppm is not disabled on a router:

  1. Display the packet processing management (PPM) configuration to determine whether distributed ppm is disabled.

    • In the following example, distributed ppm is enabled on the router. In this case, you do not need to modify the router configuration:

    • In the following example, distributed ppm is disabled on the router. In this case, you must proceed to Step 2 to modify the router configuration:

  2. Modify the router configuration to re-enable distributed ppm and restart the Ethernet OAM Connectivity Fault Management process ONLY IF distributed ppm is disabled (as determined in the previous step).

    1. Before continuing, make any necessary preparations for the possible loss of connectivity on the router.

      Restarting the ethernet-connectivity-fault-management process has the following effect on your network:

      • All connectivity fault management (CFM) sessions re-establish.

      • All ETH-DM requests on the router terminate.

      • All ETH-DM statistics and frame counts reset to 0.

    2. Modify the router configuration to re-enable distributed ppm. For example:
    3. Commit the updated router configuration. For example:
    4. To restart the Ethernet OAM Connectivity-Fault-Management process, enter the restart ethernet-connectivity-fault-management <gracefully | immediately | soft> operational mode command. For example:

Connectivity fault management (CFM) sessions operate in centralized mode over AE interfaces by default. Y.1731 performance monitoring (PM) is supported on centralized CFM sessions over AE interfaces. Also, distribution of CFM session over AE interfaces to line cards is supported from Junos OS Release 13.3. To enable the distribution of CFM sessions and to operate in centralized mode, include the ppm delegate-processing statement at the [edit routing-options ppm] hierarchy level. The mechanism that enables distribution of CFM sessions over AE interfaces provides the underlying infrastructure to support PM over AE interfaces. In addition, periodic packet management (PPM) handles time-sensitive periodic processing and performs such processes as sending process-specific packets and gathering statistics. With PPM processes running distributed on both the Routing Engine and the Packet Forwarding Engine, you can run performance monitoring processes on the Packet Forwarding Engine.

Enabling the Hardware-Assisted Timestamping Option

By default, Ethernet frame delay measurement uses software for timestamping transmitted and received ETH-DM frames. For Ethernet interfaces, you can optionally use hardware timing to assist in the timestamping of received ETH-DM frames to increase the accuracy of delay measurements.

Enabling hardware-assisted timestamping of received frames can increase the accuracy of ETH-DM calculations when the DPC is loaded with heavy traffic in the receive direction.

To enable Ethernet frame delay measurement hardware assistance on the reception path, include the hardware-assisted-timestamping statement at the [edit protocols oam ethernet connectivity-fault-management performance-monitoring] hierarchy level:

Configuring the Server-Side Processing Option

You can delegate the server-side processing (for both two-way delay measurement and loss measurement) to the Packet Forwarding Engine to prevent overloading on the Routing Engine. By default, the server-side processing is done by the Routing Engine.

To configure the server-side processing option:

  1. In configuration mode, go to the following hierarchy level:
  2. Configure the server-side processing option.
  3. Verify the configuration.

Triggering an Ethernet Frame Delay Measurements Session

Before Ethernet frame delay measurement statistics can be displayed, they must be collected. To trigger Ethernet frame delay measurement, use the monitor ethernet delay-measurement (one-way | two-way) (remote-mac-address | mep identifier) maintenance-domain name maintenance-association ma-id [count count] [wait time] operational command.

The fields for this command are described in Table 3.

Table 3: Monitor Ethernet Delay Command Parameters

Parameter

Parameter Range

Description

one-way or two-way

NA

Perform a one-way or two-way (round-trip) delay measurement.

remote-mac-address

Unicast MAC address

Send delay measurement frames to the destination unicast MAC address (use the format xx:xx:xx:xx:xx:xx). Multicast MAC addresses are not supported.

mep identifier

1–8191

The MEP identifier to use for the measurement. The discovered MAC address for this MEP identifier is used.

maintenance-domain name

Existing MD name

Specifies an existing maintenance domain (MD) to use for the measurement.

maintenance-association ma-id

Existing MA identifier

Specifies an existing maintenance association (MA) identifier to use for the measurement.

count count

1–65535 (default: 10)

(Optional) Specifies the number of Ethernet frame delay frames to send. The default is 10.

wait time

1–255 seconds (default: 1)

(Optional) Specifies the number of seconds to wait between frames. The default is 1 second.

If you attempt to monitor delays to a nonexistent MAC address, you must exit the application manually using ^C:

user@host> monitor ethernet delay-measurement two-way 00:11:22:33:44:55

Starting an ETH-DM Session

Using the monitor ethernet delay-measurement Command

After you have configured two MX Series routers to support ITU-T Y.1731 Ethernet frame delay measurement (ETH-DM), you can initiate a one-way or two-way Ethernet frame delay measurement session from the CFM maintenance association end point (MEP) on one of the routers to the peer MEP on the other router.

To start an ETH-DM session between the specified local MEP and the specified remote MEP, enter the monitor ethernet delay-measurement command at operational mode. The syntax of the command is as follows:

For a one-way frame delay measurement, the command displays a runtime display of the number of 1DM frames sent from the initiator MEP during that ETH-DM session. One-way frame delay and frame delay variation measurements from an ETH-DM session are collected in a CFM database at the router that contains the receiver MEP. You can retrieve ETH-DM statistics from a CFM database at a later time.

For a two-way frame delay measurement, the command displays two-way frame delay and frame delay variation values for each round-trip frame exchange during that ETH-DM session, as well as a runtime display of useful summary information about the session: average delay, average delay variation, best-case delay, and worst-case delay. Two-way frame delay and frame delay variation values measurements from an ETH-DM session are collected in a CFM database at the router that contains the initiator MEP. You can retrieve ETH-DM statistics from a CFM database at a later time.

Note

Although you can trigger frame delay collection for up to 65,535 ETH-DM requests at a time, a router stores only the last 100 frame delay statistics per CFM session (pair of peer MEPs).

For a complete description of the monitor ethernet delay-measurement operational command, see the CLI Explorer.

Starting a One-Way ETH-DM Session

To start a one-way Ethernet frame delay measurement session, enter the monitor ethernet delay-measurement one-way command from operational mode, and specify the peer MEP by its MAC address or by its MEP identifier.

For example:

user@host> monitor ethernet delay-measurement one-way 00:05:85:73:39:4a maintenance-domain md6 maintenance-association ma6 count 10
Note

If you attempt to monitor delays to a nonexistent MAC address, you must type Ctrl + C to explicitly quit the monitor ethernet delay-measurement command and return to the CLI command prompt.

Starting a Two-Way ETH-DM Session

To start a two-way Ethernet frame delay measurement session, enter the monitor ethernet delay-measurement two-way command from operational mode, and specify the peer MEP by its MAC address or by its MEP identifier.

For example:

user@host> monitor ethernet delay-measurement two-way 00:05:85:73:39:4a maintenance-domain md6 maintenance-association ma6 count 10
Note

If you attempt to monitor delays to a nonexistent MAC address, you must type Ctrl + C to explicitly quit the monitor ethernet delay-measurement command and return to the CLI command prompt.

Example: Configuring One-Way Ethernet Frame Delay Measurements with Single-Tagged Interfaces

This example uses two MX Series routers: MX-1 and MX-2. The configuration creates a CFM down MEP session on a VLAN-tagged logical interface connecting the two (ge-5/2/9 on Router MX-1 and ge-0/2/5 on Router MX-2).

Note

These are not complete router configurations.

Configuration on Router MX-1:

Configuration on Router MX-2:

From Router MX-2, start a one-way delay measurement to Router MX-1.

user@MX-2> monitor ethernet delay-measurement one-way mep 201 maintenance-domain md6 maintenance-association ma6 count 10

The counters are displayed as part of the local MEP database on Router MX-2.

user@MX-2> show oam ethernet connectivity-fault-management mep-database maintenance-domain md6 maintenance-domain ma6

The remote MEP database statistics are available on Router MX-1.

user@MX-1> show oam ethernet connectivity-fault-management mep-database maintenance-domain md6

The remote Router MX-1 should also collect the delay statistics (up to 100 per session) for display with mep-statistics or delay-statistics.

user@MX-1> show oam ethernet connectivity-fault-management mep-statistics maintenance-domain md6
user@MX-1> show oam ethernet connectivity-fault-management delay-statistics maintenance-domain md6
Note

When two systems are close to each other, their one-way delay values are very high compared to their two-way delay values. This is because one-way delay measurement requires the timing for the two systems to be synchronized at a very granular level and MX Series routers do not support this granular synchronization. However, two-way delay measurement does not require synchronized timing, making two-way delay measurements more accurate.

Example: Configuring Two-Way Ethernet Frame Delay Measurements with Single-Tagged Interfaces

This example uses two MX Series routers: MX-1 and MX-2. The configuration creates a CFM down MEP session on a VLAN-tagged logical interface connecting the two (ge-5/2/9 on Router MX-1 and ge-0/2/5 on Router MX-2).

Note

These are not complete router configurations.

Configuration on Router MX-1:

Configuration on Router MX-2:

From Router MX-1, start a two-way delay measurement to Router MX-2.

user@MX-1> monitor ethernet delay-measurement two-way mep 101 maintenance-domain md6 maintenance-association ma6 count 10

The counters are displayed as part of the MEP database on Router MX-1 maintenance domain MD6.

user@MX-1> show oam ethernet connectivity-fault-management mep-database maintenance-domain md6

The collected MEP statistics are saved (up to 100 per remote MEP or per CFM session) and displayed as part of the MEP statistics on Router MX-1.

user@MX-1> show oam ethernet connectivity-fault-management mep-statistics maintenance-domain md6

The collected delay statistics are also saved (up to 100 per session) and displayed as part of the MEP delay statistics on Router MX-1.

user@MX-1> show oam ethernet connectivity-fault-management delay-statistics maintenance-domain md6

Managing Continuity Measurement Statistics

Displaying Continuity Measurement Statistics

Purpose

Display continuity measurement.

The show oam ethernet connectivity-fault-management delay-statistics maintenance-domain md1 maintenance-association ma1 command is enhanced to display continuity measurement statistics for MEPs in the specified CFM maintenance association (MA) within the specified CFM maintenance domain (MD).

Action

  • To display the ETH-DM statistics collected for MEPs belonging to MA ma1 and within MD md1:

    user@host> show oam ethernet connectivity-fault-management delay-statistics maintenance-domain md1 maintenance-association ma1

Clearing Continuity Measurement Statistics

Purpose

Clear the continuity measurement statistics

By default, statistics are deleted for all MEPs attached to CFM-enabled interfaces on the router. However, you can filter the scope of the command by specifying an interface name.

Action

  • To clear the continuity measurement statistics for all MEPs attached to CFM-enabled interfaces on the router:

    user@host> clear oam ethernet connectivity-fault-management continuity-measurement maintenance-domain md-name maintenance-association ma-name local-mep local-mep-id remote-mep remote-mep-id

Viewing Ethernet Frame Delay Measurements Statistics

Once Ethernet frame delay measurement statistics have been collected, they can be displayed.

To retrieve the last 100 Ethernet frame delay measurement statistics per remote MEP or per CFM session, two types of show commands are provided:

  • For all OAM frame counters and Ethernet frame delay measurement statistics

  • For Ethernet frame delay measurement statistics only

To retrieve all Ethernet frame delay measurement statistics for a given session, use the show oam ethernet connectivity-fault-management mep-statistics maintenance-domain name maintenance-association name [local-mep identifier] [remote-mep identifier] [count count] command.

To retrieve only Ethernet frame delay measurement statistics for a given session, use the show oam ethernet connectivity-fault-management delay-statistics maintenance-domain name maintenance-association name [local-mep identifier] [remote-mep identifier] [count count] command.

Note

The only difference in the two commands is the use of the mep-statistics and delay-statistics keyword.

The fields for these commands are described in Table 4.

Table 4: Show Ethernet Delay Command Parameters

Parameter

Parameter Range

Description

maintenance-domain name

Existing MD name

Specifies an existing maintenance domain (MD) to use.

maintenance-association ma-id

Existing MA identifier

Specifies an existing maintenance association (MA) identifier to use.

local-mep identifier

1–8191

When a MEP has been specified, display statistics only for the local MEP.

remote-mep identifier

1–8191

When a MEP has been specified, display statistics only for the discovered MEP.

count count

1–100 (default:100)

The number of entries to display in the results table. By default, all 100 entries are displayed if they exist.

Note

For each MEP, you will see frame counters for sent and received Ethernet frame delay measurement frames whenever MEP statistics are displayed.

Managing ETH-DM Statistics and ETH-DM Frame Counts

Displaying ETH-DM Statistics Only

Purpose

Display ETH-DM statistics.

By default, the show oam ethernet connectivity-fault-management delay-statistics command displays ETH-DM statistics for MEPs in the specified CFM maintenance association (MA) within the specified CFM maintenance domain (MD).

Action

  • To display the ETH-DM statistics collected for MEPs belonging to MA ma1 and within MD md1:

    user@host> show oam ethernet connectivity-fault-management delay-statistics maintenance-domain ma1 maintenance-association ma1
  • To display the ETH-DM statistics collected for ETH-DM sessions for the local MEP 201 belonging to MA ma2 and within MD md2:

    user@host> show oam ethernet connectivity-fault-management delay-statistics maintenance-domain md2 maintenance-association ma2 local-mep 201
  • To display the ETH-DM statistics collected for ETH-DM sessions from local MEPs belonging to MA ma3 and within MD md3 to remote MEP 302:

    user@host> show oam ethernet connectivity-fault-management delay-statistics maintenance-domain md3 maintenance-association ma3 remote-mep 302

Displaying ETH-DM Statistics and Frame Counts

Purpose

Display ETH-DM statistics and ETH-DM frame counts.

By default, the show oam ethernet connectivity-fault-management mep-statistics command displays ETH-DM statistics and frame counts for MEPs in the specified CFM maintenance association (MA) within the specified CFM maintenance domain (MD).

Action

  • To display the ETH-DM statistics and ETH-DM frame counts for MEPs in MA ma1 and within MD md1:

    user@host> show oam ethernet connectivity-fault-management mep-statistics maintenance-domain md1 maintenance-association ma1
  • To display the ETH-DM statistics and ETH-DM frame counts for the local MEP 201 in MA ma2 and within MD md2:

    user@host> show oam ethernet connectivity-fault-management mep-statistics maintenance-domain md2 maintenance-association ma2 local-mep 201
  • To display the ETH-DM statistics and ETH-DM frame counts for the local MEP in MD md3 and within MA ma3 that participates in an ETH-DM session with the remote MEP 302:

    user@host> show oam ethernet connectivity-fault-management mep-statistics maintenance-domain ma3 maintenance-association ma3 remote-mep 302

Displaying ETH-DM Frame Counts for MEPs by Enclosing CFM Entity

Purpose

Display ETH-DM frame counts for CFM maintenance association end points (MEPs).

By default, the show oam ethernet connectivity-fault-management mep-database command displays CFM database information for MEPs in the specified CFM maintenance association (MA) within the specified CFM maintenance domain (MD).

Note

At the router attached to the initiator MEP for a one-way session, or at the router attached to the receiver MEP for a two-way session, you can only display ETH-DM frame counts.

Action

  • To display CFM database information (including ETH-DM frame counts) for all MEPs in MA ma1 within MD md1:

    user@host> show oam ethernet connectivity-fault-management mep-database maintenance-domain ma1 maintenance-association ma1
  • To display CFM database information (including ETH-DM frame counts) only for local MEP 201 in MA ma1 within MD md1:

    user@host> show oam ethernet connectivity-fault-management mep-database maintenance-domain md2 maintenance-association ma2 local-mep 201
  • To display CFM database information (including ETH-DM frame counts) only for remote MEP 302 in MD md3 within MA ma3:

    user@host> show oam ethernet connectivity-fault-management mep-database maintenance-domain ma3 maintenance-association ma3 remote-mep 302

Displaying ETH-DM Frame Counts for MEPs by Interface or Domain Level

Purpose

Display ETH-DM frame counts for CFM maintenance association end points (MEPs).

By default, the show oam ethernet connectivity-fault-management interfaces command displays CFM database information for MEPs attached to CFM-enabled Ethernet interfaces on the router or at a maintenance domain level. For Ethernet interfaces that support ETH-DM, any frame counts are also displayed when you specify the detail or extensive command option.

Note

At the router attached to the initiator MEP for a one-way session, or at the router attached to the receiver MEP for a two-way session, you can only display ETH-DM frame counts.

Action

  • To display CFM database information (including ETH-DM frame counts) for all MEPs attached to CFM-enabled Ethernet interfaces on the router:

    user@host> show oam ethernet connectivity-fault-management interfaces detail
  • To display CFM database information (including ETH-DM frame counts) only for the MEPs attached to CFM-enabled router interface ge-5/2/9.0:

    user@host> show oam ethernet connectivity-fault-management interfaces ge-5/2/9.0 detail
  • To display CFM database information (including ETH-DM frame counts) only for MEPs enclosed within CFM maintenance domains (MDs) at level 6:

    user@host> show oam ethernet connectivity-fault-management interfaces level 6 detail

Clearing ETH-DM Statistics and Frame Counts

Purpose

Clear the ETH-DM statistics and ETH-DM frame counts.

By default, statistics and frame counts are deleted for all MEPs attached to CFM-enabled interfaces on the router. However, you can filter the scope of the command by specifying an interface name.

Action

  • To clear the ETH-DM statistics and ETH-DM frame counts for all MEPs attached to CFM-enabled interfaces on the router:

    user@host> clear oam ethernet connectivity-fault-management statistics
  • To clear the ETH-DM statistics and ETH-DM frame counts only for MEPs attached to the logical interface ge-0/5.9.0:

    user@host> clear oam ethernet connectivity-fault-management statistics ge-0/5/9.0