The parameters in this topic are used in the IPv6 HA Nodal, IPv6 CN Nodal, IPv6 CN Node, FA Nodal, and End-to-End Mobile IP test cases to define the types of Mobile IPv6 and ICMPv6 messages the MNs will send.
IPv6 HA Nodal FA Nodal End-to-End Mobile IP
|
|
|
IPv6 CN Nodal |
Home Agent |
|
|
|
Authentication |
|
|
|
Measurements collected for Mobile Node related processing are reported on the MN report tab.
Use the checkbox to direct the MN to perform Home Agent Discovery when it simulates attaching to a link. This process will occur when the test starts.
Available when you select Home Agent Discovery, indicates the subnet prefix and requires an IPv6 address.
NOTE: The Home Agent SUT is now disabled when you select Home Agent Discovery on the MIP | MIPv6 tab. |
NOTE: The anycast address to which the Home Agent Address Discovery Request message is sent is defined in the HA SUT definition by including a subnet prefix with the SUT's IP Address. |
When MIP Protocol = V6 on the Test Configuration tab and you select Home Agent Discovery (Pi-MIP > MIPv6 tab), the HA SUT and HA Port fields on the Network Devices tab are not available.
Mip6MnHaDiscEnabler |
Mip6HaPrefix |
The following message counters record messages sent and received by an MN during the Home Agent Discovery process:
MN HADR Received
MN HAD Sent
Use the checkbox to enable (default) or disable MN-HA bindings. When bindings are disabled and MIPv6 IPSec is enabled, the test will simply establish SAs with the HA. No Binding Updates are transmitted in this type of test and Data Traffic cannot be used. The purpose is to stress the HA's IPSec capability.
NOTE: Authentication parameters are not available when the Home Agent Binding checkbox is disabled. |
Tcl Parameter: BindingEnableFlag
Use the checkbox to direct the MN to perform Prefix Solicitation prior to the expiration of their home addresses or when directed to do so by the HA.
Related Measurements
The following message counters record messages sent and received by an MN during the Prefix Solicitation process:
MN MPA Received
MN MPS Sent
MN BA01
Tcl Parameter: Mip6MnPfxSolEnabler
The number of seconds that an MN will request as the binding lifetime in Binding Updates sent to the HA. If a shorter lifetime is returned in a Binding Acknowledgement, that value is used for the binding's lifetime timer. Every binding's lifetime is timed independently.
When Route Optimization is used, this value is also the maximum number of seconds that the CN will accept for an MN-CN binding lifetime.
Range: N/A
Default: 3600
Tcl Parameter:
Mip6MnLifetime |
Pmip6MnLifetime |
Mip6CnLifetime |
S2aPmip6MnLifetime |
Use the checkbox to direct an MN to refresh its bindings with the HA or CN before the binding lifetime expires.
When Route Optimization is selected, use the checkbox to direct the CN to send Binding Refresh requests to the MNs before the Lifetime expires.
Time Prior to Lifetime — The number of seconds prior to the lifetime expiration that the Binding Update is sent.
Range: 0 — 100
Default: 20
Tcl Parameter:
Mip6BindingRefreshEnabler |
Mip6MnRefresh |
Mip6CnBindingRefreshEnabler |
Mip6CnRefresh |
Pmip6BindingRefreshEnabler |
Pmip6MnRefresh |
S2aPmip6BindingRefreshEnabler |
S2aPmip6MnRefresh |
The Delete checkbox is checked by default, which means that the MN will request that the HA delete its binding with the MN when the MN is disconnected or when the MN is handed off to its home link in a Returning Home test (see Mobility). When Route Optimization is used, the MN-CN binding is also deleted.
When this checkbox is cleared, the bindings are allowed to expire when their lifetimes expire.
Tcl Parameter:
MipMNDeregistrationEnabled |
Pmip6DeregistrationEnabled |
S2aPmip6DeregistrationEnabled |
NOTE: In a Session Loading or a Returning Home test, either this box must be checked or the MNs must remain idle or "at home" long enough for their bindings to expire. Otherwise, if the test attempts to re-establish a binding that still exists, the HA should reject the request. |
See Retries
Tcl Parameter:
Mip6MnRetries |
Pmip6MnRetries |
S2aPmip6MnRetries |
Defines the NAI used in the registration messages to identify the MN. You can use a static NAI for all MN nodes, or configure unique extension values with the Auto-Increment feature.
Select the MN-NAI checkbox to include the NAI in registration messages. When MN-NAI is enabled, MN-AAA Authentication is also available.
When Route Optimization is enabled on the Test Configuration tab, MN-NAI is not available for selection.
IMPORTANT: When you use an incrementing NAI extension with an HA node in an FA Nodal test, you must specify the starting value; otherwise, the corresponding NAI extensions provisioned for the HA node will continue incrementing from the last MN value. In a test with 10 MN sessions for example, somename#(0)@sometext produces somename0@sometext through somename9@sometext values for both the MNs and the HA. If you used somename#@sometext, the MNs are provisioned with somename0@sometext through somename9@sometext, but the HA is provisioned to accept somename10@sometext through somename19@sometext. |
Range: N/A
Default: N/A
Tcl Parameters: Mip6MnNai
An emulated HA will reject registration requests received with an invalid NAI extension and will reply with an error code value of 129. These errors are reported on the Mobile IP and Open RP tabs as HA Admin Prohibited (129).
Use the AAA Authentication checkbox to specify Authentication, Authorization, and Accounting values for the mobile node. Use the MIP Authentication parameters to configure the Shared Secret for the authentication extensions in the RRQ message.
NOTE: Authentication parameters are not available when the Home Agent Binding checkbox is disabled. |
The secret code to be used in the extension. You can use one of three formats to provision the code:
Static string values (default)
Binary keys (hexadecimal format)
A unique value for each MN (Auto-Increment format)
NOTE: When an incrementing format is used, the additional processing required will reduce the maximum number of MN sessions. |
Range: N/A
Default: secret
Tcl Parameter: MipV6MnAaaSecret
Use the MN HA Authentication checkbox to authenticate a Home Agent. The HA emulator simulates a Home Agent when an HA SUT is not used. The following types of mobile home authentication are used with MIPV6:
The secret code to be used in the extension. You can use one of three formats to provision the code:
Static string values (default)
Binary keys (hexadecimal format)
A unique value for each MN (Auto-Increment format)
NOTE: When an incrementing format is used, the additional processing required will reduce the maximum number of MN sessions. |
Range: N/A
Default: secret
Tcl Parameter: MipV6MnHaSecret
The Security Parameter Index identifies a security context between two Home Agent peers.
NOTE: By default, a 64-bit SPI is transmitted. If your SUT requires a fixed length other than 64 bits, use a hexadecimal format. |
Range: N/A
Default: 1000 (0 255 are reserved)
Tcl Parameter: MipV6MnHaSpi