Mesh Topology Definition
Mesh is one type of topology in which each of the device is allowed to send and receive data traffic to any other device.
Mesh Topology Definition define the mesh sites that should create the mesh connections between them.
Diagram
Section titled “Diagram”Classes
Section titled “Classes”control_policy (sdwan.centralized_policies.definitions)
Section titled “control_policy (sdwan.centralized_policies.definitions)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| mesh_topology | List | [mesh_topology] | No |
mesh_topology (sdwan.centralized_policies.definitions.control_policy)
Section titled “mesh_topology (sdwan.centralized_policies.definitions.control_policy)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| description | String | Yes | ||
| vpn_list | String | Regex: ^[A-Za-z0-9\-_]{1,32}$ | Yes | |
| mesh_groups | List | [mesh_groups] | Yes |
mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)
Section titled “mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| site_lists | List | String[Regex: ^[A-Za-z0-9\-_]{1,32}$] | No |
Examples
Section titled “Examples”Example-1: Mesh Topology for Secure Intra-VPN Communication
A customer operating a distributed enterprise network wants to ensure seamless and direct communication between branches without traffic hair-pinning through the data center. To achieve this, the customer defines a mesh topology under a centralized control policy for VPN 10, which connects all branch sites participating in shared services. This mesh topology will allow branch sites to dynamically form secure tunnels with each other, improving performance and reducing latency. The mesh group includes a site list representing the group of branches to be meshed together. This configuration enables secure, scalable, and resilient inter-site communication within the selected VPN.
The YAML defines a control policy that includes a mesh topology named BranchMeshTopology, tailored for VPN 10. The policy description outlines that it enables full mesh connectivity between all branches listed. It includes a single mesh group named BranchGroupMesh which aggregates branches defined under the site list BranchSites. This setup ensures that all the listed sites can directly establish IPsec tunnels with each other, eliminating dependency on hub sites and promoting high availability.
sdwan: centralized_policies: definitions: control_policy: mesh_topology: - name: Global_Mesh description: Full mesh topology for inter-office communication vpn_list: VPN_10 mesh_groups: - name: Global_Offices site_lists: - New_York - London - TokyoMesh is one type of topology in which each of the device is allowed to send and receive data traffic to any other device.
Mesh Topology Definition define the mesh sites that should create the mesh connections between them.
Diagram
Section titled “Diagram”Classes
Section titled “Classes”control_policy (sdwan.centralized_policies.definitions)
Section titled “control_policy (sdwan.centralized_policies.definitions)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| mesh_topology | List | [mesh_topology] | No |
mesh_topology (sdwan.centralized_policies.definitions.control_policy)
Section titled “mesh_topology (sdwan.centralized_policies.definitions.control_policy)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| description | String | Yes | ||
| vpn_list | String | Regex: ^[A-Za-z0-9\-_]{1,32}$ | Yes | |
| mesh_groups | List | [mesh_groups] | Yes |
mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)
Section titled “mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| site_lists | List | String[Regex: ^[A-Za-z0-9\-_]{1,32}$] | No |
Examples
Section titled “Examples”Example-1: Mesh Topology for Secure Intra-VPN Communication
A customer operating a distributed enterprise network wants to ensure seamless and direct communication between branches without traffic hair-pinning through the data center. To achieve this, the customer defines a mesh topology under a centralized control policy for VPN 10, which connects all branch sites participating in shared services. This mesh topology will allow branch sites to dynamically form secure tunnels with each other, improving performance and reducing latency. The mesh group includes a site list representing the group of branches to be meshed together. This configuration enables secure, scalable, and resilient inter-site communication within the selected VPN.
The YAML defines a control policy that includes a mesh topology named BranchMeshTopology, tailored for VPN 10. The policy description outlines that it enables full mesh connectivity between all branches listed. It includes a single mesh group named BranchGroupMesh which aggregates branches defined under the site list BranchSites. This setup ensures that all the listed sites can directly establish IPsec tunnels with each other, eliminating dependency on hub sites and promoting high availability.
sdwan: centralized_policies: definitions: control_policy: mesh_topology: - name: Global_Mesh description: Full mesh topology for inter-office communication vpn_list: VPN_10 mesh_groups: - name: Global_Offices site_lists: - New_York - London - TokyoMesh is one type of topology in which each of the device is allowed to send and receive data traffic to any other device.
Mesh Topology Definition define the mesh sites that should create the mesh connections between them.
Diagram
Section titled “Diagram”Classes
Section titled “Classes”control_policy (sdwan.centralized_policies.definitions)
Section titled “control_policy (sdwan.centralized_policies.definitions)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| mesh_topology | List | [mesh_topology] | No |
mesh_topology (sdwan.centralized_policies.definitions.control_policy)
Section titled “mesh_topology (sdwan.centralized_policies.definitions.control_policy)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| description | String | Yes | ||
| vpn_list | String | Regex: ^[A-Za-z0-9\-_]{1,32}$ | Yes | |
| mesh_groups | List | [mesh_groups] | Yes |
mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)
Section titled “mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| site_lists | List | String[Regex: ^[A-Za-z0-9\-_]{1,32}$] | No |
Examples
Section titled “Examples”Example-1: Mesh Topology for Secure Intra-VPN Communication
A customer operating a distributed enterprise network wants to ensure seamless and direct communication between branches without traffic hair-pinning through the data center. To achieve this, the customer defines a mesh topology under a centralized control policy for VPN 10, which connects all branch sites participating in shared services. This mesh topology will allow branch sites to dynamically form secure tunnels with each other, improving performance and reducing latency. The mesh group includes a site list representing the group of branches to be meshed together. This configuration enables secure, scalable, and resilient inter-site communication within the selected VPN.
The YAML defines a control policy that includes a mesh topology named BranchMeshTopology, tailored for VPN 10. The policy description outlines that it enables full mesh connectivity between all branches listed. It includes a single mesh group named BranchGroupMesh which aggregates branches defined under the site list BranchSites. This setup ensures that all the listed sites can directly establish IPsec tunnels with each other, eliminating dependency on hub sites and promoting high availability.
sdwan: centralized_policies: definitions: control_policy: mesh_topology: - name: Global_Mesh description: Full mesh topology for inter-office communication vpn_list: VPN_10 mesh_groups: - name: Global_Offices site_lists: - New_York - London - TokyoMesh is one type of topology in which each of the device is allowed to send and receive data traffic to any other device.
Mesh Topology Definition define the mesh sites that should create the mesh connections between them.
Diagram
Section titled “Diagram”Classes
Section titled “Classes”control_policy (sdwan.centralized_policies.definitions)
Section titled “control_policy (sdwan.centralized_policies.definitions)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| mesh_topology | List | [mesh_topology] | No |
mesh_topology (sdwan.centralized_policies.definitions.control_policy)
Section titled “mesh_topology (sdwan.centralized_policies.definitions.control_policy)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| description | String | Yes | ||
| vpn_list | String | Regex: ^[A-Za-z0-9\-_]{1,32}$ | Yes | |
| mesh_groups | List | [mesh_groups] | Yes |
mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)
Section titled “mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| site_lists | List | String[Regex: ^[A-Za-z0-9\-_]{1,32}$] | No |
Examples
Section titled “Examples”Example-1: Mesh Topology for Secure Intra-VPN Communication
A customer operating a distributed enterprise network wants to ensure seamless and direct communication between branches without traffic hair-pinning through the data center. To achieve this, the customer defines a mesh topology under a centralized control policy for VPN 10, which connects all branch sites participating in shared services. This mesh topology will allow branch sites to dynamically form secure tunnels with each other, improving performance and reducing latency. The mesh group includes a site list representing the group of branches to be meshed together. This configuration enables secure, scalable, and resilient inter-site communication within the selected VPN.
The YAML defines a control policy that includes a mesh topology named BranchMeshTopology, tailored for VPN 10. The policy description outlines that it enables full mesh connectivity between all branches listed. It includes a single mesh group named BranchGroupMesh which aggregates branches defined under the site list BranchSites. This setup ensures that all the listed sites can directly establish IPsec tunnels with each other, eliminating dependency on hub sites and promoting high availability.
sdwan: centralized_policies: definitions: control_policy: mesh_topology: - name: Global_Mesh description: Full mesh topology for inter-office communication vpn_list: VPN_10 mesh_groups: - name: Global_Offices site_lists: - New_York - London - TokyoMesh is one type of topology in which each of the device is allowed to send and receive data traffic to any other device.
Mesh Topology Definition define the mesh sites that should create the mesh connections between them.
Diagram
Section titled “Diagram”Classes
Section titled “Classes”control_policy (sdwan.centralized_policies.definitions)
Section titled “control_policy (sdwan.centralized_policies.definitions)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| mesh_topology | List | [mesh_topology] | No |
mesh_topology (sdwan.centralized_policies.definitions.control_policy)
Section titled “mesh_topology (sdwan.centralized_policies.definitions.control_policy)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| description | String | Yes | ||
| vpn_list | String | Regex: ^[A-Za-z0-9\-_]{1,32}$ | Yes | |
| mesh_groups | List | [mesh_groups] | Yes |
mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)
Section titled “mesh_groups (sdwan.centralized_policies.definitions.control_policy.mesh_topology)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| name | String | Regex: ^[A-Za-z0-9\-_]{1,127}$ | Yes | |
| site_lists | List | String[Regex: ^[A-Za-z0-9\-_]{1,32}$] | No |
Examples
Section titled “Examples”sdwan: centralized_policies: definitions: control_policy: mesh_topology: - name: MT_DEFINITION_TEST1 description: MT_DEFINITION_TEST1 vpn_list: VPN-LIST-MT-TEST1 mesh_groups: - name: MESH-REGION-TEST1 site_lists: - PHOENIX-MT-TEST - HOSUTON-MT-TEST - name: MESH-REGION-TEST2 site_lists: - MADISON-MT-TEST - KANSAS-MT-TEST