VeloCloud SD-WAN in EVE-NG, all three parts
The VeloCloud Edge, Gateway and Orchestrator are all in the Add Node list of every CloudLabBox workspace. Build a whole overlay in one lab and practise Edge activation, profiles and business policy.
Choose a planCheck it in the free demo
- Vendor
- VeloCloud
- In Add Node
- 27 images
- Templates
veloedgevelogwveloorch- Newest
veloedge-6.1.0.0-R6100
Installed versions
Every VeloCloud SD-WAN name in the Add Node image list, exactly as you’ll pick it.
Template veloedge
Edge (VCE)
veloedge-6.1.0.0-R6100veloedge-6.0.0.0-R6000veloedge-5.2.0.1-R5201veloedge-5.1.0-R5102veloedge-5.0.1.0veloedge-5.0.0.0veloedge-4.3.0veloedge-3.4.0veloedge-3.3.2
Template velogw
Gateway (VCG)
velogw-6.1.0.0-R6100velogw-6.0.0.0-R6000velogw-5.2.0.1-R5201velogw-5.1.0-R5102velogw-5.0.1.0velogw-5.0.0.0velogw-4.3.0velogw-3.4.1velogw-3.3.2
Template veloorch
Orchestrator (VCO)
veloorch-6.1.0.0-R6100veloorch-6.0.0.3-R6003veloorch-5.2.0.1-R5201veloorch-5.1.0-R5103veloorch-5.0.1.0veloorch-5.0.0.1veloorch-4.3.0veloorch-3.4.1veloorch-3.3.2
Add it to a lab
In Add Node, choose the template, then the image. The template fills in these settings; change them before you start the node.
| Image | Template | CPU | RAM | Interfaces | Console |
|---|---|---|---|---|---|
| Edge (VCE) | veloedge | 2 | 4096 MB | 6 interfaces: G1 to G6 | telnet |
| Gateway (VCG) | velogw | 4 | 8192 MB | 2 interfaces | telnet |
| Orchestrator (VCO) | veloorch | 4 | 16384 MB | 1 interface | telnet |
EVE-NG admits a node by the CPU and RAM set on it, so a running node counts against your plan at these values. The largest of these templates starts nodes at 4 vCPU and 16,384 MB, more than the free demo’s 6 vCPU and 8 GB, so use the demo to find the image and a plan to run it.
Two branch Edges, a Gateway and an Orchestrator
Run an Orchestrator and a Gateway, then activate two Edges at two branches, joined through an IOSv router that plays the internet, each with an Alpine Linux host on its LAN. You practise activation, profiles and business policy.
- 1×Orchestrator (VCO)
veloorch4 vCPU, 16384 MB - 1×Gateway (VCG)
velogw4 vCPU, 8192 MB - 2×Edge (VCE)
veloedge2 vCPU, 4096 MB each - 1×IOSv
vios1 vCPU, 1024 MB - 2×Alpine Linux
clbalpinebase2 vCPU, 512 MB each
Added with these defaults, the lab uses 17 vCPU and 34 GB of RAM. The smallest plan that fits is Organization, with 24 vCPU and 48 GB: £10 a day, or £3 an hour On-Demand.
Licences are yours to bring
CloudLabBox doesn't provide VeloCloud licences or subscriptions. Bring your own entitlement for the Orchestrator and the Edges you activate.
The images run only inside your CloudLabBox workspace; they aren’t available to download.
Questions about VeloCloud SD-WAN
What is VeloCloud SD-WAN?
VeloCloud SD-WAN has three parts: the Edge at each site, the Gateway that sits in the cloud between the Edges and the services they reach, and the Orchestrator that configures and monitors them.
How are the Gateway's and Orchestrator's interfaces labelled?
EVE-NG labels the Gateway's two interfaces Internet and Handoff, and the Orchestrator's single interface eth0/mgmt. Edge interfaces are labelled G1 to G6.
Which versions go together?
Keep the Orchestrator at the same release as the Gateway and Edges, or newer. Matching releases are installed for all three, for example veloorch-6.1.0.0-R6100, velogw-6.1.0.0-R6100 and veloedge-6.1.0.0-R6100.
Which VeloCloud SD-WAN images are installed?
27 images (9 Edge (VCE), 9 Gateway (VCG), 9 Orchestrator (VCO)), all listed on this page exactly as Add Node shows them. The newest is veloedge-6.1.0.0-R6100.
How much CPU and RAM does a VeloCloud SD-WAN node use?
When you add one, the veloedge template adds 2 vCPU and 4096 MB of RAM; the velogw template adds 4 vCPU and 8192 MB of RAM; the veloorch template adds 4 vCPU and 16384 MB of RAM. You can change both in Add Node, and your plan counts what each running node is set to.
More images
CloudLabBox is independent of the vendors named on this page. Their names identify the images in the workspace’s Add Node list.