Cisco Bug: CSCvh92115 - ADM is not able to associated flows with the granular correct child scope
Aug 13, 2019
- Cisco Tetration Analytics
Known Affected Releases
Symptom: ADM run is not associating the flows with child scope, whereas flow searchs are associating for all the flows correctly with the child scope within the same period as the ADM run. Issue is only reported on one particular scope ""Tafe Cloud:PREPROD:Splunk", after any system wise change, such as datanode flapping/upgrade. The scope "Tafe Cloud:PREPROD:Splunk" is using the Vcenter orchestrator tags as filter query. Reported problematic provider scope "Tafe Cloud:PREPROD:Splunk", that is supposed to associate with the traffic with provider port 9997 from ADM run under various consumer scopes. After the datanode flapping issue or upgrade of the system, ADM run under all scopes were reporting the flows with provider port 9997 to the parent scope "Tafe Cloud:PREPROD". Conditions: System wise change: upgrade, datanode flapping.
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases