Guest

Preview Tool

Cisco Bug: CSCut51873 - Some relations tCl field don't get updated at runtime

Last Modified

Mar 24, 2018

Products (1)

  • Cisco Application Policy Infrastructure Controller (APIC)

Known Affected Releases

1.0(3i)

Description (partial)

Symptom:
tCl for some objects refer to infraDomP (superclass) and others will refer to either physDomP or vmmDomP.

Conditions:
I was digging through the model and came across something I would like to have clarified when you have a moment. Basically what I am seeing is that the 'tCl' field between the following fvRsDomAtt objects are different, but the desired 'tDn' is the same, in this case a vmm domain.
I was wondering what the reasoning is behind the 'tCl' being different. My guess is that it is something along the lines of one being an explicit assignment whereas the 'infraDomP' could be sort of a blanket assignment that is being caught elsewhere? If you are curious as to why this came up, it is due to a tool I've been working on which gave rise to me noticing this difference.
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.