Guest

Preview Tool

Cisco Bug: CSCvv78885 - Unexpected shared-svc route-map entry from stale fvAppEpGCons

Last Modified

Oct 07, 2020

Products (1)

  • Cisco Application Policy Infrastructure Controller (APIC)

Known Affected Releases

3.2(9b)

Description (partial)

Symptom:
Stale route-map entry is causing unexpected route leaking

leaf# show bgp process vrf Tenant:VRF
.......
    Wait for IGP convergence is not configured
    Import route-map 2222222-shared-svc-leak      <--------------------
    Export RT list:
        53403:2359299
    Import RT list:
        53403:2359299
        53403:2457602
    Label mode: per-prefix

leaf# show route-map 2222222-shared-svc-leak
.......
route-map 2222222-shared-svc-leak, permit, sequence 1000
  Match clauses:
    ip address prefix-lists: IPv4-4444444-32772-11935-2222222-shared-svc-leak
    ipv6 address prefix-lists: IPv6-deny-all
  Set clauses:

leaf# show ip prefix-list
.......
ip prefix-list IPv4-4444444-32772-11935-2222222-shared-svc-leak: 1 entries
   seq 1 permit 0.0.0.0/0

Conditions:
The following stale object remains on the leaf regarding the route-map entry 1000.

leaf# moquery -c fvAppEpGCons -f 'fv.AppEpGCons.dn*"rtmap-2222222-shared-svc-leak/ent-1000"'

Total Objects shown: 1

# fv.AppEpGCons
consDn       : cdef-[uni/tn-common/brc-Contract]/epgCont-[uni/tn-Tenant/ap-AP/epg-EP]/fr-[uni/tn-common/brc-Contract/dirass/cons-[uni/tn-Tenant/ap-AP/epg-EP]-any-no]/to-[uni/tn-common/brc-Contract/dirass/prov-[uni/tn-common/out-L3Out/instP-Outside]-any-no]
childAction  :
descr        :
dn           : uni/ctxrefcont/ctxref-[sys/ctx-[vxlan-222222]]/epgref-[uni/tn-Tenant/ap-AP/epg-EP]/epgpol-[sys/rpm/rtmap-2222222-shared-svc-leak/ent-1000]/epgcons-[cdef-[uni/tn-common/brc-Contract]/epgCont-[uni/tn-Tenant/ap-AP/epg-EP]/fr-[uni/tn-common/brc-Contract/dirass/cons-[uni/tn-Tenat/ap-AP/epg-EP]-any-no]/to-[uni/tn-common/brc-Contract/dirass/prov-[uni/tn-common/out-L3Out/instP-Outside]-any-no]]
lcOwn        : local
modTs        : 2020-06-30T07:50:07.366-06:00
name         :
nameAlias    :
ownerKey     :
ownerTag     :
rn           : epgcons-[cdef-[uni/tn-common/brc-Contract]/epgCont-[uni/tn-Tenant/ap-AP/epg-EP]/fr-[uni/tn-common/brc-Contract/dirass/cons-[uni/tn-Tenant/ap-AP/epg-EP]-any-no]/to-[uni/tn-common/brc-Contract/dirass/prov-[uni/tn-common/out-L3Out/instP-Outside]-any-no]]
status       :

We can see this is from a non-existent contract relationship:
Provider EPG "tn-Tenant/ap-AP/epg-EP"
Consumer EPG "tn-common/out-L3Out/instP-Outside"
Contract "Contract"
Bug details contain sensitive information and therefore require a Cisco.com 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.