Routing Configuration Guide, Cisco Catalyst SD-WAN Releases 17.x

OMP paths

Updated: February 6, 2026

Overview

Discusses the exchange of TLOC information and the configurable limits on the number of paths shared between controllers.

The transport location (TLOC) information is advertised to the OMP peers including Cisco Catalyst SD-WAN Controller and its local-site branches. From Cisco IOS XE Catalyst SD-WAN Release 17.5.1a, the limit on the number of OMP paths that can be exchanged between Cisco Catalyst SD-WAN Controllers per VPN per prefix is extended to a maximum of 128.

Configure path limit using CLI commands

Configure the number of paths a Cisco Catalyst SD-WAN Controller can send to another Cisco Catalyst SD-WAN Controller.

Before you begin

Ensure OMP send-path-limit is set to a value equal to or greater than the number of TLOCs used for any advertised prefix.

Procedure

	1.	Create a CLI add-on profile or a CLI add-on template.
	2.	Enter the omp mode. `# omp`
	3.	Use the controller-send-path-limit command to configure the send path limit to be exchanged between Cisco Catalyst SD-WAN Controllers. You can configure a maximum of 128 send path limit. `# controller-send-path-limit <path-limit>` Example: `# controller-send-path-limit 100` Use the no form of this command to set the send path limit to default. The default configuration enables the controllers to send the information of all the paths available up to maximum of 128. Note We recommend using the default configuration, which sends information about all available paths, subject to a limit of 128 paths. This ensures that you have network visibility across controllers. We recommend not to change the path limit frequently. For any changes on the peers, Cisco Catalyst SD-WAN Controller performs a full route database update. This leads to complete network updates. For more information about configuring path limits, see controller-send-path-limit command page.

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.