Switch stack routing interfaces configuration in Meraki networks provides administrators with comprehensive Layer 3 connectivity and inter-VLAN routing capabilities for stacked switches, enabling VLAN interface creation, IP address assignment, DHCP service management, and OSPF routing integration. This functionality supports network segmentation, subnet routing, multicast forwarding, and centralized DHCP services across the switch stack. Stack routing interfaces are essential for creating routed networks, enabling inter-VLAN communication, providing DHCP services, and integrating with dynamic routing protocols in enterprise network architectures.
Important: Only one interface per switch stack can be designated as the uplink interface. Additionally, an uplink interface must be defined — no other L3 interfaces can exist on a switch stack without one.
Deleting the last remaining interface: If the last remaining L3 interface (which by definition will be the uplink) needs to be removed, the switch management IP mode must first be set to DHCP (if not already). Without this, Terraform will remove the interface from state but the interface will persist in the Meraki dashboard and will not actually be deleted.
The uplink designation behavior differs by switch type and software version:
Switch Type
Uplink Designation
MS Switches and Catalyst Switches (CS software)
The presence of default_gateway automatically designates the interface as the uplink. uplink_v4 / uplink_v6 tags are not required.
Catalyst Switches (IOS-XE software)
The uplink type must be explicitly declared. The required fields depend on the uplink type:
For Catalyst Switches (IOS-XE), the following fields are required based on uplink type:
Example-1: The example below demonstrates switch stack routing interfaces configuration including uplink designation and static DNS configuration.
This configuration creates Layer 3 routing interfaces on switch stacks for inter-VLAN routing and gateway services. The example includes subnet assignment, VLAN associations, routing parameters, uplink designation, static DNS configuration, and IPv6-only interfaces.
The switch stack named DEV_CORE includes five routing interfaces:
CORP on subnet 100.65.10.0/24 with IP 100.65.10.1 and VLAN 10. Multicast routing is enabled, participates in OSPF area 0 as a passive interface, and acts as a DHCP server with a 30-minute lease using Google Public DNS.
BMS on subnet 100.65.20.0/24 with IP 100.65.20.1 and VLAN 20. Same OSPF and DHCP configuration as CORP.
P2P on subnet 100.65.2.0/24 with IP 100.65.2.1 and VLAN 2. Designated as a dual-stack uplink (uplink_v4: true, uplink_v6: true) with default gateway 100.65.2.2, static IPv4 DNS servers (8.8.8.8, 8.8.4.4), and static IPv6 configuration with gateway and DNS servers. This is the required configuration for Catalyst switches running IOS-XE. Active in OSPF area 0 with DHCP disabled.
MGMT on subnet 100.65.30.0/24 with IP 100.65.30.1 and VLAN 30. Standard IPv4-only interface, not an uplink, passive OSPF, DHCP disabled.
IPV6_ONLY on VLAN 40. IPv6-only interface with static assignment, no uplink designation, and DHCP disabled.
Switch stack routing interfaces configuration in Meraki networks provides administrators with comprehensive Layer 3 connectivity and inter-VLAN routing capabilities for stacked switches, enabling VLAN interface creation, IP address assignment, DHCP service management, and OSPF routing integration. This functionality supports network segmentation, subnet routing, multicast forwarding, and centralized DHCP services across the switch stack. Stack routing interfaces are essential for creating routed networks, enabling inter-VLAN communication, providing DHCP services, and integrating with dynamic routing protocols in enterprise network architectures.
Example-1: The example below demonstrates switch stack routing interfaces configuration.
This configuration creates Layer 3 routing interfaces on switch stacks for inter-VLAN routing and gateway services. The example includes subnet assignment, VLAN associations, and routing parameters for stack-based Layer 3 functionality.
The switch stack named DEV_CORE includes two routing interfaces: CORP on subnet 100.65.10.0/24 with IP 100.65.10.1 and VLAN 10, and BMS on subnet 100.65.20.0/24 with IP 100.65.20.1 and VLAN 20. Both interfaces have multicast routing enabled, participate in OSPF area 0 with a cost of 1, and are set as passive interfaces. Additionally, the CORP interface acts as a DHCP server with a 30-minute lease time and uses Google Public DNS servers, while boot options are disabled.