ASA IKEv2 Debugs for Remote Access VPN Troubleshooting

Server Message Description

Debugs

Client Message Description

Date        : 04/23/2013
Time        : 16:24:55
Type        : Information
Source      : acvpnui

Description : Function: ClientIfcBase::connect
File: .\ClientIfcBase.cpp
Line: 964
A VPN connection to Anu-IKEV2 has been requested by the user.

****************************************
Date        : 04/23/2013
Time        : 16:24:55
Type        : Information
Source      : acvpnui

Description : Message type information sent to the user:
Contacting Anu-IKEV2.
****************************************
Date        : 04/23/2013
Time        : 16:24:55
Type        : Information
Source      : acvpnui

Description : Function: ApiCert::getCertList
File: .\ApiCert.cpp
Line: 259
Number of certificates found: 0
****************************************
Date        : 04/23/2013
Time        : 16:25:00
Type        : Information
Source      : acvpnui

Description : Initiating VPN connection to the secure gateway https://10.0.0.1/ASA-IKEV2
****************************************
Date        : 04/23/2013
Time        : 16:25:00
Type        : Information
Source      : acvpnagent

Description : Tunnel initiated by GUI Client.

****************************************

Date        : 04/23/2013
Time        : 16:25:02
Type        : Information
Source      : acvpnagent

Description : Function: CIPsecProtocol::connectTransport
File: .\IPsecProtocol.cpp
Line: 1629
Opened IKE socket from 192.168.1.1:25170 to 10.0.0.1:500
****************************************

The ASA receives the IKE_SA_INIT message from the client.

IKEv2-PLAT-4: RECV PKT [IKE_SA_INIT] [192.168.1.1]:25170->[10.0.0.1]:500 InitSPI=0x58aff71141ba436b RespSPI=0x0000000000000000 MID=00000000

IKEv2-PROTO-3: Rx [L 10.0.0.1:500/R 192.168.1.1:25170/VRF i0:f0] m_id: 0x0

The first pair of messages is the IKE_SA_INIT exchange. These messages negotiate cryptographic algorithms, exchange nonces, and do a Diffie-Hellman (DH) exchange.

The IKE_SA_INIT message received from the client contains these fields:

1. ISAKMP Header - SPI/version/flags.
2. SAi1 - Cryptographic algorithm that IKE initiator supports.
3. KEi - DH public key value of the initiator.
4. N - Initiator Nonce.

The ASA verifies and processes the
IKE_INIT message. The ASA:

1. Chooses the crypto suite from
   those offered by the initiator.
2. Computes its own DH secret key.
3. Computes a SKEYID value from
   which all keys can be derived for
   this IKE_SA. The headers of all
   subsequent messages are
   encrypted and authenticated. The
   keys used for the encryption and
   integrity protection are derived
   from SKEYID and are known as:
   
   
   1. SK_e - Encryption.
   2. SK_a - Authentication.
   3. SK_d - Derived and used
      for derivation of further
      keying material for
      CHILD_SAs.
   A separate SK_e and SK_a are
   computed for each direction.

Relevant Configuration:

crypto ikev2 policy 10
 encryption aes-192 integrity 
 sha group 2  prf sha lifetime 
 seconds 86400
crypto ikev2 enable outside

The ASA constructs the response message for IKE_SA_INIT exchange.

This packet contains:

1. ISAKMP Header - SPI/version/flags.
2. SAr1 - Cryptographic algorithm that IKE responder chooses.
3. KEr - DH public key value of the responder.
4. N - Responder Nonce.

The client shows the IPSec tunnel as 'initiating.'

Date        : 04/23/2013
Time        : 16:25:02
Type        : Information
Source      : acvpnagent

Description : Function: ikev2_log
File: .\ikev2_anyconnect_osal.cpp
Line: 2730
Received request to establish an IPsec tunnel; local traffic selector = Address Range: 0.0.0.0-255.255.255.255 Protocol: 0 Port Range: 0-65535 ; remote traffic selector = Address Range: 0.0.0.0-255.255.255.255 Protocol: 0 Port Range: 0-65535
****************************************
Date        : 04/23/2013
Time        : 16:25:02
Type        : Information
Source      : acvpnagent

Description : Function: CIPsecProtocol::connectTransport
File: .\IPsecProtocol.cpp
Line: 1629
Opened IKE socket from 192.168.1.1:25171 to 10.0.0.1:4500
****************************************

Authentication is done with EAP. Only a single EAP authentication method is allowed within an EAP conversation. The ASA receives the IKE_AUTH message from the client.

IKEv2-PLAT-4: RECV PKT [IKE_AUTH] [192.168.1.1]:25171->[10.0.0.1]:4500 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000001

IKEv2-PROTO-3: Rx [L 10.0.0.1:4500/R 192.168.1.1:25171/VRF i0:f0] m_id: 0x1

When the client includes an IDi payload
but not an AUTH payload, this indicates
the client has declared an identity but has
not proven it. In the debugs, the AUTH
payload is not present in the IKE_AUTH
packet sent by the client. The client
sends the AUTH payload only after the
EAP exchange is successful. If the ASA
is willing to use an extensible
authentication method, it places an EAP
payload in message 4 and defers sending
SAr2, TSi, and TSr until the initiator
authentication is complete in a
subsequent IKE_AUTH exchange.

The IKE_AUTH initiator packet contains:

1. ISAKMP Header -
   SPI/version/flags.
