The Mobile IP IPv6 HA Nodal test case tests an HA in a simulated Mobile IPv6 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
Determine the SUT's home link prefix and IPSec configuration
Configure IPv6 address pools if necessary. The local interface should have a pool that is large enough to accommodate two sets of foreign addresses: one set for the initial care-of addresses a second set that can be used in a handoff test. At least one other interface should be configured with a small pool of addresses that can be used for CN emulators.
To configure an IPv6 HA Nodal Capacity test:
The goal for the first test is to establish one MN session with the SUT using a care-of address for the MN 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 IPv6 HA Nodal test case... from the Basic library. The Test Case Settings window... opens to the General tab.
The two critical aspects of this test definition are correct IP addresses and the IPSec configuration. Build the foundation test in two stages: disable IPSec on the SUT until you have successfully executed a test, thereby validating the address definitions, and then enable IPSec and repeat the test.
Devices and Addresses — Define the SUT and the starting addresses for the MNs:
Select an HA SUT from the HA drop-down list in the SUT pane.
Define the Starting Care-of Address and Starting Home Address... The test will begin by assigning the care-of addresses to the MNs as if they were attaching to a foreign link. You should configure care-of addresses that will be compatible with future handoff tests, using the same interface identifier in both the home and care-of addresses.
The CN emulator is only used with Data Traffic, but it is required for the test definition. For now, define a local CN emulator. Select a Physical Interface that is not used by the MNs and either accept the default address or enter an IPv6 Address from the interface's address pool.
You are now ready to test your configuration. The parameters that have not been addressed control optional behaviors that should 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. The MN report tab contains counters for the messages sent and received by the MNs.
|
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 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 the starting addresses. Confirm the following:
It is also possible that the HA SUT cannot handle all of the sessions. In this case you should see error counters with Status values of 128 or 130. |
Now that you have validated the address definitions, enable IPSec on the HA and add IPSec to the test definition following the instructions in Adding IPSec to a Test for RFC-compliant testing.
Run the test again, and if the IPSec configuration is correct, you should see all sessions establish as they did without IPSec. You should also see IPSec Attempts and IPSec Successes on the MN measurement tab. If any sessions fail to establish, look for IPSec Failures and errors on the IPSec tab. Refine your IPSec configuration if necessary.
Your foundation test is functional and complete, and you can enable the rest of the MN options if desired:
Delete binding... This is enabled by default — you can disable it to allow bindings to expire when their lifetimes expire.
You can also clear the Binding... checkbox and run an IPSec-only test.
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 with or without Route Optimization.
The CN emulator that you defined in the foundation test is used as the Network Host for bearer plane traffic. First review the information in About Data Traffic and then follow the instructions in Adding Data Traffic, skipping the Network Host definition.
|
TIPS:
|