Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Example: Configuring an RFC 2544-Based Benchmarking Test on an MX104 Router for UNI Direction of Ethernet Pseudowires

This example shows how to configure the RFC2544-based benchmarking test for the user-to-network interface (UNI) direction of an Ethernet pseudowire service that is enabled between two routers. The test detects and analyzes the performance of the interconnected routers.

Requirements

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 13.3 or later

Overview

Consider a sample topology in which a router, Router A (MX104), functions as a reflector of the test frames for an RFC 2544-based benchmarking test. The logical customer edge (CE)-facing interface and inet family are configured on Router A. Router A is not part of a pseudowire and therefore, a Layer 3 family configuration is required on it. Router A, which is a customer edge device CE1 is connected to Router B (ACX), which functions as a provider edge device PE1 over an Ethernet pseudowire in the UNI direction with EtherType or Layer 2 Ethernet payload. The logical interface, family, and UNI direction are configured on Router B. Router B or PE1 is connected over an Ethernet pseudowire in the NNI direction to a provider edge device at the remote site, PE2. The link between CE1 and PE1 is an Ethernet Layer 2 network and it can be configured with any EtherType value. The link between PE1 and PE2 is an Ethernet line (E-Line) or an Ethernet Private Line (EPL) that has Layer 2 payload and Layer 3 transport sent over it. Router B or PE1 functions as an initiator and terminator of the test frames that are sent to Router A and reflected back from it.

This benchmarking test is used to compute the performance attributes in the user-to-network interface (UNI) direction of an Ethernet pseudowire service between Router A and Router B. Data traffic arriving from a network-to-network interface (NNI) toward the customer edge is ignored while the test is in progress. Packets from the CE are not sent toward the NNI because all packets are assumed to be test probes.

Figure 1 shows the sample topology to perform an RFC 2544 test for the UNI direction of an Ethernet pseudowire service.

Figure 1: RFC 2544-Based Benchmarking Test for UNI Direction of an Ethernet Pseudowire RFC 2544-Based Benchmarking Test for UNI Direction of an Ethernet Pseudowire

Configuration

In this example, you configure the benchmarking test for the UNI direction of an Ethernet pseudowire service that is enabled between two routers to detect and analyze the performance of the interconnected routers.

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 Router B (Initiator and Terminator)

Configuring Benchmarking Test Parameters on Router A (Reflector)

Configuring Benchmarking Test Parameters on Router B (Initiator and Terminator)

Step-by-Step Procedure

The following require 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 test parameters on Router B:

  1. In configuration mode, go to the [edit interfaces] hierarchy level:

  2. Configure the interface on which the test must be run.

  3. Configure VLAN tagging for transmission and reception of 802.1Q VLAN-tagged frames.

  4. Configure a logical unit and specify the protocol family as inet.

  5. Specify the address for the logical interface.

  6. Configure the VLAN ID on the logical interface as 101.

  7. Go to the top level of the configuration command mode.

  8. In configuration mode, go to the [edit services] hierarchy level.

  9. Configure a real-time performance monitoring service (RPM) instance.

  10. Configure an RFC 2544-based benchmarking test for the RPM instance.

  11. Define a name for a test profile—for example, throughput.

  12. Configure the type of test to be performed as throughput.

  13. Specify the size of the test packet as 64 bytes.

  14. Specify the period for which the test is to be performed in hours, minutes, or seconds by specifying a number followed by the letter h (for hours), m (for minutes), or s (for seconds). In this example, you configure the period as 20 minutes.

  15. Define the theoretical maximum bandwidth for the test in kilobits per second, with a value from 1 Kbps through 1,000,000 Kbps.

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

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

  18. Define a name for the test—for example, test1. The test name identifier can be up to 32 characters in length.

  19. Specify the name of the test profile—for example, throughput—to be associated with a particular test name.

  20. Specify the logical interface, ge-0/0/0.0, on which the RFC 2544-based benchmarking test is run.

  21. Specify the test mode for the packets that are sent during the benchmarking test as initiate-and-terminate.

  22. Configure the address type family, inet, for the benchmarking test.

  23. Configure the destination IPv4 address for the test packets as 192.0.2.2.

  24. Specify the UDP port of the destination to be used in the UDP header for the generated frames as 4001.

Verify the Configuration and Commit

In configuration mode, confirm your configuration on Router B 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 Router B:

When the configuration is correct, commit the configuration:

Configuring Benchmarking Test Parameters on Router A (Reflector)

Step-by-Step Procedure

The following require 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 test parameters on Router A:

  1. In configuration mode, go to the [edit interfaces] hierarchy level:

  2. Configure the interface on which the test must be run.

  3. Configure VLAN tagging for transmission and reception of 802.1Q VLAN-tagged frames.

  4. Configure a logical unit for the interface.

  5. Specify the encapsulation for Ethernet VLAN circuits.

  6. Configure the VLAN ID as 101 on the logical interface.

  7. Go to the top level of the configuration command mode.

  8. In configuration mode, go to the [edit services] hierarchy level.

  9. Configure a real-time performance monitoring service (RPM) instance.

  10. Configure an RFC 2544-based benchmarking test for the RPM instance.

  11. Define a name for the test—for example, test1. The test name identifier can be up to 32 characters in length.

  12. Specify the logical interface on which the RFC 2544-based benchmarking test is run.

  13. Specify reflect as the test mode for the packets that are sent during the benchmarking test.

  14. Configure the address type family, ccc, for the benchmarking test.

  15. Specify the direction of the interface on which the test must be run, which is UNI in this example.

Verify the Configuration and Commit

In configuration mode, confirm your configuration on Router A 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 Router A:

When the configuration is correct, commit the configuration.

Run the Benchmarking Test

  • Start the benchmarking test on the reflector (Router A).

    The test stops automatically at the initiator (Router B) when the test successfully completes. After the test successfully completes at the initiator, stop the test at the reflector (Router A).

Verifying the Benchmarking Test Results

Examine the results of the benchmarking test that is performed on the configured service between Router A and Router B.

Purpose

Verify that the necessary and desired statistical values are displayed for the benchmarking test that is run on the configured service between Router A and Router B.

Action

In operational mode, enter the show services rpm rfc2544-benchmarking (aborted-tests | active-tests | completed-tests | summary) command to display information about the results of each category or state of the RFC 2544-based benchmarking test, such as terminated tests, active tests, and completed 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 show services rpm rfc2544-benchmarking operational command, see show services rpm rfc2544-benchmarking in the CLI Explorer.