You can configure a benchmarking test to detect and measure performance attributes, such as throughput, latency, frame loss, and bursty or back-to-back frames, of network devices. An RFC 2544-based benchmarking test is performed by transmitting test packets from a device that functions as the initiator and terminator of the test. These packets are sent to a device that functions as the reflector, which receives and returns the packets back to the initiator.

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.

SRX series Firewalls support only the reflector function in RFC 2544-based benchmarking tests.



The following devices support RFC 2544-based benchmarking tests in either the initiator/terminator or reflector role, according to which families they support:

Configuring a Test Name for an RFC 2544-Based Benchmarking Test for a IPv4 Network

You can configure a test name by including the test-name test-name statement at the [edit services rpm rfc2544-benchmarking] hierarchy level. In the test name, you can configure attributes of the test iteration, such as the address family (type of service, IPv4 or Ethernet), the logical interface, and test duration that are used for a benchmarking test to be run.

To configure a test name and define its attributes for an IPv4 network:

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

[edit]
user@host# edit services

• Configure a instance.

[edit services]
user@host# edit rpm

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

[edit services rpm]
user@host# edit rfc2544-benchmarking

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

[edit services rpm rfc2544-benchmarking]
user@host# edit tests test-name test1

• Specify the test mode for the packets that are sent during the benchmarking test. The reflect option causes the test frames to be reflected on the IPv4 network.

[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set mode reflect

• Configure the address type family for the benchmarking test. The inet option indicates that the test is run on an IPv4 service.

[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set family inet

• Configure the destination IPv4 address for the test packets. This parameter is required only if you configure IPv4 family inet. If you do not configure the destination IPv4 address, the default value of 192.168.1.20 is used.

[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set destination-ipv4-address address 

• Specify the UDP port of the destination to be used in the UDP header for the generated frames. If you do not specify the UDP port, the default value of 4041 is used.

[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set destination-udp-port port-number

• (Optional) Specify the source IPv4 address to be used in generated test frames. If you do not configure the source IPv4 address for inet family, the source address of the interface is used to transmit the test frames.

[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set source-ipv4-address address

• Specify the UDP port of the source to be used in the UDP header for the generated frames. If you do not specify the UDP port, the default value of 4041 is used.

[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set source-udp-port port-number

• Specify the logical interface on which the RFC 2544-based benchmarking test is run. If you configure an inet family and the test mode to reflect the frames back on the sender from the other end, then the logical interface is used as the interface to enable the reflection service (reflection is performed on the packets entering the specified interface). If you not configure the logical interface for reflection test mode, then a lookup is performed on the source IPv4 address to determine the interface that hosts the address.

[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set test-interface interface-name