US Cable Support > Cox HSI > [NV] Constant disconnects at afternoon-night

[NV] Constant disconnects at afternoon-night

Post the signal page from your modem if you can.

T3 is usually a bad cable connection someplace or a bad modem. The common term is "upstream noise issue."

Do you want a screenshot of it? I have no idea what to copy paste from it.

Your signal levels are excellent, at least at the moment you took the screenshot.

Unfortunate news is that it's likely intermittent so it may be hard to nail down.

Guess I'll keep this page open and screenshot when the issue comes up again.

reply to Alan A
Alan A,

PM me your cable MAC and I'll take a look to see if something odd is going on.

Sent.

reply to Alan A
I had no drops at all on Sunday. It was amazing. However, come Monday night, constant drops and lag spikes. I can't even access the modem's page.

»i.imgur.com/gZFoL.png

2013-01-07 19:08:00 6-Notice I401.0 TLV-11 - unrecognized OID
2013-01-07 19:07:59 7-Information B401.0 Authorized
2013-01-07 19:07:57 5-Warning C04.1 rgstToD request sent - Response received
2013-01-07 19:07:43 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-01-07 19:07:43 3-Critical U02.0 UCD invalid or channel unusable
2013-01-07 19:07:43 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-01-07 19:07:13 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:12 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:11 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:10 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:09 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:08 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:07 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:06 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:05 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:04 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:03 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:02 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:01 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:07:00 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:06:59 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:06:58 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-07 19:06:55 7-Information C202.0 DCC depart old
2013-01-07 19:05:58 7-Information C203.0 DCC arrive new
2013-01-07 19:05:53 7-Information C202.0 DCC depart old
2013-01-07 18:51:02 7-Information C203.0 DCC arrive new
2013-01-07 18:50:57 7-Information C202.0 DCC depart old
2013-01-07 18:43:23 7-Information C203.0 DCC arrive new
2013-01-07 18:43:18 7-Information C202.0 DCC depart old
2013-01-07 18:24:29 7-Information C203.0 DCC arrive new
2013-01-07 18:24:23 7-Information C202.0 DCC depart old
2013-01-07 18:23:28 7-Information C203.0 DCC arrive new
2013-01-07 18:23:22 7-Information C202.0 DCC depart old
2013-01-07 18:18:19 7-Information C203.0 DCC arrive new
2013-01-07 18:18:14 7-Information C202.0 DCC depart old

Had another drop 10 minutes after posting.

EDIT: Dropped again 8:23 PM

reply to Alan A
2013-01-17 19:59:38 6-Notice I401.0 TLV-11 - unrecognized OID
2013-01-17 19:59:37 7-Information B401.0 Authorized
2013-01-17 19:59:35 5-Warning C04.1 rgstToD request sent - Response received
2013-01-17 19:59:19 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:59:10 3-Critical U02.0 UCD invalid or channel unusable
2013-01-17 19:59:06 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-01-17 19:59:06 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-01-17 19:58:36 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:58:35 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:58:32 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:58:30 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:58:28 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:58:26 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:58:25 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:58:25 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-17 19:58:24 4-Error C401.0 DCC-ACK not received
2013-01-17 19:58:24 7-Information C203.0 DCC arrive new
2013-01-17 19:58:24 7-Information C203.0 DCC arrive new
2013-01-17 19:58:23 7-Information C203.0 DCC arrive new
2013-01-17 19:58:23 7-Information C203.0 DCC arrive new
2013-01-17 19:58:22 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-17 19:58:21 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-17 19:58:20 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-17 19:58:19 7-Information C202.0 DCC depart old
2013-01-17 18:02:29 7-Information C203.0 DCC arrive new
2013-01-17 18:02:24 7-Information C202.0 DCC depart old
2013-01-17 18:01:29 7-Information C203.0 DCC arrive new
2013-01-17 18:01:24 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-17 18:01:23 7-Information C202.0 DCC depart old
2013-01-17 17:54:17 7-Information C203.0 DCC arrive new
2013-01-17 17:54:12 7-Information C202.0 DCC depart old
2013-01-17 17:03:18 7-Information C203.0 DCC arrive new
2013-01-17 17:03:13 7-Information C202.0 DCC depart old
2013-01-17 16:40:17 7-Information C203.0 DCC arrive new
2013-01-17 16:40:12 7-Information C202.0 DCC depart old
2013-01-17 16:39:16 7-Information C203.0 DCC arrive new
2013-01-17 16:39:10 7-Information C202.0 DCC depart old

Why is this still happening. It's really fucking frustrating.

The momentary drops due to DCCs is due to your device being DOCSIS 2 - there's not a lot to be done about that one besides get you upgraded to a DOCSIS 3.

I'm looking into those T3s though.

