Cisco Bug: CSCup45300 - Added message "Invalid DAVIC message type"
Jun 22, 2020
- Headend System Releases
Known Affected Releases
Symptom: "Invalid DAVIC message type" alarms are raised when DAVIC message traffic is received that can't be properly validated. This includes instances where a valid DAVIC message type is found but no MAC address, so the associated packet is discarded as a "broadcast" DAVIC message. The ability was added to capture the contents of invalid DAVIC messages, and messages being flagged as a broadcast message, and write them to the logs to allow post-analysis/decoding of the data in the ATM cells comprising the message. Additionally, the VPI/VCI, MAC address and demod associated with the STB that sent the message is captured and logged. Conditions: When the D9485 receives a Davic message that is not formatted correctly or missing the mac address
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