MIP Tab

• Simultaneous Bindings

• Reverse Tunnel

• Encapsulation Mode

• NAT Traversal

• Broadcast Home Agent Address

• HA Lifetime

• Re-registration

• Mobile Node De-registration

• Retries

• Initial Retry Interval

• Dynamic HA Support

• Max Number of Router Prefixes

• Request Broadcast Datagrams

• RFC 3344

• Proprietary Extensions

• MN-NAI Extension

• MN-FA Challenge Size

• PMIP4 Device Id Extension

• Registration Support Extension

• Inform Mobile Node

• Access Technology Type

• AAA Authentication

• MN-AAA-SPI

• MN-AAA-Secret

• AAA Authentication Algorithm

• HMAC Authentication

• Mobile Home Authentication

• MN-HA-SPI

• MN-HA-Secret

• HA Authentication Algorithm

• FA Authentication

• MN-FA-SPI

• MN-FA-Secret

• FA Authentication Algorithm

• Calling Station ID Extension

• Vendor ID

• Vendor NVSE Type

• Calling Station ID

• Correlation ID Extension

• Vendor ID

• Vendor NVSE Type

• Correlation ID

DMU

• MSID

• CHAP Secret

• AAA Authenticator

• MN Authenticator

• Vendor Varient

• Public Key Organization ID

• Public Key Organization Index

• PK Expansion

• Public Key File

• First Entry

• Number of Entries

• File Format

• WiMAX Support

• MIP Root Key

• Use Static Home Address

Apply Parameters from Test Data File

Use the checkbox to request simultaneous bindings on an HA SUT or to permit simultaneous bindings with an HA emulator. When enabled, you can specify whether they must be used (Mandatory) or may be used (Requested) with the drop-down list.

Options:  Requested or Mandatory

Default:   Requested

Tcl Parameter: MipReqSimulBindingsEnabled

Tcl Parameter: PiMipReqSimulBindingsEnabled

Use the checkbox to request broadcast datagrams in the MIP RRQ message.

Tcl Parameter: MipReqBcastDatagramEnable

Tcl Parameter: PiMipReqBcastDatagramEnable

Use the drop-down list to select the IP layer encapsulation that will be used to tunnel traffic between an MN or FA and an HA.

Options:  

Default:   IP/IP

Tcl Parameters:

Use the checkbox to enable the reverse tunnel CDMA2000 or Mobile IPv4 configuration. When enabled, you can specify whether the configuration must be used (Mandatory) or may be used (Allowed) with the drop-down list.

Options:  Mandatory or Allowed

Default:   Mandatory

Tcl Parameter: MipReverseTunnelEnable

Tcl Parameter: PiMipReverseTunnelEnable

This is an option to set the "Home Agent Address" field of "Registration Request Message" to "255.255.255.255". If this option is not enabled, the "Home Agent Address" field of "Registration Request Message" will be configured by the "Home Agent Address", normally this is the destination IP address of "Registration Request Message".

Tcl Parameter: MipBroadCastHaAddr

The number of seconds a session is maintained without a Re-registration Request. Enter 65535 to disable the lifetime timer.

Range:  1 — 65535

Default:  65535

Tcl Parameter: MipHaLifetime

Tcl Parameter: PiMipHaLifetime

Use the checkbox to enable Re-registration Requests. When enabled, you can define when the request is sent.

Time Prior to Lifetime — The number of seconds prior to the expiration of the lifetime timer to send the Re-registration Request.

Range:  0 — 100  

Default: 20

Tcl Parameters:

Related Measurements

• Re-register Attempts

Use the checkbox to allow the MN to de-register all care-of addresses when it returns to its home network. An RRQ with a Lifetime of 0 and with a Care of Address and Source IP Address that both equal the MN's home address identifies a de-registration request.

Tcl Parameter: MipMNDeregistrationEnabled

Tcl Parameter: PiMipMNDeregistrationEnabled

Related Measurements

• Deregistration Messages Sent

• Deregistration Messages Received

Tcl Parameters:

See Retries.

