Single-region deployment

Regions allow you to define a network hierarchy with distributed management. A Region must define a Regional Control Node (RCN) which will take over functions performed by the Network Control Node (MCN) for its Region. The MCN is the controller for the Default Region.

Static and Dynamic Virtual Paths are not permitted between Regions. RCNs manage the traffic between Regions.

A single-region deployment in an SD-WAN network can support network sites less than 550.  

You can configure a default region in the Configuration Editor of the SD-WAN appliance GUI. The Basic editor is useful to create only a small network with MCN and Client SD-WAN nodes. For configuring a multi-region network with MCN, RCN, Clients, or advanced features, use other configuration options in the configuration editor.

To configure single-region deployment:

  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.

    Single-region deployment

  2. Edit the Default_Region to change the name and configure subnets.

  3. Enable Interval 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.

  4. Click + to add subnets.

    Add subnets in single-region deployment

  5. Select a Routing Domain, enter the Network address. Click Apply. The network address is the IP address and mask for the subnet.

Single-region deployment