The Mobile IP IPv6 CN Nodal test case tests a CN for Mobile IPv6 compliance 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:
Add the SUT to the database if necessary
Configure IPv6 address pools if necessary
Determine which addresses you will use for the MN care-of addresses, the HA emulator, and the home link prefix
To configure an IPv6 CN Nodal Capacity test:
The goal for the first test is to establish one MN session using a care of address for the MN and a basic Ping DMF to confirm the test case definition, then to successfully execute the test with increased rates and multiple sessions, and finally, to add Route Optimization.
Create a new test session... and add an IPv6 CN Nodal test case... from the Basic library. The Test Case Settings window... opens to the General tab.
The critical aspect of this test definition is correct IP address definition. Build the foundation test in two stages: verify connectivity with a Ping test and then add Route Optimization.
Devices and Addresses — Define the SUT, the HA address, the home link prefix, and the starting addresses for the MNs:
Select a CN SUT from the CN drop-down list in the SUT pane.
Define the HA emulator on the Home Agent Node sub-tab.
Define the Starting Care-of Address and Starting Home Address... The test will assign the care-of addresses to the MNs as if they were attaching to a foreign link.
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. Since both the HA and MNs are simulated in this test your MN sessions should establish without a problem and the Sessions Established, Attempted Session Connects, and Actual Session Connects measurements on the Test Summary tab are all 1. The measurement definitions are located in the Measurement Reference. Explore the measurements displayed on the tabs, and you will notice that all packet counters are 0. This is because no messages are exchanged between the MN and HA emulators. In this test messages are only exchanged with the CN SUT. Stop the test session when you are ready to continue.
Next, add Data Traffic to the test.
Data Traffic — Enable Data Traffic and add a Ping DMF:
Select the Data Traffic tab.
Select Continuous from the Data Traffic drop-down list.
Click the Add button below Data Msg Flow, select Existing and the Select Data Message Flow window opens.
Select Basic from the Library drop-down list, select Basic Ping and then click Select. The Basic Ping DMF is displayed in the DMF list.
Run the test session and select the MN report tab when it is available. Now you should see Total Packets Received and Total Packets Sent. These are the pings sent to and received from the CN. The Data Traffic measurement tab is also displayed, and should report the same number of packets as the MN tab.
|
TROUBLESHOOT: If the Total Packets Received on the Data Traffic and MN tabs are 0, the ping responses are not being received. The most likely cause is an error in the SUT IP address or a connectivity issue. Test the connection to the SUT with the System Under Test Administration window. You can define a static route to the SUT if necessary. |
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:
|
Now that you have validated the address definitions and the connection to the SUT, add Route Optimization by checking the Route Optimization box on the Data Traffic pane.
Run the test again, and you will see MN RO Attempts on the MN measurement tab, accompanied by the return routability message counters, MN HOTI Sent and MN COTI Sent. If Route Optimization is successful, you will also see MN RO Successes accompanied by MN HT Received and MN COT Received.
If Route Optimization fails, Sessions Established on the Test Summary tab will be 0, as will either MN HT Received, MN COT Received, or both. If Home Test messages are received but Care-of Test messages are not, or vice versa, you may have a routing issue to either the home or care-of addresses used by the MNs.
Your foundation test is functional and complete, and you can enable Re-registration... if desired. The other MN options are only applicable to an IPv6 HA Nodal 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.