Configure IP SLA Tracking for IPv4 Static Routes on an SG550XG Switch through the CLI
PDF(1.9 MB) View with Adobe Reader on a variety of devices
ePub(2.1 MB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(1.2 MB) View on Kindle device or Kindle app on multiple devices
Updated:February 17, 2020
This article provides instructions on how to configure the IP SLA tracking settings for IPv4 static routes on
your switch. In this scenario, the static route has been preconfigured.
Note: To learn how to configure an IPv4 static route on your switch, click here.
For instructions on how to configure IP SLA tracking for IPv4 static routes through the web-based utility, click
When using static routing, you may experience a situation where a static route is active, but the destination
network is not reachable via the specified next hop. For example, if the static route in question has the lowest
metric to the destination network and the status of the outgoing interface to the next hop is Up, however the
connectivity is broken somewhere along the path to the destination network. In this case, the device can use the
static route although it does not actually provide connectivity to the destination network. The Internet
Protocol Service Level Agreement (IP SLA) Object tracking for static routes provides a mechanism to track the
connectivity to the destination network via the next hop specified in the static route. If connectivity to the
destination network is lost, the route state is set to Down, and if available, a different static route (which
is in state Up) can be selected for routing traffic.
Similar to IP SLAs tracking for Virtual Router Redundancy Protocol (VRRP), IP SLAs object tracking for static
routes also relies on IP SLAs operations to detect connectivity to destination networks. IP SLAs operation sends
Internet Control Message Protocol (ICMP) packets to the address defined by the user (a host on the required
destination network), and also defines the next hop to use for the ping operation. IP SLAs operation then
monitors success or failure of replies from the host. A track object is used to track operation results and set
the status to Up or Down, based on the success or failure of the ICMP destination. The track operation is
assigned to a static route. If the track status is down, the static route state is set to Down. If track status
is Up, the static route state remains Up.
The following describes the main terms used in this article:
Operation - Each IP SLAs ICMP Echo operation sends a single ICMP Echo request to a target
address at a
configured frequency rate. It then waits for a response.
Object State - Each tracking object maintains an operation state. The state is either Up
After object creation, the state is set to Up. The following table specifies the conversion of the IP SLAs
operation return code to the object state:
Operation Return Code
Track Operation State
Note: If the IP SLAs operation specified by the track argument is not configured or is its schedule is
pending, its state is OK. An application that is bound to a non-existing tracking object will receive the Up
SLA Operation State - This can be either Scheduled, which means the operation begins
immediately or Pending,
which means it has been created but not activated.
Timeout value - Specifies the interval time of waiting for the ICMP echo reply message or
an ICMP error
Return Code - After an operation has been finished, the operation return code is set
according to the
ICMP Echo reply has been received - Return code is set to OK.
ICMP Error reply has been received - Return code is set to error.
No any ICMP reply has been received - Return code is set to error.
Configured Source IP address or Source interface is not accessible - Return code is set to
Tracker - Tracks the results of operations.
Delay - When the result of an IP SLA operation indicates that the state of the tracking
to X from Y, the tracking object performs the following actions:
The state of the tracking object is not changed and the tracking object starts the delay timer
If during the time that the timer is set, the original state (Y) is received again, the timer is
and the state remains Y.
If the delay timer is expired, the state of the tracking object is changed to X and the X state
is passed to
the associated applications.
ip-address | hostname - Destination IP address or hostname.
nexthop-ip ip-address - (Optional) If ip-address is entered, enter the IP address of the
source-ip ip-address - (Optional) If ip-address is entered, enter the source IP address.
When a source IP
address is not specified, the IP SLAs ICMP Echo operation chooses the IP address nearest to the destination.
Note: In this example, the operation target IP address is 192.168.1.1, the source IP address is
192.168.100.126, and the next hop IP address is 192.168.100.1.
Step 6. To set the protocol data size in the payload of the request packet of an IP SLA operation, enter the
seconds - The number of seconds between the IP SLAs operations. The range is from 10 to 500
Note: A single IP SLA operation will repeat at a given frequency for the lifetime of the operation. If you
configure the frequency, the timeout must be configured as well. The new frequency value configured by this
command will impact on the current frequency interval.
Note: In this example, the frequency is set to 30 seconds.
Step 8. To set the amount of time an IP SLA operation waits for a response to its request packet, enter the