2. IDi - The tunnel-group name that
   the client wishes to connect to
   may be delivered by the IDi
   payload of type ID_KEY_ID in
   the initial message of the
   IKE_AUTH exchange. This
   occurs when the client profile* is
   preconfigured with a group name
   or, after a previous successful
   authentication, the client has
   cached the group name in its
   preferences file. The ASA
   attempts to match a tunnel-group
   name with the contents of the IKE
   IDi payload. After the first
   successful IPSec VPN is
   established, the client caches the
   group name (group alias) to which
   the user authenticated. This group
   name is delivered in the IDi
   payload of the next connection
   attempt in order to indicate the
   probable group desired by the
   user. When EAP authentication is
   specified or implied by the client
   profile and the profile does not
   contain the <IKEIdentity>
   element, the client sends an
   ID_GROUP type IDi payload
   with the fixed string
   *$AnyConnectClient$*.
   
3. CERTREQ - The client is
   requesting the ASA for a
   preferred certificate. Certificate
   request payloads may be included
   in an exchange when the sender
   needs to get the certificate of the
   receiver. The certificate request
   payload is processed by
   inspection of the 'Cert encoding'
   field in order to determine
   whether the processor has any
   certificates of this type. If so, the
   'Certification Authority' field is
   inspected in order to determine if
   the processor has any certificates
   that can be validated up to one of
   the specified certification
   authorities. This can be a chain of
   certificates.
   
4. CFG - CFG_REQUEST/
   CFG_REPLY allows an IKE
   endpoint to request information
   from its peer. If an attribute in the
   CFG_REQUEST configuration
   payload is not zero-length, it is
   taken as a suggestion for that
   attribute.The CFG_REPLY
   configuration payload may return
   that value or a new one. It may
   also add new attributes and not
   include some requested ones.
   Requestors ignore returned
   attributes that they do not
   recognize. In these debugs, the
   client is requesting the tunnel
   configuration in the
   CFG_REQUEST. The ASA
   replies to this and sends the tunnel
   configuration attributes only after
   the EAP exchange is successful.
   
5. SAi2 - SAi2 initiates the SA,
   which is similar to the phase 2
   transform set exchange in IKEv1.
   
6. TSi and TSr - The initiator and
   responder traffic selectors
   contain, respectively, the source
   and destination address of the
   initiator and responder in order to
   forward and receive encrypted
   traffic. The address range
   specifies that all traffic to and from
   that range is tunneled. If the
   proposal is acceptable to the
   responder, it sends identical TS
   payloads back.

The attributes the client must deliver for
group authentication are stored in an
AnyConnect profile file.

*Relevant Profile Configuration:

<ServerList>
<HostEntry>
  <HostName>Anu-IKEV2
  </HostName>
  <HostAddress>10.0.0.1
  </HostAddress>
  <UserGroup>ASA-IKEV2
  </UserGroup>
<PrimaryProtocol>IPsec
</PrimaryProtocol>
</HostEntry>
</ServerList>

The ASA generates a response to the IKE_AUTH message and prepares to authenticate itself to the client.

Decrypted packet:Data&colon; 540 bytes
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_RECV_AUTH
IKEv2-PROTO-3: (6): Stopping timer to wait for auth message
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_CHK_NAT_T
IKEv2-PROTO-3: (6): Check NAT discovery
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_CHG_NAT_T_PORT
IKEv2-PROTO-2: (6): NAT detected float to init port 25171, resp port 4500
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_PROC_ID
IKEv2-PROTO-2: (6): Recieved valid parameteres in process id
IKEv2-PLAT-3: (6) peer auth method set to: 0
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_CHK_IF_PEER_CERT_NEEDS_TO_BE_FETCHED_FOR_PROF_SEL
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_GET_POLICY_BY_PEERID
IKEv2-PROTO-3: (6): Getting configured policies
IKEv2-PLAT-3: New AnyConnect Client connection detected based on ID payload
IKEv2-PLAT-3: my_auth_method = 1
IKEv2-PLAT-3: (6) peer auth method set to: 256
IKEv2-PLAT-3: supported_peers_auth_method = 16
IKEv2-PLAT-3: (6) tp_name set to: Anu-ikev2
IKEv2-PLAT-3: trust point set to: Anu-ikev2
IKEv2-PLAT-3: P1 ID = 0
IKEv2-PLAT-3: Translating IKE_ID_AUTO to = 9
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_SET_POLICY
IKEv2-PROTO-3: (6): Setting configured policies
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_VERIFY_POLICY_BY_PEERID
IKEv2-PROTO-3: (6): Verify peer's policy
IKEv2-PROTO-3: (6): Matching certificate found
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_CHK_CONFIG_MODE
IKEv2-PROTO-3: (6): Received valid config mode data
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_SET_RECD_CONFIG_MODE
IKEv2-PLAT-3: (6) DHCP hostname for DDNS is set to: winxp64template
IKEv2-PROTO-3: (6): Set received config mode data
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_CHK_AUTH4EAP
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_WAIT_AUTH Event: EV_CHK_EAP
IKEv2-PROTO-3: (6): Check for EAP exchange
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_BLD_AUTH Event: EV_GEN_AUTH
IKEv2-PROTO-3: (6): Generate my authentication data
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_BLD_AUTH Event: EV_CHK4_SIGN
IKEv2-PROTO-3: (6): Get my authentication method
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_BLD_AUTH Event: EV_SIGN
IKEv2-PROTO-3: (6): Sign auth data
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_BLD_AUTH Event: EV_OK_AUTH_GEN
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_BLD_EAP_AUTH_REQ Event: EV_AUTHEN_REQ
IKEv2-PROTO-2: (6): Asking the authenticator to send EAP request

