Route Tag Policy
Location in GUI: Tenants
» XXX
» Policies
» Protocol
» Route Tag
Diagram
Section titled “Diagram”Classes
Section titled “Classes”policies (apic.tenants)
Section titled “policies (apic.tenants)”Name | Type | Constraint | Mandatory | Default Value |
---|---|---|---|---|
route_tag_policies | List | [route_tag_policies] | No |
route_tag_policies (apic.tenants.policies)
Section titled “route_tag_policies (apic.tenants.policies)”Name | Type | Constraint | Mandatory | Default Value |
---|---|---|---|---|
name | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes | |
description | String | Regex: ^[a-zA-Z0-9\\!#$%()*,-./:;@ _{|}~?&+]{1,128}$ | No | |
tag | Integer | min: 0 , max: 4294967295 | No | 4294967295 |
Examples
Section titled “Examples”Example-1: This data model creates the Context1
tag and assigns it a value of 112233
. When applied to a specific VRF, it attaches a 32-bit tag to routes during redistribution into supported protocols. This tag serves as an identifier to prevent routing loops. Additionally, Route Tag Policies allow customization of the tag value on a per-VRF basis, which is essential in multi-VRF environments where transit routes are learned from multiple VRFs.
apic: tenants: - name: ABC policies: route_tag_policies: - name: Context1 description: "My Tag" tag: 112233