Skip to content

Switch Stacks Routing Static Routes Configuration

Dashboard Location: Switching > Switch Stacks > [Stack Name] > Routing & DHCP > Static Routes

Switch stack routing static routes configuration in Meraki networks provides administrators with comprehensive manual routing control and network path specification capabilities for stacked switches, enabling custom route definitions, traffic steering, network segmentation, and integration with dynamic routing protocols. This functionality supports multi-homed connectivity, policy-based routing, network redundancy, and granular traffic control across the switch stack. Static routes are essential for connecting to remote networks, creating backup paths, implementing routing policies, and ensuring connectivity to networks not reachable through dynamic routing protocols.

Diagram

switch_stacks (meraki.domains.organizations.networks)

Section titled “switch_stacks (meraki.domains.organizations.networks)”
NameTypeConstraintMandatoryDefault Value
routing_static_routesList[routing_static_routes]No

routing_static_routes (meraki.domains.organizations.networks.switch_stacks)

Section titled “routing_static_routes (meraki.domains.organizations.networks.switch_stacks)”
NameTypeConstraintMandatoryDefault Value
nameStringmin: 1, max: 127No
subnetStringRegex: ^((25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9]?[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9]?[0-9])\/([1-9]|[12][0-9]|3[0-2])$No
next_hop_ipIPNo
advertise_via_ospfBooleantrue, falseNo
prefer_over_ospf_routesBooleantrue, falseNo
management_next_hopIPNo

Example-1: The example below demonstrates switch stack static routing configuration using tested YAML configuration from pipeline fixtures.

meraki:
domains:
- name: !env domain
administrator:
name: !env org_admin
organizations:
- name: !env org
networks:
- name: !env network_name
product_types:
- appliance
- switch
- wireless
- camera
- sensor
- cellularGateway
switch_stacks:
- name: DEV_CORE
routing_static_routes:
- name: Server Network
subnet: 10.100.100.0/24
next_hop_ip: 100.65.2.3
advertise_via_ospf: false
prefer_over_ospf_routes: false
- name: IOT Network
subnet: 100.200.100.0/24
next_hop_ip: 100.65.2.4
advertise_via_ospf: false
prefer_over_ospf_routes: false