Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Example: Configuring RFC2544-Based Benchmarking Tests on an MX104 Router for Layer 2 E-LAN Services in Bridge Domains

This example shows how to configure benchmarking tests for the Layer 2 E-LAN services in bridge domains. The example covers the four basic tests: throughput, frame-loss, back-to-back, and latency.

Requirements

Note:

MX Series routers support only the reflector function in RFC2544-based benchmarking tests. This example uses the MX104 3D Universal Edge Router as the reflector. You can also configure benchmarking tests on MX80 Series routers and MX240, MX480, and MX960 Series routers with MPC1, MPC2, and 16-port 10-gigabit Ethernet MPC from Junos OS Release 16.1 or later. To configure RFC2544-based benchmarking tests on MX240, MX480, MX960 Series routers, see Enabling Support for RFC 2544-Based Benchmarking Tests on MX Series Routers.

This example uses the following hardware and software components:

  • An MX104 (reflector)

  • An ACX Series router (initiator)

  • Junos OS Release 14.2 or later for MX Series routers

Overview

Consider a sample topology in which an ACX Series router functions as an initiator and terminator of the test frames for an RFC2544-based benchmarking test. ACX Series router is connected to a customer edge device CE1, on one side and is connected over a Layer 2 network to an MX104 Series router. The MX104 Series router functions as a reflector to reflect the test frames it receives from the ACX Series initiator back to the initiator. The MX04 Series router is also connected to a customer edge device CE2.

Note:

When Layer 2 reflection is enabled on an interface, filters are configured internally to block the ingress and egress traffic except test traffic through the test interface.

Figure 1 shows the sample topology to perform all four RFC2544-based benchmarking tests (throughput, back-to-back frames, latency, and frame-loss) for the UNI direction on a Layer 2 bridge network.

Figure 1: Layer 2 Reflection Simple TopologyLayer 2 Reflection Simple Topology

On the ACX Series router, ge-1/2/1.0 is the Layer 2 NNI interface and ge-1/1/3.0 is the Layer 2 UNI interface. On the MX104 Series router, ge-1/1/6.0 is the Layer 2 NNI interface and ge-1/1/5.0 is the Layer 2 UNI interface. The benchmarking tests are used to compute the performance attributes for an E-LAN service on a bridge domain.

Note:

Test packets can be identified using the destination MAC address, source MAC address, and test interface. Both tagged and untagged interfaces are supported. For tagged interfaces, the test interface is the VLAN sub interface. For untagged interfaces, the physical port represents the test interface. Traffic through other VLAN sub interfaces, present in the same physical port, is not affected when you configure the benchmarking test on one of the sub interfaces.

Configuration

In this example, you configure the benchmarking tests for the UNI direction for an E-LAN service on a Layer 2 bridge domain that is enabled between two routers to detect and analyze the performance of the interconnected routers. In this example, we start by configuring the ACX Series router. On the ACX Series router, you first configure each test by specifying the test profile, the test attributes, and then define the test by associating the test with the test profile with the relevant attributes. You can then configure the interface. On the MX104 Series router, you perform the same steps. However, a few attributes such as the outer VLAN ID, source UDP port, destination UDP port, the duration of each iteration, and their values are only applicable to the initiator or the ACX Series router.

Note:

When you configure the Layer 2 reflection, you can specify the service type under test as ELINE if you want to simulate an ELINE service using bridge encapsulation.

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them in a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy level:

Configuring Benchmarking Test Parameters on the ACX Series Router

Configuring Benchmarking Test Parameters on the MX104 Router

Configuring Throughput Benchmarking Test Parameters on the ACX Series Router

Step-by-Step Procedure

The following configuration requires you to configure a test profile for the throughput test and reference the test-profile in a unique test-name. The test-name defines the parameters for the throughput test to be performed on the ACX Series router.

