I recently got the arris telephony modem and sagemcom router as a replacement because my techniclor one would reboot every so often. All coax cables and snug, and there isnt any damage to the line. However, I don't think that there are supposed to be this many errors if everything is within spec. Keep in mind the internet hasn't rebooted as much, but it has rebooted once in a while.
Internet service is TWC 200/20
RF Parameters |
Downstream
DCID | Freq | Power | SNR | Modulation | Octets | Correcteds | Uncorrectables | |
Downstream 1 | 24 | 855.00 MHz | -4.10 dBmV | 38.61 dB | 256QAM | 39652633631 | 0 | 0 |
Downstream 2 | 9 | 765.00 MHz | -2.70 dBmV | 38.98 dB | 256QAM | 24123467560 | 14 | 0 |
Downstream 3 | 10 | 771.00 MHz | -3.00 dBmV | 38.98 dB | 256QAM | 23440269293 | 16 | 0 |
Downstream 4 | 11 | 777.00 MHz | -2.50 dBmV | 38.98 dB | 256QAM | 24036174878 | 14 | 0 |
Downstream 5 | 12 | 783.00 MHz | -3.10 dBmV | 38.61 dB | 256QAM | 24299592184 | 0 | 0 |
Downstream 6 | 13 | 789.00 MHz | -2.80 dBmV | 38.61 dB | 256QAM | 24594296615 | 7 | 0 |
Downstream 7 | 14 | 795.00 MHz | -3.00 dBmV | 38.61 dB | 256QAM | 24982798990 | 0 | 0 |
Downstream 8 | 15 | 801.00 MHz | -3.50 dBmV | 38.61 dB | 256QAM | 23580239150 | 0 | 0 |
Downstream 9 | 16 | 807.00 MHz | -3.50 dBmV | 38.61 dB | 256QAM | 24255311912 | 151 | 1707 |
Downstream 10 | 17 | 813.00 MHz | -4.10 dBmV | 38.61 dB | 256QAM | 29803121174 | 250 | 2417 |
Downstream 11 | 18 | 819.00 MHz | -3.70 dBmV | 38.61 dB | 256QAM | 30007145003 | 1579 | 6671 |
Downstream 12 | 19 | 825.00 MHz | -4.10 dBmV | 37.64 dB | 256QAM | 39226297486 | 9004 | 41497 |
Downstream 13 | 20 | 831.00 MHz | -3.90 dBmV | 38.61 dB | 256QAM | 31560261352 | 69 | 25 |
Downstream 14 | 21 | 837.00 MHz | -3.70 dBmV | 37.64 dB | 256QAM | 31253263264 | 0 | 0 |
Downstream 15 | 22 | 843.00 MHz | -3.90 dBmV | 37.64 dB | 256QAM | 24960057719 | 5 | 0 |
Downstream 16 | 23 | 849.00 MHz | -3.50 dBmV | 38.61 dB | 256QAM | 29831676302 | 0 | 0 |
Downstream 17 | 25 | 861.00 MHz | -3.80 dBmV | 37.64 dB | 256QAM | 25067340434 | 6 | 0 |
Downstream 18 | 26 | 867.00 MHz | -4.50 dBmV | 37.64 dB | 256QAM | 24916904286 | 5 | 0 |
Downstream 19 | 27 | 873.00 MHz | -4.20 dBmV | 38.61 dB | 256QAM | 26016415044 | 0 | 0 |
Downstream 20 | 28 | 879.00 MHz | -4.60 dBmV | 37.36 dB | 256QAM | 26302200700 | 0 | 0 |
Downstream 21 | 29 | 885.00 MHz | -4.90 dBmV | 37.64 dB | 256QAM | 26692518859 | 8 | 0 |
Downstream 22 | 30 | 891.00 MHz | -4.90 dBmV | 37.64 dB | 256QAM | 26736581525 | 17 | 0 |
Downstream 23 | 31 | 897.00 MHz | -5.50 dBmV | 37.36 dB | 256QAM | 27320522582 | 31 | 0 |
Downstream 24 | 32 | 903.00 MHz | -4.80 dBmV | 37.64 dB | 256QAM | 29934946299 | 19 | 0 |
Reset FEC Counters |
Upstream
UCID | Freq | Power | Channel Type | Symbol Rate | Modulation | |
Upstream 1 | 4 | 37.00 MHz | 43.00 dBmV | DOCSIS2.0 (ATDMA) | 5120 kSym/s | 64QAM |
Upstream 2 | 3 | 30.60 MHz | 41.75 dBmV | DOCSIS2.0 (ATDMA) | 5120 kSym/s | 64QAM |
Upstream 3 | 2 | 24.20 MHz | 41.25 dBmV | DOCSIS2.0 (ATDMA) | 5120 kSym/s | 64QAM |
Upstream 4 | 1 | 19.40 MHz | 41.25 dBmV | DOCSIS1.x (TDMA) | 2560 kSym/s | 16QAM |
Status |
System Uptime: | 20 d: 3 h: 27 m |
Computers Detected: | staticCPE(1), dynamicCPE(1) |
CM Status: | Telephony-Reg Complete |
Time and Date: | Wed 2018-05-16 08:14:25 |
Interface Parameters |
Interface Name | Provisioned | State | Speed (Mbps) | MAC address |
LAN | Enabled | Up | 1000(Full) | 90:9D:7D:86:27:01 |
CABLE | Enabled | Up | ----- | 90:9D:7D:86:27:02 |
MTA | Pass | Up | ----- | 90:9D:7D:86:27:03 |
DOCSIS(CM) Events |
Date Time | Event ID | Event Level | Description |
5/1/2018 4:12 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/1/2018 4:20 | 84000700 | 5 | RCS Partial Service;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/1/2018 9:50 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/3/2018 5:18 | 68010300 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/3/2018 5:18 | 68010600 | 6 | DHCP Renew - lease parameters time server-98.150.3.95;tftp file-?BEWGlyeQnX2GJwIKS8lv@CkvJb68yI_RSJUgeLSbnroOoSVNitv__ modified;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/4/2018 9:49 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/6/2018 17:18 | 68010300 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/6/2018 17:18 | 68010600 | 6 | DHCP Renew - lease parameters time server-98.150.3.100;tftp file-?BEWGlyeQnX2GJwIKS8lv@CkvJbzzVHudz4k0_FrH7VJOdGm2ToIb3 modified;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/8/2018 8:39 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/8/2018 20:17 | 84000700 | 5 | RCS Partial Service;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/10/2018 5:18 | 68010300 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/10/2018 5:18 | 68010600 | 6 | DHCP Renew - lease parameters time server-98.150.3.95;tftp file-?BEWGlyeQnX2GJwIKS8lv@CkvJb8QJUVQLSe2CzOdlDv4fSFHjTbfb modified;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/10/2018 5:32 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/13/2018 17:18 | 68010300 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/13/2018 17:18 | 68010600 | 6 | DHCP Renew - lease parameters tftp file-?BEWGlyeQnX2GJwIKS8lv@CkvJb2mR+r5rZc521F4jOpweUi3nLuv_ modified;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/13/2018 22:14 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/13/2018 23:54 | 84000700 | 5 | RCS Partial Service;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/14/2018 6:56 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/15/2018 5:59 | 84000700 | 5 | RCS Partial Service;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
5/15/2018 9:46 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=90:9d:7d:86:27:02;CMTS-MAC=00:01:5c:76:ba:71;CM-QOS=1.1;CM-VER=3.0; |
PacketCable(MTA) Events |
Date Time | Event ID | Description |
4/23/2018 14:33 | 16 | MTA TFTP: Successful |
4/23/2018 14:33 | 26 | MTA PROV: Successful! |
4/23/2018 14:33 | 3 | Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS |
4/23/2018 14:33 | 3 | Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS |
4/23/2018 14:36 | 16 | MTA TFTP: Successful |
4/23/2018 14:36 | 26 | MTA PROV: Successful! |
4/23/2018 14:36 | 3 | Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS |
4/23/2018 14:36 | 3 | Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS |
4/23/2018 14:42 | 16 | MTA TFTP: Successful |
4/23/2018 14:42 | 26 | MTA PROV: Successful! |
4/23/2018 14:42 | 3 | Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS |
4/23/2018 14:42 | 3 | Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS |
4/26/2018 4:48 | 16 | MTA TFTP: Successful |
4/26/2018 4:48 | 26 | MTA PROV: Successful! |
4/26/2018 4:48 | 3 | Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS |
4/26/2018 5:18 | 4000960006 | New time has been retrieved from ToD server. |
5/3/2018 5:18 | 4000960006 | New time has been retrieved from ToD server. |
5/6/2018 17:18 | 4000960006 | New time has been retrieved from ToD server. |
5/10/2018 5:18 | 4000960006 | New time has been retrieved from ToD server. |
This isn't a modem problem, it's a coax signal problem. There is interference somewhere...loose connections, chewed/water-logged coax, etc. that is causing the problem, probably cell phone frequencies leaking in. If all of your connections are tight, no unterminated ports, no damaged coax from the modem to the main line, then the issue could be somewhere in the yard, street, or further upstream.
Is this enough proof to have Tier 3 send out a lineman or would it need to be service affecting?
As I understand the procedure, a customer doesn't get to ask for a Tier 3 service crew. Tier 3 is responsible for cable plant maintenance. Your home service tech should make a request for Tier 3 assistance after determining that the problem is caused by something in the exterior cable plant, not customer or company equipment in the home. Note that different local franchises may handle this differently, despite Spectrum in theory being a single very large company with uniform policies and practices.