user@host# set test-type test-duration 20m
15. Define the theoretical maximum bandwidth for the test in kilobits per second, with
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
16. Enter the up command to go the previous level in the configuration hierarchy.
[edit services rpm rfc2544-benchmarking profiles test-profile throughput]
user@host# up
17. Enter the up command to go the previous level in the configuration hierarchy.
[edit services rpm rfc2544-benchmarking profiles]
user@host# up
18. Define a name for the test—for example, test1. The test name identifier can be up
to 32 characters in length.
[edit services rpm rfc2544-benchmarking]
user@host# edit tests test-name test1
19. Specify the name of the test profile—for example, throughput—to be associated
with a particular test name.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set test-profile throughput
20. Specify the logical interface, ge-0/0/0.1, on which the RFC 2544-based
benchmarking test is run.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set test-interface ge-0/0/0.1
21. Specify the test mode for the packets that are sent during the benchmarking test
as initiation and termination.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set mode initiate-and-terminate
22. Configure the address type family, ccc, for the benchmarking test.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set family ccc
23. Specify the direction of the interface on which the test must be run, which is NNI in
this example.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set direction nni
1371Copyright © 2017, Juniper Networks, Inc.
Chapter 37: Configuring RFC 2544-Based Benchmarking Tests
To Next Page
Loading...
Need help?
General
