Config Generation & Validation
Per-vendor CLI output and the three validation layers.
Relevant for:Professional ServicesEnterprise / NetOps
Where to find itCanvas toolbar→Generate→— and —→Validate
Config generation#
Generate renders every device through its vendor template: IOS-XE, NX-OS, EOS, ArubaOS-CX, PAN-OS set-commands, or Terraform. Output is complete and ordered like a real config — identity, management plane, L2, L3, features, lines — and can be copied per device or exported for the whole design.
Note
Secrets never appear: passwords, TACACS/RADIUS keys, SNMPv3 auth keys and NTP keys all render as the literal
PLACEHOLDER for the operator to substitute at install time.The three validation layers#
| Inline | Field-level checks as you type — IP formats, ranges (privilege 0–15, exec-timeout bounds), password-policy consistency. |
| Whole-design | The Validate drawer: duplicate hostnames/IPs, subnet overlaps, single points of failure, STP root claims, VLAN consistency across trunks, undefined object references (ACLs, route-maps, flow monitors, NTP/line ACLs), duplicate SLA ids, port capacity, media/speed mismatches. |
| Render-time | After templating: unrendered variables, missing required fields (e.g. a flow monitor with no collector), and per-platform capability notes (option omitted on this NOS). |
Why
Catching an undefined route-map reference or a duplicate IP in the design tool costs seconds; catching it during a change window costs the window. The Validate drawer is safe to run constantly — findings are advisory, ranked, and where a deterministic fix exists it is offered one-click.