Howling_Dog's profile

Frequent Visitor

 • 

7 Messages

Thursday, July 23rd, 2020 3:00 PM

Closed

Intermittent Loss of Service, Modem Log: "No Ranging Response received - T3 time-out"

I continue to have intermittent loss of connectivity about 2 to 5 times a day. The modem will reset on its own and the connection will be re-established. This is really difficult to deal with since conference calls and classes with online exams are now the norm. The modem log shows multiple T3 time outs throught out the day and seems to drop when a T4 - timeout is indicated. 

From the modem manufacturer info I noticed the downstream power is a little on the low side plus the upstream power is right on the edge. The manufacture recommends the downstream power to be between -15DbmV and +15DbmV. On the upstream recommendation is above 45Dbmv which is close but usually have 3 or all 4 channels below that. Looking for any help on this. I have been a customer for 25 years but this is really hurting the family. PS: Modem and router are new, dedicated coax cable with no splitter between the outside service connection and the modem. Net effect - same problem. 

 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked 256QAM 16 483.00 MHz -10.40 dBmV 37.64 dB 1481 8966
2 Locked 256QAM 8 435.00 MHz -9.50 dBmV 38.98 dB 1230 8560
3 Locked 256QAM 9 441.00 MHz -9.80 dBmV 38.61 dB 1581 9068
4 Locked 256QAM 10 447.00 MHz -9.70 dBmV 38.61 dB 1568 8923
5 Locked 256QAM 11 453.00 MHz -9.50 dBmV 38.98 dB 1568 9813
6 Locked 256QAM 12 459.00 MHz -9.90 dBmV 38.98 dB 1227 7295
7 Locked 256QAM 13 465.00 MHz -10.40 dBmV 38.98 dB 1485 9355
8 Locked 256QAM 14 471.00 MHz -10.20 dBmV 38.61 dB 1555 9403
9 Locked 256QAM 15 477.00 MHz -9.90 dBmV 38.61 dB 1412 9064
10 Locked 256QAM 17 489.00 MHz -10.90 dBmV 37.64 dB 995 7831
11 Locked 256QAM 18 495.00 MHz -10.70 dBmV 37.64 dB 1341 7002
12 Locked 256QAM 19 507.00 MHz -10.60 dBmV 37.64 dB 1308 7522

13 Locked 256QAM 20 513.00 MHz -10.90 dBmV 38.61 dB 1603 10255
14 Locked 256QAM 21 519.00 MHz -10.90 dBmV 38.61 dB 1562 7630
15 Locked 256QAM 22 525.00 MHz -10.90 dBmV 37.64 dB 1286 7702
16 Locked 256QAM 23 531.00 MHz -11.30 dBmV 37.64 dB 2104 7193
17 Locked 256QAM 24 537.00 MHz -11.70 dBmV 36.61 dB 1655 6607
18 Locked 256QAM 25 543.00 MHz -11.80 dBmV 37.36 dB 1320 8406
19 Locked 256QAM 26 549.00 MHz -12.20 dBmV 37.36 dB 1175 9105
20 Locked 256QAM 27 555.00 MHz -11.90 dBmV 37.64 dB 965 6033
21 Locked 256QAM 28 561.00 MHz -11.80 dBmV 37.36 dB 925 5234
22 Locked 256QAM 29 567.00 MHz -11.70 dBmV 37.64 dB 1136 5066
23 Locked 256QAM 30 573.00 MHz -12.10 dBmV 37.36 dB 1222 6108
24 Locked 256QAM 31 579.00 MHz -12.40 dBmV 37.64 dB 1350 7052
25 Locked 256QAM 32 585.00 MHz -11.70 dBmV 37.90 dB 311 3736
26 Locked 256QAM 33 591.00 MHz -11.40 dBmV 37.90 dB 90 3681
27 Locked 256QAM 34 597.00 MHz -11.60 dBmV 38.20 dB 97 3318
28 Locked 256QAM 35 603.00 MHz -12.00 dBmV 37.30 dB 52 2835
29 Locked 256QAM 36 609.00 MHz -12.20 dBmV 37.30 dB 102 2966
30 Locked 256QAM 37 615.00 MHz -12.40 dBmV 37.30 dB 58 1836
31 Locked 256QAM 38 621.00 MHz -11.90 dBmV 37.90 dB 84 2914
32 Locked 256QAM 39 627.00 MHz -11.70 dBmV 37.60 dB 51 2682

 

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 kSym/s 36.50 MHz 46.25 dBmV
2 Locked ATDMA 4 5120 kSym/s 17.30 MHz 43.25 dBmV
3 Locked ATDMA 3 5120 kSym/s 23.70 MHz 43.75 dBmV
4 Locked ATDMA 2 5120 kSym/s 30.10 MHz 44.25 dBmV

 

