Topology Group
Catalyst SD-WANTopology groups are used to organize and activate or push control policies like custom, hub spoke and mesh created under topology profiles to the SD-WAN controllers. Only one topology group can be active at a time.
A topology profile needs a topology group to be deployed properly, so profiles and groups map one to one: the group has the same name and description as the profile it references.
Topology groups are used to organize and activate or push control policies like custom, hub spoke and mesh created under topology profiles to the SD-WAN controllers. Only one topology group can be active at a time.
Diagram
Section titled “Diagram”Classes
Section titled “Classes”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| topology_groups | List | topology_groups | No |
topology_groups (sdwan)
Section titled “topology_groups (sdwan)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[^&<>! "]{1,128}$ | Yes | |
| description | String | No | ||
| activate | Boolean | true, false | No | |
| topology_ | String | Regex: ^[^&<>! "]{1,128}$ | Yes |
Examples
Section titled “Examples”Example-1: This example demonstrates creating a topology group that references a topology profile and activates it. The topology group name must match the referenced topology profile name. The policy targets SITE_100 and SITE_200 by name; groups and regions from the network hierarchy can be used instead (see the Topology Custom Policy page).
sdwan: topology_groups: - name: prod_topology description: production topology topology_profile: prod_topology activate: true feature_profiles: topology_profiles: - name: prod_topology description: production topology custom_policies: - name: route_control default_action: reject level: sites inbound_sites: - SITE_100 outbound_sites: - SITE_200 sequences: - sequence_id: 1 sequence_name: accept_all base_action: accept type: route protocol: ipv4Note: In the above example, the referenced
topology_profilemust be defined undersdwan.feature_profiles.topology_profileswith at least one policy (custom_policies, hub_spoke_policies, or mesh_policies). Conversely, every topology profile needs a topology group; define both together, as above.
Example-2: This example demonstrates a topology group with activate set to false (topology is configured but not pushed to controllers).
sdwan: topology_groups: - name: staging_topology description: staging topology topology_profile: staging_topology activate: falseExamples
Section titled “Examples”Example-1: This example demonstrates creating a topology group that references a topology profile and activates it. The topology group name must match the referenced topology profile name.
sdwan: topology_groups: - name: prod_topology description: production topology topology_profile: prod_topology activate: true feature_profiles: topology_profiles: - name: prod_topology description: production topology custom_policies: - name: route_control default_action: reject level: sites inbound_sites: - SITE_100 outbound_sites: - SITE_200 sequences: - sequence_id: 1 sequence_name: accept_all base_action: accept type: route protocol: ipv4Note: In the above example, the referenced
topology_profilemust be defined undersdwan.feature_profiles.topology_profileswith at least one policy (custom_policies, hub_spoke_policies, or mesh_policies).
Example-2: This example demonstrates a topology group with activate set to false (topology is configured but not pushed to controllers).
sdwan: topology_groups: - name: staging_topology description: staging topology topology_profile: staging_topology activate: false