Track Member
Location in GUI: Tenants » XXX » Policies » Protocol » IP SLA » Track Members
Diagram
Section titled “Diagram”Classes
Section titled “Classes”policies (apic.tenants)
Section titled “policies (apic.tenants)”| Name | Type | Constraint | Mandatory | Default Value |
|---|---|---|---|---|
| track_members | List | [track_members] | No |
track_members (apic.tenants.policies)
Section titled “track_members (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 | |
| destination_ip | IP | Yes | ||
| scope_type | Choice | l3out, bd | Yes | |
| scope | String | Yes | ||
| ip_sla_policy | String | Regex: ^[a-zA-Z0-9_.:-]{1,64}$ | Yes |
Examples
Section titled “Examples”Example-1: This data model specifies two IP addresses (10.0.0.1 and 10.0.0.2) located in the Firewall_L3 L3Out to be monitored using the L2PingEach30sec IP SLA monitoring policy.
Track Members are the fundamental units of IP SLA monitoring. They represent endpoints or next-hop IP addresses whose reachability is continuously verified. The monitoring results dynamically influence network behavior, such as static route tracking, which can be associated with either an L3Out or a Bridge Domain (BD) and referenced by a Track List.
apic: tenants: - name: ABC policies: track_members: - name: FW_1_Track_Mem destination_ip: 10.0.0.1 scope_type: l3out scope: Firewall_L3 ip_sla_policy: L2PingEach30sec - name: FW_2_Track_Mem destination_ip: 10.0.0.2 scope_type: l3out scope: Firewall_L3 ip_sla_policy: L2PingEach30sec