300-730 practice question 25 of 25

Which IKE identity does an IOS/IOS-XE headend expect to receive if an IPsec Cisco AnyConnect client uses default settings?

Full set: 175 questions
Answer options
A: *$SecureMobilityClient$*
B: *$AnyConnectClient$* Correct answer
C: *$RemoteAccessVpnClient$*
D: *$DfltlkeldentityS*
Correct Answer:
B. *$AnyConnectClient$*
Explanation

When a Cisco AnyConnect client using default settings initiates an IKEv2/IPsec connection to an IOS/IOS-XE headend, it sends a specific default string as its IKE identity. This identity is $AnyConnectClient$. The headend router uses this identifier to match the incoming connection request to a specific IKEv2 profile configured for AnyConnect clients. This is accomplished using the match identity remote key-id $AnyConnectClient$ command within the IKEv2 profile configuration, allowing the router to apply the correct policies for AnyConnect users.

Why Incorrect

A. $SecureMobilityClient$ is not the default identifier used by the AnyConnect client for IKEv2 connections.
C. $RemoteAccessVpnClient$ is a generic term and not the specific default IKEv2 identity string sent by AnyConnect.
D. $DfltlkeldentityS is not a recognized default IKEv2 identity string for any standard Cisco client.

References

1. Cisco Systems, "FlexVPN and Internet Key Exchange Version 2 Configuration Guide, Cisco IOS XE Release 3S", Section: IKEv2 Profile Configuration. Configuration examples for AnyConnect integration explicitly show matching on this key-id. For example: ikev2 profile IKEV2-PROFILE-ANYCONNECT match identity remote key-id $AnyConnectClient$.

2. Cisco Systems, "AnyConnect VPN Client/ASA/IOS Headend IKEv2 Configuration Example", Document ID: 113528. This document's IOS configuration section demonstrates the use of match identity remote key-id $AnyConnectClient$ to identify and process AnyConnect client connections.

Scroll to Top