Configure a next hop static route with tracker

Updated: April 24, 2026

Want to summarize with AI?

Use the VPN template to associate a tracker to a static route next hop. You can apply only one tracker per static route next hop.

Procedure

From the Cisco SD-WAN Manager menu, choose Configuration > Templates.

Click Feature Templates and navigate to Cisco VPN Template for the device.

For information about creating a VPN template, see Create VPN Template.

Enter Template Name and Description as required.

In Basic Configuration, by default, VPN is set to 0. Set a VPN value within (1–511, 513–65530) range for service VPNs, for service-side data traffic on Cisco IOS XE Catalyst SD-WAN devices.

You can configure static route tracker only on service VPNs.

Click IPv4 Route and New IPv4 Route.

In the IPv4 Prefix field, enter a value.

Click Next Hop. Click Add Next Hop with Tracker and enter values for the fields listed in the table.


Parameter Name	Description
Address	Specify the next-hop IPv4 address.
Distance	Specify the administrative distance for the route.
Tracker	Enter the name of the gateway tracker to determine whether the next hop is reachable before adding that route to the route table of the device.
Add Next Hop with Tracker.	Enter the name of the gateway tracker with the next hop address to determine whether the next hop is reachable before adding that route to the route table of the device.

Click Add and Save to create the static route with the next-hop tracker.

You need to fill all the mandatory fields in the form to save the VPN template.

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.