The ASN Nodal test case tests an ASN Gateway's (ASN-GW) capability to establish connections with Base Stations and support MN control plane and bearer plane traffic. This topic will guide you through configuring and running a basic Capacity Test, 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:
Data IPSec (Dynamic IPSec feature required)
You should have a basic understanding of the test system:
Gather information about the SUT and prepare the test system:
Obtain the SUT's IP address and add the SUT to the database
MN and Base Station identifiers that are acceptable to the SUT
The message authentication code used by the SUT
To configure an ASN Nodal Capacity test:
The goal for the first test is to establish one Base Station link and one MN session to confirm the test case definition, and then to successfully execute the test with increased rates and multiple sessions.
Create a new test session... and add an ASN Nodal test case... from the Basic library. The Test Case Settings window... opens to the Test Configuration tab.
On the Network Devices tab, select the SUT from the ASN drop-down list in the System Under Test pane.
Complete the Base Station definition in the Base Station Node sub-tab, and enter a unique BS ID in hexadecimal format.
Complete the Target Base Station definition in the Target Base Station Node, and enter a unique Target BS ID in hexadecimal format.
Define the MN:
Enter a MAC address for the MN in MS ID.
Select the EAP Authentication Type...
Select the MIP Scheme.
In this test case, MN addresses are obtained from a DHCP server. Click the Settings... button in the Data Traffic tab and configure the DHCP client settings following the instructions in Adding a DHCP Client.
NOTE: DHCP configuration is not supported for Client MIP. It is only available for Proxy MIP and Simple IP, and it is mandatory. |
For an ASN Nodal test, select the HA Node Emulation checkbox, and configure the HA node. (Skip this step for an end-to-end test.)
In the Mobile Subscriber tab, configure the WiMAX Forum parameters.
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 BS link and MN session are established and the BS Links Established, 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 described in The ASN Nodal Test Case topic. Stop the test session when you are ready to continue.
Next, increase the MN sessions and the test rates. Edit the test case... and set the Number of Subscribers to 100 and the Activation Rate and Deactivation Rate to 10.
OK the change, and Run the test session again. This time you should be able to see the MN sessions establish over 10 seconds (10 sessions each second) after the link is established.
TROUBLESHOOT: If all of the MN session fail to establish, Attempted Session Connects will be larger than Actual Session Connects and Sessions Established. The problem could be with the MS ID that increments for each MN session or failure to obtain an address from the DHCP server. |
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 Interval Distribution on the Mobile Subscriber pane. Click the Advanced Settings... button and the Interval Distribution dialogs opens.
You can enable EAP-TTLS authentication by clicking the Settings... button for Authentication Type: EAP to access the EAP parameters. See Using Digital Certificates for instructions on provisioning the test server with Certificate Files. Provision the EAP-TTLS settings following the guidelines for EAP-TLS.
If the SUT requires that IPSec is used, check the IPSec box and configure the parameters on the BS-ASN IPSec tab following the instructions in Adding IPSec to a Test.
After you have finished the definition and successfully tested it, save the test case and the test session as "ASN Nodal Base" or something similar. Continue building your standard tests by expanding your base test with other test activities or Data Traffic.
Select the MIP tab.
Select the Encapsulation Mode... used between the MN and HA.
The reverse tunnel model is used by default. Reverse Tunnel... can be cleared when reverse tunneling is not required, or requested when reverse tunneling is optional.
Define a starting value for the MN-NAI Extension...
Configure the MIP Authentication keys
You can use the following MIP options in the test: