Overview

Campus cluster and virtual chassis designs reduce repeated configuration work across switches with similar roles. Instead of configuring every access and aggregation switch as an isolated one-off device, the network can synchronize common role settings while preserving per-device identity.

For xSONiC campus deployments, this is most useful when multiple access closets share the same VLAN, policy, uplink, and routing patterns.

Design Model

Shared role configuration
        |
        v
Access leaf group  ----  Aggregation group  ----  Campus core
        |
        v
Device-specific interfaces, loopbacks, and uplinks

The important separation is between shared role configuration and local device configuration. The two should not be mixed casually.

Configuration Domains

Domain	Shared or Local	Examples
Role policy	Shared	VLAN list, QoS policy, security templates.
Routing baseline	Shared	BGP or OSPF templates, route policy.
Interface identity	Local	Interface IPs, loopbacks, physical uplink mapping.
Device identity	Local	Hostname, management IP, serial, rack/closet label.
Exceptions	Controlled local	Building-specific VLANs or special endpoint policy.

Benefits and Risks

Benefit	Risk if Poorly Managed
Faster rollout across repeated closets.	Bad shared config can propagate quickly.
More consistent policy enforcement.	Local exceptions may be overwritten if not modeled.
Easier replacement and recovery.	Device identity mistakes can cause route or management conflicts.
Lower manual drift.	Operators may lose visibility into what is shared vs local.

Deployment Workflow

1. Identify common access, aggregation, and core roles.
2. Define which configuration belongs to each role.
3. Reserve local fields for hostname, loopback, management, and uplink specifics.
4. Apply shared configuration to a small pilot group.
5. Validate endpoint onboarding, routing, roaming, and failure behavior.
6. Expand in waves while checking configuration drift.

Validation Checklist

Test	Expected Result
New access switch onboarding	Shared baseline applies cleanly without duplicate identity.
Endpoint VLAN and policy	Users, APs, phones, and cameras land in expected segments.
Uplink failure	Routing and aggregation recover without manual correction.
Local exception	Building-specific policy remains intact after shared updates.
Rollback	Shared change can be reverted without touching local identity.

xSONiC Platform Fit

XS-AA access switches provide the campus edge for users, APs, and cameras. XS-AA aggregation and core models provide the routed backbone where shared configuration patterns can reduce rollout time and operational drift.