Check Point CCSE lab 5 of 10
VPN troubleshooting: vpn tu and IKE debug
The branch tunnel has never worked, and nobody knows why. Work up the stack with vpn tu, cpstat, SmartLog, the IKEv2 trace and IOS debugs. Each fix uncovers the next fault, and each fault leaves different evidence: authentication, phase 2, then traffic selectors twice over.
Run this lab
It needs Standard: its 6 nodes are set to 10 vCPU and 15,872 MB in total.
In your workspace: Shared, then Check Point CCSE guided labs, then 05 - VPN troubleshooting - vpn tu and IKE debug
- Level
- Advanced
- Time
- About 100 minutes
- Nodes need
- 10 vCPU, 15,872 MB
- Smallest plan
- Standard
The scenario
A contractor configured the tunnel to the branch office, then left. It has never carried a packet. The design hasn't changed:
| Setting | Value |
|---|---|
| HQ VPN domain | HQ-LAN, 10.0.0.0/24 |
| Branch VPN domain | 172.16.0.0/24 |
| Gateways | HQ-GW 67.83.0.111, BRANCH 198.51.100.2 |
| Community | star Northgate-Branches |
| IKE | IKEv2 only, AES-256, SHA-256, DH group 19 |
| IPsec | AES-256, SHA-256, PFS with group 19 |
| Pre-shared key | Northgate-Branch-VPN-26 (this copy is correct) |
There are four separate faults. Each one hides the next, so don't change anything until you've seen the evidence for it. For each fault, note the symptom, the evidence, the fix, and the test that proves it.
What you’ll practise
- Clear a tunnel fully on both ends, and explain what a half-cleared tunnel looks like
- Turn on IKE debugging and read iked0.ikev2trace
- Use SmartLog's Reject logs and reject_category to classify a failure
- Tell an authentication failure from a phase 2 mismatch and a traffic selector mismatch
- Read the traffic selectors a gateway proposes, and spot the effect of NAT on them
The tasks
- Your toolkit
- Collect the first evidence
- Read the IKE trace
- Fix the faults, one layer at a time
- Prove the repair
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.
Every link, as text
- SMS
eth0to HQ-LAN (network) - HQ-GW
eth0to HQ-LAN (network) - HQ-GW
eth1to Internet (network) - HQ-PC
eth0to HQ-LAN (network) - ADMIN-PC
eth0to HQ-LAN (network) - ISP
Gi0/0to Internet (network) - ISP
Gi0/1to BRANCHGi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| SMS | Check Point Security Management Server | cpsms-R81.20-Licensed | 4 vCPU, 8,192 MB |
| HQ-GW | Check Point Security Gateway VE (cpsg template) | cpsg-R81.20-Licensed | 2 vCPU, 4,096 MB |
| ISP | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| BRANCH | Cisco IOSv | vios-adventerprisek9-m.SPA.159-3.M6 | 1 vCPU, 512 MB |
| HQ-PC | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| ADMIN-PC | EVE-NG Firefox browser (Docker) | eve-firefox:latest | 1 vCPU, 2,048 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Check Point CCSE guided labs.Open
05 - VPN troubleshooting - vpn tu and IKE debugand 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 Check Point CCSE labs
Related labs in other courses
CloudLabBox is independent of Check Point and Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.