Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Supported Platforms

 

Related Documentation

 

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.

 

Related Documentation

 

Published: 2012-12-11

Supported Platforms

 

Related Documentation

 

Published: 2012-12-11

Previous Page Next Page