Baseline deployment reference
A concrete lab plan with explicit customer inputs.
The 10.70.0.0/24 values below are isolated lab examples. Manager and Edge VMs can run outside EVE-NG, with lab clouds connecting the intended service paths. Replace addresses and map actual MACs, vNICs, VLANs, routes, DNS, DHCP reservations, NTP and certificate names before use.
| Role | Reference value | Purpose |
|---|
| Manager | 10.70.0.10 | TCP 443 management ingress |
| Regional inference | 10.70.0.20 | Qualified internal route |
| Branch / HQ / DC Edge | 10.70.0.31 / .32 / .33 | Separate management identities |
| Gateway / DNS / NTP | 10.70.0.1 / .2 / .3 | Accepted management services |
| Branch and HQ service ports | Gi1/2 IN / Gi1/3 OUT | Explicit service-in and service-out roles |
| DC service ports | Gi3/0 IN / Gi3/1 OUT | Keep management separate |
Reference lab sizing
| Virtual machine | Allocation | Purpose |
|---|
| Manager | 8 vCPU, 16 GiB, 120 GiB | Control services and console |
| Data | 8 vCPU, 32 GiB, 500 GiB | Databases, evidence and event storage |
| Regional | 8 vCPU, 24 GiB, 250 GiB | Model host and regional services |
| Two site nodes | 4 vCPU, 16 GiB, 150 GiB each | Branch and headquarters sites |
| Test services | 2 vCPU, 8 GiB, 100 GiB | Synthetic sources and a test ticketing system |
| Isolated workspace host (optional) | 8 vCPU, 24 GiB, 200 GiB | Workspace isolation tests |
The lab allocates 42 vCPU, 136 GiB of memory and 1,470 GiB of disk in total. It is a starting allocation for isolated testing, not a performance guarantee, and it does not establish high availability.
Begin with selected internet traffic, preserve SD-WAN control and approved DIA breakout, and verify return-path symmetry, MTU, bypass and rollback. Do not bridge service interfaces through the management switch.
Request the Architecture Guide