Cisco Bug: CSCup45356 - D9485 incorrectly resending the PETE correction message.
Jun 22, 2020
- Headend System Releases
Known Affected Releases
Symptom: If the D9485 is operating in a network with a high noise floor and/or lots of contention then this could result in it not hearing a response from any given STB when it sends power error and timing error (PETE) correction messages to them. Upon timing out waiting for a response message from a STB, the D9485 was incorrectly resending the PETE correction message again, specifying the same desired adjustment, and this could result in the final adjustment actually being (N + 1) * the desired adjustment, where N is the number of successive timeouts that occur waiting for a response. In other words, STBs were receiving the PETE correction messages, and applying them, but the D9485 was failing to receive the response from some STBs acknowledging the adjustment and so was repeatedly resending the correction messages and forcing these STBs to adjust too much. The D9485 code was modified so that now, if it doesn't receive a response to a PETE correction message, then it resends a message with no (i.e. 0) correction specified to the STB after each timeout until it either gets a response or has reached the maximum retry limit and resets the STB. This issue only appeared to manifest itself when the demod attenuation level was set to 0 dB such that the STB responses to PETE correction messages could get lost due to a high noise floor. Conditions: If the plan has a high amount of noise on the RF plant.
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