Track List

Location in GUI: Tenants » XXX » Policies » Protocol » IP SLA » Track Lists

Diagram

Classes

policies (apic.tenants)

Name	Type	Constraint	Mandatory	Default Value
track_lists	List	`[track_lists]`	No

track_lists (apic.tenants.policies)

Name	Type	Constraint	Mandatory	Default Value
name	String	Regex: `^[a-zA-Z0-9_.:-]{1,64}$`	Yes
description	String	Regex: `^[a-zA-Z0-9\\!#$%()*,-./:;@ _{\|}~?&+]{1,128}$`	No
type	Choice	`percentage`, `weight`	No	`percentage`
percentage_up	Integer	min: `0`, max: `100`	No	`1`
percentage_down	Integer	min: `0`, max: `100`	No	0
weight_up	Integer	min: `0`, max: `255`	No	`1`
weight_down	Integer	min: `0`, max: `255`	No	0
track_members	List	String[Regex: `^[a-zA-Z0-9_.:-]{1,64}$`]	No

Examples

Example-1: This data model groups two IP addresses (track members FW_1_Track_Mem and FW_2_Track_Mem) to evaluate the validity of a static route or its next-hop within an L3Out or Bridge Domain. The track members are monitored using a specified IP SLA monitoring policy (e.g., ICMP or TCP probes). Based on a configured threshold-expressed as a percentage or weight-the track list determines whether the route or next-hop is considered up or down. If marked down, the static route or next-hop is removed from the routing table; if marked up, it is reinstated. Static routes reference these track lists to dynamically manage route availability.

apic:
  tenants:
    - name: ABC
      policies:
        track_lists:
          - name: TRACK_LIST
            type: percentage
            percentage_up: 10
            percentage_down: 2
            track_members:
              - FW_1_Track_Mem
              - FW_2_Track_Mem