Created element name config-auth value
Added attribute name client value vpn to element config-auth
Added attribute name type value hello to element config-auth
Created element name version value 9.0(2)8
Added element name version value 9.0(2)8 to element config-auth
Added attribute name who value sg to element version
Generated XML message below
<?xml version="1.0" encoding="UTF-8"?>
<config-auth client="vpn" type="hello">
<version who="sg">9.0(2)8</version>
</config-auth>

IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_BLD_EAP_AUTH_REQ Event: EV_RECV_EAP_AUTH
IKEv2-PROTO-5: (6): Action: Action_Null
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_BLD_EAP_AUTH_REQ Event: EV_CHK_REDIRECT
IKEv2-PROTO-3: (6): Redirect check with platform for load-balancing
IKEv2-PLAT-3: Redirect check on platform
IKEv2-PLAT-3: ikev2_osal_redirect: Session accepted by 10.0.0.1
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000001 CurState: R_BLD_EAP_AUTH_REQ Event: EV_SEND_EAP_AUTH_REQ
IKEv2-PROTO-2: (6): Sending EAP request
IKEv2-PROTO-5: Construct Vendor Specific Payload: CISCO-GRANITEIKEv2-PROTO-3: (6): Build

The ASA sends the AUTH payload in order to request user credentials from the client. The ASA sends the AUTH method as 'RSA,' so it sends its own certificate to the client, so the client can authenticate the ASA server.

Since the ASA is willing to use an extensible authentication method, it places an EAP payload in message 4 and defers sending SAr2, TSi, and TSr until the initiator authentication is complete in a subsequent IKE_AUTH exchange. Thus, those three payloads are not present in the debugs.

The EAP packet contains:

1. Code: request - This code is sent by the authenticator to the peer.
2. id: 1 - The id helps match the EAP responses with the requests. Here the value is 1, which indicates it is the first packet in the EAP exchange. This EAP request has the 'config-auth' type of 'hello;' it is sent from the ASA to the client in order to initiate the EAP exchange.
3. Length: 150 - Length of the EAP packet includes the code, id, length, and EAP data.
4. EAP data.

Fragmentation can result if the certificates are large or if certificate chains are included. Both initiator and responder KE payloads can also include large keys, which can also contribute to fragmentation.

****************************************
Date        : 04/23/2013
Time        : 16:25:02
Type        : Information
Source      : acvpnagent

Description : Function: ikev2_verify_X509_SIG_certs
File: .\ikev2_anyconnect_osal.cpp
Line: 2077
Requesting certificate acceptance from user
****************************************
Date        : 04/23/2013
Time        : 16:25:02
Type        : Error
Source      : acvpnui

Description : Function: CCapiCertificate::verifyChainPolicy
File: .\Certificates\CapiCertificate.cpp
Line: 2032
Invoked Function: CertVerifyCertificateChainPolicy
Return Code: -2146762487 (0x800B0109)
Description: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
****************************************
Date        : 04/23/2013
Time        : 16:25:04
Type        : Information
Source      : acvpnagent

Description : Function: CEAPMgr::dataRequestCB
File: .\EAPMgr.cpp
Line: 400
EAP proposed type: EAP-ANYCONNECT
****************************************

The client responds to the EAP request with a response.

The EAP packet contains:

1. Code: response - This code is sent by the peer to the authenticator in response to the EAP request.
2. id: 1 - The id helps match the EAP responses with the requests. Here the value is 1, which indicates that this is a response to the request previously sent by the ASA (authenticator). This EAP response has the 'config-auth' type of 'init'; the client is initializing the EAP exchange and is waiting for the ASA to generate the authentication request.
3. Length: 252 - Length of the EAP packet includes the code, id, length, and EAP data.
4. EAP data.

The ASA decrypts this response, and the client says that it has received the AUTH payload in the previous packet (with the certificate) and received the first EAP request packet from the ASA. This is what the 'init' EAP response packet contains.

IKEv2-PLAT-4: RECV PKT [IKE_AUTH] [192.168.1.1]:25171->[10.0.0.1]:4500 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000002
IKEv2-PROTO-3: Rx [L 10.0.0.1:4500/R 192.168.1.1:25171/VRF i0:f0] m_id: 0x2
IKEv2-PROTO-3: HDR[i:58AFF71141BA436B - r: FC696330E6B94D7F]
IKEv2-PROTO-4: IKEV2 HDR ispi: 58AFF71141BA436B - rspi: FC696330E6B94D7F
IKEv2-PROTO-4: Next payload: ENCR, version: 2.0
IKEv2-PROTO-4: Exchange type: IKE_AUTH, flags: INITIATOR
IKEv2-PROTO-4: Message id: 0x2, length: 332
IKEv2-PROTO-5: (6): Request has mess_id 2; expected 2 through 2
REAL Decrypted packet:Data: 256 bytes
 EAP  Next payload: NONE, reserved: 0x0, length: 256
    Code: response: id: 1, length: 252
    Type: Unknown - 254
EAP data:247 bytes

