• Example: Configuring an RFC 2544-Based Benchmarking Test for UNI Direction of
Ethernet Pseudowires on page 1375
RFC 2544-Based Benchmarking Test States
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 in the brief or detailed output of
the show services rpm rfc2544-benchmarking command. The following are the names of
the states through which the test progresses after it is initiated:
1. RFC2544_TEST_STATE_START_REQUEST—This is the first state that all the triggered
tests enter. When a test enters this state, the state denotes that a request has been
sent to a Packet Forwarding Engine to start the test.
2. RFC2544_TEST_STATE_START_FAILED—This state indicates that the test failed to
start. This state occurs when the Packet Forwarding Engine responds to the
START_REQUEST message. The Status field of the brief or detailed output of the
show command displays a reason for the failure. When a test enters this state, it is
categorized as an aborted test.
3. RFC2544_TEST_STATE_RUNNING—This state occurs if the Packet Forwarding Engine
is able to successfully start the test. This state indicates that the test is in progress.
You can use the output of the show command to learn additional information about
the test progress.
4. RFC2544_TEST_STATE_STOP_REQUEST—A test enters this state when you use the
test services rpm rfc2544-benchmarking test-id stop command. A request is sent to
the Packet Forwarding Engine to stop the test.
5. RFC2544_TEST_STATE_STOP_FAILED—This state is entered when the Packet
Forwarding Engine failed to stop a test after it received the STOP_REQUEST message.
The Status field displays further information regarding the exact reason for failure.
6. RFC2544_TEST_STATE_STOPPED—This state is entered when the Packet Forwarding
Engine successfully managed to stop a test when it received the STOP_REQUEST
message.
7. RFC2544_TEST_STATE_COMPLETED—This state is entered when the test successfully
completes all necessary test steps.
8. RFC2544_TEST_STATE_ABORTED_TIMEOUT—When a request is sent to the Packet
Forwarding Engine for any test, a 10-second timer control is started. If a response is
not received from the Packet Forwarding Engine and the timer elapses, the test is
transitioned to the ABORTED_TIMEOUT state. This state is introduced to prevent a
test from indefinitely waiting to receive a reply from the Packet Forwarding Engine.
9. RFC2544_TEST_STATE_RUNTIME_ERROR—This state is entered if the Packet
Forwarding Engine encounters an error when the test is running. The Status field of
the brief or detailed output specifies the reason for the failure. Tests that encounter
the RUNTIME_ERROR state are added to the count of the aborted-tests category,
which can be viewed from the output of the show services rpm rfc2544-benchmarking
command.
Copyright © 2017, Juniper Networks, Inc.1358
ACX Series Universal Access Router Configuration Guide
To Next Page
Loading...
Need help?
General
