IP SLA Tab

Configuration > Templates & Policies > TCAs > IP SLA

Monitoring > Performance > IP SLA Summary

Using a polling process, IP SLA (Internet Protocol Service Level Agreement) tracking provides the ability to generate specific actions in the network that are completely dependent on the state of an IP interface or tunnel. The goal is to prevent black-holed traffic. For example, associated IP subnets could be removed from the subnet table, and also from subnet sharing, if the LAN-side interfaces on an appliance go down.

This tab displays all of the IP SLA rules configured on the selected appliances. To add or modify rules, click the edit icon to the left of any row in the table. To view IP SLA trends over time for an interface or tunnel, click the Realtime and Historical Charts icon. You can view trends for both latency and loss.

IP SLA Monitor Use Cases

The following examples describe five basic use cases for IP SLA monitoring.

Example #1 – Ping via Interface

• Two passthrough tunnels configured for Internet breakout and High Availability.

• If the Primary passthrough tunnel goes down, traffic goes to Backup tunnel.

• The IP SLA Rule would look like this, with the same tunnel specified for the Down and Up Actions.

  

Example #2 – HTTP/HTTPS via Interface

• Two passthrough tunnels configured for Internet breakout and High Availability.

• If the Primary passthrough tunnel goes down, traffic goes to Backup tunnel.

• The IP SLA Rule would look like this, with the same tunnel specified for the Down and Up Actions.

  

• In the URL(s) field, the protocol identifier is required only when specifying HTTPS, as in https://www.google.com.

Example #3 – Monitor Interface

• On EdgeConnect - A, we want subnet advertising to be conditional on LAN0 being up.

• Its IP SLA Rule would look like this, with the Default Subnet Action being to resume advertising subnets.

  

  Example #4 – Monitor Interface (WAN0) to Ensure High Availability

• If WAN0 goes down on the VRRP Master, we want to decrease its Priority so that traffic goes to the VRRP Backup.

• Its IP SLA Rule would look like this, with the Default Subnet Action being to revert to the original Priority.

  

  NOTE: In this instance, the WAN0 interface was given the label MPLS to match the service to which it connected.

Example #5 – Monitor VRRP

• To monitor the VRRP router state, use VRRP Monitor and specify the interface on which the VRRP instance is configured.

  In this example, it is LAN0.

• Here we are looking at an instance where the VRRP role changes, but priority does not, for whatever reason.

• Its IP SLA Rule would look like this, with the Default Subnet Action being to revert to the original Priority.

  

  NOTE: In this instance, the WAN0 interface was given the label MPLS to match the service to which it connected.

• Another option would be to specify Down Action = Modify Subnet Metric. The Web UI automatically produces another field in which you can add a positive value to the current subnet metric. Up Action = Default Subnet Action would return the subnet metric to its original value.

  

IP SLA Edit Row

Use this dialog box to set rules to your IP SLA. Define the Monitor and Actions by completing the following steps.

Monitor

There are four options to choose from for a Monitor:

Based on the Monitor chosen, the Web UI displays the appropriate fields and options.

Actions

There are eight available Down Actions:

There are two default Up Actions:

NOTE: If a default Up Action is used, it must match the Down Action.

---