Decrypted packet:Data&colon; 332 bytes
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000002 CurState: R_WAIT_EAP_RESP Event: EV_RECV_AUTH
IKEv2-PROTO-3: (6): Stopping timer to wait for auth message
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000002 CurState: R_WAIT_EAP_RESP Event: EV_RECV_EAP_RESP

IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000002 CurState: R_PROC_EAP_RESP Event: EV_PROC_MSG
IKEv2-PROTO-2: (6): Processing EAP response

Received XML message below from the client
<?xml version="1.0" encoding="UTF-8"?>
<config-auth client="vpn" type="init">
<device-id>win</device-id>
<version who="vpn">3.0.1047</version>
<group-select>ASA-IKEV2</group-select>
<group-access>ASA-IKEV2</group-access>
</config-auth>
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000002 CurState: R_PROC_EAP_RESP Event: EV_RECV_EAP_AUTH

IKEv2-PROTO-5: (6): Action: Action_Null
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000002 CurState: R_BLD_EAP_REQ Event: EV_RECV_EAP_REQ

This is the second request sent by the ASA to the client.

The EAP packet contains:

1. Code: request - This code is sent by the authenticator to the peer.
2. id: 2 - The id helps match the EAP responses with the requests. Here the value is 2, which indicates it is the second packet in the exchange. This request has the 'config-auth' type of 'auth-request'; the ASA is requesting that the client send the user authentication credentials.
3. Length: 457 - Length of the EAP packet includes the code, id, length, and EAP data.
4. EAP data.

ENCR payload:

This payload is decrypted, and its contents are parsed as additional payloads.

IKEv2-PROTO-2: (6): Sending EAP request

Generated XML message below
<?xml version="1.0" encoding="UTF-8"?>
<config-auth client="vpn" type="auth-request">
<version who="sg">9.0(2)8</version>
<opaque is-for="sg">
<tunnel-group>ASA-IKEV2</tunnel-group>
<config-hash>1367268141499</config-hash>
</opaque>
<csport>443</csport>
<auth id="main">
<form>
<input type="text" name="username" label="Username:"></input>
<input type="password" name="password" label="Password:"></input>
</form>
</auth>
</config-auth>
IKEv2-PROTO-3: (6): Building packet for encryption; contents are:
 EAP  Next payload: NONE, reserved: 0x0, length: 461
    Code: request: id: 2, length: 457
    Type: Unknown - 254
EAP data: 452 bytes

IKEv2-PROTO-3: Tx [L 10.0.0.1:4500/R 192.168.1.1:25171/VRF i0:f0] m_id: 0x2
IKEv2-PROTO-3: HDR[i:58AFF71141BA436B - r: FC696330E6B94D7F]
IKEv2-PROTO-4: IKEV2 HDR ispi: 58AFF71141BA436B - rspi: FC696330E6B94D7F
IKEv2-PROTO-4: Next payload: ENCR, version: 2.0
IKEv2-PROTO-4: Exchange type: IKE_AUTH, flags: RESPONDER MSG-RESPONSE
IKEv2-PROTO-4: Message id: 0x2, length: 524
 ENCR  Next payload: EAP, reserved: 0x0, length: 496
Encrypted data&colon; 492 bytes

IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000002
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000002 CurState: R_BLD_EAP_REQ Event: EV_START_TMR
IKEv2-PROTO-3: (6): Starting timer to wait for user auth message (120 sec)
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000002 CurState: R_WAIT_EAP_RESP Event: EV_NO_EVENT   

The client requests user authentication and sends it to the ASA as an EAP response in the next packet ('auth-reply').

Client sends another IKE_AUTH initiator message with the EAP payload.

The EAP packet contains:

1. Code: response - This code is sent by the peer to the authenticator in response to the EAP request.
2. id: 2 - The id helps match the EAP responses with the requests. Here the value is 2, which indicates that this is a response to the request previously sent by the ASA (authenticator).
3. Length: 420 - Length of the EAP packet includes the code, id, length, and EAP data.
4. EAP data.

The ASA processes this response. The client had requested that the user enter credentials. This EAP response has the 'config-auth' type of 'auth-reply.' This packet contains the credentials entered by the user.

Decrypted packet:Data: 492 bytes
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000003 CurState: R_WAIT_EAP_RESP Event: EV_RECV_AUTH
IKEv2-PROTO-3: (6): Stopping timer to wait for auth message
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000003 CurState: R_WAIT_EAP_RESP Event: EV_RECV_EAP_RESP
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000003 CurState: R_PROC_EAP_RESP Event: EV_PROC_MSG
IKEv2-PROTO-2: (6): Processing EAP response

Received XML message below from the client
<?xml version="1.0" encoding="UTF-8"?>
<config-auth client="vpn" type="auth-reply">
<device-id>win</device-id>
<version who="vpn">3.0.1047</version>
<session-token></session-token>
<session-id></session-id>
<opaque is-for="sg">
<tunnel-group>ASA-IKEV2</tunnel-group>
<config-hash>1367268141499</config-hash></opaque>
<auth>
<password>cisco123</password>
<username>Anu</username></auth>
</config-auth>
IKEv2-PLAT-1: EAP:Initiated User Authentication
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000003 CurState: R_PROC_EAP_RESP Event: EV_NO_EVENT
IKEv2-PLAT-5: EAP:In AAA callback
Retrieved Server Cert Digest: DACE1C274785F28BA11D64453096BAE294A3172E
IKEv2-PLAT-5: EAP:success in AAA callback
IKEv2-PROTO-3: Received response from authenticator
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000003 CurState: R_PROC_EAP_RESP Event: EV_RECV_EAP_AUTH
IKEv2-PROTO-5: (6): Action: Action_Null

