Check Point CCSE lab 4 of 10
Site-to-site VPN with a Cisco IOS peer
Connect a branch office whose router the management server will never manage. Describe it as an interoperable device, build a star community with IKEv2 and a pre-shared key, exempt the tunnel from hide NAT, make the gateway's identity routable, build the matching IOS side, and prove the tunnel from both ends.
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 04 - Site-to-site VPN with a Cisco IOS peer
- Level
- Advanced
- Time
- About 100 minutes
- Nodes need
- 10 vCPU, 15,872 MB
- Smallest plan
- Standard
The scenario
Northgate has opened a branch office with a Cisco router. The management server will never manage it, so you need a tunnel between two different vendors, and each side must be configured to match the other.
| Setting | Value |
|---|---|
| HQ VPN domain | HQ-LAN, 10.0.0.0/24 |
| Branch VPN domain | 172.16.0.0/24 (Loopback0 on BRANCH, address 172.16.0.1) |
| Gateways | HQ-GW 67.83.0.111, BRANCH 198.51.100.2 |
| Community | star Northgate-Branches, HQ-GW at the centre, BRANCH-RTR as satellite |
| IKE | IKEv2 only, AES-256, SHA-256, DH group 19 |
| IPsec | AES-256, SHA-256, PFS with group 19 |
| Authentication | pre-shared key Northgate-Branch-VPN-26 |
HQ-LAN already hides behind 67.83.0.111 for internet access, and that will matter.
What you’ll practise
- Create an interoperable device and define VPN domains
- Build a star community with custom IKEv2 settings and a pre-shared key
- Explain why the gateway's main IP is both its IKE identity and the source of its IKE traffic
- Exempt VPN traffic from hide NAT
- Mirror the Check Point settings in an IOS crypto map and IKEv2 profile
- Verify the tunnel with vpn tu tlist, cpstat vpn, logs and the IOS show commands
The tasks
- Check the starting point
- The gateway's identity
- VPN domains and the interoperable device
- The community
- Policy and NAT
- The IOS side
- Bring it up and prove it
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
04 - Site-to-site VPN with a Cisco IOS peerand 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.