Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
New Contributor
•
High latency / packet drop since upgrading cable modem to SBG6580
Hi All,
I upgraded my cable modem last month to a newer unit. Since upgrading, I have been having horrible latency when playing online games and the modem resets often. I view the diagnostics and see the following below. I have ran my connection on pingtest.net which is showing betwen 60 and 76% packet loss. I've used this site before and I am normally close to 0.
Does anyone have any suggestions?
Thanks!
| Startup Procedure | ||
| Procedure | Status | Comment |
| Acquire Downstream Channel | Locked | |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Configuration File | ||
| Security | Enabled | BPI+ |
| Downstream Bonded Channels | ||||||||
| Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR | Correctables | Uncorrectables |
| 1 | Locked | QAM256 | 13 | 837000000 Hz | -0.9 dBmV | 39.0 dB | 38 | 0 |
| 2 | Locked | QAM256 | 14 | 843000000 Hz | -0.7 dBmV | 39.0 dB | 14 | 24 |
| 3 | Locked | QAM256 | 15 | 849000000 Hz | -0.6 dBmV | 38.2 dB | 57 | 0 |
| 4 | Locked | QAM256 | 16 | 855000000 Hz | -0.5 dBmV | 36.2 dB | 45 | 0 |
| 5 | Locked | QAM256 | 21 | 861000000 Hz | 0.1 dBmV | 38.3 dB | 68 | 0 |
| 6 | Locked | QAM256 | 22 | 867000000 Hz | -0.7 dBmV | 38.6 dB | 32 | 0 |
| 7 | Locked | QAM256 | 23 | 873000000 Hz | 0.1 dBmV | 36.8 dB | 36 | 0 |
| 8 | Locked | QAM256 | 24 | 879000000 Hz | 0.3 dBmV | 33.3 dB | 547938 | 424 |
| Upstream Bonded Channels | ||||||
| Channel | Lock Status | US Channel Type | Channel ID | Symbol Rate | Frequency | Power |
| 1 | Locked | ATDMA | 4 | 2560 Ksym/sec | 33000000 Hz | 51.0 dBmV |
| 2 | Locked | ATDMA | 1 | 2560 Ksym/sec | 25000000 Hz | 51.0 dBmV |
| 3 | Locked | ATDMA | 3 | 2560 Ksym/sec | 29000000 Hz | 51.0 dBmV |
| 4 | Locked | TDMA and ATDMA | 5 | 2560 Ksym/sec | 37000000 Hz | 51.0 dBmV |
| Sun Dec 15 21:15:43 2013 | Warning (5) | Dynamic Range Window violation |
| Sun Dec 15 21:15:35 2013 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Warning (5) | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.0;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Thu Dec 12 05:47:33 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Sun Dec 08 17:59:59 2013 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.1;CM-VER=3.0; |
| Sun Dec 08 16:41:57 2013 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Mon Dec 02 22:30:08 2013 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.1;CM-VER=3.0; |
| Mon Dec 02 17:33:25 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.1;CM-VER=3.0; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out |
| Fri Nov 29 08:15:05 2013 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.1;CM-VER=3.0; |
| Fri Nov 29 08:14:08 2013 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Nov 29 08:13:01 2013 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Nov 29 08:13:00 2013 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Nov 29 08:12:36 2013 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=14:5b:d1:c5:18:63;CMTS-MAC=50:3d:e5:0b:96:9e;CM-QOS=1.0;CM-VER=3.0; |
Travisstorma
New Contributor
•
Todays Connection status.
Downstream Bonded Channels
0
0
Health_Edge
+5 more
Valued Contributor III
•
I notice a couple things, first in your OP, your upstream signal levels look high at 51. I also noticed in the next post the upstream decreased without the downstream increasing.
But more importantly it looks like your 8th downstream channel (Channel ID 24) at 879000000 Hz seems to have low DS SNR even though the power level is the same, this says to me its probably caused by ingress. And in the time between the two posts it caused almost 3000 uncorrectable errors, That is no doubt causing the packet loss. The question would seem to be what is causing the ingress at 879000000 Hz.
Did anything change between the two posts? Did you remove or add any wiring? Also, have you check all connections between where the cable comes into the house and where it connects to your modem?
0
0
Travisstorma
New Contributor
•
Hi!
I did not change anything cable wise. A couple of days ago I did go through and make sure all connections were tight and clean.
0
0
KipK
Former Moderator
•
Hmm, that's pretty much what we'd recommend, since the area looks clear right now. If that didn't do it then our next step would be a service call.
0
0