Copyright © 2017, Juniper Networks, Inc.
Configure an RFC 2544-based benchmarking test for the RPM instance.
10.
[edit services rpm]
user@host# edit rfc2544-benchmarking
Define a name for a test profile—for example, throughput.
11.
[edit services rpm rfc2544-benchmarking]
user@host# edit profiles test-profile throughput
Configure the type of test to be performed as throughput.
12.
[edit services rpm rfc2544-benchmarking profiles test-profile throughput]
user@host# set test-type throughput
Specify the size of the test packet as 64 bytes.
13.
[edit services rpm rfc2544-benchmarking profiles test-profile throughput]
user@host# set test-type packet-size 64
Specify the period for which the test is to be performed in hours, minutes, or seconds
14.
by specifying a number followed by the letter h (for hours), m (for minutes), or s
(for seconds). In this example, you configure the period as 20 minutes.
[edit services rpm rfc2544-benchmarking profiles test-profile throughput]
user@host# set test-type test-duration 20m
Define the theoretical maximum bandwidth for the test in kilobits per second, with
15.
a value from 1 Kbps through 1,000,000 Kbps.
[edit services rpm rfc2544-benchmarking profiles test-profile throughput]
user@host# set test-type bandwidth-kbps 500
Enter the
command to go the previous level in the configuration hierarchy.
up
16.
[edit services rpm rfc2544-benchmarking profiles test-profile throughput]
user@host# up
Enter the
up
command to go the previous level in the configuration hierarchy.
17.
[edit services rpm rfc2544-benchmarking profiles]
user@host# up
Define a name for the test—for example, test1. The test name identifier can be up
18.
to 32 characters in length.
[edit services rpm rfc2544-benchmarking]
user@host# edit tests test-name test1
Specify the name of the test profile—for example, throughput—to be associated
19.
with a particular test name.
[edit services rpm rfc2544-benchmarking tests test-name test1]
Chapter 37: Configuring RFC 2544-Based Benchmarking Tests
1379