The ASA builds a third EAP request in the exchange.

The EAP packet contains:

1. Code: request - This code is sent by the authenticator to the peer.
2. id: 3 - The id helps match the EAP responses with the requests. Here the value is 3, which indicates it is the third packet in the exchange. This packet has the 'config-auth' type of 'complete'; the ASA has received a reply, and the EAP exchange is complete.
3. Length: 4235 - Length of the EAP packet includes the code, id, length, and EAP data.
4. EAP data.

ENCR payload:

This payload is decrypted, and its contents are parsed as additional payloads.

IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000003 CurState: R_BLD_EAP_REQ Event: EV_RECV_EAP_REQ
IKEv2-PROTO-2: (6): Sending EAP request

Generated XML message below
<?xml version="1.0" encoding="UTF-8"?>
<config-auth client="vpn" type="complete">
<version who="sg">9.0(2)8</version>
<session-id>32768</session-id>
<session-token>18wA0TtGmDxPKPQCJywC7fB7EWLCEgz-ZtjYpAyXx2yJH0H3G3H8t5xpBOx3Ixag</session-token>
<auth id="success">
<message id="0" param1="" param2=""></message>
</auth>

IKEv2-PROTO-3: (6): Building packet for encryption; contents are:
 EAP  Next payload: NONE, reserved: 0x0, length: 4239
    Code: request: id: 3, length: 4235
    Type: Unknown - 254
EAP data: 4230 bytes

IKEv2-PROTO-3: Tx [L 10.0.0.1:4500/R 192.168.1.1:25171/VRF i0:f0] m_id: 0x3
IKEv2-PROTO-3: HDR[i:58AFF71141BA436B - r: FC696330E6B94D7F]
IKEv2-PROTO-4: IKEV2 HDR ispi: 58AFF71141BA436B - rspi: FC696330E6B94D7F
IKEv2-PROTO-4: Next payload: ENCR, version: 2.0
IKEv2-PROTO-4: Exchange type: IKE_AUTH, flags: RESPONDER MSG-RESPONSE
IKEv2-PROTO-4: Message id: 0x3, length: 4300
 ENCR  Next payload: EAP, reserved: 0x0, length: 4272
Encrypted data&colon;4268 bytes

IKEv2-PROTO-5: (6): Fragmenting packet, Fragment MTU: 544, Number of fragments: 9, Fragment ID: 2
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000003
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000003 CurState: R_BLD_EAP_REQ Event: EV_START_TMR
IKEv2-PROTO-3: (6): Starting timer to wait for user auth message (120 sec)
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000003 CurState: R_WAIT_EAP_RESP Event: EV_NO_EVENT

The client sends the initiator packet with the EAP payload.

The EAP packet contains:

1. Code: response - This code is sent by the peer to the authenticator in response to the EAP request.
2. id: 3 - The id helps match the EAP responses with the requests. Here the value is 3, which indicates that this is a response to the request previously sent by the ASA (authenticator). The ASA now receives the response packet from the client, which has the 'config-auth' type of 'ack'; this response acknowledges the EAP 'complete' message sent previously by the ASA .
3. Length: 173 - Length of the EAP packet includes the code, id, length, and EAP data.
4. EAP data.

The ASA processes this packet. The
EAP exchange is successful. The ASA
prepares to send the tunnel-group
configuration in the next packet, which
was previously requested by the client in
the IDi payload. The ASA receives the
response packet from the client, which
has the 'config-auth' type of 'ack'. This
response acknowledges the EAP
'complete' message that was sent by the
ASA previously.

Relevant Configuration:

tunnel-group ASA-IKEV2 
 type remote-access
tunnel-group ASA-IKEV2 
 general-attributes
 address-pool webvpn1
 authorization-server-group 
 LOCAL default-group-policy 
  ASA-IKEV2
tunnel-group ASA-IKEV2
 webvpn-attributes
 group-alias ASA-IKEV2 
 enable

The EAP exchange is now successful.

The EAP packet contains:

1. Code: success - This code is
   sent by the authenticator to the
   peer after completion of an EAP
   authentication method. This
   indicates that the peer has
   authenticated successfully to the
   authenticator.
2. id: 3 - The id helps match the
   EAP responses with the requests.
   Here the value is 3, which
   indicates that this is a response to
   the request previously sent by the
   ASA (authenticator). The third set
   of packets in the exchange was
   successful, and the EAP exchange
   is successful.
3. Length: 4 - Length of the EAP
   packet includes the code, id,
   length, and EAP data.
4. EAP data.

Decrypted packet:Data:252 bytes
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000004 CurState: R_WAIT_EAP_RESP Event: EV_RECV_AUTH
IKEv2-PROTO-3: (6): Stopping timer to wait for auth message
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000004 CurState: R_WAIT_EAP_RESP Event: EV_RECV_EAP_RESP
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000004 CurState: R_PROC_EAP_RESP Event: EV_PROC_MSG
IKEv2-PROTO-2: (6): Processing EAP response

Received XML message below from the client
<?xml version="1.0" encoding="UTF-8"?>
<config-auth client="vpn" type="ack">
<device-id>win</device-id>
<version who="vpn">3.0.1047</version>
</config-auth>