Available in HA Node, test case, indicates the maximum number of router prefixes supported. (Used in conjunction with PGW Nodal Test Case, when NEMO Emulation is selected)

Option: 0 - 16

Default: 0

Tcl Parameter: MipMaxRouterPrefixes

Tcl Parameter: PiMipMaxRouterPrefixes

Tcl Parameter: MipExtEn

See Proprietary Extensions.

Use the checkbox to enable either RFC 3344 (Checked) or RFC 2002 (Cleared) conformance. See RFC 3344, Section G. Changes since RFC 2002 for specific information on the differences between these options.

Default: Checked  

Tcl Parameter: Rfc3344Enabler

Tcl Parameter: PiRfc3344Enabler

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.

In the Mobile IPv4 test cases, the extension is optional. Check the MN-NAI Extension box to include the extension in registration messages.

Range: N/A

Default: N/A

Tcl Parameters:

Related Measurements

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).

The number of bytes to use in the CHAP challenge.

Range: 4 — 255

Default: 4

Tcl Parameters:

Select this parameter to support Device ID extension in the R3 MIP Registration Request (MIP RRQ) that holds the MSID/MAC address.

Tcl Parameter: MipDeviceIdExtensionEnable

Tcl Parameter: PiMipDeviceIdExtensionEnable

When a test case supports the MIP Revocation test activity, you can include the Revocation Support Extension (RSE) in Registration Request messages sent by an FA node, or in Registration Reply messages sent by an HA node, by checking this box. This allows revocations to be processed before the session has been completely established. (RFC3543)

Tcl Parameter: MipRseFladEnabler

Tcl Parameter: PiMipRseFladEnabler

In CDMA WiMAX Convergence testing, select the Access technology Type Extension checkbox to include it in the MIP Registration Requests. This is mainly to support Session Loading with Mobility.

Use the Inform Mobile Node checkbox to allow the CSN to be involved in determining whether the mobile node should be informed of the revocation.  When the box is cleared, the FA determines, based on its own provisioning, whether the mobile node should be informed of the revocation.

Tcl Parameter: MipIBitEnable

Tcl Parameter: PiMipIBitEnable

Use the AAA Authentication checkbox to specify Authentication, Authorization, and Accounting values for the mobile node.  Use the MIP Authentication parameters to configure the SPI, Secret, and Algorithm for the authentication extensions in the RRQ message. When a type of authentication is optional, a checkbox is presented that allows you to include or exclude that type of authentication. The following types of authentication are used with MIP:

• MN-AAA-SPI

• MN-AAA-Secret

• AAA Authentication Algorithm

• HMAC Authentication

Tcl Parameter: MobileNodeAAAAuthEnabler

Tcl Parameter: PiMobileNodeAAAAuthEnabler

The Security Parameter Index identifies a security context between two peers.

Range: N/A

Default: 1000 (0 255 are reserved)

Tcl Parameter: MipAaaSpi

Tcl Parameter: PiMipAaaSpi

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)

Range: N/A

Default: secret

Tcl Parameter: MipAaaSecret

Tcl Parameter: PiMipAaaSecret

The encryption algorithm specified in the extension. These options vary by test case.

• MN-HA Authentication

Options: MD5 Authentication or HMAC Authentication

Default: MD5 Authentication

• MN-AAA Authentication

Options: HMAC Authentication or Radius AAA Authentication

Default: Radius AAA Authentication

• MN-FA Authentication

Options: MD5 Authentication or HMAC Authentication

Default: MD5 Authentication

• Foreign-Home Authentication

Options: MD5 Authentication or HMAC Authentication

Default: MD5 Authentication

Tcl Parameter: MipAaaAuthType

Tcl Parameter: PiMipAaaAuthType

Use the HMAC Authentication method to Hash Message Authentication Code (HMAC), a type of authentication using a cryptographic hash.

Use the Mobile Home Authentication checkbox to authenticate a Home Agent.  A Home Agent is a routing device located on the local network of the mobile access router. It provides physical connection for the mobile networks. The Home Agent associates the home IP address of the mobile access router with the address of its current location on a remote network, known as its care-of address.

