The IPv4 HA Nodal test case tests an HA in a simulated Mobile IPv4 network. This topic will guide you through configuring and running a basic Capacity test, 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
Acceptable home addresses and MIP configuration
To configure an IPv4 HA Nodal 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 IPv4 HA Nodal test case... from the Basic library. The Test Case Settings window... opens to the Test Configuration tab.
Devices and Addresses — Define the SUT and either an FA emulator or co-located care-of addresses for the MNs:
Select the Network Devices tab and select an HA SUT from the HA drop-down list on the SUTs sub-tab.
Define the MN care-of address on the Mobile Subscriber tab. You can configure a test that includes a simulated FA, in which case the FA emulator's address is registered as the care-of address for each MN, or you can define co-located care-of addresses that are assigned to the MNs and registered with the HA. An FA emulator can also be used when co-located care-of addresses are used — in this case the FA acts as the MN's default router.
To include an FA, check the Foreign Agent box. Define the FA emulator on the Foreign Agent sub-tab.
To use co-located addresses alone, define the starting address and network mask in Co-Located Care of Address...
To use both, enable and define the FA emulator, check the Co-Located Care of Address box, and define the starting address and network mask.
MIP Parameters — Configure the Mobile IPv4 extensions:
Select the MIP tab.
If you are using an FA node, select the Encapsulation Mode... used between the FA and HA.
Define a starting value for the MN-NAI Extension... if the SUT requires the extension.
Enable and configure any MIP authentication types that are required.
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. Apply the test case. If any parameters fail validation, you will receive an error indicating the problem parameter. Correct the problem, and Apply 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. When an FA is used, the FA Emulation tab provides information for troubleshooting MIP problems. When co-located addresses are used, the Mobile IP tab is available. A lack of RRP Messages Received can point to connectivity problems with 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 Activation Rate and Deactivation 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 of the MN 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 MN session:
|
Finally, customize the optional behaviors to tailor the test to your purpose. You can define the following options on the General tab:
Apply a distribution model to the activation and deactivation rates with Interval Distribution... using the Advanced... button on the Mobile Node sub-tab.
On the Mobile Node sub-tab, you can also select Static Home Address... or use NAT Traversal... when testing in a VPN model.
If you are using an FA node, you can introduce errors in the test using the Advanced... options on the Foreign Agent sub-tab.
The following options are available on the MIP tab:
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.
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.