Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    RFC2544-Based Benchmarking Tests Overview

    RFC2544 defines a series of tests that can be used to describe the performance characteristics of a network-interconnecting device, such as a router, and outlines specific formats to report the results of the tests. These tests can be used to benchmark interconnected network devices and devise a guideline or a measurement pattern to analyze the health and efficiency of the network devices. These tests are the standard benchmarking tests for Ethernet networks and are known as RFC2544-based benchmarking tests. These tests measure throughput, latency, frame loss rate, and bursty frames. The test methodology enables you to define various parameters such as different frame sizes to be examined (64, 128, 256, 512, 1024, 1280, and 1518 bytes), the test time for each test iteration (10 seconds through 1,728,000 seconds), and the frame format (UDP-over-IP).

    Note: RFC2544-based benchmarking tests support only UDP over IPv4 test traffic (unicast).

    An RFC2544-based benchmarking test is performed by transmitting test packets from a device that functions as the generator or the initiator (which is also called the originator). These packets are sent to a device that functions as a reflector, which receives and returns the packets to the initiator.

    Juniper Networks MX104 3D Universal Edge Routers support only the reflector function and the corresponding benchmarking tests. Starting from release 15.1, MX104 routers also perform verification of signatures on the received test frames. By default, when the MX104 router receives a test packet that does not have the signature pattern, the packet is dropped. If you generate test traffic using a third-party vendor tool instead of an ACX Series router, you can disable signature verification. To disable signature verification, use the disable-signature-check command.

    The RFC2544-based benchmarking test methodology assesses different parameters that are defined in service-level agreements (SLAs). By measuring the performance availability, transmission delay, link bursts, and service integrity, a carrier provider can certify that the working parameters of the deployed Ethernet circuit comply with the SLA and other defined policies.

    Table 1 describes the different network topologies in which the benchmarking test is supported.

    Table 1: Supported Network Topologies for RFC2544 Benchmarking Tests

    Service Type

    Traffic Direction

    Mode

    Initial Release on MX104 Routers

    Whether the Benchmarking Test Is Supported

    E-Line (family bridge)

    (UNI) Egress

    Port

    Port, VLAN

    14.2R1

    (E-Line family bridge)

    Supported

    E-LAN

    (family bridge and family vpls)

    (UNI) Egress

    14.2R1

    (E-LAN family bridge)

    15.1R1

    (E-LAN family vpls)

    Supported

    Supported

    E-Line (family ccc)

    Ingress

    Egress

    13.3R1
    (E-Line pseudowire)

    Supported

    IP Services (family inet)

    NNI

    13.3R1

    Supported

    Note: You can configure a total of four simultaneous active reflection sessions. The four active reflection sessions can be of the same type or can be a combination of the different types of reflection sessions. For instance, you can configure either four IPv4 reflection sessions or one session each for pseudowire reflection, VPLS reflection, Layer 2 reflection, and IPv4 reflection. The maximum reflection bandwidth supported is 4 Gbps in a standalone test condition.

    Table 2 lists the interfaces and the reflection type on which the benchmarking tests are supported.

    Table 2: Supported Interfaces for RFC2544 Benchmarking Tests

    Type of Reflection

    Gigabit Interfaces (ge)

    Aggregated Interfaces (ae)

    10G Interfaces (xe)

    Pseudo Interfaces (irb, lt, vt, lo0, and others)

    IPv4

    Yes

    No

    No

    No

    Pseudowire ingress

    Yes

    No

    No

    No

    Pseudowire egress

    Yes

    Yes

    Yes

    No

    Layer 2 bridge

    Yes

    Yes

    Yes

    No

    Layer 2 VPLS

    Yes

    Yes

    Yes

    No

    All active RFC2544-based benchmarking tests are stopped when any of the following events takes place:

    • System events such as Packet Forwarding Engine restarts, Routing Engine restarts, and so on.
    • Test interface change events such as deactivation and reactivation of the interface, disabling and enabling of the interface, child link events for aggregated interfaces and so on.

      After the benchmarking tests are stopped, the test states of the tests are removed and the user can restart the same test. Other ongoing tests on other interfaces are not interrupted.

    Note: RFC2544-based benchmarking tests are not supported during unified in-service software upgrade (ISSU) and graceful Routing Engine switchover (GRES).

    Modified: 2016-01-28