The home agent tracks the location of the mobile access router roams so that the user does not need to reinitialize applications.  The Home Agent also stores addresses in its routing table of the locations where the mobile access router travels. The HA emulator simulates a Home Agent when an HA SUT is not used. The following types of mobile home authentication are used with MIP:

• MN-HA SPI

• MN-HA Secret

• HA Authentication Algorithm

Tcl Parameter: MobileHomeAuthEnabler

Tcl Parameter: PiMobileHomeAuthEnabler

The Security Parameter Index identifies a security context between two Home Agent peers.

Range: N/A

Default: 1000 (0 255 are reserved)

Tcl Parameter: MipHaSpi

Tcl Parameter: PiMipHaSpi

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)

Range: N/A

Default: secret

Tcl Parameter: MipHaSecret

Tcl Parameter: PiMipHaSecret

An HA node requires authentication.  Two types of HA authentication are available:

Options: MD5 Authentication or HMAC Authentication

Default: MD5 Authentication

Tcl Parameter: MipHaAuthType

Tcl Parameter: PiMipHaAuthType

A Foreign Agent (FA) is a routing device on a non-local network that supports the mobile access router to indicate the address of its current location on a remote network, known as its care-of address. It functions as the connection point to the mobile access router, acting as a conduit of packets tramsferred from the HA to the mobile access router. The FA is a stationary router with a direct logical connection to the mobile access router. The mobile access router and Foreign Agent do not need to be connected directly by a wireless link. For example, if the mobile access router is roaming, the foreign agent connection with the mobile access router can exist on interfaces that are not on the same subnetwork.  An FA Node requires authentication.  The following types of FA authentication are used with MIP:

• MN-FA SPI

• MN-FA Secret

• FA Authentication Algorithm

The Security Parameter Index identifies a security context between two Foreign Agent peers.

Range: N/A

Default: 1000 (0 255 are reserved)

Tcl Parameter: MipFaSpi

Tcl Parameter: PiMipFaSpi

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)

Range: N/A

Default: secret

Tcl Parameter: MipFaSecret

Tcl Parameter: PiMipFaSecret

A FA node requires authentication.  Two types of FA authentication are available:

Options: MD5 Authentication or HMAC Authentication

Default: MD5 Authentication

  Two types of authentication are available:

Options: MD5 Authentication or HMAC Authentication

Default: MD5 Authentication

Tcl Parameter: MipFaAuthType

Tcl Parameter: PiMipFaAuthType

Devices emulating a FA and HA Node requires authentication.  The following types of FA-HA authentication are used with MIP:

• FA-HA SPI

• FA-HA Secret

• FA-HA Authentication Algorithm

Tcl Parameter: ForeignHomeAuthEnabler

Tcl Parameter: PiForeignHomeAuthEnabler

The Security Parameter Index identifies a security context between a Foreign Agent and Home Agent.

Range: N/A

Default: 1000 (0 255 are reserved)

Tcl Parameter: MipFaHaSpi

Tcl Parameter: PiMipFaHaSpi

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)

Range: N/A

Default: secret

Tcl Parameter: MipFaHaSecret

Tcl Parameter: PiMipFaHaSecret

A FA node requires authentication.  Two types of FA authentication are available:

Options: MD5 Authentication or HMAC Authentication

Default: MD5 Authentication

  Two types of authentication are available:

Options: MD5 Authentication or HMAC Authentication

Default: MD5 Authentication

Tcl Parameter: MipFaHaAuthType

Tcl Parameter: PiMipFaHaAuthType

The Calling Station ID in MIP RRQ is used by the PDSN/FA to send the subscriber's IMSI to HA (transfer the user information to the HA).  

Tcl Parameter: MipCallingIdExtEn

Tcl Parameter: PiMipCallingIdExtEn

Value: True/False

• Vendor ID: The application's vendor-specific ID or enterprise code, used in the MIP RRQ.

Tcl Parameter: MipCallingExtVendorId

