Describes the notes, limitations, and restrictions that apply to traffic flow monitoring functionality.
The following sections describe notes, limitations, and restrictions related to traffic flow monitoring.
Cisco Catalyst SD-WAN Policies Configuration Guide, Releases 26.x and Later
Is this content helpful?
Thank you for your feedback. Your response has been recorded.
AI responses are currently only available to logged in users. Log in
Important. Results generated by AI. Before using results, verify accuracy and completeness.
Only ask questions about this document. To ask questions about this product as a whole, go to Technical Documentation .
Suggestions
Sorry, we couldn't generate a response for this query.
Launch error. Something went wrong. Please try again.
Cisco Catalyst SD-WAN Policies Configuration Guide, Releases 26.x and Later
Updated: April 24, 2026
Want to summarize with AI?
Log inImportant. Results generated by AI. Before using results, verify accuracy and completeness.
Describes the notes, limitations, and restrictions that apply to traffic flow monitoring functionality.
The following sections describe notes, limitations, and restrictions related to traffic flow monitoring.
Consider these restrictions when enabling collect loopback in flow telemetry with loopback TLOCs:
Supports configuration only through the Cisco Catalyst SD-WAN Controller CLI or Cisco SD-WAN Manager CLI-template. Feature template is not supported for this release.
Collect loopback in FNF VPN0 interfaces is not supported.
Collect loopback in the Decidated Internet Acccess (DIA) scenario, is not supported.
Multi-tenant scenario is not supported.
All IP or IPv6 visibility features are sub-features to flow-visibility and app-visibility. You must enable flow-visibility or app-visibility before enabling the sub-features.
Need help?
(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.