The HSGW Nodal test case tests a HSGW's capability to service MS in a simulated network. This topic will guide you through configuring and running a basic Capacity Test (with Multi-PDN and Multi-Aux Configuration in eHRPD), and then expanding the basic test with the optional behaviors available in the test case.
After you have a functioning test session, you can build tests using other test activities and options:
You should have a basic understanding of the test system:
Prepare the system and gather information about the SUT
Add the SUT to the database if necessary
The High-Speed Gateway requirements
To configure a HSGW Nodal Capacity test with Multi-PDN and Multi-Aux Configuration:
The goal for the first test is to set up 2 PDN connections and 3 Auxiliary connections per Subscriber and to confirm the test case definition, then to successfully execute the test with increased rates and multiple sessions, and finally, to customize the more advanced protocol, MS, and test case behaviors.
Create a new test session... and add a HSGW Nodal test case... from the Basic library. The Test Case Settings window... opens to the Test Configuration tab.
Enter the Number of Mobile Subscribers that will be requested by the HSGW as 1 and Auxiliary Service Instances per Subscriber as 4 on the Mobile Subscriber pane of the Test Configuration tab, activate/deactivation Rates.
Home Address Type as IPv4 and enter the Bearer IPv4 Addres Pool
Network Devices — Identify the SUT and define the HSGW emulator
Select the High-Speed Gateway SUT from the SUT list.
Define one ePCF that emulates Packet Control Functions that service the MSs/UEs. Select a Physical Interface and configure the Ethernet settings.
Define 2 LMA Nodes to indicate your requirement of 2 PDN connections including the Main connection.
RP Interface — Define the PPP parameters that indicate the Network Control Protocol for testing eHRPD
Select the Network Control Protocol on the PPP tab as VSCCP for eHRPD testing.
RP Interface — Use the RP tab to define and map Service Instance Settings (Auxillary) with the Service Instance APN Settings
The tabs displayed on the Service Instance Settings pane is Main, Aux-1, Aux-2, Aux-3, and Aux-4 and the corresponding PDN tabs is P0, P1, P2, P3, and P4. (As you set up 2 PDN and 3 Auxiliary connections, select Mobile Subscriber as 1 and Auxiliary Service Instances per Subscriber as 4 on the Mobile Subscriber pane of the Test Configuration tab).
Service Instance Settings pane:
Select Individual and Select Fill Session References to automatically provision MN Session Reference Number with a unique value in each sub-tab. That is, MN Reference Number will be 1 on the Main tab, 2 on the Aux-1 tab, 3 on Aux-3 tab, and so on.
As the goal is to assign 2 PDNs on the first 2 connections, follow these steps to set up the connection.
Set up the Main, Aux-1 as the 2 PDN connections. That is, select GRE Key Service Information Option (eHRPD Settings pane) value as SO59 (to indicate PDN connection).
Set up Aux-2, Aux-3, and Aux-4 as Auxiliary Service Instances. That is, select GRE Key Service Information Option (eHRPD Settings pane) value as SO67 (to indicate Auxiliary connection).
Service Instance APN Assignments pane:
The PDN connections are mapped one-to-one with APN assignments. Hence, Main and Aux-1 (Service Instance Settings pane) corresponds P0 and P1 (Service Instance APN Assignments pane) respectively. In addition, the set up unique APN values the 2 PDN and map each Auxiliary connection by entering the same APN as that of the PDN connection.
Enter a unique Starting Auto-Incrementable APN value on P0 and P1 tabs.
Enter the APN value on P2 as the same APN value you entered on P0.
Enter the APN value on P3 and P4 as the same APN value you entered on P1.
Quick Reference of PDN and Auxiliary connections mapping:
| Service Instance Settings pane | Service Instance APN Assignments pane |
| Main | P0 |
| AUX-1 |
P1 |
| AUX-2 |
P2
|
| AUX-3 |
P3
|
| AUX-4 |
P4
|
You are now ready to test your configuration. The parameters that have not been addressed control optional behaviors that do not affect the success of a session. Click OK to accept the test case. If any parameters fail validation, you will receive an error indicating the problem parameter. Correct the problem and when the definition is accepted, the test case is listed in the Test Session window.
Run the test session, and a validation check is performed on the test session. This validation ensures that the IP addresses used by the test case do not conflict with any other test sessions that may be running on the test server, and that the test definition does not violate rate and volume limits. You will also receive an error if you attempt to run the test session on a test server that is already running at capacity or is otherwise unable to accept a test session. See Running a Test Session for more information on handling these types of errors.
Select the Reports tab when it becomes available. Ideally, your MN session is established and the Sessions Established, Attempted Session Connects, and Actual Session Connects measurements on the Test Summary tab are all 1. Explore the measurements displayed on the tabs. The measurement definitions are located in the Measurement Reference. Stop the test session when you are ready to continue.
|
TROUBLESHOOT: If the MS session fails to connect, Attempted Session Connects will increment but no connections are recorded. Eventually, Session Errors will accumulate as the connection is retried. Common causes of session failures are connectivity problems and authentication failures. Attach Timeout on the ePCF Node and LMA measurement tabs report any connectivity problems. Confirm that the SUT address is correct, and that the address assigned to the MME node does not conflict with another device in the test network. You can also SSH to the test server as cfguser and ping the SUT. If Create Responses are being received, look at the Open R-P error counters for more information. |
Edit the test case... and set the Activation Rate (Subscribers/sec) and Deactivation Rate (Subscribers/sec) to 10. Set the Mobile Subscribers (Test Configuration tab) to 20 and Maximum Bearers per Subscriber to 5, which will result in 100 total PDP contexts.
Run the test session again. This time you should be able to see the MS sessions establish over 10 seconds (10 PDP contexts each second).
|
TROUBLESHOOT: If all of the MS sessions fail to establish, Attempted Session Connects will be larger than Actual Session Connects and Sessions Established. The most likely reason is a problem with parameter values that increment for each MME session:
|
Finally, customize the optional behaviors to tailor the test to your purpose.
General options:
You can apply a distribution model to vary the activation and deactivation rates with Advanced Settings... on the Mobile Subscriber pane on the Test Configuration tab.
You can introduce errors in an Ethernet ePCF Node and/or LMA Node using the Advanced... options.
After you have finished the definition and successfully tested it, save the test case and the test session as "HSGW Base" or something similar.
Continue building your standard tests with other test activities or Data Traffic, and then try combining multiple test cases in one test session using linked test cases and Automation Control.