The CDMA2000 Mobile IP test cases test FAs and HAs in nodal and end-to-end configurations in a simulated CDMA2000 network. This topic will guide you through configuring and running a basic Capacity Test with each of the test cases, and then expanding that 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 SUT's IP address and authentication, MIP, PPP, and RP configurations.
To configure a CDMA2000 Mobile IP Capacity test:
The goal for the first test is to establish one MN session with the SUT 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, MN, and test case behaviors.
Create a new test session... and add an End-to-End Mobile IP, FA Nodal, or HA Nodal test case... from the Basic library. The Test Case Settings window... opens to the Test Configuration tab.
Devices and Addresses — Define the SUTs and emulators used in the test:
Select the Network Devices tab and define the PDSN-FA and HA SUT(s) or emulators:
In an End-to-End Mobile IP test, select the SUT(s) to be tested from the drop-down lists.
In an FA Nodal test, select the PDSN-FA SUT from the FA drop-down list, and define the HA emulator.
In an HA Nodal test, select the HA SUT from the HA drop-down list, and define the FA emulator.
In an End-to-End Mobile IP or FA Nodal test, define the PCF emulator.
In an FA Nodal test, define a Dynamic Home Address Pool...
Protocol Parameters — Configure the protocols used in the test:
Define the RP interface between the PCF node and the PDSN-FA SUT in an End-to-End Mobile IP or FA Nodal test.
Configure PPP parameters in an End-to-End Mobile IP or FA Nodal test.
Configure the MIP interface between the PDSN-FA and the HA.
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. OK the test case. If any parameters fail validation, you will receive an error indicating the problem parameter. Correct the problem, and OK the test case again. 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 MN session fails to connect, Attempted Session Connects will increment but no connections are recorded. Eventually, Session Errors will accumulate as the connection is retried. End-to-End Testing: Look at the protocol measurement tabs, starting with the first connection attempted by the MNs, Open R-P. If you see Attempts without corresponding Successes, look at the error counters for an indication of why the RP sessions are failing. A common cause of RP session failures is a connectivity problem. Registration Reply Timeout reports RP connectivity problems. Confirm that the PDSN-FA SUT address is correct, and that the address assigned to the PCF 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 RP sessions are successful, but PPP sessions are not, the problem can lie with either PPP or MIP. If the problem lies solely with MIP, RP and PPP sessions will be connected and then disconnected when the MIP session fails. Select the Mobile IP tab and find Agent Advertisements Received. A lack of advertisements indicates that the PDSN-FA SUT is unreachable or not responsive. MIP authentication failures can also cause session failures. The error counters on the Mobile IP tab report authentication and other problems with registration requests. If RP and MIP sessions are establishing but PPP sessions are not, you will see Attempts without Successes on the PPP report tab. Look at the PPP error counters for the reason. Nodal Testing: In an FA Nodal test, the HA Emulation tab provides information for troubleshooting MIP and PPP problems. RRQ Messages Received can point to connectivity problems between the PDSN-FA and the HA node. Authorization failures are reported in HAMN Authorization Failures and HAFA Authorization Failures. In an HA Nodal test, the FA Emulation tab provides information for troubleshooting MIP problems. RRP Messages Received can point to connectivity problems between the FA node and the HA SUT. Authorization and other errors returned by the HA are recorded by the error counters. |
Next, increase the MN sessions and the test rates. Edit the test case... and set the Number of Sessions to 100 and the Session Connect Rate and Session Disconnect Rate to 10.
Apply 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).
|
TROUBLESHOOT: If all the MN session 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 MN session:
|
Finally, customize the optional behaviors to tailor the test to your purpose.
Add auxiliary service instances to the test with Aux Per Mobile Node... (End-to-End Mobile IP and FA Nodal test cases). When you use auxiliary service instances, you can define different Active Start Airlink Parameters for each instance and must check the NVSE Service checkbox to include the Service Option NVSE in RRQ messages.
Apply a distribution model to the MN rates with the Advanced Settings on the Mobile Node sub-tab.
You can introduce errors in the PCF or other node emulators using the Advanced... options on the emulator sub-tabs.
In the End-to-End Mobile IP test case, you can include a second HA for failover testing with the Secondary HA checkbox.
In the FA Nodal and HA Nodal test cases, you can encrypt MIP traffic with IPSec by checking the MIP IPSec box on the General tab. Follow the instructions in Adding IPSec to a Test to configure the IPSec settings.
After you have finished the definition and successfully tested it, save the test case and the test session as a base from which you can derive different tests with the same SUT configuration.
Continue configuring your standard test cases, or expand this test with other test activities or Data Traffic.
To configure the RP interface:
On the RP tab, confirm that the SUT Port Number is compatible with the PDSN-FA SUT.
Define the following parameters according to the SUT provisioning:
Include ESN... and/or Include MEID...
Review the Active Start Airlink Parameters and modify the defaults if necessary.
You can use the following RP options in the test:
Mobility Event Indicator Control (this option is not necessary yet, but will be needed for handoff tests)
Modify the default Magic Number... if necessary.
Select the Network Control Protocol... and enable Van Jacobson Compression... if it is required when IPCP is used.
If the SUT requires that authentication is performed, select the Authorization type on the PPP tab and configure the User Name and Password... The Auto-Increment feature gives you the ability to provision a unique User Name for each MN session.
Configure the AAA server that the SUT will use for authentication to accept the range of names that the test will produce when multiple MN sessions are used.
Select the Synchronization Mode, and configure ACCM if necessary.
You can use the following PPP options in the test:
Error Inject... (with asynchronous PPP)
Select the MIP tab.
Select the Encapsulation Mode... used between the FA 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
If DMU is required by the SUTs in an End-to-End Mobile IP test, define the MIP Key Data payload parameters.
You can use the following MIP options in the test:
Revocation Support Extension... (FA and HA Nodal tests only)