Quote:
Originally Posted by Ignitionnet
The issue is actually with a broken BPI+ implementation on the CMTS side causing the modem and the CMTS respective BPI+ state machines to go out of sync. The KSN only goes across the wire during BPI+ TEK state machine updates. A modem would have to send multiple TEK refresh requests within a very short period, milliseconds, for this to be due to upstream impediments.
Modems aren't disconnected via T3s / T4s, if they aren't properly authenticated and authorised their primary service flow would be de-authorised, reflected in the modem by a BPI+ state of 'denied'.
There is a grace period, default an hour, to mitigate modems being disconnected due to their BPI+ state machine falling out of sync with the CMTS.
Control messages, ranging requests, etc, are not encrypted by BPI+.
|
I,m not claiming to understand what your saying here Igni/seph, but what happens if the modem doesn't know what time it is.
A lot of problematic modems are showing "time not established" errors, despite numerous attempts to re-establish it.
So what I,m curious about, can the T3 actually cause an outage/loss of service if the modem doesn't know what time it is, going off what's written above in bold
Apologies if this is a dumb question