Configure the SaaS application to failover to a hub firewall pointing to a different SaaS
application destination if there are no healthy DIA links from the branch
firewall.
| Where Can I Use This? | What Do I Need? |
|---|
If your organization is leveraging a SaaS
application at a branch firewall location but the branch firewall
has no healthy DIA links to swap to, you can configure the hub firewall
as a failover alternative to maintain a healthy connection to your
SaaS application using a SaaS Quality profile pointing to a different
SaaS application destination.
If the SaaS application DIA
link health metric thresholds are exceeded and the branch firewall
has no healthy DIA links available, the link is swapped to the next hub
firewall for all new sessions. The existing session on the degraded
DIA link is not swapped over to the hub firewall.
For example,
say your branch and hub firewalls are located on opposite sides
of the country and access a SaaS cloud application deployed in a
cloud provider such as GCP. You can configure the hub firewall to
act as a failover in the event there are no healthy DIA links from
the branch firewall to the SaaS application. To accomplish this,
configure an identically named SaaS Quality profile on both the
branch and hub firewalls to automatically failover to the hub firewall
if no healthy DIA links are available from the branch firewall.
The SaaS Quality profile configured on the hub firewall to points
to the on-ramp location closest to the hub to take advantage of
local resources closest to it. This allows you flexibility in specifying
healthy failover paths and the ability to maintain accurate end-to-end
SaaS application monitoring data without congesting your network
bandwidth.
