Product Documentation
Citrix SD-WAN
Current Release 11.5 limited availability 11.3 11.2 11.1 11.0 10.2
View PDF

Multi-region deployment

March 12, 2021
Contributed by: 
S C

An SD-WAN appliance configured as Master Control Node (MCN) supports multi-region deployment. The MCN manages multiple Regional Control Nodes (RCNs). Each RCN, in turn, manages multiple client sites. The MCN can also be used to manage some of the client sites directly.

With MCN as the control node of the network and RCNs as the control nodes of the regions, SD-WAN can manage up to 6000 sites.

Multi-region deployment enables you to fragment a network into regions and set up a tiered network; such as branch (client) > RCN > MCN.

An MCN with a single region can be configured with a maximum of 550 sites. You can keep the existing sites in the default region and add new regions with RCNs and their sites for multi-region deployment.

Multi-region deployment topology

The following table provides the list of platforms supported for configuring primary and secondary MCN/RCN.

NOTE

  • The Premium Edition (PE) appliance is formerly known as the Enterprise Edition (EE).

  • Use the Citrix SD-WAN 210 SE appliance as an MCN only in the SD-WAN Orchestrator managed networks.

Platform Edition Primary/Secondary MCN Primary/Secondary RCN
110-SE No No
210-SE Yes Yes
400-SE Yes No
410-SE Yes No
1000-SE, 1000-PE Yes No
1100-SE, 1100-PE Yes Yes
VPX-SE, VPXL-SE Yes Yes
2000-SE, 2100-SE, 2000-PE, 2100-PE, 4000-SE, 4100-SE, 5100-SE, 5100-PE, 6100-SE Yes Yes

To configure multi-region deployment for an SD-WAN network:

  1. Navigate to the Global tab in the Configuration Editor. Select Regions. The default region configuration options are displayed.

    You can change the name and description for the default region by editing it.

  2. Click + Add to add a new region.

    Add region in multi-region Deployment

    Add region

  3. Enter a Name and Description for the region.

  4. Enable Internal VIP matching based on whether you want Forced Internal VIP Matching or Allow External VIP Matching.

    • Forced Internal VIP: When enabled, all non-private Virtual IP addresses in the Region are forced to match the configured subnets.

    • Allowed External VIP - When enabled, non-private Virtual IP addresses from other regions is allowed to match the configured subnets.

  5. Click + to add subnets. Choose a routing domain.

    Add subnets

  6. Enter a Network address. Click Add. The network address is the IP address and mask for the subnet. The newly created region is added to the existing list of regions.

    You can select the Default check box to use a desired region as the Default.

    Default region

    Note

    You can clone MCN to a GEO or client site.

SD-WAN Center supports multi-region deployment. For more information, see SD-WAN Center Multi-Region Deployment and Reporting.

Change management summary view

When you perform the Change Management process for appliances configured in multi-region deployment, the change management summary table is displayed in the SD-WAN appliance GUI.

The Region column displays a list of regions currently configured in the network. You can view the change management summary for a specific region by selecting it in the summary table.

Default region summary:

Region summary table

Region Summary:

AMEA region summary

Note

In some instances, the Total Sites value displayed in the Global Multi-Region Summary table is less than the sum of the remaining columns.

For example, when a branch node is not connected, it is possible that the branch is counted twice; once as “Not Connected” and once as “Preparing/Staging.”

Multi-region deployment
March 12, 2021
Contributed by: 
S C
March 12, 2021
Contributed by: 
S C

In this article

Site feedback | Your privacy choices footer linkYour Privacy Choices | Privacy and legal terms | Cookie preferences | Consent settings | docs.cloud.com
© 1999- Cloud Software Group, Inc. All rights reserved.