Tcl Parameter: PiMipCallingExtVendorId

• Vendor NVSE Type: Indicates vendor specific  type of NVSE. When a vendor NVSE is not recognized, the extension is ignored.

Tcl Parameter: MipCallingExtNvseType

Tcl Parameter: PiMipCallingExtNvseType

• Calling Station ID: Indicates the Calling Station ID sent to the HA.

Tcl Parameter: MipCallingExtId

Tcl Parameter: PiMipCallingExtId

The Correlation ID in MIP RRQ is used by the PDSN/FA to send current PPP session Correlation ID to the HA. See RFC 3115.

Tcl Parameter: MipCorrelIdExtEn

Tcl Parameter: PiMipCorrelIdExtEn

Value: True/False

• Vendor ID: The application's vendor-specific ID or enterprise code, used in the MIP RRQ.

Tcl Parameter: MipCorrelExtVendorId

Tcl Parameter: PiMipCorrelExtVendorId

• Vendor NVSE Type: Indicates vendor specific  type of NVSE. When a vendor NVSE is not recognized, the extension is ignored.

Tcl Parameter: MipCorrelExtNvseType

Tcl Parameter: PiMipCorrelExtNvseType

• Correlation ID: Indicates the current PPP session Correlation ID sent to the HA.

Tcl Parameter: MipCorrelExtId

Tcl Parameter: PiMipCorrelExtId

Use the WiMAX Support checkbox to enable or disable the WiMAX settings and enter the key values for generation and distribution to perform operations within trusted boundaries.

Tcl Parameter: MipWimaxEn

MIP Root Key

Enter the MIP root key for generation and distribution.

Range : A maximum of 64 bytes (128 hex characters excluding 0x)

Default: 0X

Tcl Parameter: WimaxMipMrk

HA Root Key

Enter the HA root key for generation and distribution.

Range : A maximum of 64 bytes (128 hex characters excluding 0x)

Default: 0X

Select and a valid IPv4 or IPv6 address.

Tcl Parameter:

Select to apply a Test Data file.

• See Applying TDF ParametersApplying TDF Parameters

  See Test Data Files for further explanation and sample files. If a sample is not found for the specific TDF, you can obtain a sample file from your Technical Support representative. You may also use the following options to select an existing TDF or create/edit TDF-CSV files (TDF-CSV Editor). 

  For most TDF Parameters used for Applying Parameters, each row in the file is the overridden value for a different “Session”, aka a different UE. But some TDFs are done in other dimensions, like Bearers, eNodeBs, Subscribers (2 per UE sometimes) or even Hosts, etc. Tooltips on the TDF Parameter: 

  

  Note that the “ID” is a unique ID. Please Provide the ID when reporting issues with a TDF. For TDFs that do not apply / override Parameters, but instead are just their own configuration or data or media files you won’t see TDF ID row details.

  TIP: When including large files, please be aware of memory limitations, since the TDF Editor shares memory with the Client.

  NOTE: The available TDF options vary. on the L3-7 | IPSec tab > IKE with RSA Settings you may only select the Certificate TDF from TAS (these are non-CSV TDFs). In addition, where applicable, any rules for defining TDFs are included in specific Test Cases. (For example, In MME Node test case, see MME Node - Provisioning TDF.) From the DMF Window, press Shift+Alt+A to display the  Save DMF as Tcl window. Click the Save to File button to save as Tcl file. See additional details on Using the Tcl API.

  Select/Create a new TDF-CSV	Allows you to create a new TDF by entering a file name that doesn’t already exist or select an existing file by entering a file name that already exists. Click to open the Select Existing or Create window. Navigate to the relevant library/folder, Enter the name of the file: If the file name already exists, the file is selected and applied in the test case. If the file name does not exist, a message displays that says you are creating a new TDF and the embedded TDF-CSV will be launched. Click Yes to launch the TDF-CSV Editor and create/save the new TDF-CSV. Click No to select a different file NOTE: If you do not have permission to save in the selected library, an error displays when you try to create a new file. TIP: You may also navigate to the relevant library/folder and select file, and click OK.
  Upload a New TDF to TAS	Click to import a new TDF file from your local folder and select in the test Case (instead of having to go to TDF Admin). Navigate to the file on your local folder and select. Then navigate to the location (library) where you want to save it on the TAS. You may rename the file, if required.
  View Edit Selected TDF in TDF-CSV Editor	Available only when you have selected a TDF on TAS. Click to open the selected file in TDF-CSV Editor (in place, that is, within the Test Case). Edit the file and save. You may also click Save As to save the edited TDF-CSV to a different library and also rename the file, if required. NOTE: You may also select a TDF from a library to which you do not have write permissions, edit the file as required, and save (Save As) only to a different library with the same file name or a different name. The only options available are Save As and Cancel.
  Open Selected TDF in Standalone TDF-CSV Editor	Available only when you have selected a TDF on TAS. Select to retrieve the CSV file and open it in the stand alone TDF-CSV Editor.
  Generate Stub TDF-CSV	TIP: Available only when a CSV specification has been defined for in the Test Case for the TDF widget ( View TDF Actions/Options Menu)   Opens an example context specific test data parametersexample context specific test data parameters, which you may save as a .CSV file or open in the TDF-CSV Editor.
  Launch Standalone TDF-CSV Editor	Click to open a blank TDF-CSV Editor. The Launch Standalone TDF-CSV editor options handles very large TDFs that may use too much Client memory if opened within the Test Case/in the embedded editor.  You may set the standalone TDF-CSV Editor memory high to edit large TDFs.

   

