VMware SD-WAN by VeloCloud: Design and Deploy [V3.x] — Lesson 1: SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints

Learning Objectives

• Break down the prerequisites, components, roles, and decision points involved in SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints.
• Complete a controlled activity for SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints and capture SD-WAN requirements matrix and high-level topology.
• Challenge the result with a branch design depending on one carrier despite a stated availability objective, then justify the corrective action.

Detailed Topics

• SD-WAN architecture
• Orchestrator
• Gateways
• Edges
• Overlays
• Underlays
• Branch models
• Business requirements
• Application classes
• Transport diversity
• Sizing
• And design constraints
• Decision ownership, prerequisites, and acceptance evidence for SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints, narrating each decision and showing how it contributes to a VMware SD-WAN design that connects branches securely and resiliently, applies business policy, optimizes application paths, integrates hubs and gateways, and provides measurable operational visibility. The demonstration records SD-WAN requirements matrix and high-level topology so learners can compare design intent with observable behavior.

Hands-On Exercise

Build or execute SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints for a defined scenario. Introduce the condition “a branch design depending on one carrier despite a stated availability objective,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in SD-WAN requirements matrix and high-level topology.

1. Record the starting state, assumptions, identities, topology, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how SD-WAN requirements matrix and high-level topology should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

When SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints produces an unexpected result, reproduce the issue with the same scope, identity, workload, and time context. Inspect SD-WAN requirements matrix and high-level topology, test whether “a branch design depending on one carrier despite a stated availability objective” explains the evidence, apply the smallest reversible correction, and retest an unaffected path for regression.

Validation Checklist

• The requirement for SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints is linked to an owner and observable acceptance condition.
• Sd-wan requirements matrix and high-level topology contains enough detail for another practitioner to repeat the check.
• Normal operation, one boundary condition, and the identified failure path have been tested.
• Access, security, downstream impact, rollback, monitoring, and support ownership are recorded.

Lesson Outcome

Learners can apply SD-WAN architecture, Orchestrator, gateways, edges, overlays, underlays, branch models, business requirements, application classes, transport diversity, sizing, and design constraints, explain the decisions made, and defend the result with SD-WAN requirements matrix and high-level topology.