Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Layer 2 and Layer 3 RFC 2544-Based Benchmarking Test Overview

In ACX Series routers, RFC 2544-based benchmark tests can be run to measure the performance characteristics of the E-LINE, E-LAN, and EVPL services.


ACX5048 and ACX5096 routers support only E-LINE services. ACX5448, ACX5048 and ACX5096 routers do not support family inet based reflection. Layer 2 reflection (Family bridge and family ccc) are supported. ACX7100 routers only support Layer 3 (family inet) IPv4 reflection; they do not support family bridge or family ccc.

  • You can configure the test on the following underlying services:

    • Between two IPv4 endpoints—In this mode, the generator sends test packets to user-configured IP destination or UDP port (which is of the reflector).

    • Between two user-to-network interfaces (UNIs) of Ethernet Virtual Connection (EVC), Ethernet Private Line (EPL, also called E-LINE), Ethernet Virtual Private Line (EVPL), EVC (EPL, EVPL)—One end is configured as the generator or initiator and the other end acts as the reflector. The generator receives the test packets that are returned from the reflector and computes the test results.


    Benchmarking tests are not supported for IPv6-based services.

  • You cannot perform multiple simultaneous RFC 2544-based benchmarking tests on the same pseudowire.

  • Interoperation of the RFC 2544 benchmarking tests with other third-party customer premises equipment (CPE) that provides embedded or dedicated benchmarking test capability is not supported.

  • Fragmented test-frames and one-way measurements of frames are not supported. You must configure one end or the source device to initiate and terminate test frames and the other end or the destination device to reflect the received frames back to the initiator.

  • RFC 2544 generator and reflector are supported with testing bandwidth up to 1 Gbps. ACX5048 and ACX5096 routers supports test bandwidth of up to 40 Gbps.

  • The test session is supported in out-of-service mode for the underlying service. You must not transmit any traffic to the UNI port, configured as a generator or a reflector, that is being tested during the duration of the test. However, other services that are not configured for the testing session are not impacted.

  • Devices embedded with benchmarking test capabilities (generators and reflectors) interoperate with other Juniper Networks devices that support the RFC 2544-based generator or reflector functionality.

  • RFC 2544 generator traffic undergoes the same traffic classifier and policer or shaper processing as the ingress customer traffic from the UNI port.

  • RFC 2544 generator produces a report with clear details of pass or fail for each critical testing metric, based on the configured thresholds.

  • The testing packets can be configured and the format of the packet depends on the underlying service on which the test is configured. For IP-based service, the IP or port values can be configured. For Ethernet-based service, unicast untagged or VLAN ID-tagged dot1p formats (IEEE 802.1p or packet classification Layer 2 headers) are supported. The Ethernet destination address and source address that you configured are used.

  • You can run RFC 2544 benchmarking inet tests on Layer 3 VPN or virtual router.

  • For an inet service, each test session needs to use a unique UDP port. On the initiator device, the source UDP port that you specify by using the source-udp-port statement must be unique and not used by other UDP services that terminate at the initiator. On the reflector device, the UDP port of the destination to be used in the UDP header for the generated frames by using the destination-udp-port statement must be unique and not used by other UDP services that terminate at the reflector.

  • You must start the test on the router that operates as the reflector before you start the test on router that functions as the initiator.

  • You must configure the size of the test packet based on the configured MTU of the packets.

  • For computation of the test results for a user-to-network interface (UNI) or ingress direction of an Ethernet pseudowire service, the customer edge (CE) device that is configured as a reflector for inet must have the reflected destination address resolved using ARP or a statically configured route must be present on the CE device to connect to the initiator.

  • For benchmarking tests on the UNI direction of an Ethernet pseudowire service, if reflection mode is configured, you must configure a static ARP entry. Otherwise, the tests fail when test frames on the UNI interface are reflected. ARP resolution does not enable a successful reflection of test frames for UNI interfaces.

  • For a CCC family and with the test performed in the egress or network-to-network interface (NNI) direction, the tests stop on the initiator and reflector when the pseudowire goes down.

  • For an RFC 2544 test that is run in the egress or network-to-network interface (NNI) direction of an Ethernet service for a CCC family, the ingress features are not applied.

  • In ACX5048 and ACX5096 routers, for a CCC family, the pseudowire has to be opened prior to the start of the RFC 2544 test and during the course of the test.

  • The configured packet size denotes the untagged packet size. Any additional VLAN in the payload causes the packet length to be increased correspondingly.

  • For an inet service, if you configure an interface on an initiator for the RFC 2544-based benchmarking test to be run without specifying the source IPv4 address for the test frames, the primary IP address of the interface is used for the test frames. If the primary IP address is not configured, the first IPv4 address of the interface is used. Similarly, for an unnumbered interface on an initiator on which the RFC 2544 test is run, the primary or the first IP address of the donor loopback interface is retrieved and used in the test frames. You must explicitly configure the source IPv4 address for the test frames by using the source-ipv4-address statement if you want a particular address to be used.

  • RFC 2544 test generates packets for performance benchmarking testing. The packets can be destined for known or unknown unicast MAC addresses, and they can be either tagged or untagged frames. UDP/IP packet is used as the frame payload. Refer to Configuring RFC 2544-Based Benchmarking Tests for the frame fields that can be configured.

  • Supported outer TPIDs for tagged frames are 0x8100, 0x88a8, 0x9100, and 0x9200.

  • RFC 2544 benchmark tests can be run in out-of-service and in in-service modes.


    In out-of-service mode, while the test is running, all the data traffic sent to and from the UNI port under test on the service is interrupted. Control protocol packets are not interrupted.

    In in-service mode, while the test is running, only the data traffic corresponding to the test session is interrupted, rest of the data traffic flow sent to and from the UNI port under test on the service are not affected. Control protocol packets are not interrupted.

  • The source MAC address, destination MAC address, and the UNI port under test configured uniquely identifies the RFC 2544 benchmark test session (or test stream).

  • You can run only one test at a time. Multiple simultaneous tests cannot be run at a time.

  • The maximum theoretical test bandwidth supported by ACX Series routers for RFC 2544 test initiator or reflector is 1 Gpbs. On ACX5048 and ACX5096 routers, the maximum theoretical test bandwidth supported for RFC 2544 reflector is 40 Gbps.

  • RFC 2544 tests can be run with different frame sizes. In ACX Series routers, the supported frame sizes are 64, 68, 72, 128, 256, 512, 768, 1024, 1280, 1518, 1522, 1600, 1728, 2496, 3584, 4016, 9104, and 9136 bytes.

  • The test uses round-trip traffic for performance measurement.

  • A history of the test results is stored in memory.

  • The test results can be copied to the local file system or a remote file system, optionally.


RFC 2544 tests cannot compute the performance attributes of multicast or broadcast traffic streams.