Quote:
Originally Posted by Broadbandings
If it were congestion sadly nothing.
If it were a signal issue possibly losses of downstream synchronisation and missed ranging responses, after the 'No Response received' bit should be T3 timeout but that gets cut off. That indicated that the CMTS didn't hear my modem giving its' periodic 'keepalive'.
Could be simple congestion if it's download speeds twitching. I get it all the time and most of the time my modem's logs are pretty quiet.
I'll show you some logs from my modem where I've had signal 'twitches' this week - there has been network sweep and clean going on in this area to prep for the overlay.
Have to love how losing downstream lock is classed as 'Information'. Silly Ambit  |
Thanks just asking for general clarification due to the amount of posts with modem logs in them.