Tcl Parameter: MipCfgFileEn

Tcl Parameter: PiMipCfgFileEn

• MIP_config_datafile.csv

• MIP_config_file.csv

When DMU is supported by the SUTs in an End-to-End Mobile IP test, use the following parameters to define the MIP Key Data payload according to the provisioning on the HA SUT and the home AAA server. You can provision unique AAA Secret, HA Secret, and Chap Secret values for each MN  by using the Auto-Increment format.

• Learn more about DMU

The decrypted MN-AAA key.

Range:  N/A  

Default: secret

Tcl Parameter: MipAaaSecret2

Tcl Parameter: PiMipAaaSecret2

The decrypted MN-AAA key.

Range:  N/A  

Default: secret

Tcl Parameter: MipHaSecret2

Tcl Parameter: PiMipHaSecret2

The Mobile Subscriber ID.

Range:  N/A  

Default: msid12345678901

Tcl Parameter: MipMsid

Tcl Parameter: PiMipMsid

The decrypted Simple IP CHAP key.

Range:  N/A  

Default: secret

Tcl Parameter: MipChapSecret

Tcl Parameter: PiMipChapSecret

The authenticator that will be received from the home AAA server.

Range:  0 — 18446744073709551615 (0x0 — 0xFFFFFFFFFFFFFFFF) when Vendor Variant = None or

Range:  0x0 — 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF) when Vendor Variant = AuthenticatorExt (Only Hex allowed)

Default: 12345678 when Vendor Variant = None or

Default: 0x12345678 when Vendor Variant = AuthenticatorExt

Tcl Parameter: MipAaaAuth

Tcl Parameter: PiMipAaaAuth

Vendor Variant is used to affect the range of AAA Authenticator and MN Authenticator. If AuthenticatorExt is selected, the AAA Authenticator and MN Authenticator fields are extended to 16 bytes and only accept Hex number with 0x prefix.

Options:  None (default), AuthenticatorExt

Tcl Parameter: DmuVendorVariant

The authenticator that will be sent from the MN to the home AAA server.

Range:  0 — 16777215 (0x0 — 0xFFFFFF)  when Vendor Variant = None or

Range:  0x0 — 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF) when Vendor Variant = AuthenticatorExt (Only Hex allowed)

Default: 123456 when Vendor Variant = None or

Default: 0x123456 when Vendor Variant = AuthenticatorExt

Tcl Parameter: MipMnAuth

Tcl Parameter: PiMipMnAuth