Cisco Bug: CSCsy95720 - FEC stream b/w not accounted for in vqes
Apr 10, 2015
- Cisco Content Delivery Engine Series
Known Affected Releases
Symptom: FEC bandwidth not accounted for on ingress streams. Conditions: If you have a network setup where the source streams use the same IP as FEC streams, meaning the source data and up to 2 associated FEC streams are all on the same IP address but different ports, then when the VQES joins the multicast IP of the source ingress streams, it also gets traffic from the FEC streams. This is a function of IGMP multicast join and the VQES has no control over this. This FEC stream data is thrown away by the kernel, but it does use up ingress bandwidth on the interface, and currently we do not account for this bandwidth (as VQES is FEC "unaware"). AMT screens currently show available bandwidth assuming that the only bandwidth being used is from the joined channels, but note that more could be used from FEC.
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