Cisco Catalyst SD-WAN CLI lab 9 of 14
Direct internet access
Let a branch reach the internet directly through its own circuit: NAT on the transport interface and a service-VPN route that points at VPN 0.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 5,632 MB in total. That fits the free demo too.
In your workspace: Shared, then Cisco Catalyst SD-WAN CLI guided labs, then 09 - Direct internet access
- Level
- Advanced
- Time
- About 50 minutes
- Nodes need
- 6 vCPU, 5,632 MB
- Smallest plan
- Lite
The scenario
Manchester's staff reach the internet through head office, which wastes the site's own internet circuit. You give the branch direct internet access (DIA): traffic for the internet leaves through BR1's own circuit, translated to BR1's public address, while traffic for other sites stays on the overlay.
| Node | System IP | Site | INET (ge0/0) | LAN, VPN 10 (ge0/1) |
|---|---|---|---|---|
| BR1 | 10.255.0.11 | 11 | 198.51.100.11 | 10.11.10.1/24, H1 10.11.10.10 |
| BR2 | 10.255.0.12 | 12 | 198.51.100.12 | 10.12.10.1/24 |
| WEB | 198.51.100.254, the provider's gateway | also hosts a public site on 203.0.113.80 |
vBond is 198.51.100.1 and vSmart is 198.51.100.2. Both edges have ip route 0.0.0.0/0 198.51.100.254 in VPN 0.
What this course leaves out. There is no SD-WAN Manager (vManage) in any of these labs. A virtual edge can't join the Manager's inventory without a signed device list from Cisco, which these labs don't have. So you won't see the Manager's GUI, dashboards, templates, Policy Builder or zero-touch onboarding. You work at the CLI of the controllers and edges, with a private lab CA and device lists typed by hand. This lab is direct internet access with NAT only. The enterprise firewall and SIG need IOS XE edges and aren't in this course. The hosts have fixed addresses set at boot, because the DHCP server on these vEdge images can lock up the edge at start-up.
What you’ll practise
- Enable NAT on a transport interface
- Add a route from a service VPN to VPN 0
- Read the NAT translations and prove the traffic left locally
The tasks
- Start the lab
- See the problem
- Enable NAT on the transport
- Point VPN 10 at VPN 0
- Prove the traffic left locally
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
- vBond
ge0/0to INET (network) - vSmart
eth0to INET (network) - BR1
G0/0to INET (network) - BR2
G0/0to INET (network) - WEB
eth0to INET (network) - BR1
G0/1to H1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| vBond | Cisco vBond | vtbond-20.12.2 | 1 vCPU, 1,024 MB |
| vSmart | Cisco vSmart | vtsmart-20.12.2 | 1 vCPU, 1,024 MB |
| BR1 | Cisco vEdge | vtedge-20.12.2 | 1 vCPU, 1,024 MB |
| BR2 | Cisco vEdge | vtedge-20.12.2 | 1 vCPU, 1,024 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| WEB | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Cisco Catalyst SD-WAN CLI guided labs.Open
09 - Direct internet accessand 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 Catalyst SD-WAN CLI labs
All Cisco Catalyst SD-WAN CLI 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.