Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

PDF

Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

IP SLA associations for static routes

Updated: April 17, 2026

Want to summarize with AI?

Log in

Cisco ACI IP service-level agreement (SLA) policies and profiles provide connectivity and performance monitoring for static routes and next-hop profiles.

Cisco ACI IP SLA uses the following components to monitor static-route connectivity and performance:

  • IP SLA monitoring policies

  • IP SLA track members

  • IP SLA track lists

IP SLA component application

Associate the following components with static routes or next-hop profiles:

  • IP SLA monitoring policies

  • IP SLA track members

  • IP SLA track lists

Configure an IP SLA monitoring policy by using the GUI

An IP SLA monitoring policy enables Cisco Application Policy Infrastructure Controller ( APIC ) to send monitoring probes for a specified SLA type.

Procedure

  1. On the menu bar, choose Tenants > tenant_name . In the navigation pane, choose Policies > Protocol > IP SLA .

  2. Right-click IP SLA Monitoring Policies and choose Create IP SLA Monitoring Policy .

  3. In the Create IP SLA Monitoring Policy dialog box, configure the monitoring policy:

    1. In the Name field, enter a unique name for the IP SLA monitoring policy.
    2. In the SLA Type field, choose the probe type.

      You can choose TCP , ICMP , L2Ping , or HTTP . ICMP is the default.

      Note

      L2Ping is supported only for Layer 1 or Layer 2 policy-based redirect (PBR) tracking.

    3. If you chose HTTP , choose a version from the HTTP Version options.
    4. If you chose HTTP , enter the HTTP URI used for service-node tracking in the HTTP URI field.

      The URI must begin with "/", for example, "/index.html".

    5. If you chose TCP , enter the destination port number in the Destination Port field.
    6. In the SLA Frequency field, enter the interval between probes in seconds.

      The range is from 1 to 300 seconds. The default value is 60 seconds. For HTTP tracking, use an interval of at least 5 seconds.

    7. In the Detect Multiplier field, enter the number of consecutive missed probes required for the system to detect a failure and mark the track as down.

      By default, the system detects a failure after three consecutive probes are missed. Changing the Detect Multiplier value changes the number of consecutive missed probes required to mark the track as down.

      The SLA Frequency and Detect Multiplier values determine the approximate failure-detection time. For example, consider the following values:

      • SLA Frequency (sec) : 5

      • Detect Multiplier : 30

      With these values, the system detects a failure in approximately 150 seconds: 5 seconds multiplied by 30.

    8. If you chose an SLA type other than TCP , enter the request-payload size in bytes in the Request Data Size (bytes) field.
    9. In the Type of Service field, enter the type of service (ToS) byte value for the IPv4 header of the IP SLA operation.
    10. In the Operation Timeout (milliseconds) field, enter how long the IP SLA operation waits for a response to a request packet.
    11. In the Threshold (milliseconds) field, enter the upper threshold used to calculate the network-monitoring statistics for the IP SLA operation.
    12. For an IPv6 network, enter the traffic-class byte value for the IPv6 header in the Traffic Class Value field.
    13. Click Submit .

    The IP SLA monitoring policy is configured.

Configure IP SLA track members by using the GUI

An IP SLA track member defines a destination to monitor and can be added to an IP SLA track list. Associate the track list with a static route to monitor the availability of its defined next hops.

Before you begin

Create an IP SLA monitoring policy and obtain the destination IP address of the next hop that the track member represents.

Procedure

  1. On the menu bar, choose Tenants > tenant_name .

  2. In the Navigation pane, expand Policies , and then expand Protocol .

  3. Expand IP SLA , right-click Track Members , and choose Create Track Member .

  4. Configure the track-member parameters:

    1. In the Name field, enter a unique name for the track member.
    2. In the Destination IP field, enter the IP address of the next hop that the track member represents.
    3. From the Scope of Track Member drop-down list, choose the bridge domain or external network to which the track member belongs.
    4. In the IP SLA Policy field, choose an existing IP SLA monitoring policy or create a policy that defines the probe used for monitoring.

  5. Click Submit .

What to do next

Repeat this procedure to create all track members required for the static route. After you configure the track members, create a track list and add the members to it.

Configure an IP SLA track list by using the GUI

An IP SLA track list groups one or more track members that represent the next hops of a static route. Associate the track list with a static route to monitor the aggregate availability of those next hops.

Before you begin

Create one or more IP SLA track members.

Procedure

  1. On the menu bar, choose Tenants > tenant_name .

  2. In the Navigation pane, expand Policies , and then expand Protocol .

  3. Expand IP SLA , right-click Track Lists , and choose Create Track List .

    The Create Track List dialog box appears.

  4. Configure the track-list parameters:

    1. In the Name field, enter a unique name for the track list.
    2. In the Type of Track List field, choose Threshold percentage to determine availability from the percentage of track members that are up or down. Choose Threshold weight to determine availability from the weight assigned to each track member.
    3. In the Track list to track member relation table, click + in the table header, and choose an existing track member. If Type of Track List is set to Threshold weight , assign a weight to the track member.

  5. Click Submit .

What to do next

Associate the track list with a static route or next-hop IP address.

Associate an IP SLA track list with a static route by using the GUI

Associating a track list with a static route enables the system to monitor the availability of the next hops represented by the track list.

Note

This procedure assumes that the static route already has a next-hop configuration.

Before you begin

Configure a routed network that contains a static route, and create the IP SLA track list that you want to associate with the route.

Procedure

  1. On the menu bar, choose Tenants > tenant_name .

  2. In the Navigation pane, expand Networking , and then expand L3Outs .

  3. Expand routed_network_name , Logical Node Profiles , logical_node_profile_name , and Configured Nodes .

  4. Click node_name .

    The Node Association work pane appears.

  5. In the Static Routes table, double-click the static route that you want to associate with the track list.

    The Static Route dialog box appears.

  6. From the Track Policy drop-down list, choose an existing IP SLA track list or create a track list to associate with the static route.

  7. Click Submit .

    The Policy Usage Warning dialog box appears.

  8. Verify that the change does not affect other nodes or policies that use the static route, and click Submit Changes .

Associate an IP SLA track list with a next-hop profile by using the GUI

Associating a track list with a next-hop profile enables the system to monitor the availability of that next hop.

Before you begin

Configure a routed network that contains a static route and next-hop profile.

Procedure

  1. On the menu bar, choose Tenants > tenant_name .

  2. In the Navigation pane, expand Networking , and then expand L3Outs .

  3. Expand routed_network_name , Logical Node Profiles , logical_node_profile_name , and Configured Nodes .

  4. Click node_name .

    The Node Association work pane appears.

  5. In the Static Routes table, double-click the static route that contains the next-hop profile.

    The Static Route dialog box appears.

  6. In the Next Hop Addresses table, double-click the next-hop entry that you want to associate with the track list.

    The Next Hop Profile dialog box appears.

  7. From the Track Policy drop-down list, choose an existing IP SLA track list or create a track list to associate with the next-hop profile.

    Note

    If you add an IP SLA policy to the next-hop profile, the system automatically creates a track member and track list and associates them with the profile.

  8. Click Submit .

    The Policy Usage Warning dialog box appears.

  9. Verify that the change does not affect other nodes or policies that use the static route, and click Submit Changes .