Cisco Bug: CSCvt16068 - in-line version change in exporter-map or modification on exporter-map list corrupt exported flows
Sep 03, 2020
- Cisco Network Convergence System 5500 Series
Known Affected Releases
Symptom: in-line version change in exporter-map or modification on exporter-map list inside a monitor-map can corrupt exported flows; "corrupt" in the sense that the template information in template records will not match precisely to data flow records exported. There are two scenarios in which the issue manifests. 1. Inline change of version in the exporter configuration from v9 to ipfix: The issue will happen consistently with this case. Only the v9 -> ipfix change leads to the flow corruption. If the change is done from ipfix to v9 the problem does not happen. When we have the broken flows in place and do the change from ipfix to v9, the flows recover. 2. Perform the following steps: a) delete exporter from the monitor-map config and the exporter itself (the flow monitor must stay in the interface config): b) recreate the exporter with different protocol and add it back to monitor-map config. In this case the problem is 100% reproducible even if we do the ipfix->v9 change.
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