Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Understanding RFC 2544-Based Benchmarking Tests on MX Series Routers and SRX Devices

RFC 2544 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 RFC 2544-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 the 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).

The RFC 2544-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.

Note:

MX Series routers and SRX devices support only the reflector function in RFC 2544-based benchmarking tests.

Note:

RFC 2544-based benchmarking tests support only UDP over IPv4 test traffic (unicast).

An RFC 2544-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.

Starting from Junos OS Release 15.1, MX104 Series routers also perform verification of signatures on the received test frames. Starting in Junos OS Release 21.1R1, SRX300 and SRX550HM devices perform verification of signatures on the received test frames. By default, when the router or device 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, configure the disable-signature-check statement at the [edit services rpm rfc2544-benchmarking tests test-name test-name] hierarchy level.

For MX80 and MX104 Universal Routing Platforms and, starting from Junos OS Release 16.1, MX240, MX480, and MX960 Universal Routing Platforms with MPC1 (MX-MPC1-3D), MPC2 (MX-MPC2-3D), and the 16-port 10-Gigabit Ethernet MPC (MPC-3D-16XGE-SFP), support the reflector function and the corresponding benchmarking tests.

Starting from Junos OS Release 17.1R1, the reflector function and the corresponding benchmarking tests are supported on MX Series routers with MPC3E (MX-MPC3E-3D), MPC3E-NG (MX-MPC3E-3D-NG), MPC4E (MPC4E-3D-32XGE-SFPP and MPC4E-3D-2CGE-8XGE), MPC5E (MPC5E-40G10G, MPC5EQ-40G10G, MPC5E-100G10G, and MPC5EQ-100G10G), and MPC6E (MX2K-MPC6E).

Starting in Junos OS Release 20.2R1, the RFC 2544-based benchmarking tests are supported on MX240, MX480, and MX960 routers with the MPC10E (MPC10E-15C-MRATE and MPC10E-10C-MRATE) line card and on MX2010 and MX2020 routers with the MX2K-MPC11E line card.

Junos OS Release 20.3R1 extends support for the RFC 2544-based benchmarking tests onto the MX240, MX480, and MX960 routers with the MPC7E-MRATE or MPC7E-10G line card, onto the MX2008, MX2010, and MX2020 routers with the MX2K-MPC8E or MX2K-MPC9E line card, and onto the MX204 and MX10003 (with the LC2103 card) routers.

Starting in Junos OS Release 21.1R1, the IPv4 Layer 3 reflector function and the corresponding benchmarking tests are supported on the SRX300 and SRX550HM devices.

Note:

To configure RFC2544-based benchmarking tests on MX Series routers, see Enabling Support for RFC 2544-Based Benchmarking Tests on MX Series Routers.

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

Table 1: Supported MX Network Topologies for RFC2544 Benchmarking Tests

Service Type

Traffic Direction

Mode

Initial Release on MX104 Series Routers

Initial Release on MX204, MX2008, and MX10003 Series Routers

Initial Release on MX240, MX480, and MX960 Series Routers

Initial Release on MX2010 and MX2020 Series Routers

Whether the Benchmarking Test Is Supported

E-Line (family bridge)

(UNI) Egress

(UNI) Ingress

Port

Port, VLAN

14.2R1

(E-Line family bridge)

17.1R1

20.3R1

20.3R1

16.1R1

17.1R1

20.2R1

20.2R1

Supported

E-LAN

(family bridge and family vpls)

(UNI) Egress

(UNI) Ingress

Port

Port, VLAN

14.2R1

(E-LAN family bridge)

15.1R1

(E-LAN family vpls)

17.1R1

20.3R1

20.3R1

16.1R1

17.1R1

20.2R1

20.2R1

Supported

E-Line (family ccc)

Ingress

Egress

Port

Port, VLAN

13.3R1

(E-Line pseudowire)

20.3R1

20.3R1

16.1R1

20.2R1

Supported

IP Services (family inet)

NNI

Port

Port, VLAN

13.3R1

20.3R1

16.1R1

20.2R1

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. Starting in Junos OS Release 20.2R1, MPC10E and MX2K-MPC11E support a maximum reflection bandwidth of 100 Gbps.

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)

40G/100G interfaces (et) for MPC10E and MX2K-MPC11E

10G Interfaces (xe)

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

IPv4

Yes

Yes

Yes

Yes

No

Pseudowire ingress

Yes

Yes

Yes

yes

No

Pseudowire egress

Yes

Yes (starting in Junos OS Release 15.1)

Yes

Yes (starting in Junos OS Release 15.1)

No

Layer 2 bridge

Yes

Yes

Yes

Yes

No

Layer 2 VPLS

Yes

Yes

Yes

Yes

No

All active RFC2544-based benchmarking tests are stopped when any of the following events take 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 an unified in-service software upgrade (ISSU) or a graceful Routing Engine switchover (GRES).

Release History Table
Release
Description
21.1R1
Starting from Junos OS Release 21.1R1, the IPv4 Layer 3 reflector function and the corresponding benchmarking tests are supported on the SRX300 and SRX550HM devices.
20.3R1
Junos OS Release 20.3R1 extends support for the RFC 2544-based benchmarking tests onto the MX240, MX480, and MX960 routers with the MPC7E-MRATE or MPC7E-10G line card, onto the MX2008, MX2010, and MX2020 routers with the MX2K-MPC8E or MX2K-MPC9E line card, and onto the MX204 and MX10003 (with the LC2103 card) routers.
20.2R1
Starting in Junos OS Release 20.2R1, the RFC 2544-based benchmarking tests are supported on MX240, MX480, and MX960 routers with the MPC10E (MPC10E-15C-MRATE and MPC10E-10C-MRATE) line card and on MX2010 and MX2020 routers with the MX2K-MPC11E line card.
17.1R1
Starting from Junos OS Release 17.1R1, the reflector function and the corresponding benchmarking tests are supported on MX Series routers with MPC3E (MX-MPC3E-3D), MPC3E-NG (MX-MPC3E-3D-NG), MPC4E (MPC4E-3D-32XGE-SFPP and MPC4E-3D-2CGE-8XGE), MPC5E (MPC5E-40G10G, MPC5EQ-40G10G, MPC5E-100G10G, and MPC5EQ-100G10G), and MPC6E (MX2K-MPC6E).
16.1
For MX80 and MX104 Universal Routing Platforms and, starting from Junos OS Release 16.1, MX240, MX480, and MX960 Universal Routing Platforms with MPC1 (MX-MPC1-3D), MPC2 (MX-MPC2-3D), and the 16-port 10-Gigabit Ethernet MPC (MPC-3D-16XGE-SFP), support the reflector function and the corresponding benchmarking tests.
15.1
Starting from Junos OS Release 15.1, MX104 Series routers also perform verification of signatures on the received test frames.