RFC 2544 Testing Overview
The RFC 2544 test methodology defines specific set of tests that operator can use to measure and report the performance characteristics of network devices and services. 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, the test time for each test iteration, and the frame format (UDP-over-IP).
The RFC 2544 methodology can be used to measure various parameters based on SLA agreements and certify it. By providing performance availability, transmission delay, link burstability and service integrity measurements, a carrier can certify that the working parameters of the delivered ethernet circuit comply with the contract.
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.
The following are some of RFC 2544 benchmarking tests methodology types that you can use to test, measure, and report performance characteristics of network devices.
Throughput—The throughput test calculates the maximum rate at which none of the offered frames are dropped by the device/system under test (DUT/SUT).This measurement translates the obtained rate into the available bandwidth of the service.
Latency—The latency test (for store-and-forward devices) refers to the time interval that begins when the last bit of the input frame reaches the input port and ends when the first bit of the output frame is seen on the output port. It is the time taken by a bit to go through the network and back. Latency variability can be a problem. With protocols like VoIP, a variable or long latency can cause degradation in voice quality.
Frame Loss—The frame loss test calculates the percentage of frames that should have been forwarded by a network device under steady state (constant) loads, that were not forwarded due to lack of resources. This measurement can be used for reporting the performance of a network device in an overloaded state, as it can be a useful indication of how a device would perform under pathological network conditions such as broadcast storms.
Burst—The burstability or back-to-back test refers to the fixed length of frames that are presented at a rate such that there is the minimum legal separation for a given medium between frames (maximum rate) over a short to medium period of time, starting from an idle state. The test result provides the number of frames in the longest burst that the device or network under test will handle without the loss of any frames.
Supported Devices for RFC2544
The following devices support RFC 2544:
ACX Series Universal Access Routers
MX Series 5G Universal Routing Platforms
Before You Begin
RFC2544 is part of Operation, Administration, and Maintenance (OAM). Before starting an OAM test, you must discover OAM capable devices. To discover OAM devices, log in to Connectivity Services Director (CSD), navigate to Service Activation Director (SAD) and click OAM-Prestage Devices > Manage OAM Devices > Discover Devices in the Applications pane on the left side of the page.
Performing an RFC 2544 test for a Service
Use the following steps to perform an RFC test on a service and view the results:
Create an RFC 2544 test profile—For step-by-step instructions on creating an RFC 2544 test profile, see Creating an RFC 2544 Test Profile for Services.
Start RFC 2544 test—To start an RFC 2544 test, select the test profile in the RFC2544 tab, and select OAM > RFC2544 Test > Start Test in the Tasks pane on the right side.
The Test Status in the RFC2544 displays the status of the tests.
Stop RFC 2544 test—To stop an RFC 2544 test, select the test profile in the RFC2544 tab, and select OAM > RFC2544 Test > Stop Test in the Tasks pane on the right side.
The Test Status appears as Stopped in the RFC2544 tab. The test results are available for the iteration till the test was stopped.
View the test results—For more information on viewing test results, see Viewing RFC 2544 Test Results.
Performing an RFC 2544 Test Between Devices
Use the following steps to perform an RFC test between devices and view the test results:
Create an RFC 2544 test profile—See Creating an RFC 2544 Test Profile for Devices for step-by-step instructions on creating an RFC 2544 test profile.
Modify an RFC 2544 test profile—To modify an RFC 2544 test, go to the OAM-RFC2544-Test > Manage Tests page, select the test you want to modify, and click Actions > Modify. The Modify Test page appears displaying the parameters of the test. See Creating an RFC 2544 Test Profile for Devices for details about the parameters of an RFC 2544 test.
After you modify an RFC 2544 test, you have to validate and deploy it again for the modified configuration to be deployed to the device.
Deploy an RFC 2544 test—See Deploying RFC 2544 Tests for step-by-step instructions on deploying an RFC 2544 test.
Start RFC2544 test—To start an RFC 2544 test, go to the OAM-RFC2544-Test > Manage Tests page, select the test you want to run, and click Actions > Start Test.
Stop RC2544 test—To stop an RFC 2544 test, go to the OAM-RFC2544-Test > Manage Tests page, select the test you want to stop, and click Actions > Stop Test. The RFC Test Status appears as Stopped in the Manage Test page. The test results are available for the iteration till the test was stopped.
View the test results— To view the results of an RFC 2544 test, go to the OAM-RFC2544-Test > Manage Tests page, select the test for which you want to view the results, and click Actions > View Test Result. For more information on viewing test results, see Viewing RFC 2544 Test Results.