Cisco StackWise Virtual (SVL) — Two Chassis as One Logical Switch

The one-sentence mental model

SVL is HSRP on steroids for the whole switch. Instead of two boxes with a virtual gateway IP that fails over between them, SVL makes the two boxes themselves one logical unit. Downstream devices see a single switch. STP sees a single switch. Routing peers see a single switch. Failover is transparent because “failover” doesn’t exist — the surviving chassis just keeps operating.

Why it matters

Classic dual-chassis campus design has ugly compromises:

• STP blocks half your uplinks. With two dist switches and redundant uplinks, STP blocks the second path.
• HSRP/VRRP for gateway redundancy. Works, but adds config and asymmetry.
• MC-LAG (mLAG) is proprietary and hard.

SVL solves all three: two chassis = one control plane = one gateway = MEC (Multi-chassis EtherChannel) uplinks from downstream. STP doesn’t block anything because there’s only one logical switch.

The pieces

StackWise Virtual Link (SVL)

The physical link(s) between the two chassis. Carries:

• Control-plane sync (routing tables, MAC tables, ARP)
• Data-plane traffic that ingressed on one chassis but must egress on the other
• Keepalives

Typical config: 2+ interfaces bundled (LACP-like within SVL), 40G or 100G to handle worst-case cross-chassis traffic. Kept on dedicated ports away from user traffic.

Dual-Active Detection (DAD)

If the SVL dies but both chassis stay up, each thinks the other is dead → both become active → split brain → duplicate MACs, IPs, routing chaos.

DAD prevents this via one of:

• DAD via a peer link — direct L2 link separate from SVL
• DAD via ePAgP — enhanced PAgP heartbeats over an EtherChannel uplink to a downstream switch (that switch relays “the other chassis is still alive” back to me)
• DAD via BFD over a management interface

When DAD detects both members active, one member goes into recovery mode — shuts all interfaces except SVL and management, waits for the SVL to come back.

MEC — Multi-Chassis EtherChannel

The killer feature. Downstream switches bundle uplinks — one to each SVL chassis — into a single Port-channel. From the downstream’s point of view it’s a normal EtherChannel to one switch. From SVL’s point of view it’s a MEC that survives either chassis failing.

No STP blocking. Both uplinks forward. If a chassis fails, the surviving chassis takes over the MEC and downstream traffic doesn’t even blip.

Sample config outline

! On both chassis:
switch 1 provision c9500-40x
stackwise-virtual
 domain 100
!
interface range TenGigabitEthernet1/0/1-2
 stackwise-virtual link 1
!
! Dual-active detection
stackwise-virtual dual-active-detection pagp trust channel-group 10

After reload, the two chassis boot as one — you SSH into the “virtual” switch, show switch shows Switch 1 (Active) and Switch 2 (Standby).

Switch roles

• Active — runs the control plane. All routing / management runs here.
• Standby — mirrors state from Active. If Active dies, Standby takes over via SSO (Stateful Switchover). Sub-second failover for most protocols.

Both chassis forward user traffic. The Active/Standby distinction is about control plane, not data plane.

Common exam / real-world mistakes

1. Not sizing the SVL for worst-case cross-chassis traffic. If a downstream sends traffic to chassis A but the destination MAC is behind chassis B, the frame crosses the SVL. Underprovisioned SVL becomes the bottleneck.
2. Skipping DAD. SVL alone is not enough. Configure DAD via ePAgP or a dedicated link.
3. Mixing switch models. Both chassis must be identical model + license.
4. Assuming SVL = HA cluster. SVL is a single logical switch, not two switches in a cluster. Config is applied once and syncs. Upgrades are In-Service Software Upgrade (ISSU) or scheduled reload.
5. Confusing SVL with legacy VSS. Same concept, different platform. VSS was on Catalyst 6500/6800 with dedicated VSL cards. SVL is on Catalyst 9500/9600 using front-panel ports. Do not carry over old VSS-specific commands.

Cheat strip

Purpose      two chassis → one logical switch
Platforms    Catalyst 9500 / 9600 (SVL) ; Cat 6500/6800 (VSS legacy)

SVL          bundled 10/40/100G between chassis. Control + data cross-chassis.
DAD          Dual-Active Detection. Options: ePAgP | dedicated link | BFD.
MEC          Multi-chassis EtherChannel. Downstream sees one Port-channel.

Roles        Active (control) + Standby (mirror). SSO for sub-second failover.
STP          eliminated for uplinks — no blocking, both paths forward.

Config       stackwise-virtual domain N ; stackwise-virtual link 1 on member ifs