Legal Disclaimer: The resource assets in this website may include abbreviated and/or legacy terminology for HPE Aruba Networking products. See www.arubanetworks.com for current and complete HPE Aruba Networking product lines and names.
Aruba Central Online Help
The following sections explain the process to configure SaaS Express to route the SaaS application traffic to the best available path.
The following steps provide a brief description of the task purpose in each step:
- Configuring an SLA Profile—Set a threshold value for the latency, jitter, packet loss, and uplink utilization parameters.
- Configuring an Exit Profile—Define a primary link for all SaaS application traffic, and secondary and tertiary uplinks as fallback options, if the primary path does not meet the criteria for configured SLA of the SaaS application.
- Configuring DNS Servers for Path Exit—Specify the Branch Gateway as the DNS Domain Name System. A DNS server functions as a phone book for the intranet and Internet users. It converts human-readable computer host names into IP addresses and IP addresses into host names. It stores several records for a domain name such as an address 'A' record, name server (NS), and mail exchanger (MX) records. The Address 'A' record is the most important record that is stored in a DNS server, because it provides the required IP address for a network peripheral or element. server for SaaS application FQDN Fully Qualified Domain Name. FQDN is a complete domain name that identifies a computer or host on the Internet. resolution by defining the DNS server for that uplink.
- Configuring the SaaS Express Policy—Create a policy for a SaaS application that is present in HPE Aruba Networking Central using the parameters defined in the first three steps.
For information about monitoring the SaaS application performance, see SaaS Express Monitoring Dashboards
