13 Messages
No Ranging Response received - T3 time-out
I had a tech out a few months ago after upgrading my Internet speeds and not being able to obtain promised upload speeds. He voluntarily replaced one of the outside lines and coax splitters. Then, suddenly there were frequent announcements that work was being done in town that lasted over an week, no explanation given.
Unfortunately, family emergencies kept me at a hospital. Back at home I still wasn’t receiving advertised upload speeds. Things have finally calmed down and I went to take a closer look at what was going on because we have been receiving intermittent disconnects.
Two days ago, I went crazy speaking with online outsourced tech support and got nowhere. I even posted some of my modem’s logs for them to see the disconnects and errors. When one rep found out I had been using my own modem, he simply stated I needed to rent one from you which is ridiculous. I’ve had my own modems for over 15 years without any issues like this. In fact, the modem was working fine prior to the speed upgrade and also the original person updating my modem’s bootfile.
I can’t afford to have these intermittent connections, so I replaced my 1 year-old supported Motorola Docsis 3.1 modem with a newer Arris S34 last night and provisioned it.
Lo and behold, I’ve gone up from ~45 mbps upload speeds to around 340 mbps speeds.
It would have nice if your techs were knowledgeable/trained enough from the start to let me know that the poor upload speeds could have been resolved with a newer modem that had more upload channels. It would have saved everyone a lot of time.
This aside, I’m still getting some critical errors that I’m monitoring closely. I’ve checked my connections and the coax is a home run. The connections are all tight, even the new ones on the outside. No splitters. T3 critical errors indicate that the problem is a CMTS communication issue back Xfinity, with the intermittent problem likely at the street. I don’t know if you have a newer bootfile for this brand new model (also recently released) that could address these errors.
It’s a new modem, and I was having issues with the previous one as well so I’m ruling out these supported modems as a culprit. I don’t want to be held random to your modems as a “solution” either.
Please address this without giving me the run around over and over again. Thank you.
Here is the latest logs:
Downstream Bonded Channels | |||||||
---|---|---|---|---|---|---|---|
Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
4 | Locked | 256QAM | 411000000 Hz | -1.3 dBmV | 43.4 dB | 0 | 0 |
12 | Locked | 256QAM | 459000000 Hz | -1.3 dBmV | 40.4 dB | 0 | 0 |
20 | Locked | 256QAM | 507000000 Hz | -1.3 dBmV | 43.4 dB | 0 | 0 |
28 | Locked | 256QAM | 555000000 Hz | -1.8 dBmV | 40.9 dB | 0 | 0 |
1 | Locked | 256QAM | 393000000 Hz | -1.4 dBmV | 43.4 dB | 0 | 0 |
2 | Locked | 256QAM | 399000000 Hz | -1.4 dBmV | 43.4 dB | 0 | 0 |
3 | Locked | 256QAM | 405000000 Hz | -1.4 dBmV | 40.9 dB | 0 | 0 |
5 | Locked | 256QAM | 417000000 Hz | -1.4 dBmV | 40.9 dB | 0 | 0 |
6 | Locked | 256QAM | 423000000 Hz | -1.4 dBmV | 40.9 dB | 0 | 0 |
7 | Locked | 256QAM | 429000000 Hz | -1.4 dBmV | 40.9 dB | 0 | 0 |
8 | Locked | 256QAM | 435000000 Hz | -1.6 dBmV | 43.4 dB | 0 | 0 |
9 | Locked | 256QAM | 441000000 Hz | -1.6 dBmV | 40.9 dB | 0 | 0 |
10 | Locked | 256QAM | 447000000 Hz | -1.5 dBmV | 40.9 dB | 0 | 0 |
11 | Locked | 256QAM | 453000000 Hz | -1.3 dBmV | 43.4 dB | 0 | 0 |
13 | Locked | 256QAM | 465000000 Hz | -1.3 dBmV | 43.4 dB | 0 | 0 |
14 | Locked | 256QAM | 471000000 Hz | -1.2 dBmV | 43.4 dB | 0 | 0 |
15 | Locked | 256QAM | 477000000 Hz | -1.3 dBmV | 40.9 dB | 0 | 0 |
16 | Locked | 256QAM | 483000000 Hz | -1.3 dBmV | 40.9 dB | 0 | 0 |
17 | Locked | 256QAM | 489000000 Hz | -1.3 dBmV | 43.4 dB | 0 | 0 |
18 | Locked | 256QAM | 495000000 Hz | -1.3 dBmV | 40.9 dB | 0 | 0 |
19 | Locked | 256QAM | 501000000 Hz | -1.3 dBmV | 40.9 dB | 0 | 0 |
21 | Locked | 256QAM | 513000000 Hz | -1.4 dBmV | 40.9 dB | 0 | 0 |
22 | Locked | 256QAM | 519000000 Hz | -1.3 dBmV | 40.9 dB | 0 | 0 |
23 | Locked | 256QAM | 525000000 Hz | -1.4 dBmV | 40.9 dB | 0 | 0 |
24 | Locked | 256QAM | 531000000 Hz | -1.5 dBmV | 40.9 dB | 0 | 0 |
25 | Locked | 256QAM | 537000000 Hz | -1.6 dBmV | 40.9 dB | 0 | 0 |
26 | Locked | 256QAM | 543000000 Hz | -1.7 dBmV | 40.9 dB | 0 | 0 |
27 | Locked | 256QAM | 549000000 Hz | -1.8 dBmV | 40.9 dB | 0 | 0 |
29 | Locked | 256QAM | 561000000 Hz | -1.9 dBmV | 40.9 dB | 0 | 0 |
30 | Locked | 256QAM | 567000000 Hz | -1.9 dBmV | 40.9 dB | 0 | 0 |
31 | Locked | 256QAM | 573000000 Hz | -1.9 dBmV | 40.9 dB | 0 | 0 |
32 | Locked | 256QAM | 579000000 Hz | -2.0 dBmV | 40.4 dB | 0 | 0 |
193 | Locked | OFDM PLC | 690000000 Hz | -3.2 dBmV | 42.0 dB | 37412729 | 0 |
194 | Locked | OFDM PLC | 957000000 Hz | -6.9 dBmV | 40.0 dB | 56558461 | 0 |
Upstream Bonded Channels | ||||||
---|---|---|---|---|---|---|
Channel ID | Lock Status | US Channel Type | Frequency | Width | Power | |
18 | Locked | SC-QAM | 22800000 Hz | 6400000 | 38.0 dBmV | |
20 | Locked | SC-QAM | 35600000 Hz | 6400000 | 38.8 dBmV | |
19 | Locked | SC-QAM | 29200000 Hz | 6400000 | 38.3 dBmV | |
17 | Locked | SC-QAM | 16400000 Hz | 6400000 | 37.3 dBmV | |
43 | Locked | OFDMA | 36200000 Hz | 44400000 | 35.0 dBmV |
10/03/2024 10:26:22 | Critical | No Ranging Response received - T3 time-out;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
/03/2024 08:08:50 | Warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
10/03/2024 08:08:50 |
Warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
10/03/2024 07:59:54 | Warning | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
10/03/2024 07:59:31 | Error | Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
10/03/2024 07:58:20 |
Critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
10/03/2024 07:57:29 |
Warning | Lost MDD Timeout;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
10/03/2024 07:57:26 |
Notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
10/03/2024 07:57:21 |
Critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
10/03/2024 07:56:09 |
Warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=[REMOVED];CMTS-MAC=[REMOVED];CM-QOS=1.1;CM-VER=3.1; |
10/03/2024 07:56:09 |
Warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided |
No Responses!