IKEv2-PLAT-3: (6) aggrAuthHdl set to 0x2000
IKEv2-PLAT-3: (6) tg_name set to: ASA-IKEV2
IKEv2-PLAT-3: (6) tunn grp type set to: RA
IKEv2-PLAT-1: EAP:Authentication successful
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000004 CurState: R_PROC_EAP_RESP Event: EV_RECV_EAP_SUCCESS
IKEv2-PROTO-2: (6): Sending EAP status message
IKEv2-PROTO-3: (6): Building packet for encryption; contents are:
 EAP  Next payload: NONE, reserved: 0x0, length: 8
    Code: success: id: 3, length: 4

IKEv2-PROTO-3: Tx [L 10.0.0.1:4500/R 192.168.1.1:25171/VRF i0:f0] m_id: 0x4
IKEv2-PROTO-3: HDR[i:58AFF71141BA436B - r: FC696330E6B94D7F]
IKEv2-PROTO-4: IKEV2 HDR ispi: 58AFF71141BA436B - rspi: FC696330E6B94D7F
IKEv2-PROTO-4: Next payload: ENCR, version: 2.0
IKEv2-PROTO-4: Exchange type: IKE_AUTH, flags: RESPONDER MSG-RESPONSE
IKEv2-PROTO-4: Message id: 0x4, length: 76
 ENCR  Next payload: EAP, reserved: 0x0, length: 48
Encrypted data&colon;44 bytes

IKEv2-PLAT-4: SENT PKT [IKE_AUTH] [10.0.0.1]:4500->[192.168.1.1]:25171 InitSPI=0x58aff71141ba436b RespSPI=0xfc696330e6b94d7f MID=00000004

IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000004 CurState: R_PROC_EAP_RESP Event: EV_START_TMR
IKEv2-PROTO-3: (6): Starting timer to wait for auth message (30 sec)
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000004 CurState: R_WAIT_EAP_AUTH_VERIFY Event: EV_NO_EVENT

When EAP authentication is specified or
implied by the client profile and the
profile does not contain the
<IKEIdentity> element, the client sends
an ID_GROUP type IDi payload with
the fixed string *$AnyConnectClient$*.

The ASA processes this message.

Relevant Configuration:

crypto dynamic-map dynmap 1000 
 set ikev2 ipsec-proposal 3des
crypto map crymap 10000 
 ipsec-isakmp dynamic dynmap
crypto map crymap interface 
 outside

Decrypted packet:Data: 92 bytes
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_WAIT_EAP_AUTH_VERIFY Event: EV_RECV_AUTH
IKEv2-PROTO-3: (6): Stopping timer to wait for auth message
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_GET_EAP_KEY
IKEv2-PROTO-2: (6): Send AUTH, to verify peer after EAP exchange
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_VERIFY_AUTH
IKEv2-PROTO-3: (6): Verify authentication data
IKEv2-PROTO-3: (6): Use preshared key for id *$AnyConnectClient$*, key len 20
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_GET_CONFIG_MODE
IKEv2-PLAT-3: Config mode reply queued
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_NO_EVENT
IKEv2-PLAT-3: PSH: client=AnyConnect client-version=3.0.1047 client-os=Windows client-os-version=
IKEv2-PLAT-3: Config mode reply completed
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_OK_GET_CONFIG
IKEv2-PROTO-3: (6): Have config mode data to send
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_CHK4_IC
IKEv2-PROTO-3: (6): Processing initial contact
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_CHK_REDIRECT
IKEv2-PROTO-5: (6): Redirect check is already done for this session, skipping it
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_PROC_SA_TS
IKEv2-PROTO-2: (6): Processing auth message
IKEv2-PLAT-1: Crypto Map: Map dynmap seq 1000. Adjusted selector using assigned IP
IKEv2-PLAT-3: Crypto Map: match on dynamic map dynmap seq 1000
IKEv2-PLAT-3: PFS disabled for RA connection
IKEv2-PROTO-3: (6):
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_NO_EVENT
IKEv2-PLAT-2: Received PFKEY SPI callback for SPI 0x30B848A4, error FALSE
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_VERIFY_AUTH Event: EV_OK_RECD_IPSEC_RESP

IKEv2-PROTO-2: (6): Processing auth message

The ASA builds the IKE_AUTH response message with the SA, TSi, and TSr payloads.

The IKE_AUTH responder packet contains:

1. ISAKMP Header - SPI/version/flags.
2. AUTH payload - With the chosen authentication method.
3. CFG - CFG_REQUEST/ CFG_REPLY allows an IKE endpoint to request information from its peer. If an attribute in the CFG_REQUEST configuration payload is not zero-length, it is taken as a suggestion for that attribute. The CFG_REPLY configuration payload may return that value or a new one. It may also add new attributes and not include some requested ones. Requestors ignore returned attributes that they do not recognize. The ASA replies to the client with the tunnel configuration atrributes in the CFG_REPLY packet.
4. SAr2 - SAr2 initiates the SA, which is similar to the phase 2 transform set exchange in IKEv1.
5. TSi and TSr - The initiator and responder traffic selectors contain, respectively, the source and destination address of the initiator and responder in order to forward and receive encrypted traffic. The address range specifies that all traffic to and from that range is tunneled. If the proposal is acceptable to the responder, it sends identical TS payloads back.

