Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configuring RFC 2544-Based Benchmarking Tests

This topic describes how to configure a test-profile and a test-name, start and stop a RFC2544-benchmark test, and copy the test result to a local or a remote file.

Test Profile and Test Name Overview

To configure a RFC 2544 benchmark test on an initiator, you must first configure a test-profile and reference the test-profile in a unique test-name. The test-name defines the parameters for the tests to be performed.

To configure a test-profile, include the test-profile profile-name statement at the [edit services rpm rfc2544-benchmarking] hierarchy level. Test profile is applicable only for the initiator, not the reflector.

To configure a test-name, include the test-name test-name statement at the [edit services rpm rfc2544-benchmarking] (Junos OS) or [edit services monitoring rfc2544 tests] (Junos OS Evolved) hierarchy level.

(Junos OS) To configure Ethernet loopback as the test mode on a logical interface, include the Ethernet-loopback statement at the [edit services rpm rfc2544-benchmarking] hierarchy level.

The table below lists the parameters for configuring the test profile at the initiator.

Table 1: Parameters for test-profile Configuration at the Initiator

Parameters

Description

test-type

RFC 2544 test type (throughput | latency | frame-loss | back-back-frames).

packet-size

Size of the test packet.

The valid packet sizes are 64, 68, 72, 128, 256, 512, 768, 1024, 1280, 1518, 1522, 1600, 1728, 2496, 3584, 4016, 9104, and 9136 bytes.

bandwidth-kbps

Define the maximum bandwidth limit, in kilobits per second (kbps).

Range: 1,000 kpbs through 1,000,000 kbps.

step-percent

Specify the step percentage for frame-loss tests.

Default: 10 percent

Range: 1 through 100 percent

The table below lists the parameters for configuring a test-name at initiator and reflector.

Table 2: Parameters for test-name Configuration at the Initiator and the Reflector

Parameters

Description

check-test-interface-mtu

When the check-test-interface-mtu parameter is configured, the software validates the MTU size of the test packets with the MTU size configured on the interface and the following would be the behavior for initiator and reflector modes:

  • On the initiator, if the MTU size of the test packet is larger than the MTU size configured on the interface, then the RFC2544-based benchmarking test fails to start.

  • On the reflector, if the test packets coming to the reflector does not confirm to the MTU size configured on the interface, then these test packets do not get reflected and are dropped.

destination-ipv4-address

Specify the destination IPv4 address.

This parameter is mandatory when family inet is specified and optional when family ccc is specified.

If a value is not specified, then by default 192.168.1.20 is used.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

destination-mac-address

Specify the destination MAC address. For example, 0011.2233.4455.

This parameter cannot be used when family inet is specified.

This parameter is optional when family ccc and ethernet-switching is specified. If not specified, then the default value of 0x00:0x11:0xAE:0x92:0x2F:0x28 is used.

destination-udp-port

Specify the destination UDP port number for the test frames. Default: 4041.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

direction

Specify the test direction (egress | ingress). This parameter is valid only when family ccc, ethernet-switching and bridge.

This parameter is mandatory for mode ethernet-loopback

disable-signature-check

Disable signature verification on the received test frames.

dscp-code-points

Specify the value of the Differentiated Services (DiffServ) field. For example, 001111.

If a value is not specified, then '0' is used in IP header.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

family

Configure the test family (bridge | ccc | ethernet-switching | inet).

This parameter is mandatory for mode ethernet-loopback

forwarding-class

Specify the forwarding class to be used for test frames.

halt-on-prefix-down

If specified, a prefix that moves to the down state causes the corresponding tests to be stopped.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

ignore-test-interface-state

When the ignore-test-interface-state parameter is configured for RFC2544 benchmarking tests, the test continues to run even if there are any occurrences of interface up or down events. This is applicable to both initiator and reflector test modes.

in-service

If specified, only the data traffic corresponding to the test session is interrupted, rest of the data traffic flow sent to and from the UNI port under test on the service are not affected.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

ivlan-cfi

CFI bit used in the inner VLAN tag.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

ivlan-id

