During IKE Phase I, the IPSec peers authenticate each other and negotiate the IKE SA that will protect the keying material exchanged during IKE Phase II. If you selected IKE With Pre-Shared Keys or IKE With RSA Signature for the test's IKE mode, you can configure the credentials, algorithms, and methods used during IKE Phase I with the parameters described in this topic. With Pre-Provisioned mode, you configure the algorithms and keys described in IPSec Algorithms and Keys.
The topics listed under Related Parameters describe general IPSec test support settings, the settings used during Phase II, and the settings that determine how traffic is routed when multiple tunnels are used.
Use the drop-down list to select the mode used for IKE Phase I when IKEv1 is used. Aggressive mode is faster but less secure; Main mode is more secure but requires more processing. Options:
Default: Aggressive Tcl Parameters: DataIkeMasterType
|
||||
|
Authentication Credentials Two types of credentials are presented for authentication: peer credentials that identify an individual peer and IPSec credentials that identify a peer as a member of a trusted group. Peer credentials are defined by Identification Type, are typically unique to one peer, and consist of an IP address or FQDN. The IPSec credentials used depend on the IKE mode you selected — pre-shared key or RSA signature — and may be common to many peers. |
|||
Use the drop-down list to select the type of peer credentials that are used for authentication.
Tcl Parameter: DataIpSecIdType Options:
Tcl Parameter: DataDistinguishedName
Host/User Name Range: N/A Default: MN# Tcl Parameter: DataMobileNodeHostName Domain Name
Range: N/A Default: HomeAgent.net Tcl Parameter: DataHaDomainName
Default: Local IP Address MIPv6 TestingMN Host Name and MN Domain Name are always required regardless of the type of credentials selected. |
||||
The key, known to both peers, that is used during IKE Phase I authentication when IKE With Pre-Shared Keys is selected. Range: N/A Default: 0 Tcl Parameter: DataPreSharedKey |
||||
IKE With RSA Signature Options |
||||
When IKEv2 is used, the local peer can also support EAP authentication. Use the checkbox to enable EAP and click the EAP Settings.. button to open the settings window. Tcl Parameter: DataAsnEapEn
|
||||
SA Lifetime Value |
You can define the IKE SA lifetime Type / Value requested during IKE Phase I. The test will attempt to refresh the SA with the peer prior to expiration of the lifetime. A different lifetime can be requested for the IPSec SA during IKE Phase II. SA Lifetime TypeUse the drop-down list to select the way in which the lifetime will be measured. Options: Seconds or Kilobytes Default: Seconds Tcl Parameter: BsAsnSaLifeDurType SA Lifetime ValueThe maximum lifetime in seconds or kilobytes. Range: N/A Default: 28800 Tcl Parameter: DataSaLifeDur
|
|||
Select to enable reestablishment of IPSec session after tunnel deletion. Tcl Parameter: DataReestablishIpsecTunnelEn |
||||
Only available in the Network Host test case. Used to send Delete Request for established IPSec session after timer expires. Range : 0 to 65535 Default: 0 Tcl Parameter: DataSendDeleteInformationalMsgInterval |
||||
Disable Child SA Delete Messages on shutdown is available for IKE With Pre-Shared Keys and IKE With RSA Signature for IKE V1 and V2. Select Disable Child SA Delete Messages on shutdown to ensure that the Child SA is not deleted at the end of test. The default, not selecting the parameter deletes Child SA and IKE SA. Default: Disabled Value: 0 (disable) / 1 (enable) Default: 0 (disabled) Tcl Parameter: DisableSendDelIpsecMsgEn |
||||
Ignore Timeout on Rekey Delete Response is available for IKE With Pre-Shared Keys and IKE With RSA Signature only for IKE V2. Select Ignore Timeout on Rekey Delete Response to support client initiated rekey attempts. (Selecting this parameter ensures that the new SA is up when the request acknowledgement is sent and the rekey is complete. That is, Landslide ignores the Informational Delete response from SecGW in phase1 rekey process). Not selecting Ignore Timeout on Rekey Delete Response ensures that no subsequent rekey occurs after the 1st rekey attempt by the client, and a IKE Phase 1 timeout message is logged. I then enabled the "Ignore Timeout on Rekey Delete Response" chdckbox and re-ran the test. I verified that the client initiated rekey attempts worked and that the error OM was no longer pegged. Default: disabled Value: 0 (disable) / 1 (enable) Default: 0 (disabled) Tcl Parameter: IgnoreTimeoutRekeyDelRespEn
|
||||
The Inspect Rekey Packet only needed for IKEv2. Select the Inspect Rekey Packet checkbox to allow the encrypted IKEv2 payload to be inspected before determining the packet's destination. Default: disabled Value: 0 (disable) / 1 (enable) Tcl Parameter: DataInspectPacketEn
|
||||
This is applicable for IKE Version 1 only. Select when you would like to receive initial notification from the dropdown list: Following Phase 1 Negotiation or During Phase 1 Negotiation. Tcl Parameter: DataIpsecInitialContactNotification
|
||||
This is applicable for IKE Version 2 only. Select the checkbox when you would like to receive/initiate contact notification from the dropdown list: "SA_INIT" or "SA_Auth"
Tcl Parameter: DataIkev2InitContactNotification
|