Preview Tool

Cisco Bug: CSCvt18546 - Add fault for missing Unicast TEP configuration with Remote Leaf Direct

Last Modified

Jul 25, 2020

Products (1)

  • Cisco Application Policy Infrastructure Controller (APIC)

Known Affected Releases


Description (partial)

This is an enhancement to add a fault if the Unicast VTEP IP address is missing from the Pod Connection Profile and remote leaf direct is enabled.

When the remote leaf direct feature is enabled, a Unicast VTEP is required in the Pod Connection Profile for the pod that the remote leaf is associated to. 

If this is missed during configuration, unicast traffic coming from the spines will be dropped on the remote leaf with drop vector "INFRA_ENCAP_SRC_TEP_MISS," assuming second generation+ platforms, because the leaf is expecting to receive traffic from the Unicast VTEP but one is not configured.

The MO class of the Unicast TEP entry is fvExtRoutableUcastConnP. The Unicast VTEP IP is in the attribute named "addr".

The MO class of fabric-wide settings is infraSetPol. The "enableRemoteLeafDirect" attribute determines whether remote leaf direct is enabled or not.

Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.