| reply to No_Strings
Re: Internet Reliability issues Thanks for moving my post, I apologize for the extra work. Here are the logs from the past few days. I reset factory defaults for my modem so there aren't any logs beyond this yet.
5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
5-Warning T203.0 MDD message timeout;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
6-Notice Cable Modem Reboot due to T4 timeout ;CM-;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
3-Critical R03.0 Ranging Request Retries exhausted;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
3-Critical R02.0 No Ranging Response received - T3 time-out;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0;
5-Warning T202.0 Lost MDD Timeout;CM-;CMTS-;CM-QOS=1.1;CM-VER=3.0; |
|
| Just as an update... the tech came out today and said it sounded like the bandwidth on our node was maxed. He said that during peak hours if there wasn't enough bandwidth we'd get randomly kicked. Likewise, if it wasn't peak hours and someone was using a ton of bandwidth (or several someones), then we could just as easily get disconnected. He said he was going to speak with his lead tech and work on it. Does this sound feasible? |
|
|
|
TheWiseGuyDog And ButterflyPremium,MVM
join:2002-07-04
East Stroudsburg, PA
kudos:2 Reviews:
 ·Optimum Online
| I'm far from an expert but there are specific slots reserved for ranging and its seems unlikely to me that you would get T3 timeouts due to one user doing large downloads. The normal explanation I have heard for T3 time outs is Noise, normally on the upstream.
This is the Cisco page that explains error messages
»www.cisco.com/univercd/cc/td/doc···errs.htm
This explains ranging slots
»web.archive.org/web/200712180625···l/09.htm
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
