Forum Discussion

chanmiro's avatar
chanmiro
Contributor
12 years ago
Solved

Constant Upload Problems in Rogers AR

I'm posting here because I'm tired of trying to explain this to Cox Support over the phone. It will be pretty long so please bare with me. This is going on in south Rogers, AR.

For the last 3 to 4 weeks I've been noticing issues with the bonded upstream channels, causing my internet connection to time out and occasionally cause the modem to reset automatically. Currently I have 3 upload channels (channels 2, 3 and 4), and out of the 3, channels 3 and 4 are constantly timing out, showing an "Aborted" status within the modem's diagnostics (192.168.100.1). Sometime after Cox does some repairs (assuming somewhere in their distribution), it seems to happen again. It also happens some hours after I have reset the modem via Cox automated and live person calls. It gets worse on the weekends.

Now, this is my history with Cox Support:

- Some weeks ago, when I called Cox some time after I started noticing the issues, I found out that this area was flagged for an outage. So I waited a day to call again. It seemed to go back to normal for a few days then it started again.

- By the second time I called, the support person said that the outage was taken care of and they sent in the tech to check my connection. The tech showed up, very good tech by the way, and proceeded to replace all of my coax connections and splitters (I already have RG6 cable throughout my house). He ran his tests checking for noises and he couldn't see anything wrong within my house. The power levels in the modem improved, so I can testify of the great signals I still have at this point (I work with electronics).  After checking all this, he stated that if the problem persisted, that it would most likely be outage related, which I agree 100%. It worked great for a few of days.

- This last week it started yet again to drop the 2 channels so I went to buy a new modem to see if it would help. I upgraded from the SB6121 to the SB6141 to get the 8 channels of downstream. I must say, that the internet was working fine before I installed the new modem so I expected it to work after the installation. It worked good for a couple of days until yesterday (10/18/2013). My modem did automatic resets several times. I also did a full factory default reset, just like I've dome some times before in case it helped. I would have internet for less than 1 hour before it would time out again.

- So when I called yesterday (10/18/2013), I spoke to support and they stated that my area was flagged for an outage and that someone was out troubleshooting. So I waited until today to check it out. After some time using on the internet, I noticed that it dropped the channels again. My modem has not automatically reset yet.

- Here is the info I'm seeing from my modem
Please note that the Dowstream channels are working perfectly at 37-38dB Signal to Noise Ratio and 0dBmV Power Levels

------------- Upstream Channels ---------------------

UpstreamBonding Channel Value
Channel ID
Frequency 28700000 Hz  23700000 Hz  35300000 Hz 
Ranging Service ID 4250  4250  4250 
Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec 
Power Level 41 dBmV  41 dBmV  44 dBmV 
Upstream Modulation [ 6 ] 16QAM
 
[ 6 ] 16QAM
 
[ 6 ] 16QAM
 
Ranging Status Aborted  Success  Aborted 


----------------------- Log Posts ------------------------------

Once the channels go to Aborted status, the log FILLS COMPLETELY with messages like this:

TimePriorityCodeMessage
Oct 19 2013 18:02:16 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:cf;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:15 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:14 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:14 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:13 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:12 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:12 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
Oct 19 2013 15:32:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

------------------------------------------------------------------

With all this said, is there someone in these forums that can help with this issue? Concluding from what the tech said and my opinion, the problem is not within my household, it seems to be withing the Cox infrastructure.
I would appreciate it if someone forwards this message to a person that would have good understanding of this situation and could perhaps give an update on what is going on.

