dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
606
share rss forum feed

oazanki

join:2013-02-10

[CA] Random Intermittent Connection - SoCal

I recently upgraded to SB6141 and it works great most of the time. However, I tend to suffer from connection loss at random times and recycling the modem and router does not seem to resolve those issues.

Here is the info requested:

Modem: Motorola SB6141
Router: Netgear WNDR3700
Cox Speed Tier: Preferred Package

Signal Levels during connection loss:

Downstream Bonding Channel Value
Channel ID 5 6 7 8
Frequency 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
6 dBmV 5 dBmV 5 dBmV 5 dBmV

Upstream Bonding Channel Value
Channel ID 3
Frequency 35580000 Hz
Ranging Service ID 2145
Symbol Rate 2.560 Msym/sec
Power Level 42 dBmV
Upstream Modulation [2] QPSK
[3] 16QAM

Ranging Status Success

Signal Stats (Codewords) Bonding Channel Value
Channel ID 5 6 7 8
Total Unerrored Codewords 18756943 18046135 18054674 18062843
Total Correctable Codewords 32 67 65 82
Total Uncorrectable Codewords 493 487 583 587

Cable modem is connected directly to the wall.

An example of speedtests during connection disruption:

»speedtest.net/result/2323908177.png

»speedtest.net/result/2323914508.png

I had another issue today and I could not even perform a speed test.

Ping and Traceroute results during connection disruption today:

Ping has started…

PING google.com (74.125.224.167): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
64 bytes from 74.125.224.167: icmp_seq=0 ttl=55 time=8078.824 ms
64 bytes from 74.125.224.167: icmp_seq=1 ttl=55 time=7864.606 ms
64 bytes from 74.125.224.167: icmp_seq=2 ttl=55 time=7942.258 ms
64 bytes from 74.125.224.167: icmp_seq=3 ttl=55 time=8184.279 ms
64 bytes from 74.125.224.167: icmp_seq=4 ttl=55 time=8277.907 ms
64 bytes from 74.125.224.167: icmp_seq=5 ttl=55 time=9704.258 ms
64 bytes from 74.125.224.167: icmp_seq=6 ttl=55 time=9475.630 ms
64 bytes from 74.125.224.167: icmp_seq=7 ttl=55 time=10165.721 ms
64 bytes from 74.125.224.167: icmp_seq=8 ttl=55 time=10661.984 ms
64 bytes from 74.125.224.167: icmp_seq=9 ttl=55 time=10687.537 ms

--- google.com ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 7864.606/9104.300/10687.537/1096.614 ms

Traceroute has started…

traceroute: Warning: www.google.com has multiple addresses; using 74.125.224.179
traceroute to www.google.com (74.125.224.179), 64 hops max, 72 byte packets
1 192.168.1.1 (192.168.1.1) 3667.626 ms 0.209 ms 0.170 ms
2 * * *
3 * * *
4 * * ip68-4-11-8.oc.oc.cox.net (68.4.11.8) 4765.192 ms
5 ip68-4-11-94.oc.oc.cox.net (68.4.11.94) 44.576 ms 8.074 ms 7.507 ms
6 68.1.5.137 (68.1.5.137) 8.968 ms 7.744 ms 8.610 ms
7 langbbrj01-ge050000804.r2.la.cox.net (68.105.30.181) 11.163 ms 11.405 ms 12.998 ms
8 64.233.174.238 (64.233.174.238) 13.480 ms 11.900 ms 9.412 ms
9 72.14.236.11 (72.14.236.11) 10.329 ms 12.068 ms 9.707 ms
10 lax02s01-in-f19.1e100.net (74.125.224.179) 7.608 ms 12.971 ms 15.736 ms

I have a wired connection to the router.

Issue was not resolved when bypassing router.

No other services from Cox besides internet.


