dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
736
share rss forum feed


NOCTech75
Premium
join:2009-06-29
Marietta, GA
Reviews:
·Comcast

[Connectivity] Here we go again, how to cut through Concasts hor

Well after nearly a month of the last packet lost outage in my area Concast is at it again. Started Sept 6th and their phone support was pathetic... took me saying several times wi-fi was not involved and that everything was wired in before he finally understood it. So here is the list of problems that they say it is:

1) Router
2) my devices behind the router
3) bad ports on the router
4) modem

This despite I have the following in my modem logs started 9/6:

No Ranging Response received - T3 time-out;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:01:5c:23:72:59;CM-QOS=1.1;CM-VER=3.0;

But according to him nothing was wrong with Comcast.. he couldn't answer why I was getting T3 time-outs. Oh, they blasted 4 pings at the modem and said oh no packet loss.. close to 600 packets at yahoo, 4% loss. Connection pretty much buggered for online streaming and gaming. Only other alternative is to sit around for hours waiting on their truck roll to tell me they can't do a damned thing. Since they have thrown double middle fingers up to the Direct support forum what other options is there?


beachintech
There's sand in my tool bag
Premium
join:2008-01-06
kudos:5

Re: [Connectivity] Here we go again, how to cut through Concasts

Twitter @comcastcares. Works pretty well. I got a call from "executive support" within 24 hours.

In the mean time, post up your modem signal levels and logs.


NOCTech75
Premium
join:2009-06-29
Marietta, GA
Reviews:
·Comcast
Last 4 log entries:

Sep 07 2013 15:17:51 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:01:5c:23:72:59;CM-QOS=1.1;CM-VER=3.0;
Sep 06 2013 23:03:12 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:01:5c:23:72:59;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 06 2013 23:01:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:01:5c:23:72:59;CM-QOS=1.1;CM-VER=3.0;

Reboot was me, last time this happened (modem has been clean ever since):

Jul 25 2013 20:57:58 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:01:5c:23:72:59;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to IP loss ;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:01:5c:23:72:59;CM-QOS=1.1;CM-VER=3.0;
Jul 25 2013 20:52:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:01:5c:23:72:59;CM-QOS=1.1;CM-VER=3.0;
Jul 25 2013 14:40:01 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:75:4a:74:d0:e0;CMTS-MAC=00:01:5c:23:72:59;CM-QOS=1.1;CM-VER=3.0;

Channel ID 2 3 4 6
Frequency 579000000 Hz 585000000 Hz 591000000 Hz 603000000 Hz
Signal to Noise Ratio 35 dB 36 dB 36 dB 36 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
0 dBmV 0 dBmV 0 dBmV 0 dBmV
Upstream Bonding Channel Value
Channel ID 1 2 3
Frequency 34800000 Hz 27900000 Hz 22600000 Hz
Ranging Service ID 11545 11545 11545
Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec
Power Level 50 dBmV 51 dBmV 52 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM
[3] QPSK
[2] 16QAM

Ranging Status Success Success Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 2 3 4 6
Total Unerrored Codewords 2862323624 2862323410 2862323778 2862324077
Total Correctable Codewords 4941 5091 4726 4428
Total Uncorrectable Codewords 1440 1444 1443 1444


swintec
Premium,VIP
join:2003-12-19
Alfred, ME
kudos:5
Reviews:
·Time Warner Cable
·VoicePulse
·Sprint Mobile Br..
·RapidVPS
Your upstream power level is quite high and can cause T3 errors. Do you normally have only 3 channels bonded or is it dropping channels at times?
--
Usenet Block Accounts | Unlimited Accounts


NOCTech75
Premium
join:2009-06-29
Marietta, GA
It's been the same level for awhile now... It was the same level Sept 5th, Sept 4th, Sept 3rd, etc. It was the same level during the last outage.


swintec
Premium,VIP
join:2003-12-19
Alfred, ME
kudos:5
Reviews:
·Time Warner Cable
·VoicePulse
·Sprint Mobile Br..
·RapidVPS
Same modulation and channel type? This changes everything.

Do the values change much during the day when it is hotter outside?

Max transmit is about 52 for a bonded DOCSIS 3 modem. You are right there according to your posted levels. Any fluctuations due to weather (or something else) could easily cause issues.

I would get things at least under 50 before looking at anything else.
--
Usenet Block Accounts | Unlimited Accounts

rody_44
Premium
join:2004-02-20
Quakertown, PA
reply to NOCTech75
Yea, 52 power is border ok. If you cant get it down you are going to need a tech. As long as you stay at them levels its going to be in and out. As much as you try phone support isnt going to be able to help you with out of spec levels.


NOCTech75
Premium
join:2009-06-29
Marietta, GA
Reviews:
·Comcast
reply to NOCTech75
Power levels had nothing to do with the outage. Did a truck roll and got the upstream dropped a couple of DB... when the tech logged in there was an "outage" declared in my area. No idea what the hell the outage is.. well it didn't get fixed until early Friday morning, connection good as new. Now it's Saturday night, same issue, T3 timeouts and again an outage has been declared. This is getting to be absurd.. completely shoddy service that had nothing to do with my signals.