Thank you!!
  • I pulled the maintenance and outage ticket history for your area, and there is some kind of intermittent noise issue going on here. It looks like on 10/8 it got bad enough to trigger an outage, but various smaller maintenance tickets have continued since then as we've tried to track the noise.

    The latest is actually from today, but it dropped off again before the tech assigned to it could finish triangulating. That's how these issues always go, I'm afraid. We get closer to the source each time. The comments from the ticket mark off the segment of the system we know the interference is coming from. Per the notes from tech 9523, "this is an intermittent floor have definitely determined it is off amp 42 but dropped again. Will monitor."

    So at this point, I don't think we need to do anything else at your location. Though I don't know exactly how long it will take to finish isolating the upstream ingress, I know we'll get it nailed down soon.

  • KipK's avatar
    KipK
    Valued Contributor II

    Hmm. Well, first off, when you upgraded to Premier yesterday the representative used the wrong code. Sorry about that. I fixed that issue, but that's not the main problem. (I swear, one day we'll figure that out.)

    You've got what we flag as marginal-low upstream SNR on one of the channels and acceptable SNR on the other. (27.7dB @ 23.7MHz, 27.4dB @ 35.3MHz, 25dB @ 28.7MHz at the current snapshot) This probably means there's ingress somewhere, since the frequency with lowest SNR is around the amateur radio 10-meter bands if I'm not mistaken.

    It will take me some time to check for any maintenance tickets around you and check a bunch of nearby modems. It could also be ingress on the drop from outside if absolutely everything else has been replaced inside.

  • Thank you so much for the update, really informative. And thanks for fixing the Premier, because I did notice quite the difference today.

    The tech that replaced all the connections and splitters did mention that although I have RG6 cable, it appeared to be single shielded. This is cable I put in 2 or 3 years ago when I got it at the local hardware store. I don't know if you would consider this adequate, or if this would be part of the issue, but it still seems to be in good condition. But then again, the tech did run tests at different spots (at the modem, in the attic and outside where the cable comes into the house).

    Again, I appreciate the work and time you're putting into this. Hopefully you'll find something conclusive, which I know is hard when it comes to an intermittent issue like this.

  • KipK's avatar
    KipK
    Valued Contributor II

    I pulled the maintenance and outage ticket history for your area, and there is some kind of intermittent noise issue going on here. It looks like on 10/8 it got bad enough to trigger an outage, but various smaller maintenance tickets have continued since then as we've tried to track the noise.

    The latest is actually from today, but it dropped off again before the tech assigned to it could finish triangulating. That's how these issues always go, I'm afraid. We get closer to the source each time. The comments from the ticket mark off the segment of the system we know the interference is coming from. Per the notes from tech 9523, "this is an intermittent floor have definitely determined it is off amp 42 but dropped again. Will monitor."

    So at this point, I don't think we need to do anything else at your location. Though I don't know exactly how long it will take to finish isolating the upstream ingress, I know we'll get it nailed down soon.

  • Kip,

    First off, I'm glad that you guys are on the case, and I'm confident you'll get rid of the pesky issue.

    I do see that it happened today at 11:22 am. It does seem like the outages happen at random times and they don't last long. I understand the short outages make it hard to catch.

    As of example of how random these things happen, 2 days ago it happened around 7 pm, yesterday (10/22/2013) around 10:40 pm, and of course today at 11:22 am. Before this, I've seen log entries at other times like around 2am, 9 am, 3pm, etc. at different days of the week (some last several minutes).

    As a preventive measure, yesterday I went around and removed any unnecessary connections and splitters, including an old VHS that was in line with a TV (which I suspected of because of how old it is). The power levels stayed very good at the modem. You can imagine my disappointment when the internet died around 10:40pm (LOL ... DARN!!).

    Anyways, I wish you and your team luck with this issue. Thank you  for the update.

  • mhren's avatar
    mhren
    New Contributor II

    chanmiro ...

    I am taking your advice from the dslreports forum and posting here.  Interestingly enough, just after I posted there this afternoon I saw the same two upstream frequencies were in "aborted" status on my modem and, sure enough, shortly thereafter (at 15:54 CDT) my modem rebooted due to T4 timeout.   So I decided that was a good time to leave the home for a bit .. and what do you know, there was a Cox truck on the main street and the tech there had been dispatched for an "outage" ..... I did not get to talk with him much, but he seemed frustrated with what he indicated was some intermittent issue that he had on the scope in the car (he pointed to it but I was not sure what I was looking at).

    Honestly, I may not bee in the same area as you are in Rogers being here in Bentonville, but who knows .....  I just rebooted my modem to get a good clean signal so I could post here and this is what my upstream channels look like when things are good.

    UpstreamBonding Channel Value
    Channel ID
    Frequency 23700000 Hz  28700000 Hz  35300000 Hz 
    Ranging Service ID 113  113  113 
    Symbol Rate 2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
    Power Level 45 dBmV  46 dBmV  43 dBmV 
    Upstream Modulation [3] 16QAM
    [3] 64QAM
     
    [3] 16QAM
    [3] 64QAM
     
    [3] 16QAM
    [3] 64QAM
     
    Ranging Status Success  Success  Success 

    When bad .. the power levels are about the same, but the modulation shifts to "[ 6 ] 16QAM" and the ranging status often ends up "Aborted" particularly for the 287 and 353 frequencies...

    As an aside .. this really started here in October after at least a year of no issues at all . and I too noticed this happens about every other day or so ... but sometimes daily.  When daily, I notice it more between midnight and 6am.  Today, however, was particularly bad with issues every few hours from about 6am on to 4pm.  We'll see if the tech in the truck was able to find anything.    Oh, I have a service call scheduled for Tuesday next week but considering how these problems only seem to come up every few years and they are always outside the home, I'm not hopeful that will be worth Cox (or my) time......

    Update:  7pm and at least the 4th reboot due to T4 timeout today alone.  There may have been more since I'm not always watching the log as it wraps.  I guess I could call tech support again but instead I will wait for the tech to visit on Tuesday.  It sure looks like whatever the Cox tech was working a pole or two over from my home was not fixed (or more likely, trouble not found) :(

  • mhren

    It seems that you're having pretty bad outages today. It reminds me of the consistent timeouts I was having last Friday night (10/18). I haven't had an outage since yesterday morning, which makes me think that you're not in the same affected group as me. I'm sure these guys will correct me if I'm wrong.

    Oddly enough, you seem to show the same information that I've been seeing.

    Well, let's see what they say about your issues today.

  • I wanted to give an update on the issue I posted. After some time Cox has seem to have done something that has greatly improved my situation, and perhaps all the other users that were potentially affected by this.

    Since the last time they seem to have troubleshooted the issue, I've only had one outage (according to my modem's logs), and that was last Tuesday 10/29/2013 at around 11am.

    One of the reason why I noticed a change on the service is because all 3 channels (2, 3 and 4) are constantly showing Upstream modulation in both [3]16QAM and [3]64QAM, which was never been the case before, at least not for all channels constantly.

    Upstream Bonding Channel Value
    Channel ID
    Frequency 35300000 Hz  23700000 Hz  28700000 Hz 
    Ranging Service ID 4250  4250  4250 
    Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec 
    Power Level 42 dBmV  41 dBmV  41 dBmV 
    Upstream Modulation [3] 16QAM
    [3] 64QAM
     
    [3] 16QAM
    [3] 64QAM
     
    [3] 16QAM
    [3] 64QAM
     
    Ranging Status Success  Success  Success 


    Hopefully this post helps others, and I would like to thank KipK and the techs that worked with him to solve the issue.

    Now, assuming that an amp was the issue, according to the tech KipK was checking with, then I will select that post as the answer.

    Thank you so much for your help.