Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: One-Way Ethernet Frame Delay Measurement

Description of the One-Way Frame Delay Measurement Example

This example shows how you can configure two MX Series routers (MX-PE1 and MX-PE2) to support an ETH-DM session between two peer MEPs (MEP 201 and MEP 101), initiate a one-way ETH-DM session (from MEP 101 to MEP 201), and then display the ETH-DM statistics and frame counts collected. To increase the accuracy of the ETH-DM statistics, enable optional hardware-assisted timestamping of received ETH-DM frames on the router that contains the receiver MEP.

Routers Used in This Example

• Routers MX-PE1 and MX-PE2 are MX Series routers.
• The system clocks of routers MX-PE1 and MX-PE2 are closely synchronized.
• On router MX-PE1, interface ge-5/2/9 is an Ethernet port. The traffic load received is heavy.
• On router MX-PE2, interface ge-0/2/5 is an Ethernet port.

ETH-DM Frame Counts for this Example

• At router MX-PE2, which contains the initiator MEP 101, the CFM database stores the ETH-DM frame counts for a one-way ETH-DM initiator (the count of 1DM frames sent).
• At router MX-PE1, which contains the receiver MEP 201, the CFM database stores the ETH-DM frame counts for a one-way ETH-DM receiver (the count of valid 1DM frames received and the count of invalid 1DM frames received).

ETH-DM Statistics for this Example

For a one-way frame delay measurement, only the router that contains the receiver MEP measures and stores frame delay statistics. In this example, ETH-DM statistics collected for the session are available only at router MX-PE1.

Steps for the One-Way Frame Delay Measurement Example

