To add and configure the routes for the site, do the following:
Continuing in the Connections tree for the new MCN site, click + to the left of Routes.
This displays the Routes table for the site.
2. Click + to the right of the Routes branch to add a route.
This opens the Routes table for editing and adds a blank route entry to the table (top entry).
3. Enter the route configuration information for the new route.
Enter the following:
- Network IP Address – Enter the Network IP Address.
- Cost – Enter a weight from 1 to 15 for determining the route priority for this route. Lower-cost routes take precedence over higher-cost routes. The default value is 5.
- Service Type – Select the service type for the route from the drop-down menu for this field. The options are as follows:
* Virtual Path – This service manages traffic across the Virtual Paths. A Virtual Path is a logical link between two WAN links. It comprises a collection of WAN Paths combined to provide high service-level communication between two SD-WAN nodes. This is accomplished by constantly measuring and adapting to changing application demand and WAN conditions. SD-WAN Appliances measure the network on a per-path basis. A Virtual Path can be static (always exists) or dynamic (exists only when traffic between two SD-WAN Appliances reaches a configured threshold).
* Internet – This service manages traffic between an Enterprise site and sites on the public Internet. Traffic of this type is not encapsulated. During times of congestion, the SD-WAN actively manages bandwidth by rate-limiting Internet traffic relative to the Virtual Path, and Intranet traffic according to the SD-WAN configuration established by the Administrator.
* Intranet – This service manages Enterprise Intranet traffic that has not been defined for transmission across a Virtual Path. As with Internet traffic, it remains unencapsulated, and the SD-WAN manages bandwidth by rate-limiting this traffic relative to other service types during times of congestion. Note that under certain conditions, and if configured for Intranet Fallback on the Virtual Path, traffic that ordinarily travels by means of a Virtual Path may instead be treated as Intranet traffic, in order to maintain network reliability.
* Passthrough – This service manages traffic that is to be passed through the Virtual WAN. Traffic directed to the Passthrough Service includes broadcasts, ARPs and other non-IPv4 traffic, as well as traffic on the Virtual WAN Appliance local subnet, specifically-configured subnets, or Rules applied by the Network Administrator. This traffic is not delayed, shaped or modified by the SD-WAN. Consequently, you must ensure that Passthrough traffic does not consume substantial resources on the WAN links that the SD-WAN Appliance is configured to use for other services.
* Local – This service manages IP traffic local to the site that matches no other service. SD-WAN ignores traffic sourced and destined to a local route.
* GRE Tunnel – This service manages IP traffic destined for a GRE tunnel, and matches the LAN GRE tunnel configured at the site. The GRE Tunnel feature enables you to configure SD-WAN Appliances to terminate GRE tunnels on the LAN. For a route with service type GRE Tunnel, the gateway must reside in one of the tunnel subnets of the local GRE tunnel.
- Gateway IP Address – Enter the Gateway IP Address for this route.
4. Click + to the left of the new entry.
This opens the Eligibility Settings form for the route.
5. Enter the route Eligibility settings.
The settings are as follows:
- Next Hop Site – This indicates the remote site to which Virtual Path packets will be directed.
- Eligibility Based on Path (checkbox) – (Optional) If enabled, the route will not receive traffic when the selected path is down.
- Path – This specifies the path to be used for determining route eligibility.
9. Click Apply.
10. To add more routes for the site, click + to the right of the Routes branch, and proceed as above.
You have now finished entering the primary configuration information for the new MCN site. The following two sections provide instructions for additional optional steps:
If you do not want to configure these features at this time, you can proceed directly to the section Naming, Saving, and Backing Up the MCN Site Configuration.