Configure inner VLAN ID for the test frames.

This parameter is valid only for family ccc mode.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

ivlan-priority

Configure the priority value for the IEEE 802.1p bit in the inner VLAN tag.

Range: 0 through 7.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

mode

Specify the test mode (ethernet-loopback, initiate-and-terminate, or reflect).

  • ethernet-loopback—Test frames are loopbacked to the measuring device after the source MAC address and the destination MAC addresses are swapped.

  • initiate-and-terminate—Test frames are initiated and terminated at the same end. If you specify this mode, then a reflector should be configured on the peer end to bring back the test frames.

  • reflect—Test frames are reflected on the chosen service.

outer-tag-protocol-id

TPID to be used in the outer VLAN tag.

Supported values are 0x8100, 0x88a8, 0x9100, 0x9200.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

ovlan-cfi

CFI bit used in the outer VLAN tag.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

ovlan-id

Configure the outer VLAN ID for the test frames.

Range: 0 through 4094

This parameter is valid only for family ccc mode.

ovlan-priority

Configure the priority value for the IEEE 802.1p bit in the outer VLAN tag.

Range: 0 through 7

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

packet-loss-priority

Specify the packet loss priority (PLP) value.

If a value is not configured, then the default value of low is used.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

reflect-etype

Specify the EtherType ID to be used for reflection of test frames. This parameter is valid only in mode reflect. If not specified, then all EtherTypes are reflected.

Range: 1 through 65,535.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

reflect-mode

Specify the reflection mode (mac-rewrite | mac-swap | no-mac-swap).

  • mac-rewrite—MAC values specified in source-mac-address and destination-mac-address would be used.

  • mac-swap—Swaps the source-mac-adddress and destination-mac-address in the test frame. This is the default behavior.

  • no-mac-swap—Does not swap MAC addresses. Test frames are returned back as-is.

reflector-port

Port used to configure reflector functionality for RFC 2544 test. The range of ports that can be used based on the front panel port number are:

  • On ACX5048 [16 through 53]

  • On ACX5096 [64 through 95, 100 through 103].

service-type

Specify the service type (E-Line or E-LAN)

skip-arp-iteration

This parameter is valid only in family inet mode. ARP iteration is a 3-second iteration that is run for all inet tests. The results of ARP iteration are ignored in test result calculations. The primary use of sending test frames for 3 seconds is to ensure that all devices on the path to destination build their ARP entries.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

source-ipv4-address

Specify the source IPv4 address used for the test frames. If a value is not specified for this parameter, then:

  • For family ccc, if a value is not specified, then by default 192.168.1.10 is used.

  • For family inet, the source address of the interface is used to send out test frames.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

source-mac-address

Specify the source MAC address. For example, 0011.2233.4455

This parameter cannot be used when family inet is specified.

This parameter is optional when family ccc or ethernet-switching is specified. If not specified, then the default value of 0x00:0x60:0x67:0x71:0xC6:0x62 is used.

source-udp-port

Specify the source UDP port number for the test frames.

Default: 4040

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

test-finish-wait-duration

Number of seconds to wait after transmitting the last frame and before concluding that the test as complete.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

test-iterator-duration

Specify the duration of each iteration in seconds.

Range: 10 through 120 seconds

The default value for test types throughput, back-to-back frames and frame loss rate is 20 seconds. The default value for test type latency is 120 seconds.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

test-interface

Specify the name of the logical interface (UNI) on which the test needs to be run.

When you specify the family as inet and mode as initiate-and-terminate the test-interface is ignored. Instead, the test is run on the egress logical interface that is determined by the route lookup on the specified destination-ipv4-address.

When you specify the family as inet and mode as reflect, the test-interface is used as the interface to enable reflection service. If test-interface is not configured, a lookup is performed on the source-ipv4-address parameter to determine the interface hosting the address.

This parameter is mandatory for mode ethernet-loopback.

test-profile

Specify the name of the test-profile to be used for the test.

The test-profile parameter is ignored when mode reflect is used.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

vlan-cfi

CFI bit used in the VLAN tag.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

vlan-id

