Disconnected from "Received Response to Broadcast Maintenance Request"
Does any know what this is? Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1c:1b:68:a1:6d:3f;CMTS-MAC=00:12:d9:54:26:c0;CM-QOS=1.1;CM-VER=3.0; This is from my modem's event log. Every time this happens I get disconnected from the internet.26KViews0likes22CommentsSlow real time upload speed - conflicting speed test results
I'm experiencing slow real time upload speeds. The speed test on Cox website have conflicting results. I've had 8 techs out to my house over the last 4 months and the issue has not been resolved. I am experiencing the same exact issues as usernoah82. We are both in Arizona. Here is his thread.http://forums.cox.com/forum_home/internet_forum/f/5/t/13025.aspx9.3KViews0likes34CommentsPacket Loss and Latency Spikes
This is not the first time this is happened (it happens periodically), but I am having issues with packet loss and disconnects between my modem and the ISP (hop 2). They are intermittent and very annoying. I pay $75 a month for fast internet, and I am the only person who uses it, yet I have constant problems. I had these issues with the old Cox-issed Cisco modem and my current Surfboard SB6183. Same issues with three different routers as well (Apple AirPort Extreme, Netgear Nighthawk X6, Linksys WRT1900AC). It has to be on Cox's end, but I get zero help when I call in and talk to support. They always ask me stupid questions (have you reset the modem, have you checked your router, have you tried connecting directly to the modem via ethernet, etc.) and say everything looks fine on their end. I had a tech out last month and he pulled a filter/splitter off and replaced it and said things were fixed. I was at work when he came and my housemate said that he was here for about 10 minutes. Below is a screenshot of Pingplotter, the status page of my modem, and the event log of my modem. http://i.imgur.com/1Gnp1a5.png Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 73 813000000 Hz 8.7 dBmV 40.2 dB 9 65 2 Locked QAM256 74 819000000 Hz 9.1 dBmV 40.3 dB 23 48 3 Locked QAM256 75 825000000 Hz 8.9 dBmV 40.3 dB 17 56 4 Locked QAM256 76 831000000 Hz 9.1 dBmV 40.2 dB 43 133 5 Locked QAM256 77 837000000 Hz 9.4 dBmV 40.3 dB 15 84 6 Locked QAM256 78 843000000 Hz 9.8 dBmV 40.1 dB 11 67 7 Locked QAM256 79 849000000 Hz 9.7 dBmV 40.5 dB 13 60 8 Locked QAM256 80 855000000 Hz 9.6 dBmV 40.3 dB 18 69 9 Locked QAM256 89 909000000 Hz 8.8 dBmV 40.3 dB 15 55 10 Locked QAM256 90 915000000 Hz 8.7 dBmV 40.3 dB 38 61 11 Locked QAM256 91 921000000 Hz 8.7 dBmV 40.3 dB 24 98 12 Locked QAM256 92 927000000 Hz 9.2 dBmV 40.5 dB 38 31 13 Locked QAM256 93 933000000 Hz 8.8 dBmV 40.3 dB 22 81 14 Locked QAM256 94 939000000 Hz 8.2 dBmV 40.1 dB 49 107 15 Locked QAM256 95 945000000 Hz 7.7 dBmV 39.9 dB 18 57 16 Locked QAM256 96 951000000 Hz 8.2 dBmV 40.0 dB 12 69 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 5120 Ksym/sec 37300000 Hz 36.9 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 19400000 Hz 34.8 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 24300000 Hz 35.3 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 30800000 Hz 36.0 dBmV Current System Time:Mon Jan 02 20:18:17 2017 Time Priority Description Mon Jan 02 20:02:24 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:45:13 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:44:45 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:44:44 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:43:15 2017 Warning (5) Dynamic Range Window violation Mon Jan 02 19:40:31 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 19:39:48 2017 Notice (6) TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jan 02 19:38:47 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Mon Jan 02 19:14:32 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Jan 02 14:49:12 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Jan 01 12:18:24 2017 Critical (3) Resetting the cable modem due to docsDevResetNow Sun Jan 01 12:06:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:08 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 10:18:04 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 07:45:18 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 04:12:00 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:36 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 02:49:26 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 01:04:25 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Jan 01 00:34:59 2017 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 22:08:29 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 21:16:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:37:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:57 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:36:44 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:29:30 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:21:46 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 19:04:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 18:26:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 17:06:43 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 14:38:58 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:22:19 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 10:20:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 31 09:14:17 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 20:11:54 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:32:03 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 19:31:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 14:19:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:53:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:32:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 12:06:47 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:44:52 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 11:16:42 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 09:43:45 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Fri Dec 30 08:47:55 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 23:01:39 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:40:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 17:37:28 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:10:05 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 15:09:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:05:10 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 13:04:38 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 12:16:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 10:44:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 04:02:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:35:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 02:34:46 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Thu Dec 29 01:28:56 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 20:58:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 14:04:29 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:26:04 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 12:25:50 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:26:12 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:24:58 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:38 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:23:36 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Wed Dec 28 10:18:33 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:29:10 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 18:27:38 2016 Critical (3) Resetting the cable modem due to docsDevResetNow Tue Dec 27 14:13:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 14:06:05 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 13:57:24 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 12:15:27 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 11:34:07 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Tue Dec 27 09:26:31 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 17:42:40 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:59 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Mon Dec 26 04:52:45 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 14:20:37 2016 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 13:40:15 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:58:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 09:39:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 04:37:19 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sun Dec 25 00:05:00 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 14:36:22 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0; Sat Dec 24 09:44:20 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:7b:4d;CMTS-MAC=00:21:a0:fb:6a:74;CM-QOS=1.1;CM-VER=3.0;8.6KViews0likes24CommentsArris SBG6700-AC Slow and Dropping Wifi
I have seen a few other forum posts regarding slow/dropped WiFi connections through Arris devices. The solution is consistently to disable IPv6 (link-local only) in the device settings. I have searched high and low in the settings, but am unable to find this option in settings for my Arris SBG6700-AC. Anybody know where this is?7.9KViews0likes2CommentsNew SB8200 - improper provisioning
I just purchased and installed a new Arris SB8200 for use at my home to replace an aging SB6120. I followed the installation instructions and I called cox customer service to register the new modem via it's SN and MAC address. The modem is connected and I'm able to connect to the internet. But here's the problem... My download speeds are horrendously slow now. Immediately before I disconnected the SB6120, I ran a speed test and I was getting in excess of my current plan speeds. ~60Mbps down and about 7-8Mbps up. Now, the same test yields around 10Mbps or less down and, at times, really high upload speeds around 20-30 Mbps. I have checked all of the signal levels reported by the modem webpage and they all appear nominal. It also appears that all 32 download channels have been bonded and 4 upload channels are bonded (see bottom). Here's a current speed test report from the cox website. as you can see horrendously slow on the download side which is less than 10% of what I should be receiving. Test Results Download Upload 4 Mbps 6 Mbps My Internet Plan COX INTERNET PREFERRED Download Upload 50 Mbps 5 Mbps Speed Test Results Device Type Latency desktop 31 ms IP Address Test Server So what gives? I know that many other cox users including those in Phoenix and elsewhere in AZ have reported that this modem works as advertised when provisioned. Has mine been provisioned improperly? I know from other users of the modem that the firmware version being pushed out by COX and other providers is at least one or more revisions older than the modem's current firmware revision which is: Software Version D31CM-PEREGRINE-1.0.0.2-GA-01-NOSH Why is my quality of service all of a sudden negatively impacted by upgrading my modem (which is something Cox want's you to do every few years) to the latest model which is officially supported by Cox? As a long time cox customer going back 17 years, this is not meeting my expectation of performance and service currently. :-( I am not connecting to the modem wirelessly, but through a wired Ethernet connection. I have tried connecting directly to my PC and through my router and the results are exactly the same. Downstream Bonded Channels Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables 170 Locked QAM256 807000000 Hz 5.6 dBmV 39.8 dB 0 0 169 Locked QAM256 801000000 Hz 5.9 dBmV 40.0 dB 0 0 206 Locked QAM256 975000000 Hz 1.4 dBmV 37.2 dB 0 0 171 Locked QAM256 813000000 Hz 5.5 dBmV 39.8 dB 0 0 172 Locked QAM256 819000000 Hz 5.6 dBmV 39.8 dB 0 0 173 Locked QAM256 825000000 Hz 5.6 dBmV 39.7 dB 0 0 174 Locked QAM256 831000000 Hz 5.5 dBmV 39.6 dB 0 0 175 Locked QAM256 837000000 Hz 5.6 dBmV 39.7 dB 0 0 176 Locked QAM256 843000000 Hz 5.6 dBmV 39.7 dB 0 0 177 Locked QAM256 849000000 Hz 5.6 dBmV 39.5 dB 0 0 178 Locked QAM256 855000000 Hz 5.7 dBmV 39.5 dB 0 0 179 Locked QAM256 861000000 Hz 5.8 dBmV 39.5 dB 0 0 180 Locked QAM256 867000000 Hz 5.7 dBmV 39.5 dB 0 0 181 Locked QAM256 873000000 Hz 5.4 dBmV 39.3 dB 0 0 182 Locked QAM256 879000000 Hz 4.9 dBmV 39.1 dB 0 0 183 Locked QAM256 885000000 Hz 4.5 dBmV 38.8 dB 0 0 184 Locked QAM256 891000000 Hz 4.0 dBmV 38.5 dB 0 0 185 Locked QAM256 897000000 Hz 3.6 dBmV 38.4 dB 0 0 186 Locked QAM256 903000000 Hz 3.2 dBmV 38.1 dB 0 0 187 Locked QAM256 909000000 Hz 2.9 dBmV 38.0 dB 0 0 188 Locked QAM256 915000000 Hz 3.0 dBmV 37.9 dB 1 0 189 Locked QAM256 921000000 Hz 3.1 dBmV 37.9 dB 0 0 190 Locked QAM256 927000000 Hz 3.3 dBmV 38.0 dB 0 0 191 Locked QAM256 933000000 Hz 3.5 dBmV 38.0 dB 2 0 192 Locked QAM256 939000000 Hz 3.6 dBmV 38.0 dB 2 0 201 Locked QAM256 945000000 Hz 3.2 dBmV 37.9 dB 2 0 202 Locked QAM256 951000000 Hz 3.1 dBmV 37.9 dB 0 0 203 Locked QAM256 957000000 Hz 2.6 dBmV 37.5 dB 0 0 204 Locked QAM256 963000000 Hz 2.2 dBmV 37.4 dB 1 0 205 Locked QAM256 969000000 Hz 1.8 dBmV 37.4 dB 1 0 207 Locked QAM256 981000000 Hz 1.1 dBmV 37.1 dB 0 0 208 Locked QAM256 987000000 Hz 0.7 dBmV 37.0 dB 0 0 Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 2 Locked SC-QAM 23300000 Hz 6400000 Hz 37.3 dBmV 2 1 Locked SC-QAM 18400000 Hz 3200000 Hz 36.9 dBmV 3 3 Locked SC-QAM 29800000 Hz 6400000 Hz 37.3 dBmV 4 4 Locked SC-QAM 36300000 Hz 6400000 Hz 38.8 dBmV5.3KViews0likes3CommentsMotorola Arris SB 6190 Firmware Update?
Hello. I am between buying the Motorola Arris SB 6183 and the SB 6190 modems. I have read that there is a firmware update that is either a make or break for the SB 6190. Has this firmware been pushed out to the users or is it still being tested? Thank you. Kris4.2KViews0likes4CommentsArris SB8200 Docsis 3.1 GigaBlast No Blue Lights Up or Down
Called Cox for new internet options. Told me I was grandfathered in at 150. Quoted me 300 and Giga. Call ended. I had a Netgear 3.0 modem / router combo that worked fine. I buy a 3.0 modem and a mesh router to increase my WIFI area. I try to get it calibrated only to find out I have a work order for GigaBlast speeds and my 3.0 equipment is unusable. So as a patient person I go and swap my 3.0 for a 3.1 modem costing me more money. I call to get the 3.1 calibrated by Cox and it shows all green lights 3.0, no blue lights for Arris SB8200 Docsis 3.1 GigaBlast No Blue Lights Up or Down. Speeds are 250 down and 20 up and that is before and after a modem factory reset with ONLY my laptop plugged in. Tried with a desktop as well with the same result. - Called and asked was GiagBlast and Docsis 3.1 avilable in my area and told it was - Forced to GigaBlast without request and told I can't return to my original speed - Asked me to upgrade my equipment to take advantage of GigaBlast but when equipment is installed it I only get 3.0 and low speeds - Called from 10am to Midnight and text chat too. After dealing with 6 different people and a whole day wasted I still got nowhere - Best of all I was told no work could be done while there was an "outage" in my area. One that lasted from 2pm to 7pm, and then another that started at 12am forecast to end at 6am. Anybody else have these issues and if so how were they resolved??? - Do yourself a favor and DO NOT, I repeat DO NOT engage in the text chat option from your phone. A waste of time and resources!!!! Similar situations like mine so I know I am not alone when it comes to the level of customer service andtechnical support https://forums.cox.com/forum_home/internet_forum/f/internet-forum/22627/gigablast-activation/86619#86619 https://forums.cox.com/forum_home/internet_forum/f/internet-forum/20283/issues-with-gigablast Standard Specification Compliant Docsis 3.1 Hardware Version 4 Software Version D31CM-PEREGRINE-1.1.1.0-GA-14-NOSH Connection 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 957000000 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 30 Locked QAM256 957000000 Hz 2.6 dBmV 37.3 dB 103 482 1 Locked QAM256 783000000 Hz 1.3 dBmV 37.9 dB 0 0 2 Locked QAM256 789000000 Hz 1.3 dBmV 37.9 dB 0 0 3 Locked QAM256 795000000 Hz 1.4 dBmV 37.8 dB 0 0 4 Locked QAM256 801000000 Hz 1.3 dBmV 37.9 dB 0 0 9 Locked QAM256 831000000 Hz 1.2 dBmV 37.7 dB 0 0 10 Locked QAM256 837000000 Hz 1.6 dBmV 37.8 dB 0 0 11 Locked QAM256 843000000 Hz 1.6 dBmV 37.9 dB 0 0 12 Locked QAM256 849000000 Hz 1.7 dBmV 37.8 dB 0 0 17 Locked QAM256 879000000 Hz 1.9 dBmV 37.5 dB 0 0 18 Locked QAM256 885000000 Hz 1.7 dBmV 37.3 dB 0 0 19 Locked QAM256 891000000 Hz 1.8 dBmV 37.4 dB 0 0 20 Locked QAM256 897000000 Hz 1.7 dBmV 37.3 dB 0 0 21 Locked QAM256 903000000 Hz 1.5 dBmV 37.2 dB 0 0 22 Locked QAM256 909000000 Hz 1.6 dBmV 37.1 dB 0 0 25 Locked QAM256 927000000 Hz 2.3 dBmV 37.3 dB 0 0 26 Locked QAM256 933000000 Hz 2.7 dBmV 37.4 dB 0 0 27 Locked QAM256 939000000 Hz 2.9 dBmV 37.4 dB 0 0 28 Locked QAM256 945000000 Hz 2.8 dBmV 37.3 dB 0 0 29 Locked QAM256 951000000 Hz 2.8 dBmV 37.4 dB 0 0 33 Not Locked Unknown 357000000 Hz -46.1 dBmV 0.0 dB 0 0 34 Not Locked Unknown 363000000 Hz -45.9 dBmV 0.0 dB 0 0 35 Not Locked Unknown 369000000 Hz -45.9 dBmV 0.0 dB 0 0 36 Not Locked Unknown 375000000 Hz -45.8 dBmV 0.0 dB 0 0 37 Not Locked Unknown 381000000 Hz -45.7 dBmV 0.0 dB 0 0 38 Not Locked Unknown 387000000 Hz -45.5 dBmV 0.0 dB 0 0 41 Not Locked Unknown 405000000 Hz -45.8 dBmV 0.0 dB 0 0 42 Not Locked Unknown 411000000 Hz -46.0 dBmV 0.0 dB 0 0 43 Not Locked Unknown 417000000 Hz -46.5 dBmV 0.0 dB 0 0 44 Not Locked Unknown 423000000 Hz -47.2 dBmV 0.0 dB 0 0 45 Not Locked Unknown 429000000 Hz -47.8 dBmV 0.0 dB 0 0 46 Not Locked Unknown 435000000 Hz -48.3 dBmV 0.0 dB 0 0 159 Locked Other 300000000 Hz -47.2 dBmV 0.0 dB 0 0 Upstream Bonded Channels Channel Channel ID Lock Status US Channel Type Frequency Width Power 1 1 Locked SC-QAM 16900000 Hz 6400000 Hz 40.0 dBmV 2 2 Locked SC-QAM 23500000 Hz 6400000 Hz 41.0 dBmV 3 3 Locked SC-QAM 29900000 Hz 6400000 Hz 42.0 dBmV 4 4 Locked SC-QAM 36300000 Hz 6400000 Hz 42.0 dBmV Current System Time:Tue Apr 16 01:05:19 20194.1KViews1like2CommentsSB6190 Event Log with Internet speed 73 Kbps from Cox Preferred 100 Mbps service
I have intermittent connection issue. The COAX cable is connected directly to Arris Surfboard Cable Modem SB6190 There is no splitter. Event Log The table below contains the log of events that the SB6190 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur. Time Priority Description Sun Jan 07 19:48:41 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 19:48:41 2018 5 RCS Partial Service;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 19:48:42 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 19:48:42 2018 5 RCS Partial Service;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 19:48:47 2018 5 Lost MDD Timeout;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 19:49:35 2018 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 19:50:11 2018 5 RCS Partial Service;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 20:44:15 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 20:44:15 2018 5 RCS Partial Service;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 20:44:15 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 20:44:15 2018 5 RCS Partial Service;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 20:44:19 2018 5 Lost MDD Timeout;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 20:45:10 2018 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 21:04:40 2018 5 RCS Partial Service;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 21:04:40 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 21:04:40 2018 5 RCS Partial Service;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 21:04:40 2018 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 21:04:41 2018 5 RCS Partial Service;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 21:04:45 2018 5 Lost MDD Timeout;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0; Sun Jan 07 21:05:31 2018 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:18:c2:59;CMTS-MAC=00:59:dc:79:41:cc;CM-QOS=1.1;CM-VER=3.0;2.8KViews0likes5CommentsArris SBG8300 Upstream QAM Speeds.
I bought an Arris SBG8300 modem/router in one last June and upgraded to Gigablast. We've had several Cox techs to the house to narrow down the root cause of slow speed and intermittent connectivity issues we have. We have a new large gauge wire (11?) from the post in our yard to our house. From there it is a direct line (no splitters) to our Arris. So . I ran a speed test hard wired to the modem/router. Here are the result (23 DL, 33 UL...on gigablast 😞 https://www.speedtest.net/result/11076560076 When contacting Arris about the issue they seemed adamant that the Upstream power levels were the issue (all five approximately 34dbmv) as they are well below the minimum recommended of 45dbmv. They way I understand it, Cox should be telling the modem what upstream power it expects, so the issue could be that this specific model was spec'd out incorrectly in Cox's system. I say this after having had the issue with two of these same Arris's since last June coupled with the fact that the tech who saw this modem tonight acted like I had exposed electrical wires (anecdotal, but techs see a lot of different hardware, so I think there's possibly some good reason for his reaction). What're the forum's thoughts? I don't want to just buy more hardware as I have a hefty sum invested in this one and Arris is not exactly making it easy to get a refund. Thanks, Jamie2.4KViews0likes7Comments