Cisco Bug: CSCun60242 - Flow_Get failure for ip version 6 and ip version 4 demands
Last Modified
Jan 28, 2017
Products (1)
- Cisco MATE Collector
Known Affected Releases
5.5.2
Description (partial)
Symptom: The stack trace generated 2014.03.07 20:56:53.579 +0000] [FATAL ] [flow_get] [16650] aInAttrName: [Traffic] is not contained in either namingAttributeChanges:[ServiceClass, Source, Destination, TrafficLevel]] neither in noNamingAttributeChanges:[] com.cariden.mate.util.Assertions$AssertionException: aInAttrName: [Traffic] is not contained in either namingAttributeChanges:[ServiceClass, Source, Destination, TrafficLevel]] neither in noNamingAttributeChanges:[] at com.cariden.mate.util.Assertions.assertTrue(Assertions.java:21) at com.cariden.mate.moholders.ManagedObjectConfigChangeHolder.getAttributeValueOrNull(ManagedObjectConfigChangeHolder.java:847) at com.cariden.mfc.importer.MfcImporter.generateInterASFlowsAndDemands(MfcImporter.java:410) at com.cariden.mfc.importer.MfcImporterCmdLine.process(MfcImporterCmdLine.java:421) at com.cariden.mate.cmdline.CommonCmdLine.run(CommonCmdLine.java:57) at com.cariden.mfc.importer.MfcImporterCmdLine.mainAlt(MfcImporterCmdLine.java:80) at com.cariden.mfc.importer.MfcImporterCmdLine.main(MfcImporterCmdLine.java:52) Conditions: Running FLOW_GET twice creates the error.
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