Frequent Visitor

 • 

7 Messages

5 years ago

The connection from the outside service is a straight run of coax. No spitters or any other device in the line. Ran a dedicated line of RG6 quad shield. Modem is new, Arris SB6190 and is on the list of recommended devices. The Arris modem replaced a Zoom modem I have had for a couple of years but the problem persists with exactly the same symptoms. Any help would be appreciated. Below is the current contents of the modem log which seems to hold about 20 of the lastest events. At least one outage should be captured in this log around 11:50ish. 

 

Time Priority Description
Thu Jul 23 11:49:39 2020 6 TLV-11 - unrecognized OID;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 11:54:09 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 11:58:21 2020 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 12:01:00 2020 6 TLV-11 - unrecognized OID;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 12:01:09 2020 3 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 13:49:28 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 14:40:59 2020 3 Ranging Request Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 14:40:59 2020 3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 14:41:23 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 14:47:47 2020 3 Ranging Request Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 14:47:47 2020 3 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 14:48:11 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 14:55:48 2020 6 TLV-11 - unrecognized OID;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 14:56:28 2020 5 RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 15:16:18 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 15:23:06 2020 5 RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 15:32:46 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 15:33:15 2020 5 RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 15:44:22 2020 3 No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;


Thu Jul 23 15:44:46 2020 5 RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;

 

Expert

 • 

110.3K Messages

5 years ago

The downstream power is low to being out of spec on some channels and it may be intermittently fluctuating even lower to out of spec levels on the rest. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

New Poster

 • 

1 Message

5 years ago

Checking the Internet Troubleshooting tips here is the signal level specs listed:

 

Downstream power level: min -10dBmV, max +10dBmV

Downstream signal to noise: Min 35dB

Upstream Power Level: min +35dBmV, Max +50dBmv

Upstream signal to noise: 31dB

 

An update on my end. Here is the latest stats from the modem log. 

 

Ok downstream power is within range so is signal to noise. Upstream power is within range  but upstream signal to noise is not displayed.

 