To configure the throughput test parameters on the ACX Series router:

  1. In configuration mode, at the [edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.

  2. Define a name for the first test profile—for example, tput for the throughput test profile.

  3. Configure the type of test to be performed as throughput, specify the packet size as 128 bytes, and define the theoretical maximum bandwidth for the test in kilobits per second (Kbps), with a value from 1 Kbps through 1,000,000 Kbps.

  4. Enter the up command twice to go to the [edit services rpm rfc2544-benchmarking] level in the configuration hierarchy.

  5. Define a name for the throughput test—for example, tput-test. The test name can be up to 32 characters in length.

  6. Specify the name of the test profile, tput, to be associated with the test name.

  7. Configure the source and destination MAC address for the test packet.

  8. Configure the outer VLAN ID for the test frames and specify the service type under test to be E-LAN.

  9. Specify the test mode for the packets that are sent during the benchmarking test as initiation and termination.

  10. Configure the family type, bridge, for the benchmarking test and specify the direction, egress. Also, specify the source and destination UDP port to be used in the UDP headers of the test packet.

  11. Specify the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds, and specify the logical interface, ge-0/2/1.0, on which the RFC2544-benchmarking tests are run.

Configuring Back-to-Back Frames Benchmarking Test Parameters on the ACX Series Router

Step-by-Step Procedure

The following configuration requires you to configure a test profile for the back to back frames test and reference the test-profile in a unique test-name. The test-name defines the parameters for the back to back frames test to be performed on the ACX Series router.

To configure the back-to-back frames test parameters on the ACX Series router:

  1. In configuration mode, at the [edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.

  2. Define a name for the back-to-back test profile—for example, b2bt.

  3. Configure the type of test to be performed as back-to-back frames, specify the packet size as 128 bytes, and define the theoretical maximum bandwidth for the test in kilobits per second, with a value from 1 Kbps through 1,000,000 Kbps.

  4. Enter the up command twice to go to the [edit services rpm rfc2544-benchmarking] level in the configuration hierarchy.

  5. Define a name for the back-to-back frames test—for example, b2bt-test. The test name can be up to 32 characters in length.

  6. Specify the name of the test profile, b2bt, to be associated with the test name.

  7. Configure the source and destination MAC address for the test packet.

  8. Configure the outer VLAN ID for the test frames and specify the service type under test.

  9. Specify the test mode for the packets that are sent during the benchmarking test as initiation and termination.

  10. Configure the family type, bridge, for the benchmarking test and specify the direction, egress.

  11. Specify the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds. Also, specify the logical interface, ge-0/2/1.0, on which the RFC2544-based benchmarking test is run.

Configuring Latency Benchmarking Test Parameters on the ACX Series Router

Step-by-Step Procedure

The following configuration requires you to configure a test profile for the latency test and reference the test-profile in a unique test-name. The test-name defines the parameters for the latency test to be performed on the ACX Series router.

To configure the latency test parameters on the ACX Series router:

  1. In configuration mode, at the [edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.

  2. Define a name for the latency test profile—for example, lty.

  3. Configure the type of test to be performed as latency, specify the packet size of the test packet, and define the maximum bandwidth for the test in kilobits per second, with a value form 1 Kbps through 1,000,000 Kbps.

  4. Enter the up command twice to go to the previous level in the configuration hierarchy.

  5. Define a name for the latency test—for example, lty-test. The test name can be up to 32 characters in length.

  6. Specify the name of the test profile, lty, to be associated with the test name.

  7. Configure the source and destination MAC address for the test packet.

  8. Configure the outer VLAN ID for the test frames and specify the service type under test.

  9. Specify the test mode for the packets that are sent during the benchmarking test as initiation and termination.

  10. Configure the family type, bridge, for the benchmarking test and specify the direction, egress. Also, specify the source and destination UDP port to be used in the UDP headers of the test packet.

  11. Specify the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds. Also, specify the logical interface, ge-0/2/1.0, on which the RFC2544-based benchmarking test is run.

Configuring Frame Loss Benchmarking Test Parameters on the ACX Series Router

Step-by-Step Procedure

The following configuration requires you to configure a test profile for the frame loss test and reference the test-profile in a unique test-name. The test-name defines the parameters for the frame loss test to be performed on the ACX Series router.

To configure the frame loss test parameters on the ACX Series router:

  1. In configuration mode, at the [edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.

  2. Define a name for the frame loss test profile—for example, frloss.

  3. Configure the type of test performed as frame loss, specify the packet size of the test packet, and define the maximum bandwidth for the test in kilobits per second, with a value from 1 Kbps through 1,000,000 Kbps.

  4. Enter the up command to go to the previous level in the configuration hierarchy.

  5. Define a name for the frame loss test—for example, frloss-test. The test name can be up to 32 characters in length.

  6. Specify the name of the test profile, frloss, to be associated with the test name.

  7. Configure the source and destination MAC address for the test packet.

  8. Configure the outer VLAN ID for the test frames and specify the service type under test.

  9. Specify the test mode for the packets that are sent during the benchmarking test as initiation and termination.

  10. Configure the family type, bridge, for the benchmarking test and specify the direction, egress. Also, specify the source and destination UDP port to be used in the UDP headers of the test packet.

  11. Specify the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds. Also, specify the logical interface, ge-0/2/1.0, on which the RFC2544-based benchmarking test is run.

  12. Enter the exit command to go to the [edit] hierarchy level.

Configuring Other Benchmarking Test Parameters on the ACX Series Router

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode.

To configure the interface and bridge domain on the ACX Series router:

  1. Configure the Layer 2 NNI interface on which the tests must be run from the [edit] hierarchy level.

  2. Configure flexible VLAN tagging for the transmission of untagged frames or 802.1Q single-tagged and dual-tagged frames on the logical interface. You can also specify the maximum transmission unit (MTU) size for the interface and the encapsulation.

  3. Configure a logical unit for the interface, specify the encapsulation, and configure the VLAN ID on the logical interfaces.

  4. Configure the Layer 2 UNI interface.

  5. Configure flexible VLAN tagging for transmission of non-tagged frames or 802.1Q single-tag and dual-tag frames on the logical interface. You can also specify the maximum transmission unit (MTU) size for the interface and the encapsulation.

  6. Configure a logical unit for the interface and specify the encapsulation and configure the VLAN ID on the logical interfaces.

  7. Configure the bridge domain, bd1, and specify the VLAN ID associated with the bridge domain and the associated interfaces from the [edit] hierarchy level.

Configuring Benchmarking Test Parameters on the MX104 Router

Step-by-Step Procedure

The following configuration requires you to configure a unique test-name for the benchmarking test on the MX104 Series router. The test-name defines the parameters for the benchmarking test to be performed. Because the test interface and test MAC addresses are the same, you can create a single test configuration at the reflector (MX104).

To configure the benchmarking test parameters on the MX104 Series router:

  1. In configuration mode, at the [edit] hierarchy level, configure a real-time performance monitoring service (RPM) instance and an RFC2544-based benchmarking test for the RPM instance.

  2. Define a name for the test—for example, l2b-reflector. The test name can be up to 32 characters in length.

  3. Specify the source and destination MAC addresses of the test packet.

  4. Specify the service type under test and the mode which is reflect, at the reflector.

  5. Specify the mode which is reflect at the reflector.

  6. Configure the family type, bridge and specify the direction, egress, for the benchmarking test. Also, specify the logical interface, ge-1/1/5.0, on which the RFC2544-based benchmarking test is being run.

Configuring Other Benchmarking Test Parameters on the MX104 Router

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode.

To configure the interface and bridge domain on the MX104 Series router:

  1. Configure the Layer 2 NNI interface on which the tests must be run.

  2. Configure flexible VLAN tagging for transmission of untagged frames or 802.1Q single-tagged and dual-tagged frames on the logical interface. You can also specify the maximum transmission unit (MTU) size for the interface and the encapsulation.

  3. Configure a logical unit for the interface, specify the encapsulation, and configure the VLAN ID on the logical interface.

  4. Configure the Layer 2 NNI interface.

  5. Configure flexible VLAN tagging for transmission of untagged frames or 802.1Q single-tagged and dual-tagged frames on the logical interface. You can also specify the maximum transmission unit (MTU) size for the interface and the encapsulation.

  6. Configure a logical unit for the interface, specify the encapsulation, and configure the VLAN ID on the logical interfaces.

  7. Configure the bridge domain, bd1, and specify the VLAN ID associated with the bridge domain, and the associated interfaces from the [edit] hierarchy level.

  8. Start the benchmarking test on the reflector.

    After the test is successfully completed at the initiator, you can stop the test at the reflector by entering the test services rpm rfc2544-benchmarking test l2b-reflector stop command.

Results

In configuration mode, confirm your configuration on the ACX Series router and the MX104 Series router by entering the show command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

Benchmarking Test Parameters on the ACX Series router :

Benchmarking Test Parameters on the MX104 Series router:

Verifying the Results of the Benchmarking Tests for Layer 2 Services (E-LAN) in Bridge Domains

Examine the results of the benchmarking tests that are performed on the configured service between the ACX Series router and the MX104 Series router. Start the test on the reflector first and then start the test on the initiator.

Verifying the Throughput Benchmarking Test Results

Purpose

Verify that the necessary and statistical values are displayed for the benchmarking tests that are run on the configured service between the ACX Series router and the MX104 Series router.

Action

In operational mode, enter the show services rpm rfc2544-benchmarking test-id test-id-number detail command on the ACX Series router.

In operational mode, enter the show services rpm rfc2544-benchmarking test-id test-id-number detail command on the MX104 Series router.

You can also use the show services rpm rfc2544-benchmarking (aborted-test | active-tests | completed-tests | summary) command to display information about the results of each category or state of the RFC2544-based benchmarking tests for each real-time performance monitoring (RPM) instance.

Meaning

The output displays the details of the benchmarking test that was performed. For more information about the run show services rpm rfc2544-benchmarking operational command, see show services rpm rfc2544-benchmarking in the CLI Explorer.

Verifying the Back-to-Back Benchmarking Test Results

Purpose

Verify that the necessary and statistical values are displayed for the benchmarking tests that are run on the configured service between the ACX Series router and the MX104 Series router.

Action

In operational mode, enter the show services rpm rfc2544-benchmarking test-id test-id-number detail command on the ACX Series router.

In operational mode, enter the show services rpm rfc2544-benchmarking test-id test-id-number detail command on the MX104 Series router.

You can also use the show services rpm rfc2544-benchmarking (aborted-test | active-tests | completed-tests | summary) command to display information about the results of each category or state of the RFC2544-based benchmarking tests for each real-time performance monitoring (RPM) instance.

Meaning

The output displays the details of the benchmarking test that was performed. For more information about the run show services rpm rfc2544-benchmarking operational command, see show services rpm rfc2544-benchmarking in the CLI Explorer.

Verifying the Frame Loss Benchmarking Test Results

Purpose

Verify that the necessary and statistical values are displayed for the benchmarking tests that are run on the configured service between the ACX Series router and the MX104 Series router.

Action

In operational mode, enter the show services rpm rfc2544-benchmarking test-id test-id-number detail command on the ACX Series router.

In operational mode, enter the show services rpm rfc2544-benchmarking test-id test-id-number detail command on the MX104 Series router.

You can also use the show services rpm rfc2544-benchmarking (aborted-test | active-tests | completed-tests | summary) command to display information about the results of each category or state of the RFC2544-based benchmarking tests for each real-time performance monitoring (RPM) instance.

Meaning

The output displays the details of the benchmarking test that was performed. For more information about the run show services rpm rfc2544-benchmarking operational command, see show services rpm rfc2544-benchmarking in the CLI Explorer.

Verifying the Latency Benchmarking Test Results

Purpose

Verify that the necessary and statistical values are displayed for the benchmarking tests that are run on the configured service between the ACX Series router and the MX104 Series router.

Action

In operational mode, enter the show services rpm rfc2544-benchmarking test-id test-id-number detail command on the ACX Series router.

In operational mode, enter the show services rpm rfc2544-benchmarking test-id test-id-number detail command on the MX104 Series router.

You can also use the show services rpm rfc2544-benchmarking (aborted-test | active-tests | completed-tests | summary) command to display information about the results of each category or state of the RFC2544-based benchmarking tests for each real-time performance monitoring (RPM) instance.

Meaning

The output displays the details of the benchmarking test that was performed. For more information about the run show services rpm rfc2544-benchmarking operational command, see show services rpm rfc2544-benchmarking in the CLI Explorer.