Quote:
Originally Posted by Moldova
We both agree not critical to the modem operation.
What would you expect to see in the logs if the was an issue.
|
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.
Quote:
Mon Apr 20 15:17:13 2009 Mon Apr 20 15:17:13 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Wed Apr 22 09:19:58 2009 Wed Apr 22 09:19:58 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Wed Apr 22 13:05:31 2009 Wed Apr 22 13:05:31 2009 Information (7) Downstream sync ok
Wed Apr 22 13:05:31 2009 Wed Apr 22 13:05:31 2009 Information (7) locked and synced to rescue CMTS...all is well!
Wed Apr 22 13:05:31 2009 Wed Apr 22 13:05:31 2009 Information (7) Downstream sync ok
Wed Apr 22 13:05:30 2009 Wed Apr 22 13:05:30 2009 Information (7) Locked on the rescue CMTS ds. try to re-acquire ds sync...
Wed Apr 22 13:05:30 2009 Wed Apr 22 13:05:30 2009 Information (7) Downstream lock ok
Wed Apr 22 13:05:29 2009 Wed Apr 22 13:05:29 2009 Information (7) Downstream lock failed
|
Have to love how losing downstream lock is classed as 'Information'. Silly Ambit