Note that downstream power has increased since the last post. What has changed is the installation of a new pull of RG6 Quad Sheild Coax from termination of the underground service on the side of the house to the modem. Direct connection with no splitters and just connectors on each end.  Still see T3 time outs in the log. Just connected new pull last night so will see what happens. The short outages are intermittent so I'm not holding my breath on this but the new cable pull did improve the downstream power levels.

 

 

 

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM16483.00 MHz-6.50 dBmV38.98 dB460627397
2Locked256QAM17489.00 MHz-6.80 dBmV38.98 dB511727485
3Locked256QAM18495.00 MHz-6.90 dBmV38.98 dB292924069
4Locked256QAM19507.00 MHz-6.70 dBmV40.37 dB412623356
5Locked256QAM20513.00 MHz-6.90 dBmV40.37 dB296720659
6Locked256QAM21519.00 MHz-6.90 dBmV40.37 dB402525382
7Locked256QAM22525.00 MHz-6.80 dBmV38.98 dB398124029
8Locked256QAM23531.00 MHz-7.20 dBmV38.98 dB285822123
9Locked256QAM24537.00 MHz-7.50 dBmV38.98 dB298922250
10Locked256QAM25543.00 MHz-7.60 dBmV40.37 dB399220050
11Locked256QAM26549.00 MHz-8.00 dBmV38.98 dB268119461
12Locked256QAM27555.00 MHz-7.60 dBmV40.37 dB301921086
13Locked256QAM28561.00 MHz-7.50 dBmV38.98 dB280220373
14Locked256QAM29567.00 MHz-7.50 dBmV38.61 dB305414927
15Locked256QAM30573.00 MHz-7.90 dBmV38.61 dB236914355
16Locked256QAM31579.00 MHz-8.20 dBmV40.37 dB305017764
17Locked256QAM32585.00 MHz-7.50 dBmV40.37 dB306617688
18Locked256QAM33591.00 MHz-7.10 dBmV40.37 dB368820167
19Locked256QAM34597.00 MHz-7.30 dBmV40.95 dB240117429
20Locked256QAM35603.00 MHz-7.70 dBmV38.98 dB231115255
21Locked256QAM36609.00 MHz-7.90 dBmV38.61 dB190412982
22Locked256QAM37615.00 MHz-7.90 dBmV38.61 dB170914528
23Locked256QAM38621.00 MHz-7.50 dBmV38.98 dB187514437
24Locked256QAM39627.00 MHz-7.20 dBmV40.37 dB286016499
25Locked256QAM40633.00 MHz-7.60 dBmV39.20 dB25313166
26Locked256QAM41639.00 MHz-8.20 dBmV38.90 dB40513128
27Locked256QAM42645.00 MHz-8.20 dBmV39.50 dB33513455
28Locked256QAM43651.00 MHz-7.50 dBmV39.50 dB28910077
29Locked256QAM44657.00 MHz-7.80 dBmV39.20 dB37011836
30Locked256QAM45663.00 MHz-8.40 dBmV38.90 dB40810699
31Locked256QAM46675.00 MHz-8.40 dBmV38.60 dB34511922
32Locked256QAM47681.00 MHz-9.10 dBmV38.60 dB43911745

 

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 kSym/s36.50 MHz43.00 dBmV
2LockedATDMA45120 kSym/s17.30 MHz39.00 dBmV
3LockedATDMA35120 kSym/s23.70 MHz39.75 dBmV
4LockedATDMA25120 kSym/s30.10 MHz41.50 dBmV



 

Current System Time: Fri Jul 24 09:54:11 2020

 

 

Time Priority Description

Thu Jul 23 20:59:46 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 21:16:31 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 21:31:11 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 21:48:22 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 21:48:22 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 22:01:04 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 22:29:26 20203SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 22:29:40 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 22:30:32 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jul 23 22:53:23 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 01:50:52 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 01:50:53 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 02:31:27 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 03:22:09 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 03:26:02 20203SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 04:11:38 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 04:11:38 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 04:36:23 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 04:36:23 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Fri Jul 24 04:45:56 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;

 

Expert

 • 

110.3K Messages

5 years ago

Well the downstream power is still on the weak side. 0 to +5 dB is the preferred area.

 

The upstream SNR can only be read by them from their end. When in doubt, get a tech out as stated.  Good luck !

Frequent Visitor

 • 

7 Messages

5 years ago

 

Ok I thought I was doing better with the replacement of the original house coax, vintage 1989, with a new pull of dedicated RG6 quad shield with no splitters, cable clamps, or other devices attached. Downstream power looks better and SNR looks better too. But just as I thought I might be over the intermittent loss of service issue it shows up again. Very frustrating. Looks to me like everytime a T4 time out error is registered the modem goes offline and has to re-intialize. Service is restored after the approximatly 5 minuite process. This seems to happen most frequently between 11:30am and about 6PM. Now everthing has been replaced, router, modem, coax to the service hookup point on the outside of the house. What a time consuming, expensive, and frustrating experience this continues to be. Given working from home and online school connectivity is critical. 

 

How can I connect with some techinical support from Comcast other than the usual lets reset the modem script that the front line service folks? Who can I call and what is the contact information for some technical help that can really help? Can someone check at the head end of the system and look at the what might be the issue here?

 

 

Time Priority Description

