Delivery service set
Delivery service set allows you to create delivery services such as the Internet, Intranet, and so on. These delivery services are defined at a global level and applied to WAN links in individual sites, as applicable. Each WAN link can apply all or a subset of relevant services, and setup relative shares of bandwidth (%) among all the delivery services. Virtual Path service is available on all the links by default. The other services can be added on a need basis.
To configure intranet or internet services:
Navigate to the customer configuration dashboard. Go to Configuration > Delivery Service Set.
An internet service is created by default. The branch traffic uses the transit sites to reach the internet.
Click Add Service and select a Service Type. Depending on the add-on delivery service that you would like to create, choose the required service type, and proceed with the configuration.
Internet Service definition is made available by default as part of the Delivery service set. Internet transit sites can be configured to enable Internet access to the sites which do not have direct internet connectivity.
Cost: Route cost for internet service traffic.
Transit sites: Add sites as Internet transit sites to enable Internet access to the sites which do not have direct Internet connectivity.
Each transit site can be assigned a route cost. The sites with internet service available will access the internet directly since the direct route would be the lowest cost routing path. Sites without internet service can route to the internet through the configured transit sites. When the internet transit sites are configured, routes to the internet through these transit sites automatically get pushed to all the sites.
For example, let’s say San Francisco and New York are configured as internet transit sites. Routes to the internet via San Francisco and New York automatically get pushed to all the sites.
A user can create multiple intranet services. Once the intranet service is created at the global level, you can reference it at the WAN Link level.
Provide a Service Name. Select desired Routing Domain and Firewall Zone.
Intranet networks: Add all the intranet IP addresses across the network, that other sites in the network might need to talk to.
Intranet transit sites: Add sites as transit sites to enable all the non-intranet sites to access the intranet networks configured. Each transit site can be assigned a route cost. The available sites with intranet service will access the intranet networks directly since the direct route would be the lowest cost routing path. Sites without intranet service can route to the intranet networks through the configured transit sites. When the transit sites are configured, routes to intranet networks through these transit sites automatically get pushed to all the sites.
For example, assume 10.2.1.0/24 is an intranet network, and Austin and Dallas are configured as transit sites. Routes to that network address through Austin and Dallas automatically get pushed to all the sites.
If you are configuring Zscaler service, configure LAN GRE. Provide a service name. Select the routing domain, firewall zone. Add site bindings. For more information about Zscaler service, see Zscaler Integration by using GRE tunnels and IPsec tunnels.
Provide service name and select service type. Configure required IPsec parameters. For more information, see How to configure IPsec tunnels for virtual and dynamic paths topic.