test services monitoring rfc2544
Syntax
test services monitoring rfc2544 (test test-name | test-id id) <routing-instance <routing-instance-name>> (clear-counters | start | stop)
Description
Start or stop an RFC 2544-based benchmarking test, or clear the statistical counters for a
test. You can start or stop a specific test name, or you can stop a test based on its test
identifier. When you trigger an RFC 2544-based benchmarking test, it passes through a
series of states. These states are displayed in the Test state field of the show
services monitoring rfc2544 command.
The RFC 2544 test is stopped at the initiator automatically after the test successfully
completes all of the test steps. You need not explicitly enter the test services
monitoring rfc2544-benchmarking (test test-name | test-id
test-id) stop command. However, at the reflector, you must
explicitly enter this command to stop the test after the test is completed at the
initiator.
Options
| (test test-name | test-id id) |
Name of the test to be started or stopped or the unique identifier of the test to be stopped. |
| routing-instance routing-instance-name | (Optional) Name of the routing instance for the test. |
| (clear-counters | start | stop) | Clear the statistics associated with a test, or start or stop a test. |
Additional Information
Required Privilege Level
view
Sample Output
- test services monitoring rfc2544 test test-name start
- test services monitoring rfc2544 test test-name routing-instance instance-name start
- test services monitoring rfc2544 test-id test-id stop
- test services monitoring rfc2544 test test-name clear-counters
test services monitoring rfc2544 test test-name start
user@host> test services monitoring rfc2544 test mytest start
If successful, the identifier of the started test is displayed:
Test mytestid 1 started
If unsuccessful, an error message is displayed:
Error starting test mytest: error-description
Some examples:
-
If you try to start a test that is already running:
Error starting test mytest: previous session with id 1 still active
-
If you try to start an INET reflector test that has an incorrect address configured on the
destination-ipv4-addressstatement:Error starting test mytest: inet address '192.0.2.2' not local for default routing-instance
-
If you try to start a test for a test name that has not been configured on the
test-namestatement:Error starting test mytest: configuration entry for test 'mytest' not found
test services monitoring rfc2544 test test-name routing-instance instance-name start
user@host> test services monitoring rfc2544 test mytest routing-instance lg01 start
If successful, the identifier of the started test is displayed:
Test mytest id 1 started
If unsuccessful, an error message is displayed:
Error starting test mytest: error-description
Some examples:
-
If you try to start an INET reflector test in a routing instance that has an address configured on the
destination-ipv4-addressstatement that is not in the given routing-instance:Error starting test mytest: inet address '192.0.2.2' not local in routing-instance lg01
-
If you try to start a test for a routing instance that has not been configured on the
routing-instancestatement:Error starting test mytest: routing instance 'lg01' not found
test services monitoring rfc2544 test-id test-id stop
user@host> test services monitoring rfc2544 test-id 1 stop
If successful, the identifier of the started test is displayed:
Test test-name id 1 stopped
If unsuccessful, an error message is displayed:
Error stopping test with id 1: error-description
For example, if the test identifier you specified when you issued the command doesn't exist:
Error stopping test test-name: no active sessions found
test services monitoring rfc2544 test test-name clear-counters
user@host> test services monitoring rfc2544 test mytest clear-counters
If successful, a message is displayed describing which counters were cleared.
Test mytest id test-id clearing counters
If unsuccessful, an error message is displayed:
Error clearing counters for test mytest: error-description
For example, if you try to clear counters for a test that does not have active sessions:
Error clearing counters for test mytest: no active sessions found
Release Information
Command introduced for Junos OS Evolved Release 21.1R1.