Contributor
•
60 Messages
Started Unicast Maintenance Ranging - No Response received - T3 time-out -- every day
Some days ago, I received several text messages from Comcast indicating there was an urgent problem with my internet service and that it would be unavailable for several hours.
This happened at least twice.
We noticed no internet trouble and there were no outages.
However, ever since these text messages arrived, my modem (Arris S33) reports errors about once a day. Sometimes twice a day.
The error is of the sort: Started Unicast Maintenance Ranging - No Response received - T3 time-out; XXX CM-VER=3.1;
The modem logs never had these errors other than when first booting, and since the texts, every day.
Is this an issue? Whose issue is it and how do I get it fixed?
_____
The status listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.
| Startup Procedure | ||
|---|---|---|
| Procedure | Status | Comment |
| Acquire Downstream Channel | 489000000 Hz | Locked |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Configuration File | OK | |
| Security | Enabled | BPI+ |
| DOCSIS Network Access Enabled | Allowed | |
| Downstream Bonded Channels | |||||||
|---|---|---|---|---|---|---|---|
| Channel ID | Lock Status | Modulation | Frequency | Power | SNR/MER | Corrected | Uncorrectables |
| 13 | Locked | QAM256 | 489000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 10 | Locked | QAM256 | 471000000 Hz | 8 dBmV | 42 dB | 0 | 0 |
| 11 | Locked | QAM256 | 477000000 Hz | 9 dBmV | 42 dB | 0 | 0 |
| 12 | Locked | QAM256 | 483000000 Hz | 8 dBmV | 42 dB | 0 | 0 |
| 14 | Locked | QAM256 | 495000000 Hz | 9 dBmV | 42 dB | 0 | 0 |
| 15 | Locked | QAM256 | 507000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 16 | Locked | QAM256 | 513000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 17 | Locked | QAM256 | 519000000 Hz | 9 dBmV | 42 dB | 0 | 0 |
| 18 | Locked | QAM256 | 525000000 Hz | 9 dBmV | 42 dB | 0 | 0 |
| 19 | Locked | QAM256 | 531000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 20 | Locked | QAM256 | 537000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 21 | Locked | QAM256 | 543000000 Hz | 9 dBmV | 42 dB | 0 | 0 |
| 22 | Locked | QAM256 | 549000000 Hz | 9 dBmV | 42 dB | 0 | 0 |
| 23 | Locked | QAM256 | 555000000 Hz | 7 dBmV | 41 dB | 0 | 0 |
| 24 | Locked | QAM256 | 561000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 25 | Locked | OFDM PLC | 690000000 Hz | 5 dBmV | 38 dB | 720339312 | 0 |
| 26 | Locked | QAM256 | 567000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 27 | Locked | QAM256 | 573000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 28 | Locked | QAM256 | 579000000 Hz | 7 dBmV | 41 dB | 0 | 0 |
| 29 | Locked | QAM256 | 585000000 Hz | 7 dBmV | 41 dB | 0 | 0 |
| 30 | Locked | QAM256 | 591000000 Hz | 8 dBmV | 41 dB | 0 | 0 |
| 31 | Locked | QAM256 | 597000000 Hz | 7 dBmV | 41 dB | 0 | 0 |
| 32 | Locked | QAM256 | 603000000 Hz | 7 dBmV | 40 dB | 0 | 0 |
| 33 | Locked | QAM256 | 609000000 Hz | 7 dBmV | 40 dB | 0 | 0 |
| 34 | Locked | QAM256 | 615000000 Hz | 7 dBmV | 40 dB | 0 | 0 |
| 35 | Locked | QAM256 | 621000000 Hz | 7 dBmV | 40 dB | 0 | 0 |
| 36 | Locked | QAM256 | 627000000 Hz | 6 dBmV | 40 dB | 0 | 0 |
| 37 | Locked | QAM256 | 633000000 Hz | 6 dBmV | 40 dB | 0 | 0 |
| 38 | Locked | QAM256 | 639000000 Hz | 6 dBmV | 40 dB | 0 | 0 |
| 39 | Locked | QAM256 | 645000000 Hz | 6 dBmV | 40 dB | 0 | 0 |
| 40 | Locked | QAM256 | 651000000 Hz | 6 dBmV | 40 dB | 0 | 0 |
| 41 | Locked | QAM256 | 657000000 Hz | 6 dBmV | 40 dB | 0 | 0 |
| Upstream Bonded Channels | ||||||
|---|---|---|---|---|---|---|
| Channel ID | Lock Status | US Channel Type | Frequency | Width | Power | |
| 2 | Locked | SC-QAM | 16300000 Hz | 6400000 | 35.0 dBmV | |
| 3 | Locked | SC-QAM | 22800000 Hz | 6400000 | 34.8 dBmV | |
| 4 | Locked | SC-QAM | 29200000 Hz | 6400000 | 34.0 dBmV | |
| 9 | Locked | SC-QAM | 35600000 Hz | 6400000 | 35.3 dBmV | |
| 10 | Locked | SC-QAM | 40400000 Hz | 3200000 | 37.5 dBmV | |
Current System Time:Tue Dec 10 09:00:17 2024
XfinityBradM
Official Employee
•
739 Messages
24 days ago
Hey there, @vadeltachi. The downstream is a bit on the high side which can cause the T3 timeouts you're mentioning. Have you gone around to check on any splitters in the home and eliminated any of those or check if the connections have gotten loose over the years? That is a great place to start on the physical troubleshooting end. What other troubleshooting steps have you taken?
0
0
EG
Expert
•
107.8K Messages
24 days ago
@vadeltachi @XfinityBradM
FWIW. Eliminating splitters will make the downstream power even higher....
@vadeltachi
T3's once or twice a day is nothing. They are only a problem when they become more numerous / continuous. If you are not experiencing any connection problems / dropouts, don't sweat it.
0
0