IP SLA guidelines and limitations

• IP SLA supports IPv4 and IPv6 addresses.

• IP SLA is supported on all second-generation Cisco Nexus switches, including -EX and -FX switches.

• Beginning with Cisco Application Policy Infrastructure Controller ( APIC ) Release 4.1(1), the IP SLA monitoring policy validates the IP SLA port value. When TCP is configured as the IP SLA probe type, Cisco APIC does not accept an IP SLA port value of 0. Earlier releases allowed this value. If an IP SLA monitoring policy from an earlier release uses port 0, the policy becomes invalid after you upgrade Cisco APIC to Release 4.1(1) or later. The invalid policy causes configuration imports and snapshot rollbacks to fail.

  Before you upgrade Cisco APIC , configure a nonzero IP SLA port value. Use only snapshots and configuration exports that you create after changing the port value.

• To use IP SLA with remote leaf switches, enable global GIPo:

  1. On the menu bar, choose System > System Settings .

  2. In the System Settings navigation pane, choose System Global GIPo .

  3. In the System Global GIPo Policy work pane, click Enabled .

  4. In the Policy Usage Warning dialog box, review the nodes and policies that might use the GIPo policy. If appropriate, click Submit Changes .

• Statistics under Fabric > Inventory > Pod number > Leaf Node name > Protocols > IP SLA > ICMP Echo Operations or TCP Connect Operations can be collected only at 5-minute intervals. The default interval is 15 Minute . Change the interval to 5 Minute .

• IP SLA policies are not supported for endpoints connected through a vPod.

• IP SLA is supported in single-pod fabrics, Cisco ACI Multi-Pod deployments, and remote leaf switch deployments.

• IP SLA is not supported when the destination IP address being tracked is connected across Cisco ACI Multi-Site .

• If a border leaf switch has a static route that is redistributed into Multiprotocol Border Gateway Protocol (MP-BGP) for a virtual routing and forwarding (VRF) instance, the MP-BGP route has the same administrative distance as the static route, as shown in the following example:

  leaf102# show ip route 10.10.10.10/32 vrf test:VRF-1
                                                  IP Route Table for VRF "test:VRF-1"
                                                  '*' denotes best ucast next-hop
                                                  '**' denotes best mcast next-hop
                                                  '[x/y]' denotes [preference/metric]
                                                  '%<string>' in via output denotes VRF <string>
                                                  10.10.10.10/32, ubest/mbest: 1/0
                                                  *via 102.0.0.2, vlan45, [1/0], 01w00d, static

  The route is injected into the fabric MP-BGP routes for the VRF instance. Other remote leaf switches learn the route as an internal BGP (iBGP) route, as shown in the following example:

  leaf103# show ip route 10.10.10.10/32 vrf test:VRF-1
                                                  IP Route Table for VRF "test:VRF-1"
                                                  '*' denotes best ucast next-hop
                                                  '**' denotes best mcast next-hop
                                                  '[x/y]' denotes [preference/metric]
                                                  '%<string>' in via output denotes VRF <string>
                                                  10.10.10.10/32, ubest/mbest: 1/0
                                                  *via 10.0.200.64%overlay-1, [1/0], 01w00d, bgp-65310, internal, tag 65310
                                                  recursive next hop: 10.0.200.64/32%overlay-1

  The administrative distance of the iBGP route is the same as the administrative distance of the static route instead of the administrative distance normally used for iBGP routes. This behavior occurs in Cisco APIC Releases 4.1(1) and 5.0(1).

For verified IP SLA scale limits, see the appropriate Verified Scalability Guide for Cisco APIC on the Cisco APIC documentation page .