Solution Track

Enterprise Campus Solutions

Compare solution notes, whitepapers, and deployment paths for this environment.

Representative 24-port RJ45 xSONiC access switch chassis; exact configuration varies

Architecture lens

Plan access, aggregation and the WAN handoff as one service.

Define the campus edge as an end-to-end service: endpoint authentication and PoE at access, resilient routing at aggregation, then an explicit Layer 3 handoff into the enterprise WAN or SD-WAN edge.

Access, PoE and NAC
Resilient aggregation
WAN and SD-WAN handoff

Solution notes: 1
Whitepapers: 4

Solution notes

1 available

01 Enterprise Campus

Campus Refresh

Modernize campus access and aggregation without vendor lock-in.

Whitepapers

4 available

W01 Whitepaper

MC-LAG and STP Interoperability Guide

Design guidance for resilient campus aggregation using MC-LAG with controlled STP boundaries.

W02 Whitepaper

Enterprise Campus Policy-Based Routing (PBR) Guide

Practical guidance for using policy-based routing on xSONiC campus and aggregation switches.

W03 Whitepaper

PoE Campus Deployment Guide

Comprehensive PoE planning and deployment guide for xSONiC campus access switches.

W04 Whitepaper

Campus Cluster and Virtual Chassis Guide

Guidance for simplifying campus leaf-spine rollout with synchronized cluster configuration.

Planning FAQ

Enterprise Campus architecture questions.

Direct answers and a selection guide for moving from architecture intent to a supportable product shortlist.

What must an enterprise campus WAN or SD-WAN handoff define?

Document the Layer 3 demarcation, VLAN or VRF ownership, static or dynamic routing, route filtering, QoS mapping, security inspection path, high-availability behaviour, monitoring ownership, and the failover test between campus aggregation and the WAN or SD-WAN edge.

Where should campus aggregation end and the WAN edge begin?

Campus aggregation should own resilient access-layer concentration and local policy. The WAN or SD-WAN edge should own site-to-site and internet path selection. Make that boundary explicit with routed links, named route owners, failure-state traffic flows, and a rollback plan.

What should a campus pilot validate before a wider refresh?

Validate endpoint onboarding, 802.1X and fallback policy, PoE load, voice and IoT segmentation, aggregation member loss, WAN failover, telemetry, help-desk workflow, and rollback using the exact hardware revision and SONiC image proposed for production.

Where should enterprise campus product selection start?

Start with endpoint, power, uplink, redundancy, WAN handoff, operations, and support requirements. Only then compare access and aggregation platforms against a documented acceptance plan.

Next Steps

Move from solution planning into the next discussion.

Use this page to narrow down the right solution story, then open a conversation when you are ready to evaluate products or deployment fit.

Talk to xSONiC