Creating an RFC 2544 Test Profile for Devices

You must create a test profile (parameters for the RFC 2544-based benchmarking test), which specifies the type of test and the manner in which it must be performed, and associate the test profile with a test name. The test name that you configure contains details, such as the address family and the test mode, for the test. You can associate the same test profile with multiple test names.

RFC 2544 test profile configuration is done in two parts:

Configure General Settings—Use the General Settings pane to define the tests (throughput, latency, back-to-back, and frame loss) that you want to be part of the RFC 2544 test.
Configure Test Settings—Use the Test Settings pane to define the initiator and reflector device settings for the RFC 2544 test.

To create an RFC 2544 test profile:

Log into Junos Space application and click on Junos SPACE in the Connectivity Services Director banner.
From the Applications pane on the left, select Services Activation Director.
The Services Activation Director dashboard is displayed.
From the pane on the left, click OAM-RFC2544-Test > Manage Test Configuration > Create RFC2544 Test.
The General Settings pane displays fields required for configuring an RFC 2544 test.
Complete the configuration for General Settings according to the guidelines provided in Table 1.
Click Next after you have completed configuring General Settings.
The Test Settings pane displays fields required for configuring the test devices.
Complete the configuration for Test Settings according to the guidelines provided in Table 2.
Click Finish.
The Deployment Options page appears providing various deployment options.
- Select Save only and Validate options to validate the test profile against the device and save in the database.
- Select Deploy Now option deploy the test profile to the device.
- Select Schedule Deployment option to deploy the test profile at a scheduled date and time; enter the date and time at which the test profile needs to be deployed to the device.
Click OK to save/deploy the test profile.
The Job Details page appears displaying the job ID that has been created to validate and save/deploy the test profile. You can double-click on the job ID to view the details of the job.
Click OK to close the Job Details page.
The newly created RFC 2544 test profile appears in the Manage Service Orders page. Double-click on the it to view the details of the test profile.

If you have just saved the new test profile, it is listed in the Manage Test Configuration page. Once you deploy the test profile, it is listed in Manage Test page. For more information on deploying an RFC 2544 test, see Deploying RFC 2544 Tests.

For more information on running the RFC 2544 and viewing the results, see RFC 2544 Testing Overview.

Table 1 describes the fields in the General Settings pane.

Table 1: Fields on the General Settings Pane

Field	Description
Name	Enter a unique string of alphanumeric characters, dashes, and underscores. Colons, and periods are not allowed, and the maximum length is 50 characters.
Comments	Enter a description for the RFC 2544 test; maximum length is 250 characters.
Throughput	Select Throughput to add it as test parameter in the RFC 2544 test. When you select a test parameter, the other test parameters are disabled. Note: You can choose only one performance metric for each test profile. If you want to test more an than one performance metric, you must create one test profile for each performance metric. For example, if you want to measure the throughput and latency for a device, then you must create two test profiles—one test profile to measure throughput and another to measure latency.
Bandwidth	Enter a numerical value for the bandwidth for which throughput needs to be tested. The maximum value is 1000000.
Packet Size	Select the packet size(s) for the throughput test. You can select multiple packet sizes for the test; the maximum number of packet sizes you can select is 10.
Frame Loss	Select Frame Loss to add it as test parameter in the RFC 2544 test. When you select a test parameter, the other test parameters are disabled. Note: You can choose only one performance metric for each test profile. If you want to test more an than one performance metric, you must create one test profile for each performance metric. For example, if you want to measure the throughput and latency for a device, then you must create two test profiles—one test profile to measure throughput and another to measure latency.
Bandwidth	Enter a numerical value for the bandwidth for which frame loss needs to be tested. The maximum value is 1000000.
Packet Size	Select the packet size(s) for the frame loss test. You can select multiple packet sizes for the test; the maximum number of packet sizes you can select is 10.
Step Percent	Enter the numerical value for the frame loss ratio. The maximum valueis 100.
Latency	Select Latency to add it as test parameter in the RFC 2544 test. When you select a test parameter, the other test parameters are disabled. Note: You can choose only one performance metric for each test profile. If you want to test more an than one performance metric, you must create one test profile for each performance metric. For example, if you want to measure the throughput and latency for a device, then you must create two test profiles—one test profile to measure throughput and another to measure latency.
Bandwidth	Enter a numerical value for the bandwidth for which latency needs to be tested. The maximum value is 1000000.
Packet Size	Select the packet size(s) for the latency test. You can select multiple packet sizes for the test; the maximum number of packet sizes you can select is 10.
Back-to-Back	Select Back-to-Back to add it as test parameter in the RFC 2544 test. When you select a test parameter, the other test parameters are disabled. Note: You can choose only one performance metric for each test profile. If you want to test more an than one performance metric, you must create one test profile for each performance metric. For example, if you want to measure the throughput and latency for a device, then you must create two test profiles—one test profile to measure throughput and another to measure latency.
Bandwidth	Enter a numerical value for the bandwidth for which back-to-back (or burst) needs to be tested. The maximum value is 1000000.
Packet Size	Select the packet size(s) for the back-to-back test. You can select multiple packet sizes for the test; the maximum number of packet sizes you can select is 10.

