Quote:
Originally Posted by Sephiroth
Well, I've explained the T3 timeouts. Looks like the engineer came close to the same diagnosis. You'll feel the modem fairly warm if the upstream dBmv is always arpund the 50 mark. 40dBmv is comfortable.
What are your normal levels?
|
Wed Nov 4 13:08:23 2009 Wed Nov 4 21:09:53 2009 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:xx:xx:xx:xx:xx;CMTS-MAC=00:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Wed Nov 4 22:18:58 2009 Wed Nov 4 22:43:46 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:xx:xx:xx:xx:xx;CMTS-MAC=00:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
I also get the Timing Synchronization failures since this morning when a new config file was downloaded to the modem:
Mod Edit.
I had to manually restart the modem this morning since it hung with that.
---------- Post added at 23:17 ---------- Previous post was at 22:57 ----------
Quote:
Originally Posted by Broadbandings
50-52dBmV upstream transmit power is absolutely fine. Due to variations in distance from amplification, etc, it's not possible to have all modems at 40dBmV.
Quick FYI:
T3s usually don't cause transmit power to increase, the only time transmit power is increased due to CMTS not responding is during initial ranging, after this every time the modem transmits a range request and doesn't get a response back within 200ms the T3 counter is incremented but the modem does not increase transmit power. Once the modem has ranged and come online this only happens when the modem is told to in the range-response from the CMTS.
Here check this out:
http://www.dslreports.com/faq/comcast/2.1_Modems
Scroll to the bottom for the timeouts.
Also
http://bradyvolpe.com/2009/03/03/doc...n-maintenance/ |
Thanks for this, how about the 12dB incoming, is that too high in your view?
So if the errors logged are not due to level missmatch how can they be sorted out?