ENCR payload:

This payload is decrypted, and its contents are parsed as additional payloads.

IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_BLD_AUTH Event: EV_MY_AUTH_METHOD
IKEv2-PROTO-3: (6): Get my authentication method
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_BLD_AUTH Event: EV_GET_PRESHR_KEY
IKEv2-PROTO-3: (6): Get peer's preshared key for *$AnyConnectClient$*
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_BLD_AUTH Event: EV_GEN_AUTH
IKEv2-PROTO-3: (6): Generate my authentication data
IKEv2-PROTO-3: (6): Use preshared key for id hostname=ASA-IKEV2, key len 20
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_BLD_AUTH Event: EV_CHK4_SIGN
IKEv2-PROTO-3: (6): Get my authentication method
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_BLD_AUTH Event: EV_OK_AUTH_GEN
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_BLD_EAP_AUTH_VERIFY Event: EV_GEN_AUTH
IKEv2-PROTO-3: (6): Generate my authentication data
IKEv2-PROTO-3: (6): Use preshared key for id hostname=ASA-IKEV2, key len 20
IKEv2-PROTO-5: (6): SM Trace-> SA: I_SPI=58AFF71141BA436B R_SPI=FC696330E6B94D7F (R) MsgID = 00000005 CurState: R_BLD_EAP_AUTH_VERIFY Event: EV_SEND_AUTH
IKEv2-PROTO-2: (6): Send AUTH, to verify peer after EAP exchange
IKEv2-PROTO-3:   ESP Proposal: 1, SPI size: 4 (IPSec negotiation),
Num. transforms: 3
   AES-CBC   SHA96   
IKEv2-PROTO-5: Construct Notify Payload: ESP_TFC_NO_SUPPORTIKEv2-PROTO-5: Construct Notify Payload: NON_FIRST_FRAGSIKEv2-PROTO-3: (6): Building packet for encryption; contents are:
 AUTH  Next payload: CFG, reserved: 0x0, length: 28
    Auth method PSK, reserved: 0x0, reserved 0x0
Auth data&colon; 20 bytes
 CFG  Next payload: SA, reserved: 0x0, length: 4196
    cfg type: CFG_REPLY, reserved: 0x0, reserved: 0x0

   attrib type: internal IP4 address, length: 4

     01 01 01 01
   attrib type: internal IP4 netmask, length: 4

     00 00 00 00
   attrib type: internal address expiry, length: 4

     00 00 00 00
   attrib type: application version, length: 16

     41 53 41 20 31 30 30 2e 37 28 36 29 31 31 36 00
   attrib type: Unknown - 28704, length: 4

     00 00 00 00
   attrib type: Unknown - 28705, length: 4

     00 00 07 08
   attrib type: Unknown - 28706, length: 4

     00 00 07 08
   attrib type: Unknown - 28707, length: 1

     01
   attrib type: Unknown - 28709, length: 4

     00 00 00 1e
   attrib type: Unknown - 28710, length: 4

     00 00 00 14
   attrib type: Unknown - 28684, length: 1

     01
   attrib type: Unknown - 28711, length: 2

     05 7e
   attrib type: Unknown - 28679, length: 1

     00
   attrib type: Unknown - 28683, length: 4

     80 0b 00 01
   attrib type: Unknown - 28725, length: 1

     00
   attrib type: Unknown - 28726, length: 1

     00
   attrib type: Unknown - 28727, length: 4056

     3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d 22 31
     2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 55 54
     46 2d 38 22 3f 3e 3c 63 6f 6e 66 69 67 2d 61 75
     74 68 20 63 6c 69 65 6e 74 3d 22 76 70 6e 22 20
     74 79 70 65 3d 22 63 6f 6d 70 6c 65 74 65 22 3e
     3c 76 65 72 73 69 6f 6e 20 77 68 6f 3d 22 73 67
     22 3e 31 30 30 2e 37 28 36 29 31 31 36 3c 2f 76
     65 72 73 69 6f 6e 3e 3c 73 65 73 73 69 6f 6e 2d
     69 64 3e 38 31 39 32 3c 2f 73 65 73 73 69 6f 6e
<snip>
     72 6f 66 69 6c 65 2d 6d 61 6e 69 66 65 73 74 3e
     3c 2f 63 6f 6e 66 69 67 3e 3c 2f 63 6f 6e 66 69
     67 2d 61 75 74 68 3e 00
   attrib type: Unknown - 28729, length: 1

     00
 SA  Next payload: TSi, reserved: 0x0, length: 44
IKEv2-PROTO-4:   last proposal: 0x0, reserved: 0x0, length: 40
  Proposal: 1, Protocol id: ESP, SPI size: 4, #trans: 3
IKEv2-PROTO-4:     last transform: 0x3, reserved: 0x0: length: 12
    type: 1, reserved: 0x0, id: AES-CBC
IKEv2-PROTO-4:     last transform: 0x3, reserved: 0x0: length: 8
    type: 3, reserved: 0x0, id: SHA96
IKEv2-PROTO-4:     last transform: 0x0, reserved: 0x0: length: 8
    type: 5, reserved: 0x0, id:

 TSi  Next payload: TSr, reserved: 0x0, length: 24
    Num of TSs: 1, reserved 0x0, reserved 0x0
    TS type: TS_IPV4_ADDR_RANGE, proto id: 0, length: 16
    start port: 0, end port: 65535
    start addr: 10.2.2.1, end addr: 10.2.2.1
 TSr  Next payload: NOTIFY, reserved: 0x0, length: 24
    Num of TSs: 1, reserved 0x0, reserved 0x0
    TS type: TS_IPV4_ADDR_RANGE, proto id: 0, length: 16
    start port: 0, end port: 65535
    start addr: 0.0.0.0, end addr: 255.255.255.255