Configure the VLAN ID for the test frames.

This parameter is valid only for mode ethernet-loopback.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

vlan-priority

Configure the VLAN priority value.

Range: 0 through 7.

Note:

This parameter is not supported on ACX5048 and ACX5096 routers.

Configure a Test Profile for an RFC 2544-Based Benchmarking Test

You can configure a test profile by including the test-profile profile-name statement at the [edit services rpm rfc2544-benchmarking] hierarchy level.

This procedure shows how to configure a test profile for Junos OS. Routers running Junos OS Evolved only support reflector mode, and so you cannot configure a test profile on these routers.

To configure a test profile:

  1. In configuration mode, go to the [edit services] hierarchy level.
  2. Configure an RPM service instance.
  3. Configure an RFC 2544-based benchmarking test for the RPM instance.
  4. Define a name for a test profile—for example, profile1.
  5. Define the theoretical maximum bandwidth for the test in kilobits per second, with a value from 1,000 Kbps through 1,000,000 Kbps. Specify a complete decimal number.
  6. Specify the size of the test packet in bytes, with a value from 64 through 9136, to be used for each test iteration. You can specify up to 10 packet sizes, separated by a space, that are used sequentially for the test. The valid packet sizes are 64, 68, 72, 128, 256, 512, 768, 1024, 1280, 1518, 1522, 1600, 1728, 2496, 3584, 4016, 9104, and 9136 bytes. If you specify a packet size other than the ones listed here as valid sizes, the configuration is saved when you commit the setting and no error message is displayed. However, when you start the test by entering the test services rpm rfc2544-benchmarking test test-name start command, an error message is displayed specifying that you configured an invalid packet size in the test profile associated with the test name.
    Note:

    • The minimum frame size for untagged frames should be 64.

    • The minimum frame size for single-tagged frames should be 68.

    • The minimum frame size for dual-tagged frames should be 72.

    These values are no applicable for inet.
  7. Specify the step percentage for frame-loss tests with a value from 1 through 100. This parameter is not applicable for other test types.
  8. Configure the type of test to be performed.

    • To configure a throughput test, use the throughput option with the test-type statement.

    • To configure a latency test, use the latency option with the test-type statement.

    • To configure a frame-loss test, use the frame-loss option with the test-type statement.

    • To configure a back-to-back frames test, use the back-back-frames option with the test-type statement.

Configure a Test Name for an RFC 2544-Based Benchmarking Test For an Initiator

You can configure a test name by including the test-name test-name statement at the [edit services rpm rfc2544-benchmarking] (Junos OS) or [edit services monitoring rfc2544] (Junos OS Evolved) hierarchy level.

Routers running Junos OS Evolved support only reflector mode.

