T3 and T4 Timeouts from an ex-field technician
Starting in September of 2013, I noticed my connection becoming intermittent at best. Voice conferencing and gaming would literally go from 23 ms to over 10k ms and then obviously I would disconnect from the server. About a week after this first started happening, it started to randomly disconnect while I was simply browsing the internet. I found the modem was cycling itself. At the time I had an extremely old but trusty Motorola Surfboard SB5100. Despite having this modem throughout the DOCSIS 3.0 updates, and despite it having worked fine through it all hither to the point in time, I figured it may be the modem (after a 12 year run, I wasn't complaining...) I accessed the modem diagnostic page at 192.168.100.1 and saw that in the logs there were massive amounts of T3 timeouts. Being an ex-field technician for Cox, I knew this could have gone one of two ways. It was either the modem or it was something in the node (most likely an amplifier in the trunk line) that was to blame. I called Cox for the heck of it just to see if they could see anything on their end, and as usual, no. Everything on their end was fine, but again, having been a field tech for 5 years, I know that phone based customer service is very limited, they're not at the house, they don't have a meter and they're sure as heck not taking level readings. Ok, fair enough. I purchased a Motorola Surfboard SB6141 to replace the 5100 and finally upgrade to DOCSIS 3.0. I called them, had the modem provisioned, went to the diagnostics page, was "wowed" by 8 downstream and 4 upstream channels, wondering why I had not upgraded the modem sooner, but alas, not 2 hours after provisioning, there was a T3 timeout. Now I know it's not the modem, time to get on the phone and make things happen. I called, they said they would send a tech out. The tech (CONTRACTOR) came out and I explained the whole situation to him. I showed him the modem diagnostics, I explained what I knew about everything, and he agreed with me. He did NOT check levels, he did NOT check the tap at the pole (I have a 340 foot drop from the pole to the house, it's RG-11. A new install was done less than a year ago, including the drop and inside lines, and I told him this, so he probably "assumed" things were good up there...). He scheduled a 5C, which is the "internal" code name for "get a maintenance (plant) technician out to the pole to see what's up". I got a call from my old lead technician about a week later. He told me that the maintenance tech found water in the drop and cut it back to where the "stinger" (copper in the connector) wasn't black from water damage, and that another tech would be out in the next day or two in order to run a new drop. Two days later ANOTHER CONTRACTOR comes to the house to run the new drop. I saw his spool of RG-11 and I knew he didn't have enough left to get from the pole to the house. He removed the drop at the sub pole, and due to not wanting to bother him, I came back inside. 20 minutes later I went back out and he was gone. He never replaced the drop. He probably figured he didn't have enough cable to do it after removing the drop at the sub pole, rehung it, and left. This pissed me off. In the meantime I contacted my old lead and asked him what the deal was, explaining that not only were these T3's still happening, but they were getting worse, and they were leading into T4's. He scheduled for the drop to be re-run AGAIN the next week and made sure it would be an in house guy arriving, NOT a contractor. Sure enough, another lead technician and a field tech came to the house and ran a new drop. They didn't have enough RG-11 so they ran half RG-11, then installed a ground block at the sub pole and ran RG-6 the rest of the way. He said he would be back (this was a month ago and it still hasn't happened) to replace the RG-6 half of the drop with RG-11. He gave me his cell number to contact directly if this kept going on. It kept going on. The T3's were getting worse. I asked him on the phone to set up a 5C, he said he would but this was a week and a half after he replaced the drop and hadn't been out to finish the RG-11, so my faith in relying on him was null. I therefore called customer service. I explained that, despite having JUST bought a new modem, FIOS was a phone call away if this wasn't resolved. Per usual, they went RIGHT back to square one and wanted to send out a tech. I told them to stop reading the script from their screen and focus on their keyboard in order to LISTEN AND UNDERSTAND exactly what I had JUST explained to them. For over a month I was implying that this was a plant issue, no one wanted to listen. The phone techs didn't want to listen, the lead techs did not want to listen, the lead techs kept coming back with 50 other excuses as to what could be causing it. I questioned them as to why they would do this when they knew I used to be a tech and I wasn't an idiot. The final call was made to customer service. Again, they said they had to send a tech out, despite two months of this **, in order to get a 5C scheduled. Ok, last time I am playing this game. The tech came out and I caught him on my way home from work. He was an in house guy and I caught him as he was at the pole taking levels. He told me that every port from the tap was bonkers, he replaced the tap and the levels were STILL bonkers, and that he did not understand how two lead techs and four field techs didn't realize this was a plant issue from day one. I concurred. He took down every piece of information I gave him about the new drop, the new modem, signal levels at the modem, etc, etc, and made a detailed log for the maintenance techs who came out. He also told me that there are only SIX HOUSES ON MY NODE, LITERALLY. This means that the trunk line feeding my house only feeds a total of 6 houses. Do you know how easy that is for plant (maintenance) to troubleshoot? There is one amplifier that is literally humping my tap, if here's an inch of trunk line from the amplifier into the tap then it's a lot. I suspected that amplifier from the get go, but even if it wasn't, there would only be at most ONE MORE amplifier in that node, so yeah, one amp checked out good, guess which one's bad? Real easy stuff here people, real easy. So, the tech scheduled the 5C (the second one that had to happen in this whole fiasco), and the maintenance tech came out. I don't know if it was the same or a different one, but this time around (after TWO MONTHS OF THIS **) the problem was resolved. It has been two weeks and I have not seen a single T3 or T4 in my log. I see where it lost connection due to the maintenance guy doing what he had to do and of course the service gets interrupted during this, but honestly, after the modem cycle, there is not ONE added entry to the log, nothing; whereas every other "visit" would result in a T3 less than 10 minutes later. These T3 (and later T4's due to the issue getting progressively worse) were happening every ten to twenty minutes on some days, other days every hour or so. I use VOIP for telephone. Imagine not having 911 access for the whole day because your ISP can't get it's act together. I held out having FIOS reinstalled (it was installed here when it first came out) because I honestly can't stand those hacks. Having said that, had that last tech not been so thorough, had the second maintenance tech not done his job and resolved the issue, Verizon was seriously the next phone call. I didn't go into a whole lot of detail about levels and diagnostics here because I did enough of that with customer service and all the techs that visited. I wanted to make a point here to Cox. Not all customers are complete idiots. Not all customers have zero clue about how information travels from their house to the MTC. Maybe instead of treating everyone equally as morons, you should start treating them all equally as intelligent folk. Imagine how many folks out there were never field techs, imagine how many would have switched back to Verizon within the first week, let alone sticking it out for two months. I was a field tech, I have working knowledge of the system, I was treated like a complete idiot, how do you think that makes me feel? It actually makes me feel pretty damned good right about now knowing I was right the whole damned time about the issue being a plant related occurrence, but I can tell you right now when these people tell you over the phone and face to face that you're "wrong", and that they need to go through steps that, again as an ex-tech, you KNOW they don't need to go through, all the while the internet that we pay for monthly and (in some cases) our phone service (through another provider in my instance) has fallen to complete useless garbage, labeling it as "infuriating" somehow undermines the true nature of it. I know that not every single problem faced is one of a plant issue, this is obvious. Red flags should be raised, however, after every single other step has been taken and fails, instead of attempting to loop the same damned process all over again; that is simply ridiculous. What is also ridiculous is the fact that contractors are being sent in place of in house technicians and basically this leads to repeat trouble calls. This is something that is completely unacceptable, especially when one has to take time out of their day (or out of work) every time a call has to be rescheduled. I know not every contractor is a bad contractor, but out of the entire bunch, I can name 3 that I would have work at my house, that's about it. To make it relative to the in house technicians, I can list about 20 off the top of my head that I would let work at my house from start to finish with a cable job any day of the year. I hope this type of issue, or at least the steps to the resolution of this type of problem does not happen again. I will definitely be more prone to calling Verizon early on if an issue is not resolved in a suitable amount of time, not TWO MONTHS AFTER.46KViews4likes2Comments
DHCP RENEW WARNING - Field invalid in response
I'm experiencing intermittent internet connection drop outs. I'm trying to troubleshoot which component is causing the issue. The cable modem log file contains numerous occurrences of the following DHCP renewal warnings (see below). Does anyone have any idea if this might be the problem? DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:1a:de:6d:0c:c20KViews0likes1Comment
upload packet loss 15-25% please help.
Ok so, i upgraded my services several months ago from preferred to premier. Upgrading to this tier requires a docsis 3 modem as you all know. First day i upgraded my speeds changed from 27/8 to 33/10 average. I was very disappointed. after 2 techs an several hours of phone calls i finally got in touch with someone to fix the issue. it was the "coding" i believe it was worded. Basically they hooked up my modem but didnt adjust the speed form the com center. Bam, i was getting great speed now. One problem, major packet loss. I figured it wasnt that big of an issues as i was getting better upload speeds than before and just wrote it off. Well after comparing voip and video to my parents 25/5 connection with no packet loss, its was a problem. I am a gamer and we spend a considerable amount of time using programs like skype to connect with my family across the US as well as my wife using for conference calls to conduct business. I spent over a decade dealing with internet issues as a teenager living at my parents an was the one who would call and have techs come out. I've never seen this much packet loss and after comparing i got on the phone and started trouble shooting with techs. i have had 3 techs come out for this issue. Things that have been done are running a new line that feeds into the house, one tech added an amp because my signals down where in the -8 and greater range causing some disconnect issues, the last tech to come out got me off the amp stating i didnt need it an that it could be causing the upload packet problem and he also changed splitters and fittings. No luck still. i have seen several of these issues resolved from different things, but all seem to be a long road and a headache. iam inquiring about eatels fiber optics as they are becoming available in my area but before i make a switch i want to give this a valiant effort as my wife loves the tv package we have with dvr that is considerably more money with eatel. Is there a expert team, or a set of procedures to fix this issue or am i just spinning my wheels? any one with a docsis 3 with premier or ultimate getting 0 or very little packet loss? any info at this point would be helpful.16KViews0likes13CommentsTrouble with Motorola SB6141 Docsis 3.0 modem and T3 errors.
I upgraded to a DOCSIS 3.0 modem yesterday, and ever since, I've been having internet drops at random times, seemingly starting with T3 errors, looking at the logs, but I'm not sure about that. What happens is suddenly I am unable to access the internet, and similarly unable to access the router configuration or the modem configuration, which makes no sense to me, but, ignoring that, here's a sample of the log: ***Edited to remove logs contain MAC address The T3 happened around the time everything went wonky. Not sure if it's the cause or not. and here's my signal information: and finally, some information from the help page: Model Name: SB6141 Vendor Name: Motorola Firmware Name: SB_KOMODO-1.0.6.12-SCM00-NOSH Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3 Hardware Version: 7.0 In addition, my download speeds seem to be pinned at 32 Mbps max, I should be getting up to 50, and my upload starts out anywhere from 7-12 Mbps, but then quickly drops to 3-4 and stays there.Solved13KViews0likes15Comments
High downstream and upstream power levels
I have seen post about high downstream and high upstream power levels but not at the same time. It seems to always be that only one of the levels is high and the other is low. I am having both high at the same time. Here are my normal readings. Downstream is normally around 8 to 9 dBmV Upstream is normally around 53 to 54 dBmV What could case both to be high at the same time? I am asking because I am having problems with online gaming. Server kicks, lag, ect. Thanks12KViews0likes8CommentsResolving Host and Slow Speed
I have the preferred internet service, but have been having really bad internet lately and today has been the worst. 1st. When browsing, I regularly have a slow response with "Resolving Host" showing on the bottom status bar. After 10 seconds or so, the browser finally loads my webpage. This isn't a browser problem as I have never had this happen on any other internet connection, seriously. Also, I've already cleared my cache and whatnot so please don't ask me to do that. 2nd. Today's internet speeds have been dismal. In fact at one point I could have done better on dial up. This is not what I pay for, and it is extremely disappointing and frustrating. I just ran a speed check using the Cox tool and this is what I got... Download 0.97 Mbps Upload 3.67 Mbps Ping 303ms How in the world is my ping 303ms to the Cox servers? That silly. Any help you can possibly give me?10KViews0likes8CommentsSlow internet connection while paying for 50 mbps
Hi, I have recently upgraded my internet connection to the 50mbps package and I noticed a significant increase in speed for a few hours on the first day it updated. It now seems to be very inconsistent and I am getting as low as 3 mbps downloads up to around 18. The uploads seem to be just fine as I've gotten around 18mbps. The past few days have been a real disappointment. Please help.9KViews0likes14CommentsInternet connection stopping every few minutes
I've only had Cox for about a year now. But lately, it has been a pain. My modem keeps shutting off and on, and my internet drops constantly. It's frustrating when you are online, and have to start over, and over, and over... I've tried resetting in, closing my internet page, and clicking on it again etc. You all need to fix Cox! How do I fix this constant dropping?7.8KViews0likes10Comments
Internet Keeps dropping out
I have motorola surfboard sbg6580. It seem like my internet and wireless keep coming and going. I had a tech out here, but still does not seem like it has gotten any better. This is from my event log, but I do not know what this mean or if I can fix anything on my side of it. Wed Jul 24 21:05:50 2013 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Wed Jul 24 09:06:33 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Wed Jul 24 09:05:56 2013 Warning (5) Dynamic Range Window violation Wed Jul 24 09:05:52 2013 Notice (6) TLV-11 - unrecognized OID;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Wed Jul 24 09:05:51 2013 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Wed Jul 24 09:05:51 2013 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.0;CM-VER=3.0; Wed Jul 24 02:16:25 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Tue Jul 23 20:11:47 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Tue Jul 23 09:26:00 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jul 22 16:39:49 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Mon Jul 22 10:13:23 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Mon Jul 22 00:41:31 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Jul 20 17:11:32 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Sat Jul 20 00:55:05 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Fri Jul 19 11:07:53 2013 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Fri Jul 19 09:14:18 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Fri Jul 19 03:46:07 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Thu Jul 18 11:18:29 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out Wed Jul 17 22:07:57 2013 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:75:4a:24:eb:d7;CMTS-MAC=70:81:05:2c:fc:8f;CM-QOS=1.1;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out6.8KViews0likes4Comments
No Ranging Response received - T3 time-out
Several months ago I started experiencing internet connectivity issues. The connection would drop and not return until after a hard reboot. When I called tech support I was told that the cox "system" did not play well with the Motorola SB modem. So, in an attempt to troubleshoot the problem I purchased a Cisco modem from Cox, no change. I then returned the Cisco and re-installed Motorola. Simultaneously, I made several setting changes to my D-Link router. The end result was things improved until this week. Now I get random drops for several minutes and then the connection returns, then drops and returns. The modem log shows a series of errors: Dec 15 2013 20:26:15 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e4:83:99:77:b3:a9;CMTS-MAC=00:24:14:63:6a:b5;CM-QOS=1.1;CM-VER=3.0; Dec 15 2013 20:26:15 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e4:83:99:77:b3:a9;CMTS-MAC=00:24:14:63:6a:b5;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:77:b3:a9;CMTS-MAC=00:24:14:63:6a:b5;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=e4:83:99:77:b3:a9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; Dec 15 2013 20:25:32 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e4:83:99:77:b3:a9;CMTS-MAC=00:24:14:63:6a:b5;CM-QOS=1.1;CM-VER=3.0; Dec 15 2013 20:25:32 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e4:83:99:77:b3:a9;CMTS-MAC=00:24:14:63:6a:b5;CM-QOS=1.1;CM-VER=3.0; I've seen other threads that address the similar issues but have not seen a solution. Any assistance would be greatly appreciated. Marc5.6KViews0likes1Comment
Trouble with Motorola SB6141 Docsis 3.0 modem and T3 errors.
I upgraded to a DOCSIS 3.0 modem yesterday, and ever since, I've been having internet drops at random times, seemingly starting with T3 errors, looking at the logs, but I'm not sure about that. What happens is suddenly I am unable to access the internet, and similarly unable to access the router configuration or the modem configuration, which makes no sense to me, but, ignoring that, here's a sample of the log: ***Edited to remove logs contain MAC address The T3 happened around the time everything went wonky. Not sure if it's the cause or not. and here's my signal information: and finally, some information from the help page: Model Name: SB6141 Vendor Name: Motorola Firmware Name: SB_KOMODO-1.0.6.12-SCM00-NOSH Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3 Hardware Version: 7.0 In addition, my download speeds seem to be pinned at 32 Mbps max, I should be getting up to 50, and my upload starts out anywhere from 7-12 Mbps, but then quickly drops to 3-4 and stays there.
