Intermittent Critical Modem Events
Recently I have been encountering upstream issues which appear to be tied to critical priority (tier 3) events in my modem's event log. I can still hear people talking to me over VoIP, but I cannot talk, and I cannot open new connections, such as opening a browser and accessing a web page. My equipment: Netgear CM1200 The main errors I encounter: SYNC Timing Synchronization failure - Loss of Sync Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 time out No Ranging Response received - T3 time-out I'm also getting some non-critical errors I think may be of significance: REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW Dynamic Range Window violation These issues don't just occur during the day with increased use due to covid (alongside the increased ping and packet loss) - they will also happen randomly at say4AM, when almost nobody is using the internet. These events are a complete loss of internet access, where during the day I can still access the internet. Many times the upstream light on my modem will start to blink (not always). Sometimes, when I look at my ping to google which I constantly log for diagnostics, I'll see that the packet loss is on and off about every other second. During these situations, my internet is functioning barely. Some web pages will load slowly as it gets trickled in through the constant packet loss and loss of internet. No one else is using the internet in my house during these times, so I can safely say it's not an in-home use scenario. How do I get someone to come out who has some actual technical knowledge that can troubleshoot this for me? I had a technician out today and it seems like he doesn't really know too much other than how to plug their device into the tap/coax in my house and tell me 'it looks good right now'. Not 30 minutes later and it's happening again to me. I have a feeling it's something to do with their lines up to my house, or perhaps the local node. But I don't want to jump to conclusions.
Slow Upload and Timeouts still not fixed after 4th Tech
This is starting to get really baffling to me as I never had this much trouble with COX. I had this issue since June where I would constantly time out with T3 timeouts. I came to the forums because I wasn't getting help with when I called or used their chat. That is when I talked about my issues and everything. This is what I was met with: 1st tech told me it was the dbmv of the modem, where it was set to +10 (It goes up to 15 per my old modem's manual, which was MG7540) and he set it down to about 5dbmv. The issue continued with T3 timeouts. 2nd tech told me that he "cleaned up the lines" outside and that it should be much better now. Power went to about +11. Issue continued with T3 timeouts. COX told me they wouldn't send out another tech until I replaced my modem and router. I spent $300 on the Arris SB8200 and the Nighthawk since I wanted to upgrade to Gigablast at some point. The issue continued with T3 timeouts. 3rd tech came out and disconnected us for about 10 minutes while running his tester to the main line. Told us it was the main line and that it would be fixed within 48 hours as he had to call a guy who works with cables. (It was not fixed as I gave it a full week to be fixed) 4th tech came out, yesterday, and gave me a new COAX cable (the one inside was about a year old), said all the signals were good, even the main line that the tech before him checked, and then proceeded to tell me techs are lazy. Then he had me try a bunch of things that I've already tried, and then told me it was my new modem's fault and that I should use my old modem/router combo while I wait for my replacement. Now I re-activated my old modem/router and it's out of spec now due to the dbmv being at +18. So now I have to get another tech out here to lower the power until my replacement modem comes in later this week to switch it again, to which I'll need another tech out to increase the dbmv for the Arris. Every single tech that's been out here has been a contractor with COX but does not actually work for COX. I feel like every one of them doesn't really know what's going on and all they tell me is that my signals in my house are good. I wanted to upgrade to Gigablast but if this issue isn't resolved with my replacement modem of the Arris, then there really isn't a reason to upgrade if all I'm going to receive is 1.5mbps of upload and timeouts.. My upload speed should not be anywhere between 0.9-2.6 and be near 10 which is what I am paying for. It's crazy that no one can figure out what's going on or even listen to me when I say that the signal dropping out is intermittent. I know my download speeds are great but everything upload is garbage. It just feels like I'm being ignored and it's frustrating.
T3 Timeouts and Constant Disconnects
I, once again, have to come to the forums as I have gotten mediocre support over the chat system/phone. I created a post last week about having issues and had a tech come out on Wednesday. He told me that he "cleaned up" all the wires and that everything should be working and kept showing me how the connection was good. I asked what if it's not fixed, to which he sounded a bit offended and gave me a card to this cable company that I'm guessing deals with the cable at the pole? Either way, I have replaced my modem and my router and still am getting timed out, while also having my upload speed run at 2.4mbps. I have said this in the ticket and I guess 2.4 mbps is normal even though I pay for 10? I need 6mbps upload speed to remote into my job's server, so having 2.4 always knocks me off the remote desktop session. I have expressed this to support today, since the tech told me to give the connection "a day to settle down" since he did a lot with the wires outside. The support agent I dealt with today was frustrating as they told me it was the fault of the router, even if the T3 timeouts were coming from the Modem. I told them I replaced the modem and router 4 days ago and I'm still having the same issue, to which they replied that I should get the modem/router remote support and that they would add it to my account for $5.95/mo. I said no and that was that conversation. I don't understand why I am having issues getting a tech out. I've never been this frustrated with COX service before as they always were quick and helpful. Now I can't even get a tech out here to actually help me. I've dealt with COX since 2009 and this is the first time I actually had an issue that hasn't been resolved after a full month of my first ticket. Before anyone asks, I have one COAX cable that runs into the house that doesn't have a splitter.
Internet Connection Keeps Dropping/Resetting
Hello from the Phoenix Area, I've been fighting with support for over a month now to get my service stabilized. I'm expecting my 3rd Tech Visit tomorrow, which is supposed to be a Supervisor Technician. I've been calling and tracking the outages. I'm getting between 10-15 disconnects a day. Some lasting up to 2 hours. I've only had service for 7 weeks now with a brand new out of the box modem, which I've already replaced with another brand new out of the box modem. Both having the same issues. The cable has been tested and checked and new connectors put on the ends twice. We've moved the connection to a different node. Still getting dropped internet. This happens throughout the day. It doesn't seem to matter the time, amount of internet traffic, or possible other usage related issues. It'll drop at 2am or 2pm or any other time in between either way. I'm getting charged $75 for each tech visit to come in and "redo my cabling" (ie put new connectors on) and I'd gladly pay for the first tech trip if it would have fixed the issue. However, it hasn't and I'm on my 3rd tech trip now.My Meraki Router is showing outages coinciding with the critical errors in the event log with the record going all the way back to July 31st. During the busy hours (Evenings 5pm to Midnight) latency will jump20-25ms to 35-50ms, dropped packets will go from 0-3% tovaryingbetween 10-50%. This is consistent every evening. I've had to contact support, insist on speaking to a manager (Which BTW none one wants to let you talk to), and demand escalated service because it's been weeks of "Reset you modem, check to make sure your connections are tight, look we reset your modem it's working now...." and getting nothing fixed. How does COX expect to retain customers if they can't provide the service that we are paying for? Hopefully we can bring this to a resolution before decide it's not work dealing with COX anymore and switch to a different ISP. Just know, if I switch at home, so to will I switch at work where we have over 60+ retail locations in the Metro Phoenix and surrounding areas.COX isn't the only ISP in town and customer service should remember that Business Users are made up of Home Users. Piss off the wrong home user and you lose a lot of business overnight. And yes I'm venting because I'm at the end of my patience. Anyways, here's the pertinent information below concerning my modem, router, errors, connection stats, etc. Current Hardware Arris SB6183 Modem Meraki MX64 Router Current Status Log 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 2 789000000 Hz -5.8 dBmV 37.6 dB 680 673 2 Locked QAM256 1 783000000 Hz -5.6 dBmV 37.6 dB 598 453 3 Locked QAM256 3 795000000 Hz -5.5 dBmV 37.7 dB 670 756 4 Locked QAM256 4 801000000 Hz -5.9 dBmV 37.5 dB 496 691 5 Locked QAM256 5 807000000 Hz -6.6 dBmV 37.2 dB 596 341 6 Locked QAM256 6 813000000 Hz -7.0 dBmV 37.1 dB 708 568 7 Locked QAM256 7 819000000 Hz -6.9 dBmV 37.1 dB 650 743 8 Locked QAM256 8 825000000 Hz -6.7 dBmV 37.2 dB 457 720 9 Locked QAM256 17 879000000 Hz -7.0 dBmV 37.1 dB 459 448 10 Locked QAM256 18 885000000 Hz -7.9 dBmV 36.6 dB 468 549 11 Locked QAM256 19 891000000 Hz -8.2 dBmV 36.4 dB 625 609 12 Locked QAM256 20 897000000 Hz -8.2 dBmV 36.5 dB 547 762 13 Locked QAM256 21 903000000 Hz -8.6 dBmV 36.4 dB 612 678 14 Locked QAM256 22 909000000 Hz -8.6 dBmV 36.3 dB 2783 640 15 Locked QAM256 23 915000000 Hz -8.4 dBmV 36.3 dB 3684 939 16 Locked QAM256 24 921000000 Hz -8.3 dBmV 36.3 dB 766 556 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 44.0 dBmV 2 Locked ATDMA 1 2560 Ksym/sec 18400000 Hz 43.8 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 47.0 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 47.3 dBmV Current System Time:Mon Aug 06 19:23:08 2018 Current Modem Event Log Time Priority Description Mon Aug 06 14:40:02 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:15:01 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:14:13 2018 Notice (6) TLV-11 - unrecognized OID;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;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 Ranging Response received - T3 time-out Mon Aug 06 13:13:25 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 13:11:15 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:41:48 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 12:40:04 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:37:56 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:37:54 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:26:34 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 12:24:55 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:45 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:45 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 12:22:44 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 11:12:47 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 11:10:31 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 11:08:21 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 10:54:45 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 10:53:01 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 10:50:50 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:53:55 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:08:31 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 04:06:43 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 04:04:33 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:30:05 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:28:55 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:17:48 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Aug 06 00:15:24 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Mon Aug 06 00:13:14 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 23:46:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 21:58:50 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Aug 05 21:56:58 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 21:54:48 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 12:09:11 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:34:23 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sun Aug 05 04:32:33 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:30:23 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:30:23 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 04:29:39 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sun Aug 05 00:21:47 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:51:02 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 23:49:06 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Sat Aug 04 23:42:46 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:37:26 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 23:35:13 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:33:34 2018 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 23:33:03 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:20:15 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 22:18:20 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Sat Aug 04 22:10:12 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 22:08:18 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:06:08 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:05:41 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 22:05:41 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:51:53 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 21:50:07 2018 Critical (3) Resetting the cable modem due to docsDevResetNow Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 21:48:32 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:22 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:20 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:46:19 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:59 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:58 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:47 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:30 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:45:26 2018 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 21:37:31 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:56:03 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Aug 04 15:54:07 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:51:57 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0; Sat Aug 04 15:16:36 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:b2:fb;CMTS-MAC=04:2a:e2:c6:89:5e;CM-QOS=1.1;CM-VER=3.0;