Skip to main content
Cisco Meraki

IPv6 Support on MX Security & SD-WAN Platforms - Routing

Routing

There are several routing decisions that MX perform:

Uplink Selection 

This option determines which uplink should be the primary connection (IPv4 only). VPN traffic and management traffic to the Meraki Dashboard use the primary uplink. If load balancing is disabled, all traffic will use the primary uplink unless an uplink preference is configured specifying otherwise. For IPv6 traffic, regardless of the primary uplink and load balancing selections, flows will be routed via the source origin. During a failover event, the MX will use NAT and NPTv6 to forward traffic via the active interface.

Configuration:

  • Browse to Security & SD-WAN > SD-WAN & Traffic Shaping > Uplink selection > Primary uplink > select WAN

Static Routes

MX supports IPv4 and IPv6 static routes. With IPv6, you can configure a static route using a Global or Link-Local IPv6 address.

Configuration:

    • From the Addressing & VLANs page click Add Static Route button

    • Select IPv6 for the IP version and configure the IPv6 Prefix and Next Hop IP

  • Click the update button and Save the changes to commit the configuration

Note:

  • The Next hop IP must belong to an already configured prefix on the LAN/VLANs configuration.

    • From the Addressing & VLANs page, click Add Static Route button

    • Select IPv6 for the IP version and configure the IPv6 Prefix and Next Hop IP

    • When a Link-Local IP is used, the MX will prompt for a “Next hop VLAN”

  • Select the appropriate VLAN where the downstream next hop Link-Local IP address belongs to and click update

  • Save the configuration to commit the change made

 

 

Refer to the main KB: IPv6 Support on MX Security & SD-WAN Platforms [Core Fundamentals]

  • Was this article helpful?