You can define the number of times the test will re-transmit (retry) a message after a timeout occurs while waiting for a response, and in some cases, the amount of time the test will wait for a response.
|
NOTE: When the retry attempts have been exhausted, the applicable timeout counter is incremented. The test continues to transmit the message unless otherwise noted. |
Retries can be used in the following protocols:
Your ability to define retry behavior depends on the data application and transport protocols. If the total number of retries have been attempted without receiving a response, the appropriate error counters are incremented. Retry time at the TCP layer is controlled by the TCP Retransmission Timer selection. All Advanced Data protocols support configurable retry processing, and you can define the number of retries and the retry timer in the Data Message Flow window...
|
NOTES:
|
Total Retries — The maximum number of attempts made by the client or server to send a request message after the Data Response Time has expired.
Range: N/A
Default: 0
Data Response Time — The number of milliseconds to wait for a response from the other end.
Range: 3000 — 2,000,000,000
Default: Varies by protocol
You can define both the amount of time a DHCP client will wait for a message from the server and number of times the client will re-transmit a message until a response is received.
|
DhcpOfferTime |
DhcpAckTime |
|
MgmtDhcpOfferTime |
MgmtDhcpAckTime |
|
WanDhcpOfferTime |
WanDhcpAckTime |
Retries — The number of times a message is re-transmitted. Enter 0 to disable retries.
Range: 0— 65535
Default: 3
V4 Offer Message or V6 Advertise Message — The number of seconds the client will wait for a DHCPOFFER message in an IPv4 test or an Advertise message in an IPv6 test.
Range: 0— 65535
Default: 1
V4 Ack Message or V6 Reply Message — The number of seconds the client will wait for a DHCPACK message in an IPv4 test or a Reply message in an IPv6 test.
Range: 0— 65535
Default: 1
You can define both the amount of time the test will wait for a response from an SGSN or from a GGSN, and the number of times a message will be re-transmitted. If a response has not been received by the time the T3 timer expires, and if N3 - Command Request Attempts has not been exceeded, the message is re-transmitted. When all retries have been exhausted, the timeout counter is incremented and no further attempt is made to transmit the message.
|
NOTE: When Start Retries is enabled in a Capacity Test, retries will continue indefinitely. |
N3 - Command Request Attempts — The maximum number of attempts made by GTP to send a request message without receiving an associated response message from the GGSN. Enter 1 to disable retries.
Range: 1— 65535
Default: 5
Tcl Parameter: N3Attempts
T3 - Wait time for GGSN Response — The number of seconds to wait for a command request response. The T3 timer starts when a signaling request message (for which a response has been defined) is sent.
Range: 1— 65535
Default: 20
Tcl Parameter: T3Time
The following measurements record the number of timeouts encountered for the different types of requests:
You can define both the amount of time the test will wait for a response from a GSN or CGF, and the number of times a message will be transmitted.
The number of seconds to wait for a GTP' message. If a response is not received by the time the interval expires, another message is sent if Retries is enabled.
Range: 0 — 65536
Default: 10
The number of times a GTP' message will be re-transmitted if a response is not received within the Retry Interval. Enter 0 to disable retries.
Range: N/A
Default: 5
You can define both the number of times an L2TP tunnel establishment will be retried and the maximum amount of time to wait between attempts with Retries and Max Retry Interval on the L2TP tab in a Simple IP VPN test case.
Max Retry Interval — The maximum number of seconds to wait between attempts. The first retry is made at 1 second, the second at 2 seconds, and the third at 4 seconds. The retry interval will continue to double until the maximum is reached.
Range: 1— 65535
Default: 8
Retries — The number of times a message will be re-transmitted after the retry interval expires.
Range: 1— 65535
Default: 3
The following measurements record L2TP session failures and the number of messages sent due to a timeout:
You can define the MIP retry behavior with Retries and Initial Retry Interval on the MIP tab in CDMA2000 and Mobile IP IPv4 test cases.
|
NOTE: When Start Retries is enabled in a Capacity Test, retries will continue indefinitely. |
Retries — The number of times a message will be re-transmitted after the retry interval expires.
Range: N/A
Default: 1
Initial Retry Interval — The number of seconds that the test will wait for a response if a response is expected. If a response is not received before the time expires and Retries has not been exceeded, the message is re-transmitted, the number of retries is incremented, and this value is doubled for the next retry interval.
Range: 1 — 60
Default: 5
The following measurements record Registration Request retries:
You can define the NAS retry behavior on the SI-MME tab in the MME Nodal Test Case.
Retries — The number of times a message will be re-transmitted after the retry time/interval expires.
Retry Time — The value for the retry interval timer. The second retry attempt, if any, will be made after both Idle Entry Time and the Retry Time are exceeded.
Idle Entry Time — The length of time to wait before attaching to MME.
Tracking Area Update Time — The length of time to wait before sending the Tracking Area location used by UE during the attach procedure with the MME.
Retries is defined for Mobile IP IPv6 test cases specifies the number of times an MN will re-transmit Home Test Init, Care of Test Init, Mobile Prefix Solicitation, or Binding Update messages until a response is received from an HA or a CN.
|
NOTE: When Start Retries is enabled in a Capacity Test, retries will continue indefinitely. |
Range: N/A
Default: 3
Error counters on the MN report tab record the number of retries and the number of times Retries was exceeded for each type of message.
You can define the number of times an MN registration will be retried, the amount of time to wait for a reply, and the amount of time to wait between retry attempts with Registration Timeout, Retries, Retry Interval, and Max Retry Interval on the RP tab in CDMA2000 test cases.
Registration Timeout — The number of seconds the test will wait for a registration reply. If Retries are enabled, the first retransmission will occur when this timer expires and subsequent retries will occur after both this timer and the Retry Interval timer expire.
Range: 0— 65535
Default: 3
Retries — The number of times a message will be re-transmitted. Enter 0 to disable retries.
Range: 0— 10
Default: 3
Retry Interval — The starting value and the incrementing value for the retry interval timer. The second retry attempt, if any, will be made after both Registration Timeout and the interval timer are exceeded, and the interval timer will be incremented by the starting value for each subsequent attempt until Max Retry Interval is reached. Example:Example:
Using the default values as an example:
The test sends a registration request.
If a reply is not received in 3 seconds (Registration Timeout), a second request is sent.
If a reply to the second request is not received in 3 seconds, the Retry Interval timer starts and runs for 10 seconds. The third request is sent when the interval timer expires.
If more than 3 Retries are defined, the Retry Interval timer is incremented by 10 seconds (the starting value) for each subsequent retry attempt until Max Retry Interval is reached.
Range: 0— 65535
Default: 10
Max Retry Interval — The maximum value for the Retry Interval timer.
Range: 1— 65535
Default: 60
|
NOTE: When Start Retries is enabled in a Capacity Test, retries will continue indefinitely. Otherwise, the test will stop if retries are exhausted for all MNs. |
Range: 0 — 10
Default: 3
The following RP measurements record Registration Request retries:
Retries and LCP Timer are defined on the PPP tab, and specify the number of times PPP session establishment will be attempted and the length of time to wait for a response during LCP negotiation.
|
NOTE: When Start Retries is enabled in a Capacity Test, retries will continue indefinitely. |
Retries — The number of times a message will be re-transmitted until a response is received. Enter 0 to disable retries.
Range: 0 — 10
Default: 3
LCP Timer — The number of milliseconds to wait for a response during LCP negotiation.
Range: 0 — 65535
Default: 5000
The following measurements record the number of times this threshold is exceeded:
Retry Time and Retry Count are on the NAS tab. Retry Time defines the amount of time to wait for an Access Response or Accounting Response message in response to an Access Request or Accounting Request message. Retry Count defines the number of times an Access Request or Accounting Request message can be sent.
|
NOTES:
|
Retry Time — The amount of time, in milliseconds, that the test will wait for a response if a response is expected. When the time expires and the Retry Count has not been exceeded, the message is re-transmitted.
Range: N/A
Default: 1000
Tcl parameter: NasRetryTime
Retry Count — The maximum number of times a message will be sent. The default (1) disables retries.
Range: N/A
Default: 1
Tcl parameter: NasRetryCount
Retry Time and Retry Count are in the CoA Simulation pane and are only used when CoA support is enabled. Retry Time defines the amount of time the node will wait for a CoA ACK or a CoA NACK in response to a CoA Request message. Retry Count defines the number of times a CoA Request can be sent.
Retry Time — The amount of time, in milliseconds, that the test will wait for a response. When the time expires and the Retry Count has not been exceeded, the message is re-transmitted. If a subsequent request is received from a NAS that triggers a new CoA Request, the time is reset and the node will no longer track the response to the previous request.
Range: N/A
Default: 1000
Retry Count — The maximum number of times a message will be sent. Enter 1 to disable retries.
Range: 1 — 65536
Default: 5
You can define both the amount of time the Base Station nodes will wait for a control plane response from the SUT, and the number of times a message will be transmitted. DHCP and Data Traffic retry behavior are separately defined.
The number of seconds to wait for a response. If a response is not received by the time the interval expires, another message is sent if Retries is enabled.
Range: 0 — 65536
Default: 0
The number of times a message will be re-transmitted if a response is not received within the Retry Interval. Enter 0 to disable retries.
Range: N/A
Default: 0