A switch virtual interface (SVI) is a logical, software-based interface on a network switch that gives a VLAN a Layer 3 (routed) identity. It has no physical port of its own. Instead, it acts as the bridge between a VLAN’s switched traffic and the switch’s built-in routing engine, allowing devices in different VLANs to communicate with each other and giving network administrators an IP address they can use to manage the switch remotely.
How an SVI Works
In a basic network, a VLAN groups devices together at Layer 2, meaning they can exchange frames with each other but can’t talk to devices in a different VLAN without a router. Traditionally, that meant sending traffic out of the switch, through a physical router, and back into the switch on a different VLAN. This “router-on-a-stick” approach works but creates a bottleneck because all inter-VLAN traffic funnels through a single physical link.
An SVI solves this by creating a virtual routed interface directly inside a Layer 3 switch. You assign it an IP address, and it becomes the default gateway for every host in that VLAN. When a device in VLAN 10 needs to reach a device in VLAN 20, the packet hits the SVI for VLAN 10, gets routed internally by the switch’s hardware routing engine, and exits through the SVI for VLAN 20. Because the routing happens in hardware on the switch itself rather than traveling to an external router, it is significantly faster.
SVIs for Remote Management
Even Layer 2 switches that don’t perform routing still use SVIs for one important purpose: remote management. By assigning an IP address to an SVI (commonly on a dedicated management VLAN), you give the switch a network-reachable address. You can then connect to it over SSH or a web interface for configuration and monitoring without needing to be physically plugged into a console cable.
On a Layer 2 switch, you’ll typically have just one SVI. A Layer 3 switch can have many, one for each VLAN that needs routing or management access.
Inter-VLAN Routing With SVIs
The most common use of SVIs on a Layer 3 switch is inter-VLAN routing. The setup is straightforward: you create one SVI per VLAN, assign each SVI an IP address that serves as the default gateway for hosts in that VLAN, and then enable IP routing globally on the switch.
For example, if you have VLAN 10 (192.168.10.0/24) and VLAN 20 (192.168.20.0/24), you’d create two SVIs. The SVI for VLAN 10 might get the address 192.168.10.1, and the SVI for VLAN 20 gets 192.168.20.1. Hosts in VLAN 10 set their default gateway to 192.168.10.1, hosts in VLAN 20 use 192.168.20.1, and the switch routes between them internally. Without enabling IP routing on the switch, the SVIs will have addresses but won’t actually forward traffic between VLANs.
SVI vs. Physical Router Interface
A physical interface on a router creates a separate network segment and broadcast domain for each port. An SVI doesn’t work that way. Multiple VLANs can share the same physical switch ports (through trunking), while each VLAN still gets its own logical interface and broadcast domain via its SVI. This means you can scale to dozens of VLANs without needing a dedicated physical port for each one.
The number of SVIs a switch supports depends on the hardware model and software version. Enterprise-grade switches can handle hundreds, but the exact ceiling varies. You can usually check your switch’s capacity documentation or run a show command to confirm the limit for your specific platform.
What Keeps an SVI Up
An SVI won’t come online just because you created it. Four conditions need to be met for the interface to show an active status:
- The VLAN must exist and be active in the switch’s VLAN database. If the VLAN is deleted or suspended, the SVI goes down with it.
- The SVI must not be administratively shut down. New SVIs are often shut down by default, so you need to explicitly bring them up.
- At least one physical port in that VLAN must have a live link. This can be an access port or a trunk port carrying that VLAN.
- At least one of those ports must be in a spanning-tree forwarding state. If all ports in the VLAN are blocked by spanning tree, the SVI’s protocol status drops to down even though the interface itself shows as up.
When troubleshooting an SVI that shows “up/down” (interface up, protocol down), the spanning-tree condition is often the culprit. Verifying that at least one port is forwarding in that VLAN usually points you to the fix.
Common Troubleshooting Issues
Beyond the basic up/down conditions, SVIs can land in a suspended state for less obvious reasons. If you assign the SVI to a VRF (a virtual routing table) that doesn’t actually exist on the switch, the interface won’t activate. On certain platforms, hardware limitations prevent you from mapping both a VXLAN network identifier and an SVI to the same VLAN simultaneously, which silently suspends the SVI.
If your SVI is configured correctly but still isn’t passing traffic, check three things in order: confirm the VLAN is active, verify that physical ports in the VLAN are up and forwarding, and make sure IP routing is enabled globally if you’re trying to route between VLANs. Missing any one of those three steps is the source of most SVI problems.