(Junos OS) To configure a test name and define its attributes for initiator mode:

  1. Navigate to the correct hierarchy level in configuration mode.
  2. Define a name for the test—for example, test1.

    The test name identifier can be up to 32 characters in length. This step sets the correct hierarchy level for the rest of the steps in this procedure.

  3. Configure the destination IPv4 address for the test packets.

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

  4. (Optional) Specify the source MAC address used in generated test frames.

    You configure this statement for family ccc; you cannot configure it for an inet family. If you specify this parameter for an inet family, a commit error occurs when you commit the configuration. If you do not configure the source MAC address, the default value of 0x00:0x60:0x67:0x71:0xC6:0x62 is used.

  5. Specify the destination MAC address used in generated test frames.
  6. Specify the logical interface on which the RFC 2544-based benchmarking test is run.

    This interface is a local user-to-network interface (UNI) on behalf of which the test frames are generated when the test direction is egress.

  7. Specify the family for the benchmarking test.

    The inet option indicates that the test is run on an IPv4 service. The ccc option indicates that the test is run on an CCC or Ethernet pseudowire service. The bridge option indicates that the test is run on a Layer 2 service.

  8. Specify the initiate-and-terminate mode for the packets that are sent during the benchmarking test.

    The initiate-and-terminate option causes the test frames to be initiated from one end and terminated at the same end. The initiation and termination mode requires a reflector to be configured at the peer end to return the test frames from the peer to the originator.

  9. Specify the direction (egress | ingress) of the interface on which the test must be run.

    The egress option causes the test to be run in the egress direction of the interface (traffic sent from user-to-network interface (UNI) toward network-to-network interface (NNI)). The ingress option causes the test to be run in the ingress direction of the interface (traffic sent on user-to-network interface (UNI)). You cannot configure ingress for a bridge family.

  10. Configure the outer VLAN ID for the test frames.

    This statement is valid only for a CCC or an Ethernet pseudowire family.

  11. Configure the inner VLAN ID for the test frames.

    This statement is valid only for a CCC or an Ethernet pseudowire family.

  12. Configure the priority value for the IEEE 802.1p bit in the outer VLAN tag.

    The priority value is configured when the UNI interface is dual-tagged.

  13. (Optional) Configure the priority value for the IEEE 802.1p bit in the inner VLAN tag.
  14. (Optional) Configure the CFI value for the outer VLAN tag.
  15. (Optional) Specify the source IPv4 address to be used in generated test frames.

    If you do not configure the source-ipv4-address for an inet family, the source address of the interface is used to transmit the test frames. If you do not configure the source-ipv4-address for a ccc family, the default value of 192.168.1.10 is used.

  16. Specify the destination IPv4 address to be used in generated test frames.
  17. Specify the source UDP port to be used in the UDP header for the generated frames.

    If you do not specify the UDP port, the default value of 4040 is used.

  18. Specify the destination UDP port 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.

  19. Specify the value of the Differentiated Services (DiffServ) field within the IP header of the test frames.

    The DiffServ code point (DSCP) bits value must be set to a valid 6-bit pattern. If you do not specify this value, 0 is used in the DSCP fields in the IP header.

  20. Specify the forwarding class to be used for test frames. The forwarding class specifies the manner in which the test frames are processed by the Packet Forwarding Engine of the router. If you do not configure this parameter, test frames are treated as best-effort traffic.
  21. Specify the halt-on-prefix-down option to enable a prefix that moves to the down state to cause the corresponding tests to be stopped.

    The show command output for the test displays that the test was terminated because the prefix went 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.

  22. Specify the duration of each iteration in seconds.

    If you configure this value, the default value of each iteration depends on the type of test being run. For throughput, back-back-frames, and frame-loss types of tests, the default value is 20 seconds. For latency tests, the default value is 120 seconds.

  23. Specify the name of the test profile to be associated with a particular test name.

    You must have previously configured the profile by using the test-profile profile1 statement at the [edit services rpm rfc2544-benchmarking] hierarchy level. The test profile is required when the test mode is configured as initiation and termination. The test-profile profile1 parameter is disregarded when the test mode is configured as reflection. A reflection service does not use the parameters specified in the test profile because the reflection service uses the same parameters for the test frames as the received test frames when it returns the frames to the initiator.

Configure a Test Name for an RFC 2544-Based Benchmarking Test For a Reflector

To configure a test name and define its attributes for reflector mode:

Note:

In ACX5048 and ACX5096 routers, while performing a RFC 2544 benchmark test, you must ensure that there are no configurations associated with the reflector port.
  1. Navigate to the correct hierarchy level in configuration mode:
    1. For Junos OS:
    2. For Junos OS Evolved:
  2. Define a name for the test—for example, test1.

    The test name identifier can be up to 32 characters in length. This step sets the correct hierarchy level for the rest of the steps in this procedure.

    1. For Junos OS:
    2. For Junos OS Evolved:
  3. Specify the test mode for the packets that are sent during the benchmarking test.

    The reflect option causes the test frames to be reflected back to the initiator end.

  4. Specify the family for the benchmarking test.

    Configure the bridge option for Junos OS or the ethernet-switching option for Junos OS Evolved.

    1. For Junos OS:
    2. For Junos OS Evolved:
  5. Specify the direction (egress | ingress) of the interface on which the test must be run.

    The egress option causes the test to be run in the egress direction of the interface (traffic sent from user-to-network interface (UNI) toward network-to-network interface (NNI)). The ingress option causes the test to be run in the ingress direction of the interface (traffic sent on user-to-network interface (UNI)). You cannot configure ingress for a bridge or ethernet-switching family.

  6. Configure the destination IPv4 address for the test packets.

    You configure this statement only if you configure the IPv4 family inet option. This option is not required if you specify circuit cross-connect (CCC) or ethernet-switching as the family. If you do not configure the destination IPv4 address, the default value of 192.168.1.20 is used.

  7. Specify the source MAC address used in generated test frames.

    You configure this statement for a ccc or ethernet-switching family and not for an inet family. If you specify this parameter for an inet family, a commit error occurs when you commit the configuration. This parameter is optional. If you do not configure the source MAC address, the default value of 0x00:0x60:0x67:0x71:0xC6:0x62 is used.

  8. Specify the destination MAC address used in generated test frames.
  9. Specify the logical interface on which the RFC 2544-based benchmarking test is run.

    This interface is a local user-to-network interface (UNI) on behalf of which the test frames are generated when the test direction is egress. You cannot configure this statement for Layer 3 reflection (family inet).

  10. Specify the service type as E-Line or E-LAN.
  11. (Junos OS) Specify the forwarding class to be used for test frames.

    The forwarding class specifies the manner in which the test frames are processed by the Packet Forwarding Engine of the router. If you do not configure this parameter, test frames are treated as best-effort traffic.

  12. (Optional) Specify the EtherType to be used for reflection of the test frames.

    The EtherType is a two-octet field in an Ethernet frame that defines the protocol encapsulated in the frame payload. If you do not configure this statement, all EtherTypes are reflected. Use an EtherType value that matches the EtherType value set on the customer premises equipment (CPE) to which your router connects. The EtherType value appears in the Ethernet type field of the packet. It specifies the protocol being transported in the Ethernet frame.

  13. (Optional) Specify the reflection mode for the benchmarking test.

Start and Stop the RFC 2544-Based Benchmarking Test

To start an RFC 2544-based benchmarking test:

  • For Junos OS, issue the test services rpm rfc2544-benchmarking test test-name start CLI command.

  • For Junos OS Evolved, issue the test services monitoring rfc2544 test test-name start CLI command.

To stop an RFC 2544-based benchmarking test:

  • For Junos OS, issue the test services rpm rfc2544-benchmarking test test-name stop CLI command.

  • For Junos OS Evolved, issue the test services monitoring rfc2544 test test-name stop CLI command.

To start an RFC 2544 benchmarking inet tests on Layer 3 VPN or virtual router:

  • For Junos OS, issue the test services rpm rfc2544-benchmarking test test-name routing-instance routing-instance-name start CLI command.

  • For Junos OS Evolved, issue the test services monitoring rfc2544 test test-name routing-instance routing-instance-name start CLI command.

To stop an RFC 2544 benchmarking inet tests on Layer 3 VPN or virtual router:

  • For Junos OS, issue the test services rpm rfc2544-benchmarking test test-name routing-instance routing-instance-name stop CLI command.

  • For Junos OS Evolved, issue the test services monitoring rfc2544 test test-name routing-instance routing-instance-name stop CLI command.

Copying an RFC 2544-Based Benchmarking Test Result

You can copy the RFC 2544-based benchmarking test results for a particular test ID to a local or a remote file.

  • To copy test results to a local file:

    • For Junos OS, issue the show services rpm rfc2544-benchmarking test-id number detail | save rfc-2544-test-result-session-id-number CLI command.

    • For Junos OS Evolved, issue the show services monitoring rfc2544 test-id number detail | save rfc-2544-test-result-session-id-number CLI command.

  • To copy test results to a remote file:

    • For Junos OS, issue the show services rpm rfc2544-benchmarking test-id number detail | save ftp://username:password@sftpchannel.example.com/rfc-2544-test-result-session-id-number.

    • For Junos OS Evolved, issue the show services monitoring rfc2544 test-id number detail | save ftp://username:password@sftpchannel.example.com/rfc-2544-test-result-session-id-number.

Related Documentation