1. At router MX-PE1, configure MEP 201 as a CFM maintenance association endpoint in CFM maintenance domain md6 as follows:

   1. Define the maintenance domain md6 by associating it with maintenance domain level 6 and maintenance association identifier ma6.
   2. Configure the maintenance association by specifying continuity protocol options and specifying MEP identifier 201.
   3. Configure MEP 201 by attaching it to logical interface ge-5/2/9.0, which is a single-tag interface on VLAN 512.

   The following configuration is only a partial example of a complete and functional router configuration:

   [edit]

   interfaces { # Configure a single-tag logical interface on VLAN 512ge-5/2/9 { vlan-tagging;unit 0 {vlan-id 512;}}}

   protocols {oam {ethernet {connectivity-fault-management {traceoptions {file eoam_cfm.log size 1g files 2 world-readable;flag all;}maintenance-domain md6 { # Define MD ’md6’ on router MX-PE1level 6;maintenance-association ma6 { # Configure MA ’ma6’ on router MX-PE1continuity-check {interval 100ms;hold-interval 1;}mep 201 { # Configure MEP 201 on router MX-PE1interface ge-5/2/9.0; # Attach to logical interface on VLAN 512direction down;auto-discovery;}}}}}}}

2. At router MX-PE2, configure MEP 101 as a CFM maintenance association endpoint in CFM maintenance domain md6 as follows:

   1. Define the maintenance domain md6 by associating it with maintenance domain level 6 and maintenance association identifier ma6.
   2. Configure the maintenance association by specifying continuity protocol options and specifying MEP identifier 101.
   3. Configure MEP 101 by attaching it to logical interface ge-0/2/5.0, which is a single-tag interface on VLAN 512.

   The following configuration is only a partial example of a complete and functional configuration for router MX-PE2:

   [edit]

   interfaces { # Configure a single-tag logical interface on VLAN 512ge-0/2/5 {vlan-tagging;unit 0 {vlan-id 512;}}}

   protocols {oam {ethernet {connectivity-fault-management {traceoptions {file eoam_cfm.log size 1g files 2 world-readable;flag all;}maintenance-domain md6 { # Define MD ’md6’ on router MX-PE2level 6;maintenance-association ma6 { # Configure MA ’ma6’ on router MX-PE2continuity-check {interval 100ms;hold-interval 1;}mep 101 { # Configure MEP 101 on router MX-PE2interface ge–0/2/5.0; # Attach to logical interface on VLAN 512direction down;auto-discovery;}}}}}}

3. (Optional) To increase the accuracy of the ETH-DM statistics, modify the configuration of router MX-PE1, which contains the receiver MEP, by enabling hardware-assisted timestamping of 1DM frames received on the router.

   [edit protocols]

   oam {ethernet {connectivity-fault-management {performance-monitoring {hardware-assisted-timestamping;}}}}
4. At router MX-PE2, start a one-way frame delay measurement session from local MEP 101 to remote MEP 201 on router MX-PE1:
   user@MX-PE2> monitor ethernet delay-measurement one-way mep 201 maintenance-domain md6 maintenance-association ma6 count 10

   One-way ETH-DM request to 00:90:69:0a:43:94, Interface ge-0/2/5.0
   1DM Frames sent : 10
   --- Delay measurement statistics ---
   Packets transmitted: 10
   Average delay: NA, Average delay variation: NA
   Best case delay: NA, Worst case delay: NA

5. At router MX-PE2, which contains the initiator MEP, only the ETH-DM frame counts are available. Furthermore, the only frame count tallied for the initiator of a one-way frame delay measurement is the count of 1DM frames transmitted.

   ETH-DM frame counts (the number of 1DM, DMM, and DMR frames exchanged during an ETH-DM session) are stored in the CFM database of both the initiator and receiver MEPs. When you display CFM database information, you can also display the ETH-DM frame counts. You can display CFM database information for all interfaces on the router, or you can limit the output to MEPs associated with certain CFM MDs and MAs.

   • To display CFM database information for MEPs specified by enclosing CFM entities, use the mep-database form of the show oam ethernet connectivity-fault-management command. A CFM database also stores any ETH-DM frame counts.

     In the example configuration for router MX-PE2, MEP 101 is the only MEP defined in MA ma6 within MD md6. Therefore, the show oam ethernet connectivity-fault management mep-database command output displays CFM database information for MEP 101 only, even though you do not filter the command output by including the local-mep or remote-mep command options.

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

     Maintenance domain name: md6, Format: string, Level: 6
       Maintenance association name: ma6, Format: string
       Continuity-check status: enabled, Interval: 100ms, Loss-threshold: 3 frames
       MEP identifier: 101, Direction: down, MAC address: 00:90:69:0a:48:57
       Auto-discovery: enabled, Priority: 0
       Interface name: ge-0/2/5.0, Interface status: Active, Link status: Up
       Defects:
         Remote MEP not receiving CCM                  : no
         Erroneous CCM received                        : no
         Cross-connect CCM received                    : no
         RDI sent by some MEP                          : no
       Statistics:
         CCMs sent                                     : 1590
         CCMs received out of sequence                 : 0
         LBMs sent                                     : 0
         Valid in-order LBRs received                  : 0
         Valid out-of-order LBRs received              : 0
         LBRs received with corrupted data             : 0
         LBRs sent                                     : 0
         LTMs sent                                     : 0
         LTMs received                                 : 0
         LTRs sent                                     : 0
         LTRs received                                 : 0
         Sequence number of next LTM request           : 0
         1DMs sent                                     : 10
         Valid 1DMs received                           : 0
         Invalid 1DMs received                         : 0
         DMMs sent                                     : 0
         DMRs sent                                     : 0
         Valid DMRs received                           : 0
         Invalid DMRs received                         : 0
       Remote MEP count: 1
         Identifier    MAC address        State    Interface
           201     00:90:69:0a:43:94       ok    ge-0/2/5.0
     

   • To display CFM database information for MEPs specified by interface name, use the interfaces detail form of the show oam ethernet connectivity-fault-management command. A CFM database also stores any ETH-DM frame counts.

     In the example configuration for router MX-PE2, MEP 101 is the only MEP assigned to an interface on the router. Therefore, the show oam ethernet connectivity-fault-management interfaces (detail | extensive) command output displays CFM database information for MEP 101 only, even though you do not filter the command output by including the ethernet-interface-name or level md-level command options.

     user@MX-PE2> show oam ethernet connectivity-fault-management interfaces detail

     Interface name: ge-0/2/5.0, Interface status: Active, Link status: Up
       Maintenance domain name: md6, Format: string, Level: 6
         Maintenance association name: ma6, Format: string
         Continuity-check status: enabled, Interval: 100ms, Loss-threshold: 3 frames
         MEP identifier: 101, Direction: down, MAC address: 00:90:69:0a:48:57
         MEP status: running
         Defects:
           Remote MEP not receiving CCM                  : no
           Erroneous CCM received                        : no
           Cross-connect CCM received                    : no
           RDI sent by some MEP                          : no
         Statistics:
           CCMs sent                                     : 1590
           CCMs received out of sequence                 : 0
           LBMs sent                                     : 0
           Valid in-order LBRs received                  : 0
           Valid out-of-order LBRs received              : 0
           LBRs received with corrupted data             : 0
           LBRs sent                                     : 0
           LTMs sent                                     : 0
           LTMs received                                 : 0
           LTRs sent                                     : 0
           LTRs received                                 : 0
           Sequence number of next LTM request           : 0
           1DMs sent                                     : 10
           Valid 1DMs received                           : 0
           Invalid 1DMs received                         : 0
           DMMs sent                                     : 0
           DMRs sent                                     : 0
           Valid DMRs received                           : 0
           Invalid DMRs received                         : 0 
         Remote MEP count: 1
           Identifier    MAC address        State    Interface
             201     00:90:69:0a:43:94       ok    ge-0/2/5.0
     

   Note: You can use these same commands—show oam ethernet connectivity-fault-management mep-database and show oam ethernet connectivity-fault-management interfaces (detail | extensive)—at router MX-PE1 to display the CFM database information (which includes any ETH-DM frame counts) for receiver MEP 201.

6. At router MX-PE1, which contains the receiver MEP, you can use two different show oam ethernet connectivity-fault-management commands to display ETH-DM statistics and ETH-DM frame counts.

   • To display only the delay statistics, use the delay-statistics form of the show oam ethernet connectivity-fault-management command:
     user@MX-PE1> show oam ethernet connectivity-fault-management delay-statistics maintenance-domain md6

     MEP identifier: 201, MAC address: 00:90:69:0a:43:94
     Remote MEP count: 1
     
       Remote MAC address: 00:90:69:0a:48:57
         Delay measurement statistics:
         Index  One-way delay  Two-way delay
                   (usec)         (usec)    
           1        370          
           2        357          
           3        344          
           4        332          
           5        319          
           6        306          
           7        294          
           8        281          
           9        269          
           10       255          
         Average one-way delay          : 312 usec
         Average one-way delay variation: 11 usec
         Best case one-way delay        : 255 usec
         Worst case one-way delay       : 370 usec
     

   • To display both the ETH-DM statistics and the CFM database information (which includes any ETH-DM frame counts), use the mep-statistics form of the show oam ethernet connectivity-fault-management command:
     user@MX-PE1> show oam ethernet connectivity-fault-management mep-statistics maintenance-domain md6

     MEP identifier: 201, MAC address: 00:90:69:0a:43:94
     Remote MEP count: 1
       CCMs sent                                     : 3240
       CCMs received out of sequence                 : 0
       LBMs sent                                     : 0
       Valid in-order LBRs received                  : 0
       Valid out-of-order LBRs received              : 0
       LBRs received with corrupted data             : 0
       LBRs sent                                     : 0
       LTMs sent                                     : 0
       LTMs received                                 : 0
       LTRs sent                                     : 0
       LTRs received                                 : 0
       Sequence number of next LTM request           : 0
       1DMs sent                                     : 0
       Valid 1DMs received                           : 10
       Invalid 1DMs received                         : 0
       DMMs sent                                     : 0
       DMRs sent                                     : 0
       Valid DMRs received                           : 0
       Invalid DMRs received                         : 0
     
       Remote MEP identifier: 101
       Remote MAC address: 00:90:69:0a:48:57
         Delay measurement statistics:
         Index  One-way delay  Two-way delay
                   (usec)         (usec)    
           1        370          
           2        357          
           3        344          
           4        332          
           5        319          
           6        306          
           7        294          
           8        281          
           9        269          
           10       255          
         Average one-way delay          : 312 usec
         Average one-way delay variation: 11 usec
         Best case one-way delay        : 255 usec
         Worst case one-way delay       : 370 usec