CloudLabBox
Try the free demo

Cisco ASA lab 10 of 15

Remote-access VPN headend: Secure Client SSL and IKEv2 on the ASA

Prepare HQ-FW to accept Cisco Secure Client (AnyConnect) users over TLS and IKEv2: a certificate trustpoint, an address pool, a split-tunnel group policy, a connection profile, local VPN-only users and the NAT exemption, then verify the portal and certificate from a remote host on the internet.

Run this lab

It needs Lite: its 4 nodes are set to 4 vCPU and 3,584 MB in total. That fits the free demo too.

In your workspace: Shared, then Cisco ASA Firewall SCOR 350-701 guided labs, then 10 - Remote-access VPN headend - Secure Client SSL and IKEv2 on the ASA

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
4 vCPU, 3,584 MB
Smallest plan
Lite

The scenario

Kestrel staff will work from home with Cisco Secure Client (formerly AnyConnect). Build the headend on HQ-FW:

ItemValue
Public namevpn.kestrel.example = 203.0.113.2
Certificateself-signed for now (trustpoint VPN-SELF, 2048-bit key VPN-KEY); a public CA certificate replaces it later
ProtocolsTLS/DTLS (SSL client) and IKEv2, both on the outside interface
Address poolRA-POOL 10.99.99.10–10.99.99.200 /24
Group policyGP-STAFF: split tunnel only to 10.10.10.0/24, DNS 10.10.10.53, domain kestrel.example, idle timeout 30 min, 2 simultaneous logins
Connection profileRA-STAFF, alias STAFF shown on the login page, local authentication
Usersalice / Kestrel-Alice-26, VPN only (no CLI access)

What you’ll practise

  • Create a self-signed identity certificate and bind it to the outside interface for TLS
  • Enable the SSL VPN and IKEv2 client services on the outside interface
  • Build a group policy with split tunnelling and a connection profile (tunnel group) with an address pool
  • Create VPN-only local users and exempt VPN pool traffic from PAT
  • Verify the headend from a remote host: the certificate, the portal and the connection profile list

The tasks

  1. Certificate
  2. Pool, split tunnel and group policy
  3. Connection profile and user
  4. Turn the services on
  5. Verify from the internet

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Remote-access VPN headend - Secure Client SSL and IKEv2 on the ASA4 nodes and 1 network, 4 links. Every link is listed as text below the diagram.HQ-FWPC1ISPREMOTEInternetGi0/1eth0Gi0/0Gi0/0Gi0/0
4 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • HQ-FW Gi0/0 to PC1 Gi0/0
  • HQ-FW Gi0/1 to Internet (network)
  • ISP Gi0/0 to Internet (network)
  • REMOTE eth0 to Internet (network)
Nodes in Remote-access VPN headend: Secure Client SSL and IKEv2 on the ASA, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
HQ-FWCisco ASAvasav-9.22.1.1-PLR-Licensed1 vCPU, 2,048 MB
PC1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
ISPCisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
REMOTEAlpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Cisco ASA Firewall SCOR 350-701 guided labs.

  3. Open 10 - Remote-access VPN headend - Secure Client SSL and IKEv2 on the ASA and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More Cisco ASA labs

All Cisco ASA labs

Related labs in other courses

CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.