Sun Jul 26 16:15:37 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:23:04 20203Ranging Request Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:23:04 20203Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:23:28 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:29:52 20203Ranging Request Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:29:52 20203Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:30:16 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:36:40 20203Ranging Request Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:36:40 20203Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:37:04 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:41:52 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:44:36 20206TLV-11 - unrecognized OID;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:44:39 20203Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:47:15 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:51:27 20203Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 01 00:01:45 19703No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:54:16 20206TLV-11 - unrecognized OID;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 16:56:55 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 17:04:20 20205RCS Partial Service;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 17:05:58 20203No Ranging Response received - T3 time-out;CM-MAC=a4:98:13:cb:e3:e1;CMTS-MAC=00:01:5c:74:08:50;CM-QOS=1.1;CM-VER=3.0;

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM16483.00 MHz-6.20 dBmV38.98 dB8905989
2Locked256QAM8435.00 MHz-5.30 dBmV40.37 dB4624210
3Locked256QAM9441.00 MHz-5.50 dBmV40.37 dB6014977
4Locked256QAM10447.00 MHz-5.50 dBmV40.37 dB4084168
5Locked256QAM11453.00 MHz-5.30 dBmV40.37 dB13785766
6Locked256QAM12459.00 MHz-5.80 dBmV40.37 dB13824426
7Locked256QAM13465.00 MHz-6.20 dBmV40.37 dB8746360
8Locked256QAM14471.00 MHz-6.10 dBmV40.37 dB8274989
9Locked256QAM15477.00 MHz-5.70 dBmV40.95 dB8964766
10Locked256QAM17489.00 MHz-6.60 dBmV38.98 dB7724889
11Locked256QAM18495.00 MHz-6.70 dBmV38.98 dB5454181
12Locked256QAM19507.00 MHz-6.50 dBmV40.37 dB11054674
13Locked256QAM20513.00 MHz-6.70 dBmV40.37 dB4324195
14Locked256QAM21519.00 MHz-6.50 dBmV40.37 dB4514303
15Locked256QAM22525.00 MHz-6.50 dBmV38.98 dB7854900
16Locked256QAM23531.00 MHz-6.90 dBmV40.37 dB6211909
17Locked256QAM24537.00 MHz-7.20 dBmV38.98 dB3814560
18Locked256QAM25543.00 MHz-7.30 dBmV40.37 dB5614037
19Locked256QAM26549.00 MHz-7.60 dBmV38.98 dB6414220
20Locked256QAM27555.00 MHz-7.40 dBmV40.37 dB3903369
21Locked256QAM28561.00 MHz-7.30 dBmV38.98 dB4494390
22Locked256QAM29567.00 MHz-7.20 dBmV38.98 dB5462068
23Locked256QAM30573.00 MHz-7.60 dBmV38.61 dB5233946
24Locked256QAM31579.00 MHz-7.90 dBmV40.37 dB3902145
25Locked256QAM32585.00 MHz-7.20 dBmV39.50 dB1403590
26Locked256QAM33591.00 MHz-6.80 dBmV39.50 dB662801
27Locked256QAM34597.00 MHz-7.00 dBmV39.90 dB681833
28Locked256QAM35603.00 MHz-7.40 dBmV39.20 dB692947
29Locked256QAM36609.00 MHz-7.50 dBmV39.20 dB892973
30Locked256QAM37615.00 MHz-7.70 dBmV38.90 dB753009
31Locked256QAM38621.00 MHz-7.20 dBmV39.50 dB1572857
32Locked256QAM39627.00 MHz-7.00 dBmV39.90 dB1182717

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 kSym/s36.50 MHz42.00 dBmV
2LockedATDMA45120 kSym/s17.30 MHz39.00 dBmV
3LockedATDMA35120 kSym/s23.70 MHz39.50 dBmV
4LockedATDMA25120 kSym/s30.10 MHz40.50 dBmV


 

Current System Time: Sun Jul 26 19:31:45 2020

New Poster

 • 

1 Message

5 years ago