2013-01-19 15:50:58 7-Information C203.0 DCC arrive new
2013-01-19 15:50:53 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-19 15:50:52 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-19 15:50:51 7-Information C202.0 DCC depart old
2013-01-19 15:26:17 7-Information C203.0 DCC arrive new
2013-01-19 15:26:12 7-Information C202.0 DCC depart old
2013-01-19 15:16:40 6-Notice I401.0 TLV-11 - unrecognized OID
2013-01-19 15:16:39 7-Information B401.0 Authorized
2013-01-19 15:16:37 5-Warning C04.1 rgstToD request sent - Response received
2013-01-19 15:16:26 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-01-19 15:16:26 3-Critical U02.0 UCD invalid or channel unusable
2013-01-19 15:16:20 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-19 15:16:16 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-19 15:16:10 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-19 15:16:09 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-19 15:16:07 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-19 15:16:05 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-19 15:15:54 7-Information C202.0 DCC depart old
2013-01-19 15:10:54 7-Information C203.0 DCC arrive new
2013-01-19 15:10:49 7-Information C202.0 DCC depart old
2013-01-19 14:24:47 7-Information C203.0 DCC arrive new
2013-01-19 14:24:42 7-Information C202.0 DCC depart old
2013-01-19 14:22:43 7-Information C203.0 DCC arrive new
2013-01-19 14:22:38 7-Information C202.0 DCC depart old
2013-01-19 14:12:23 7-Information C203.0 DCC arrive new
2013-01-19 14:12:18 7-Information C202.0 DCC depart old
2013-01-19 14:11:21 7-Information C203.0 DCC arrive new
2013-01-19 14:11:16 7-Information C202.0 DCC depart old
2013-01-19 13:36:06 7-Information C203.0 DCC arrive new
2013-01-19 13:36:01 7-Information C202.0 DCC depart old
2013-01-19 13:21:03 6-Notice I401.0 TLV-11 - unrecognized OID
2013-01-19 13:21:02 7-Information B401.0 Authorized

reply to Alan A
2013-01-24 17:37:14 7-Information C203.0 DCC arrive new
2013-01-24 17:37:09 7-Information C202.0 DCC depart old
2013-01-24 17:35:10 7-Information C203.0 DCC arrive new
2013-01-24 17:35:05 7-Information C202.0 DCC depart old
2013-01-24 17:08:12 7-Information C203.0 DCC arrive new
2013-01-24 17:08:07 7-Information C202.0 DCC depart old
2013-01-24 16:49:44 7-Information C203.0 DCC arrive new
2013-01-24 16:49:39 7-Information C202.0 DCC depart old
2013-01-24 16:18:10 6-Notice I401.0 TLV-11 - unrecognized OID
2013-01-24 16:18:09 7-Information B401.0 Authorized
2013-01-24 16:18:07 5-Warning C04.1 rgstToD request sent - Response received
2013-01-24 16:17:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:45 3-Critical U02.0 UCD invalid or channel unusable
2013-01-24 16:17:41 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-01-24 16:17:41 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-01-24 16:17:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:10 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:07 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:05 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-24 16:17:00 4-Error C401.0 DCC-ACK not received
2013-01-24 16:17:00 7-Information C203.0 DCC arrive new
2013-01-24 16:16:59 7-Information C203.0 DCC arrive new
2013-01-24 16:16:59 7-Information C203.0 DCC arrive new
2013-01-24 16:16:59 7-Information C203.0 DCC arrive new
2013-01-24 16:16:58 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-24 16:16:57 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-24 16:16:56 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-24 16:16:55 7-Information C202.0 DCC depart old
2013-01-24 15:06:12 7-Information C203.0 DCC arrive new
2013-01-24 15:06:07 7-Information C202.0 DCC depart old

reply to Alan A
2013-01-26 10:52:50 7-Information C203.0 DCC arrive new
2013-01-26 10:52:45 7-Information C202.0 DCC depart old
2013-01-26 10:51:49 7-Information C203.0 DCC arrive new
2013-01-26 10:51:44 7-Information C202.0 DCC depart old
2013-01-26 10:50:16 7-Information C203.0 DCC arrive new
2013-01-26 10:50:11 7-Information C202.0 DCC depart old
2013-01-26 10:49:14 7-Information C203.0 DCC arrive new
2013-01-26 10:49:09 7-Information C202.0 DCC depart old
2013-01-26 10:47:21 6-Notice I401.0 TLV-11 - unrecognized OID
2013-01-26 10:47:20 7-Information B401.0 Authorized
2013-01-26 10:47:18 5-Warning C04.1 rgstToD request sent - Response received
2013-01-26 10:47:06 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:57 3-Critical U02.0 UCD invalid or channel unusable
2013-01-26 10:46:53 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-01-26 10:46:53 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-01-26 10:46:23 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:22 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:19 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:13 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:12 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:12 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-01-26 10:46:11 4-Error C401.0 DCC-ACK not received
2013-01-26 10:46:11 7-Information C203.0 DCC arrive new
2013-01-26 10:46:11 7-Information C203.0 DCC arrive new
2013-01-26 10:46:10 7-Information C203.0 DCC arrive new
2013-01-26 10:46:10 7-Information C203.0 DCC arrive new
2013-01-26 10:46:09 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-26 10:46:08 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-26 10:46:07 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-01-26 10:46:06 7-Information C202.0 DCC depart old
2013-01-26 10:45:10 7-Information C203.0 DCC arrive new
2013-01-26 10:45:05 7-Information C202.0 DCC depart old
2013-01-26 10:44:09 7-Information C203.0 DCC arrive new
2013-01-26 10:44:04 7-Information C202.0 DCC depart old
2013-01-26 10:43:08 7-Information C203.0 DCC arrive new
2013-01-26 10:43:03 7-Information C202.0 DCC depart old

PLEASE GOD FIX THIS