IKEv2-PROTO-3: Tx [L 10.0.0.1:4500/R 192.168.1.1:25171/VRF i0:f0] m_id: 0x5
IKEv2-PROTO-3: HDR[i:58AFF71141BA436B - r: FC696330E6B94D7F]
IKEv2-PROTO-4: IKEV2 HDR ispi: 58AFF71141BA436B - rspi: FC696330E6B94D7F
IKEv2-PROTO-4: Next payload: ENCR, version: 2.0
IKEv2-PROTO-4: Exchange type: IKE_AUTH, flags: RESPONDER MSG-RESPONSE
IKEv2-PROTO-4: Message id: 0x5, length: 4396
 ENCR  Next payload: AUTH, reserved: 0x0, length: 4368
Encrypted data&colon; 4364 bytes

****************************************
Date        : 04/23/2013
Time        : 16:25:07
Type        : Information
Source      : acvpndownloader

Description : Function: ProfileMgr::loadProfiles
File: ..\Api\ProfileMgr.cpp
Line: 148
Loaded profiles:
C:\Documents and Settings\All Users\Application Data\Cisco\Cisco AnyConnect Secure Mobility Client\Profile\anyconnect-ikev2.xml
****************************************
****************************************
Date        : 04/23/2013
Time        : 16:25:07
Type        : Information
Source      : acvpndownloader

Description : Current Preference Settings:
ServiceDisable: false
CertificateStoreOverride: false
CertificateStore: All
ShowPreConnectMessage: false
AutoConnectOnStart: false
MinimizeOnConnect: true
LocalLanAccess: false
AutoReconnect: true
AutoReconnectBehavior: DisconnectOnSuspend
UseStartBeforeLogon: false
AutoUpdate: true
RSASecurIDIntegration: Automatic
WindowsLogonEnforcement: SingleLocalLogon
WindowsVPNEstablishment: LocalUsersOnly
ProxySettings: Native
AllowLocalProxyConnections: true
PPPExclusion: Disable
PPPExclusionServerIP:
AutomaticVPNPolicy: false
TrustedNetworkPolicy: Disconnect
UntrustedNetworkPolicy: Connect
TrustedDNSDomains:
TrustedDNSServers:
AlwaysOn: false
ConnectFailurePolicy: Closed
AllowCaptivePortalRemediation: false
CaptivePortalRemediationTimeout: 5
ApplyLastVPNLocalResourceRules: false
AllowVPNDisconnect: true
EnableScripting: false
TerminateScriptOnNextEvent: false
EnablePostSBLOnConnectScript: true
AutomaticCertSelection: true
RetainVpnOnLogoff: false
UserEnforcement: SameUserOnly
EnableAutomaticServerSelection: false
AutoServerSelectionImprovement: 20
AutoServerSelectionSuspendTime: 4
AuthenticationTimeout: 12
SafeWordSofTokenIntegration: false
AllowIPsecOverSSL: false
ClearSmartcardPin: true
****************************************
Date        : 04/23/2013
Time        : 16:25:07
Type        : Information
Source      : acvpnui

Description : Message type information sent to the user:
Establishing VPN - Examining system...
****************************************
Date        : 04/23/2013
Time        : 16:25:07
Type        : Information
Source      : acvpnui

Description : Message type information sent to the user:
Establishing VPN - Activating VPN adapter...
****************************************
Date        : 04/23/2013
Time        : 16:25:07
Type        : Information
Source      : acvpnagent

Description : Function: CVirtualAdapter::DoRegistryRepair
File: .\WindowsVirtualAdapter.cpp
Line: 1869
Found VA Control key: SYSTEM\CurrentControlSet\ENUM\ROOT\NET\0000\Control

****************************************
Date        : 04/23/2013
Time        : 16:25:07
Type        : Information
Source      : acvpnagent

Description : A new network interface has been detected.
****************************************
Date        : 04/23/2013
Time        : 16:25:07
Type        : Information
Source      : acvpnagent

Description : Function: CRouteMgr::logInterfaces
File: .\RouteMgr.cpp
Line: 2076
Invoked Function: logInterfaces
Return Code: 0 (0x00000000)
Description: IP Address Interface List:
10.2.2.1
192.168.1.1
****************************************
Date        : 04/23/2013
Time        : 16:25:08
Type        : Information
Source      : acvpnagent

Description : Host Configuration:
 Public address: 192.168.1.1
 Public mask: 255.255.255.0
 Private Address: 10.2.2.1
 Private Mask: 255.0.0.0
 Private IPv6 Address: N/A
 Private IPv6 Mask: N/A
 Remote Peers: 10.0.0.1 (TCP port 443, UDP port 500), 10.0.0.1 (UDP port 4500)
 Private Networks: none
 Public Networks: none
 Tunnel Mode: yes
****************************************

The connection is entered into the Security Association  (SA) database, and the status is REGISTERED. The ASA also performs some checks like Common Access Card (CAC) stats, presence of duplicate SAs, and sets values like dead peer detection (DPD) and so forth.