Same issue here. The modem log is full of "No Ranging Response received - T3 time-out;" until the connection is finally lost. Mine does not reboot on its own, need to do that myself. It was fine a week or two after we got connected to Xfinity, but now outages become more and more frequent and interfere with my work. RF parameters look OK. Research on the internet tells me the issue is cable-related and can only be resolved by the specialists. However, no means of contact is provided for such case by Xfinity. Am I to speak with their chatbot for that? Must I visit an Xfinity store? They are of absolutely no help.

 

If I am mistaken and the human tech support do have an email or phone which opens into the outer world, please let me know. 

Frequent Visitor

 • 

7 Messages

5 years ago

I had a zoom modem which did not "reset" itself and come back online. In my effort to solve the issue I replaced it with a Arris SB6190. At least it will figure out the connection is lost and re-establish the connection. This is important since the wife is not real happy about unplugging the modem and getting a connection back. 

 

BTW: A co-worker has the same Comcast issue along with his mothers' Comcast connection. He is in the general area but not on the same Comcast network segment. Also there are some great youtube videos about T3 and T4 time outs. 

 

One thing I wonder about is my downstream power is in the -7dbmv range which is acceptable by Comcast standards (+10dbmv thru -10dbmv) but wonder if it would help if the downstream power level was more like 0dbmv to +2dbmv range? Is the power level  a function of the modem to Comcast communications negotiations? Is it only of function of the infastructure cable connections? Can this be adjusted by Comcast? 

 

Also the intermittent loss of communications happens primarily in the time frame of 11:30am to about 6pm. This is very suspicious. Could this be a high traffic time on the section of the Comcast network that I am connected to? Is this a symptom of Comcast inability to deal with more traffic due to the current home bound situation? All I want is a stable internet connection which is what I pay for. Really don't want to change providers but this is getting really old.

Frequent Visitor

 • 

7 Messages

5 years ago

Good information about cable modems and broadband infastructure from Volpe Firm. See youtube videos from this guy. Learning more than I ever wanted to know about this in an effort to just get stable internet service. Can anybody help from Comcast here?

 

https://volpefirm.com/

 

I seem to get a drop in service when I get a T4 timeout in the modem log. The modem re-registers and service will be restored in about 5 min. I seem to always get T3 time outs but is able to maintain an internet connection when just T3's happens. 

 

From Volpe:

T4 Timeout ( Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received )

Explanation: The cable modem did not received a station maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) message within the T4 timeout period (30 to 35 seconds). The cable modem is resetting its cable interface and restarting the registration process. Typically, this indicates an occasional, temporary loss of service, but if the problem persists, check for possible service outages or maintenance activity on this particular headend system. This error message is DOCSIS event message is R04.0, Ranging Request.

Frequent Visitor

 • 

7 Messages

5 years ago

Put in my last ditch effort to at least minimize this problem. I moved the modem to the basement so I could have a 6 foot section of RG6 from the outside of the house to the modem. Than ran the ethernet to the router from there. So the downstream power is in a better place but within 10 min of doing this another intermittent outage. I've done all I can do on this one. 

 