This is a snapshot from Logs for today (I am assuming these are related to the issues I am seeing:

6-Notice I401.0 TLV-11 - unrecognized OID
5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
5-Warning T07.0 RCS Partial Service
6-Notice I401.0 TLV-11 - unrecognized OID
5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1

For comparison purposes, here are my Signal levels when the connection is working properly:

Downstream Bonding Channel Value
Channel ID 5 6 7 8
Frequency 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz
Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
6 dBmV 5 dBmV 5 dBmV 5 dBmV

Upstream Bonding Channel Value
Channel ID 2
Frequency 30210000 Hz
Ranging Service ID 2145
Symbol Rate 5.120 Msym/sec
Power Level 40 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM

Ranging Status Success

Signal Stats (Codewords) Bonding Channel Value
Channel ID 5 6 7 8
Total Unerrored Codewords 762255732 761544045 761551817 761559540
Total Correctable Codewords 1377 2292 3057 3519
Total Uncorrectable Codewords 493 487 583 587

And here is a corresponding speed test: »speedtest.net/result/2499997803.png


oazanki

join:2013-02-10

Also just to clarify, I had the same issue when I was using Cox's Arris modem. I then purchased my own SB6141 and that gave me a boost in speed, but the disconnection issue is still unresolved, although I think it happens less frequently now.



Anonguy

@cox.net

I see one real problem.

In your trace:

1 192.168.1.1 (192.168.1.1) 3667.626 ms

Never ever should a ping to your router be over 1ms.

I know you said bypassing your router did not make the problem stop, If so that leads to a more local problem such as PC, NIX, Cat5 Cable or software issue such as Firewall/Antivirus.

I would run a 100 time ping to 192.168.1.1

If it ever goes over 1ms that indicates the problem is clearly local.


oazanki

join:2013-02-10
reply to oazanki

Thanks for the response. I did the 100 ping to 192.168.1.1. Here are the results:

--- 192.168.1.1 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.181/0.232/0.779/0.057 ms

But that does not point to the problem now, because my connection is working properly. I will repeat this test again when I have the problem.

I was comparing the signal report between the time I had connection issues and when it was working properly, The only difference I could see was in Upstream Bonding Channel Value:

Bad Connection:
Channel ID 3
Frequency 35580000 Hz
Ranging Service ID 2145
Symbol Rate 2.560 Msym/sec
Power Level 42 dBmV
Upstream Modulation [2] QPSK
[3] 16QAM

Good Connection
Channel ID 2
Frequency 30210000 Hz
Ranging Service ID 2145
Symbol Rate 5.120 Msym/sec
Power Level 40 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM

I am not sure if that means anything?


oazanki

join:2013-02-10
reply to oazanki

I guess there are also differences between Codewords:

Bad Connection:

Signal Stats (Codewords) Bonding Channel Value
Channel ID 5 6 7 8
Total Unerrored Codewords 18756943 18046135 18054674 18062843
Total Correctable Codewords 32 67 65 82
Total Uncorrectable Codewords 493 487 583 587

Good Connection:

Signal Stats (Codewords) Bonding Channel Value
Channel ID 5 6 7 8
Total Unerrored Codewords 762255732 761544045 761551817 761559540
Total Correctable Codewords 1377 2292 3057 3519
Total Uncorrectable Codewords 493 487 583 587



Anonguy

@cox.net
reply to Anonguy

NIC not NIX...



Anonguy

@cox.net
reply to oazanki

said by oazanki:

I guess there are also differences between Codewords:

Bad Connection:

Signal Stats (Codewords) Bonding Channel Value
Channel ID 5 6 7 8
Total Unerrored Codewords 18756943 18046135 18054674 18062843
Total Correctable Codewords 32 67 65 82
Total Uncorrectable Codewords 493 487 583 587

Good Connection:

Signal Stats (Codewords) Bonding Channel Value
Channel ID 5 6 7 8
Total Unerrored Codewords 762255732 761544045 761551817 761559540
Total Correctable Codewords 1377 2292 3057 3519
Total Uncorrectable Codewords 493 487 583 587

That is not any indication of a problem.
Because you should have a higher number when you are having a bad connection. But the number is higher when the connection is good.