Skip to content

Switch Stacks Routing Static Routes Configuration

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

Switch Stack Static Route Management

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

Diagram

Classes

switch_stacks (meraki.domains.organizations.networks)

NameTypeConstraintMandatoryDefault Value
routing_static_routesList[routing_static_routes]No

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

Examples

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

Configuration Parameters

ParameterTypeRequiredDescription
routing_static_routesarrayNoList of static route configurations
routing_static_routes[].namestringYesDescriptive name for the static route
routing_static_routes[].subnetstringYesDestination subnet in CIDR notation
routing_static_routes[].next_hop_ipstringYesIP address of the next-hop gateway
routing_static_routes[].advertise_via_ospfbooleanNoAdvertise this route via OSPF (true/false)
routing_static_routes[].prefer_over_ospf_routesbooleanNoPrefer static route over OSPF learned routes (true/false)

Route Planning Guidelines

Route TypeSubnet ExampleUse CaseOSPF Advertisement
Host Route10.1.1.1/32Specific serverUsually no
Network Route192.168.100.0/24Department networkUsually yes
Aggregate Route10.0.0.0/8Large network blockYes (summarization)
Default Route0.0.0.0/0Internet gatewayRarely
Management10.10.10.0/24Out-of-band mgmtUsually no

OSPF Integration Strategies

StrategyAdvertise OSPFPrefer Over OSPFUse Case
Static PrimaryYesTruePreferred path
Static BackupNoFalseBackup only
Policy RouteNoTrueTraffic engineering
Summary RouteYesFalseRoute aggregation

Network Design Patterns

PatternDescriptionConfigurationBenefits
Primary/BackupRedundant pathsMultiple routes same destHigh availability
Traffic EngineeringPath controlPrefer over OSPFOptimized routing
Network IsolationSegmented routingNo OSPF advertisementSecurity boundary
Default GatewayInternet access0.0.0.0/0 routeSimplified routing