Anybody from Comcast there?????? A phone number for technical support other than someone to tell be to reset the modem???? Could use some support on this!

 

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM16483.00 MHz-2.70 dBmV40.37 dB739
2Locked256QAM17489.00 MHz-2.90 dBmV40.37 dB00
3Locked256QAM18495.00 MHz-2.90 dBmV40.95 dB00
4Locked256QAM19507.00 MHz-2.80 dBmV40.37 dB00
5Locked256QAM20513.00 MHz-3.10 dBmV40.95 dB60
6Locked256QAM21519.00 MHz-3.20 dBmV40.95 dB00
7Locked256QAM22525.00 MHz-3.20 dBmV40.37 dB00
8Locked256QAM23531.00 MHz-3.40 dBmV40.37 dB00
9Locked256QAM24537.00 MHz-3.70 dBmV40.37 dB00
10Locked256QAM25543.00 MHz-3.70 dBmV40.37 dB70
11Locked256QAM26549.00 MHz-4.20 dBmV40.37 dB00
12Locked256QAM27555.00 MHz-4.00 dBmV40.37 dB00
13Locked256QAM28561.00 MHz-3.80 dBmV40.95 dB00
14Locked256QAM29567.00 MHz-3.80 dBmV40.37 dB00
15Locked256QAM30573.00 MHz-3.70 dBmV40.37 dB00
16Locked256QAM31579.00 MHz-3.90 dBmV40.95 dB00
17Locked256QAM32585.00 MHz-3.20 dBmV40.37 dB00
18Locked256QAM33591.00 MHz-3.10 dBmV40.95 dB00
19Locked256QAM34597.00 MHz-3.40 dBmV40.95 dB00
20Locked256QAM35603.00 MHz-3.60 dBmV40.37 dB00
21Locked256QAM36609.00 MHz-3.40 dBmV40.37 dB00
22Locked256QAM37615.00 MHz-3.30 dBmV40.37 dB00
23Locked256QAM38621.00 MHz-2.90 dBmV40.37 dB00
24Locked256QAM39627.00 MHz-2.90 dBmV40.95 dB00
25Locked256QAM40633.00 MHz-3.50 dBmV38.20 dB00
26Locked256QAM41639.00 MHz-4.10 dBmV39.20 dB00
27Locked256QAM42645.00 MHz-3.70 dBmV41.10 dB00
28Locked256QAM43651.00 MHz-2.80 dBmV39.50 dB00
29Locked256QAM44657.00 MHz-3.00 dBmV39.50 dB00
30Locked256QAM45663.00 MHz-3.80 dBmV38.90 dB00
31Locked256QAM46675.00 MHz-3.90 dBmV38.90 dB00
32Locked256QAM47681.00 MHz-4.50 dBmV38.60 dB00

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 kSym/s36.50 MHz40.50 dBmV
2LockedATDMA45120 kSym/s17.30 MHz36.75 dBmV
3LockedATDMA35120 kSym/s23.70 MHz37.75 dBmV
4LockedATDMA25120 kSym/s30.10 MHz38.75 dBmV


 

Current System Time: Tue Jul 28 19:08:06 2020

Visitor

 • 

1 Message

4 years ago

I know this is a year old, but wanted to say that I suffer the exact same issues, for years now. Like you I went through all of the hoops replacing stuff. Comcast is of no help and gives generic responses, or tells me it is my responsibility.

My Downstream and SNR is good. But the problems persist. This has to be a service interrupt...

I just wanted to show that even with really good numbers, the issue persists.

1 Locked QAM256 13 495000000 Hz -1.6 dBmV 42.1 dB
2 Locked QAM256 1 423000000 Hz -1.2 dBmV 42.5 dB
3 Locked QAM256 2 429000000 Hz -1.4 dBmV 42.4 dB
4 Locked QAM256 3 435000000 Hz -1.3 dBmV 42.4 dB
5 Locked QAM256 4 441000000 Hz -1.4 dBmV 42.4 dB
6 Locked QAM256 5 447000000 Hz -1.3 dBmV 42.4 dB
7 Locked QAM256 6 453000000 Hz -1.3 dBmV 42.3 dB
8 Locked QAM256 7 459000000 Hz -1.3 dBmV 42.3 dB
9 Locked QAM256 8 465000000 Hz -1.1 dBmV 42.3 dB
10 Locked QAM256 9 471000000 Hz -1.0 dBmV 42.4 dB
11 Locked QAM256 10 477000000 Hz -1.0 dBmV 38.9 dB
12 Locked QAM256 11 483000000 Hz -1.1 dBmV 41.3 dB
13 Locked QAM256 12 489000000 Hz -1.4 dBmV 42.3 dB
14 Locked QAM256 14 501000000 Hz -1.8 dBmV 42.0 dB
15 Locked QAM256 15 507000000 Hz -2.0 dBmV 40.1 dB
16 Locked QAM256 16 513000000 Hz -2.4 dBmV 41.5 dB

(edited)

Expert

 • 

110.3K Messages

@Kupua

Please create a new topic of your own here on this board detailing your issue. Thanks.  Year old dead thread now being closed.

 

I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Please mark an Accepted Answer!tick
forum icon

New to the Community?

Start Here