Capacity Test Settings

These parameters are accessible by clicking the Settings... button in the Test Activity pane when Capacity Test is selected from the Test Activity drop-down list.

Learn more about the Capacity Test

Start Retries

When you check the Start Retries box, the test will continue to attempt to re-connect any sessions that failed. The test first attempts to start all of the sessions defined for the test and then retries failed sessions. A session failure includes any failure to reach the established state and any failure after the session is established. Error counters are incremented for each session failure.

When you clear the checkbox, the test attempts to start all of the sessions defined for the test and will only retry failed sessions as defined in the control protocol retries. After all sessions have been attempted, the test case advances to the Running state regardless of whether all sessions were successfully established.

NOTES:

When Start Retries is enabled and any sessions fail to be initially established, the test case remains in the Started state. Any Automation Control steps that depend on the test case reaching the Running state will not be executed, nor will any test events that use a When All Sessions Established trigger such as Traffic Start.
Start Retries cannot be used when Auto Stop Control Layer is enabled since the test would attempt to re-connect sessions that were disconnected when bearer plane traffic stopped.

Disconnect Initiated By

Use the drop-down list to select the emulated mode for disconnecting sessions in a CDMA2000 or GPRS test.

CDMA2000 Testing

Options:

Mobile Node

Stops sessions from the Traffic Layer.

Data traffic stops -> MIP Layer stops (optional, if this layer exists) -> PPP Layer stops -> RP Layer stops.

Mobile Node PPP

Stops sessions from PPP Layer.

PPP Layer stops -> RP Layer stops. The MIP Layer (if it exists) disconnects only when its timers expires.

PCF

Stops sessions from RP Layer. Both MIP Layer (if it exists) and PPP Layer disconnects only when their timers expires.

Default: Mobile Node

GPRS Testing

Options:

Mobile Node — Emulates a disconnect by the mobile node, with the PPP or IPv4 layer initiating the disconnect.
SGSN — Emulates a disconnect initiated by the SGSN at the GTP layer.

Default: Mobile Node

MME Testing / 5G Testing

Options:

Mobile Node — Emulates a disconnect by the mobile node.
MME — Emulates a disconnect initiated by the MME.
HSS — Emulates a disconnect initiated by the HSS.

Default: Mobile Node

AMF Nodal / Initiate PDU Connection

Options:

When All UEs Registered - 0 (default) - Send PDU request only after all UEs have registered
When UE Registered - Send PDU request immediately after each UE has registered. For support of 1 Service Request for Multiple PDNs - Select "When UE Registered" and set Data Traffic - "Traffic Start" to "When Session Established" with "Data Start Delay (ms)" to 1500.

Initiate Next PDN Connection

Added selection to create multiple Default Bearers in Attach procedure. Available when Default Bearers per Session is > 1.

Options:

When All Initial PDN Connections Established
When Initial PDN Connection Started

Idle ODC Timeout (s)

Available in AMF Nodal, MME Nodal, and SGW Nodal. Select Idle ODC Timeout and configure a value in seconds for Auto-stopping test cases.

Range: 1 to 604800, Default : 60

The Test Session will be automatically taken down when the Idle ODC Timeout functionality is enabled and the delay time between two consecutive ODC commands (or before the very 1^st^ ODC Command) exceeds the configured value of Idle ODC Timeout.

Tcl Parameter: IdleOdcTimeEn

Tcl Parameter: IdleOdcTime

These parameters are accessible by clicking the Settings... button in the Test Activity pane when Command Mode Test is selected from the Test Activity drop-down list.

Learn more about the Command Mode Test