VPN BGP Configuration

Dashboard Location: Security and SD-WAN > Configure > Site-to-site VPN

BGP Routing Protocol Management

VPN BGP configuration in Meraki appliances enables dynamic routing protocol support for site-to-site VPN connections through Border Gateway Protocol (BGP). This functionality allows external automatic route advertisement and learning from VPN enabled networks, supporting complex network topologies with redundant paths and dynamic failover capabilities. BGP integration is essential for organizations requiring scalable routing, multi-homed connections, and advanced traffic engineering across their VPN infrastructure while maintaining automated route convergence and network resilience.

Diagram

Classes

meraki

Name	Type	Constraint	Mandatory	Default Value
domains	List	domains	No

domains (meraki)

Name	Type	Constraint	Mandatory	Default Value
organizations	List	organizations	Yes

organizations (meraki.domains)

Name	Type	Constraint	Mandatory	Default Value
networks	List	networks	No

networks (meraki.domains.organizations)

Name	Type	Constraint	Mandatory	Default Value
appliance	Class	appliance	No

appliance (meraki.domains.organizations.networks)

Name	Type	Constraint	Mandatory	Default Value
vpn_bgp	Class	vpn_bgp	No

vpn_bgp (meraki.domains.organizations.networks.appliance)

Name	Type	Constraint	Mandatory
enabled	Boolean	`true`, `false`	Yes
as_number	Integer	min: `1`, max: `4294967295`	No
ibgp_hold_timer	Integer	min: `12`, max: `240`	No
neighbors	List	neighbors	No

neighbors (meraki.domains.organizations.networks.appliance.vpn_bgp)

Name	Type	Constraint	Mandatory
ip	IP		No
ipv6	IP		No
remote_as_number	Integer	min: `1`, max: `4294967295`	Yes
receive_limit	Integer	min: `0`, max: `2147483647`	No
allow_transit	Boolean	`true`, `false`	No
ebgp_hold_timer	Integer	min: `12`, max: `240`	Yes
ebgp_multihop	Integer	min: `1`, max: `255`	Yes
source_interface	String	min: `1`, max: `10`	No
next_hop_ip	IP		No
ttl_security	Boolean	`true`, `false`	No
password	String	min: `5`, max: `64`	No

Examples

Example-1: The example below demonstrates VPN BGP configuration using tested YAML configuration from pipeline fixtures.

This configuration enables BGP on the Meraki appliance with local AS number 65001 and establishes a VPN BGP session to a remote neighbor at 192.168.99.99 (AS 65002) via WAN1, using a next-hop of 192.168.10.1, with eBGP multihop set to 2 and a hold timer of 60 seconds, allowing dynamic route exchange and resilient connectivity over the VPN.

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
              appliance:
                vpn_bgp:
                  enabled: true
                  as_number: 65001
                  neighbors:
                    - remote_as_number: 65002
                      ip: 192.168.99.99
                      ebgp_hold_timer: 60
                      ebgp_multihop: 2
                      next_hop_ip: 192.168.10.1
                      source_interface: wan1