Table 2 describes the fields in the Test Settings pane.

Table 2: Fields in the Test Settings Pane

Field	Description
Initiator
Device Name	Select the device that you want to be the initiator or reflector for the RFC 2544 test.
Family	Select the address type family for the benchmarking test. The inet option indicates that the test is run on an IPv4 service.
Test Interface	Specify the logical interface on which the RFC 2544-based benchmarking test is run. Note: You can only select the test interface for the reflector device. This field is disabled for the initiator device.
Source IPv4 Address	Enter the source IPv4 address of the initiator. This parameter is required only if you selected IPv4 family inet.
Source MAC Address	Enter the source MAC address of the initiator. The MAC address is only applicable for the ccc family.
Source UDP Port	Enter the UDP port of the source to be used in the UDP header for the generated frames.
Destination IPv4 Address	Enter the destination IPv4 address of the reflector. This parameter is required only if you have selected IPv4 family inet.
Destination MAC Address	Enter the destination MAC address of the reflector. The MAC address is only applicable for the ccc family.
Destination UDP Port	Enter the UDP port of the destination to be used in the UDP header for the generated frames.
Direction	Select the direction of the interface on which the test must be run. This parameter is valid only for the ccc family. To enable the test to be run in the egress direction of the interface (network-to-network interface (NNI)), use the egress option. To enable the test to be run in the ingress direction of the interface (user-to-network interface (UNI)), use the ingress option.
DSCP Code Points	Specify the value of the Differentiated Services (DiffServ) field within the IP header of host-generated RPM packets. The DiffServ code point (DSCP) bits value must be set to a valid 6-bit pattern.
Forwarding Class	Forwarding classes (FCs) allow you to group packets for transmission and to assign packets to output queues. The forwarding class and the loss priority define the per-hop behavior (PHB in DiffServ) of a packet. assured-forwarding—Provides a group of values you can define and includes four subclasses—AF1, AF2, AF3, and AF4—each with three drop probabilities (low, medium, and high). best-effort—Provides no service profile. For the BE forwarding class, loss priority is typically not carried in a class-of-service (CoS) value, and random early detection (RED) drop profiles are more aggressive. expedited-forwarding—Provides a low-loss, low-latency, low-jitter, assured-bandwidth, end-to-end service. network-control—This class is typically high priority because it supports protocol control.
Halt on prefix down	By default, the RFC 2544-based benchmarking test ignores a prefix-down event (when the prefix associated with the test goes down) and continues to run. If you select this option, a prefix that moves to the down state causes the corresponding tests to be stopped. The show command output for the test displays that the test was terminated due to the prefix going down.
Inner VLAN ID	For dynamic VLAN interfaces, enter the VLAN ID to rewrite for the inner tag of the final packet.
Mode	initiate-and-terminate—Causes the test frames to be initiated at the router and the reflected back frames to be terminated. This mode requires a reflector to be configured at the peer end of the network to return back the generated frames. For initiator device, the initiate-and-terminate mode is selected by default. reflect—Causes the received test frames to be reflected back on the configured service (for example, inet, ccc). For reflector device, the reflect mode is selected by default.
Outer VLAN ID	The Outer VLAN ID field is disabled unless you provide a value for the Inner VLAN ID. Enter the outer VLAN ID for the test frames. Range: 0 through 4094 This parameter is valid only for family ccc mode.
Skip ARP Iteration	Select this option to disable the Address Resolution Protocol (ARP) test iteration for IPv4 or inet services during a benchmarking test. This parameter is valid only for an inet family. An ARP test iteration is a three-second iteration that is run for all inet tests. The results of this iteration are disregarded in the test result calculations. The ARP test iteration is executed by sending test frames to all the devices on the path to the destination for 3 seconds. This is to ensure that all devices add ARP entries in the cache of the corresponding devices. This parameter is not applicable for the ccc family.
Test Iteration Duration	Enter the duration of each iteration in seconds, with a value from 10 seconds to 1,728,000 seconds.
Reflect eType	Specify the EtherType to be used for reflection of the test frames. EtherType is a two-octet field in an Ethernet frame that defines the protocol in the frame payload. This statement is valid only if you configure the test mode to be a reflector. If you do not configure this statement, all EtherTypes are reflected.
Reflect Mode	Select the reflection mode for the benchmarking test. mac-swap—Swaps the source and destination MAC addresses in the test frame. This is the default behavior. no-mac-swap—Does not swap the source and destination MAC addresses in the test frame. The frame is returned to the originator without any modification to the MAC addresses. mac-rewrite—(ACX Series routers only) Enable rewriting of the MAC address on the reflected frames. The MAC addresses specified in the Source MAC Address and Destination MAC Address options are used.

Creating an RFC 2544 Test Profile for Devices

Related Documentation