21. 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.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set dscp-code-points dscp-code-bits
22. Configure the address type 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 direction statement that you configured
in Step 11 specifies the direction (ingress or egress) to be used for the test.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set family inet
23. 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.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set forwarding-class class-name
24. 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 aborted 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.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set halt-on-prefix-down
25. 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, bursty
or back-back-frames, and frame-loss types of tests, the default value is 20 seconds.
For latency tests, the default value is 120 seconds.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set test-iterator-duration seconds
26. 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.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set test-profile profile1
1351Copyright © 2017, Juniper Networks, Inc.
Chapter 37: Configuring RFC 2544-Based Benchmarking Tests