The values on the L2TP tab report the processing measurements for L2TP tunnel establishment and the L2TP sessions between L2TP peers. They are available in the following test cases:
In the default view, the Reports tab displays the Summary view, which summarizes the measurements for the test session. If your test includes multiple test cases, you can view the report for a single test case by changing the report view...
Unless otherwise noted, cumulative values report the number of occurrences or rates calculated since the start of the test, and per-interval values report the number of occurrences or rates calculated during the interval. You can view either by changing the measurement values...
Elapsed Time is the first measurement on every tab. It reports the amount of time between the start of the test and the end of the report interval.
Test Iteration reports the current iteration in a repeating test session. It is only displayed when a Number of Iterations is defined for the test session.
Minimum Connect Time —The minimum time, in microseconds, required to establish a L2TP session.
Maximum Connect Time —The maximum time, in microseconds, required to establish a L2TP session.
Connect Count —The number of sessions that have been connected.
Minimum Disconnect Time —The minimum time, in microseconds, required to disconnect a L2TP session.
Maximum Disconnect Time —The maximum time, in microseconds, required to disconnect a L2TP session.
The following measurements report on the data sessions established through the L2TP tunnel:
Session Data Bytes Sent — The number of bytes sent by the local peer.
Session Data Bytes Received — The number of bytes received by the local peer.
Session Data Packets Sent — The number of packets sent by the local peer.
Session Data Packets Received — The number of packets received by the local peer.
Session Attempts — The number of sessions attempted.
Session Successes — The number of sessions established.
Session Failures — The total number of sessions that failed due to one of the following errors.
Session Failure Unspecified — The number of sessions that failed due to an unknown reason.
Session Tunnel Failure — The number of sessions that could not be established because the tunnel was not established, and the number of established sessions that failed due to a tunnel failure.
Session MEI Set — The number of sessions that failed due to a CDN received from the LAC containing the following result code values and cause message value: RC=0 or 2,CM=254.
Session MEI Not Set — The number of sessions that failed due to a CDN received from the LAC containing the following result code values and cause message value: RC=0 or 2,CM=255.
Session LNS Terminations — The number of sessions that were terminated by the LNS.
Session LAC Terminations — The number of sessions that were terminated by the LAC.
Session Failures Insufficient Resources — The number of sessions that failed due to insufficient resources, which can be indicated by the following result code values and error code values in the sent/received CDN message: RC=4 or 5, or (RC=2,EC=4), or (RC=12, EC=6).
Session Failures Poorly Formed Request — The number of sessions that failed due to a poorly formed request, which can be indicated by the following result code values and error code values in the sent/received CDN message: RC=6 or (RC=2,EC=2, 3, 5, or 8).
Session Timeout Failures — The number of session attempts that resulted in the number of Retries being exceeded.
Session No Carrier — The number of sessions that failed due to no carrier detected, indicated by the following result code value in the sent/received CDN message: RC=7.
Session Busy — The number of sessions that failed due to detection of a busy signal, indicated by the following result code value in the sent/received CDN message: RC=8.
Session No Dialtone — The number of sessions that failed due to lack of a dial tone, indicated by the following result code value in the sent/received CDN message:RC=9.
Session Framing Error — The number of sessions that failed due to call was connected but no appropriate framing was detected, indicated by the following result code value in the sent/received CDN message: RC=11.
Session Vendor-Specific — The number of sessions that failed due to vendor-specific reasons, indicated by the following result code value, error code, cause code and cause message values in the sent/received CDN message: (RC=0,EC=0,CC=0,CM=256,257), (RC=2,EC=0,CC=0,CM=256,257), or (RC=2,EC=6).
Session Try Another Destination — The number of sessions that failed due to try another destination, indicated by the following result code value and error code value in the sent/received CDN message: RC=2,EC=7.
The following measurements report on L2TP tunnels established between the peers:
Tunnel Attempts — The number of tunnels attempted.
Tunnel Successes — The number of tunnels established.
Tunnel Failures — The number of tunnels that failed due to one of the errors listed.
Tunnel LNS Terminations — The number of tunnels that were terminated by the LNS.
Tunnel LAC Terminations — The number of tunnels that were terminated by the LAC.
Tunnel Failure Insufficient Resources — The number of tunnels that failed due to insufficient resources, indicated by the following result code value and error code value in the sent/received stopCCN message: RC=2,EC=4.
Tunnel Failure Authentication — The number of tunnels that failed due to authentication failure, indicated by the following result code value in the sent/received stopCCN message: RC=4.
Tunnel Failure Poorly Formed Request — The number of tunnels that failed due to a poorly formed request, indicated by the following result code value and error code values in the sent/received stopCCN message:RC=2,EC=2, 3, 5, or 8.
Tunnel Failure Unspecified — The number of tunnels that failed due to unspecified reasons, indicated by the following result code value and error code values in the sent/received stopCCN message:RC=2,EC>8.
Tunnel Unsupported Version — The number of tunnels that failed due to unsupported version, indicated by the following result code value in the sent/received stopCCN message: RC=5.
Tunnel Vendor-Specific — The number of tunnels that failed due to vendor-specific reasons, indicated by the following result code value and error code value in the sent/received stopCCN message: RC=2,EC=6.
Tunnel Try Another Destination — The number of tunnels that failed due to try another destination, indicated by the following result code value and error code value in the sent/received stopCCN message: RC=2,EC=7.
Tunnel Fsm Error — The number of tunnels that failed due to finite state machine errors, indicated by the following result code value in the sent/received stopCCN message: RC=7.
Tunnel Requester Shutdown — The number of tunnels that failed due to requester shutdown, indicated by the following result code value in the sent/received stopCCN message: RC=6.
Tunnel Control Channel Exits — — The number of tunnels that failed due to control channel exits, indicated by the following result code value in the sent/received stopCCN message: RC=3.
Tunnel Delivery Failure — The number of tunnels that failed due to delivery failures, indicated by the following result code value and error code value in the sent/received stopCCN message: RC=2,EC=1.
Tunnel Control Re-transmissions — The number of control packets re-transmitted after a timeout.
Tunnel Control Packets Sent — The total number of control packets sent to the remote peer.
Tunnel Control Packets Received — The total number of control packets received from the remote peer.
Tunnel Data Packets Sent — The number of data traffic packets sent through the tunnel (when Data Traffic is used in the test).
Tunnel Data Packets Received — The number of data traffic packets received through the tunnel (when Data Traffic is used in the test).
Disconnect Count — The number of tunnels disconnected.
Average Connect Time — The average number of seconds required to establish a tunnel.
Average Disconnect Time — The average number of seconds required to tear down a tunnel.