10. Configure an RFC 2544-based benchmarking test for the RPM instance.
[edit services rpm]
user@host# edit rfc2544-benchmarking
11. 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
12. Specify the logical interface, ge-0/0/4.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/4.1
13. Specify reflect as the test mode for the packets that are sent during the
benchmarking test.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set mode reflect
14. Configure the address type family, ccc, for the benchmarking test.
[edit services rpm rfc2544-benchmarking tests test-name test1]
user@host# set family ccc
15. 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
Results
In configuration mode, confirm your configuration on Router A and Router B by entering
the show command. If the output does not display the intended configuration, repeat
the configuration instructions in this example to correct it.
Configuring Benchmarking Test Parameters on Router A:
[edit interfaces]
ge-0/0/0 {
vlan-tagging;
unit 0 {
encapsulation vlan-ccc;
vlan-id 101;
}
}
[edit services rpm]
rfc2544-benchmarking {
1373Copyright © 2017, Juniper Networks, Inc.
Chapter 37: Configuring RFC 2544-Based Benchmarking Tests
To Next Page
Loading...
Need help?
General
