Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Creating an RFC 2544 Test Profile for Services

Before you begin to create an RFC test for a service, ensure that:

  • You have created an E-LINE or IP service on which you want to perform the RFC test.

    • Note:

      You can perform RFC tests on E-LINE and IP services only.

    • Note:

      You must configure unit 0 for E-line service and interface IP for IP services to run an RFC 2544 test. You can configure unit 0 for E-line service and interface IP for IP services by using device or service templates. You can delete these service templates after the test is completed. For more information, see Configuring RFC 2544-Based Benchmarking Tests on MX Series Routers.

    • Note:

      You cannot perform an RFC test on an E-LAN service as it cannot be provisioned on ACX 2k devices, it can only be provisioned on ACX 5k devices. The initiator PE device can only be an ACX 2k device. ACX 5k devices cannot serve as the initiator, only as the reflector. Therefore, you will not be able to perform the RFC 2544 test on an E-LAN service. You can, however, run an RFC 2544 test at device-level. For more information on this, see Creating an RFC 2544 Test Profile for Devices. You can also refer Example: Configuring Benchmarking Tests to Measure SLA Parameters for E-LAN Services on an MX104 Router Using VPLS to understand how to configure benchmarking tests for E-LAN services using VPLS.

  • The functional audit status (FA Status) is Up for the service that you want to perform an RFC test.

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.

To create an RFC 2544 test profile:

  1. Log into Junos Space application and select Connectivity Services Director in the Applications pane on the left.

    The Connectivity Services Director dashboard is displayed.

  2. On the Connectivity Services Director banner, click Views and select Service View.

    The Service View page is displayed.

  3. From the Service View pane on the left, select an E-LINE or IP service on which you want perform an RFC test.

    The details of the service is loaded in the View Service Details pane.

  4. On the Connectivity Services Director banner, click Monitor in Task Categories.

    The Service Summary tab is loaded.

  5. Select the RFC2544 tab.

    The RFC2544 tab is loaded.

  6. On the Tasks pane on the right side of the page, select OAM > RFC2544 Test > Create Test.

    The Create RFC Test Profile page is displayed.

  7. Complete the configuration of the RFC test according to the guidelines provided in Table 1.
  8. Click Save.

    The test profile is created, saved, and deployed. The details of the test profile is displayed on the Create RFC Test Profile page in view-only mode.

  9. Click OK to close the Create RFC Test Profile page.

    The newly created RFC 2544 test profile appears in the RFC2544 tab.

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

Table 1 describes the fields in the Create Test page.

Table 1: Fields on the Create Test Page

Field

Description
General Settings

Name

Enter a unique string of alphanumeric characters, dashes, and underscores. Colons, and periods are not allowed, and the maximum length is 10 characters.

Description

Enter a description for the RFC 2544 test; maximum length is 250 characters.

RFC Test Profile

Select the test performance metric for the test profile. You can measure the throughput, latency, frame loss, and back-to-back of a service.

Note:

You can choose one performance metric for each test profile. If you want to test more 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 service, then you must create one test profile to measure throughput and another test profile to measure latency.

Bandwidth

Enter a numerical value for the bandwidth (in Kbps) that needs to be tested. The maximum value is 1000000.

Packet Size

Select the packet size(s) for the test. You can select multiple packet sizes for a test; the maximum number of packet sizes you can select is 10.

Step Percent

Enter a numerical value for the frame loss ratio. The maximum value is 100.

Note:

Step percent information is only applicable if you select Frame Loss as the RFC test profile.
Initiator Settings

Provider Edge (PE) Device

PE device lists all the devices on which the service is running. Select the device that you want to act as the initiator for the RFC 2544 test.

Note:

The initiator PE device can only be an ACX device.

Family

Select the address type family for the benchmarking test.

Note:

This field is auto-populated based on the types of service you have selected.

Test Interface

Select the logical interface on which the service (that you want to run an RFC test on) is running. This parameter is required only if you selected the ccc family.

Note:

By default, only the interfaces on which the service is running is listed.

Source IPv4 Address

Enter the source IPv4 address of the initiator. This parameter is required only if you have 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.

Inner VLAN ID

For dynamic VLAN interfaces, enter the VLAN ID to rewrite for the inner tag of the final packet.

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.
Reflector Settings

PE Device

PE device lists all the devices on which the service is running. Select the device that you want to act as the reflector for the RFC 2544 test.

Family

Select the address type family for the benchmarking test.

Test Interface

Select the logical interface on which the service (that you want to RFC test) is running.

Note:

By default, only the interfaces on which the service is running is listed.

Source IPv4 Address

Enter the source IPv4 address of the reflector. This parameter is required only if you selected IPv4 family inet.

Source MAC Address

Enter the source MAC address of the reflector. 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.

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 3-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 performed by sending test frames for 3 seconds to ensure that all devices on the path to destination 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.

Related Documentation