Cisco Bug: CSCul59035 - Endian conversion for netflow not working properly
May 12, 2018
- Cisco Carrier Routing System
Known Affected Releases
Symptom: When customer issues a command to match ipv4 destination of 220.127.116.11/8, instead of matching destination prefixes with 239 in the first octet, it matches all destination prefixes with 239 in the last octet. IPV4SrcAddr IPV4DstAddr IPV4TOS 18.104.22.168 22.214.171.124 0 126.96.36.199 188.8.131.52 0 184.108.40.206 220.127.116.11 0 18.104.22.168 22.214.171.124 0 126.96.36.199 188.8.131.52 0 184.108.40.206 220.127.116.11 0 18.104.22.168 22.214.171.124 0 126.96.36.199 188.8.131.52 0 Conditions: This issue happens when RP and the linecard are of different architectures (i.e. intel versus ppc). It works fine if both RP and linecard have the same architecture. This is because of different byte ordering of integers between the architectures.
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