 CoxVegas
join:2011-07-25
Las Vegas, NV
kudos:2 | reply to Alan A
Re: [NV] Cox Internet continually dropping in Las Vegas area DCC = Downstream Channel Change - your modem is shifting to a new channel for load balancing, and is something that was fixed in DOCSIS 3 (by virtue of doing the channel bonding, you're never reliant on a single channel at a time).
If you want to PM me your cable MAC, I can see if there's any reason you're getting those more than usual, but a few times a day, especially in the evening when the channels are busiest, are Just Going To Happen. |
|
|
|
Alan A
join:2012-10-24
Las Vegas, NV | Sent it to you. |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to Alan A
2013-02-06 20:43:31 7-Information C203.0 DCC arrive new
2013-02-06 20:43:26 7-Information C202.0 DCC depart old
2013-02-06 20:41:58 7-Information C203.0 DCC arrive new
2013-02-06 20:41:53 7-Information C202.0 DCC depart old
2013-02-06 20:37:57 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-06 20:37:56 7-Information B401.0 Authorized
2013-02-06 20:37:54 5-Warning C04.1 rgstToD request sent - Response received
2013-02-06 20:37:35 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-06 20:37:35 3-Critical U02.0 UCD invalid or channel unusable
2013-02-06 20:37:35 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-02-06 20:37:05 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:37:04 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:37:02 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:37:01 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:37:00 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:59 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:58 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:57 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:56 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:55 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:54 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:53 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:52 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:51 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:50 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:49 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-06 20:36:47 7-Information C202.0 DCC depart old
2013-02-06 20:32:20 7-Information C203.0 DCC arrive new
2013-02-06 20:32:15 7-Information C202.0 DCC depart old
2013-02-06 20:27:47 7-Information C203.0 DCC arrive new
2013-02-06 20:27:42 7-Information C202.0 DCC depart old
2013-02-06 20:26:16 7-Information C203.0 DCC arrive new
2013-02-06 20:26:11 7-Information C202.0 DCC depart old
2013-02-06 20:18:43 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-06 20:18:42 7-Information B401.0 Authorized
2013-02-06 20:18:40 5-Warning C04.1 rgstToD request sent - Response received
Can you please fucking fix this problem? I'm fed up with this shit. It happens EVERY DAY, CONSTANTLY, ALL THE TIME. IT'S A PAIN TO DEAL WITH. I can't get through a single god damn game without it dropping and reconnecting. It's god fucking awful. |
|
CoxVegas
join:2011-07-25
Las Vegas, NV
kudos:2 | said by Alan A:Can you please fucking fix this problem? I'm fed up with this shit. It happens EVERY DAY, CONSTANTLY, ALL THE TIME. IT'S A PAIN TO DEAL WITH. I can't get through a single god damn game without it dropping and reconnecting. It's god fucking awful. Please reply to the PM I sent you 3 weeks ago asking for information. |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to CoxVegas
Re: [NV] Cox Internet continually dropping in Las Vegas area I did send it three weeks ago. Look in your PM box and find the date. |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to Alan A
2013-02-10 13:35:13 7-Information C203.0 DCC arrive new
2013-02-10 13:35:07 7-Information C202.0 DCC depart old
2013-02-10 13:34:48 7-Information B401.0 Authorized
2013-02-10 13:34:38 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 13:34:35 5-Warning C04.1 rgstToD request sent - Response received
2013-02-10 13:34:14 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:34:13 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:34:01 3-Critical U02.0 UCD invalid or channel unusable
2013-02-10 13:33:51 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-10 13:33:51 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-02-10 13:33:21 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:33:20 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:33:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:33:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:33:12 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:33:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:33:10 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:33:10 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:33:09 4-Error C401.0 DCC-ACK not received
2013-02-10 13:33:09 7-Information C203.0 DCC arrive new
2013-02-10 13:33:09 7-Information C203.0 DCC arrive new
2013-02-10 13:33:08 7-Information C203.0 DCC arrive new
2013-02-10 13:33:08 7-Information C203.0 DCC arrive new
2013-02-10 13:33:07 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:33:06 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:33:05 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:33:04 7-Information C202.0 DCC depart old
2013-02-10 13:32:07 7-Information C203.0 DCC arrive new
2013-02-10 13:32:02 7-Information C202.0 DCC depart old
2013-02-10 13:31:36 7-Information C203.0 DCC arrive new
2013-02-10 13:31:31 7-Information C202.0 DCC depart old
2013-02-10 13:30:52 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 13:30:51 7-Information B401.0 Authorized
2013-02-10 13:30:49 5-Warning C04.1 rgstToD request sent - Response received
Oh my god PLEASE fix this. I'm dropping in a tournament. |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to Alan A
2013-02-10 13:43:19 7-Information C203.0 DCC arrive new
2013-02-10 13:43:14 7-Information C202.0 DCC depart old
2013-02-10 13:42:08 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 13:42:07 7-Information B401.0 Authorized
2013-02-10 13:42:05 5-Warning C04.1 rgstToD request sent - Response received
2013-02-10 13:41:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:41:48 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:41:39 3-Critical U02.0 UCD invalid or channel unusable
2013-02-10 13:41:29 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-10 13:41:29 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-02-10 13:40:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:40:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:40:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:40:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:40:51 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:40:50 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:40:49 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:40:48 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:40:48 4-Error C401.0 DCC-ACK not received
2013-02-10 13:40:47 7-Information C203.0 DCC arrive new
2013-02-10 13:40:47 7-Information C203.0 DCC arrive new
2013-02-10 13:40:47 7-Information C203.0 DCC arrive new
2013-02-10 13:40:46 7-Information C203.0 DCC arrive new
2013-02-10 13:40:46 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:40:45 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:40:44 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:40:42 7-Information C202.0 DCC depart old
2013-02-10 13:40:17 7-Information C203.0 DCC arrive new
2013-02-10 13:40:12 7-Information C202.0 DCC depart old
2013-02-10 13:35:13 7-Information C203.0 DCC arrive new
2013-02-10 13:35:07 7-Information C202.0 DCC depart old
2013-02-10 13:34:48 7-Information B401.0 Authorized
2013-02-10 13:34:38 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 13:34:35 5-Warning C04.1 rgstToD request sent - Response received
It keeps fucking going. 10 times in the last 10 minutes. |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to Alan A
2013-02-10 13:46:08 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 13:46:07 7-Information B401.0 Authorized
2013-02-10 13:46:05 5-Warning C04.1 rgstToD request sent - Response received
2013-02-10 13:45:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:45:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:45:47 3-Critical U02.0 UCD invalid or channel unusable
2013-02-10 13:45:34 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-10 13:45:34 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-02-10 13:45:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:45:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:45:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:44:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:44:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:44:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:44:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:44:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 13:44:53 4-Error C401.0 DCC-ACK not received
2013-02-10 13:44:52 7-Information C203.0 DCC arrive new
2013-02-10 13:44:52 7-Information C203.0 DCC arrive new
2013-02-10 13:44:52 7-Information C203.0 DCC arrive new
2013-02-10 13:44:52 7-Information C203.0 DCC arrive new
2013-02-10 13:44:51 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:44:50 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:44:49 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 13:44:47 7-Information C202.0 DCC depart old
2013-02-10 13:44:21 7-Information C203.0 DCC arrive new
2013-02-10 13:44:16 7-Information C202.0 DCC depart old
2013-02-10 13:43:50 7-Information C203.0 DCC arrive new
2013-02-10 13:43:45 7-Information C202.0 DCC depart old
2013-02-10 13:43:19 7-Information C203.0 DCC arrive new
2013-02-10 13:43:14 7-Information C202.0 DCC depart old
2013-02-10 13:42:08 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 13:42:07 7-Information B401.0 Authorized
2013-02-10 13:42:05 5-Warning C04.1 rgstToD request sent - Response received |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to Alan A
Re: [NV] Cox Internet continually dropping in Las Vegas area 013-02-10 14:53:22 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 14:53:21 7-Information B401.0 Authorized
2013-02-10 14:53:19 5-Warning C04.1 rgstToD request sent - Response received
2013-02-10 14:53:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:52:50 3-Critical U02.0 UCD invalid or channel unusable
2013-02-10 14:52:37 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-10 14:52:37 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-02-10 14:52:07 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:52:06 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:52:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:52:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:51:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:51:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:51:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:51:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 14:51:56 4-Error C401.0 DCC-ACK not received
2013-02-10 14:51:55 7-Information C203.0 DCC arrive new
2013-02-10 14:51:55 7-Information C203.0 DCC arrive new
2013-02-10 14:51:55 7-Information C203.0 DCC arrive new
2013-02-10 14:51:54 7-Information C203.0 DCC arrive new
2013-02-10 14:51:54 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 14:51:53 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 14:51:52 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 14:51:50 7-Information C202.0 DCC depart old
2013-02-10 14:46:19 7-Information C203.0 DCC arrive new
2013-02-10 14:46:14 7-Information C202.0 DCC depart old
2013-02-10 14:37:05 7-Information C203.0 DCC arrive new
2013-02-10 14:37:00 7-Information C202.0 DCC depart old
2013-02-10 14:09:29 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 14:09:28 7-Information B401.0 Authorized
2013-02-10 14:09:26 5-Warning C04.1 rgstToD request sent - Response received |
|
 firerx
join:2005-01-28
Avondale, AZ | reply to Alan A
It's been doing the same this here in West Phoenix. I starting to get perturbed.  |
|
CoxVegas
join:2011-07-25
Las Vegas, NV
kudos:2 | reply to Alan A
said by Alan A:Oh my god PLEASE fix this. I'm dropping in a tournament. PM sent regarding getting someone out to your house to take a look, but the problem does seem localized to your location (no one else on your street is having the number of T3s you're seeing).
Your levels are good, which leads me to believe some noise is creeping in somewhere. Do you have any splitters on your modem without something plugged in on the other leg? Unshielded (or poorly shielded) coax in the runs? Anything along those lines? |
|
CoxVegas
join:2011-07-25
Las Vegas, NV
kudos:2 | reply to firerx
said by firerx:It's been doing the same this here in West Phoenix. I starting to get perturbed.
T3 errors are always very localized types of problems - they can't go any further than your node, and usually are more localized than even that. If you're getting a ton of T3s, check your local cabling, or call in to have a technician come out, measure your line for signal and noise, and if found, correct it. |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to Alan A
2013-02-10 20:41:17 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-10 20:41:16 7-Information B401.0 Authorized
2013-02-10 20:41:14 5-Warning C04.1 rgstToD request sent - Response received
2013-02-10 20:41:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:40:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:40:47 3-Critical U02.0 UCD invalid or channel unusable
2013-02-10 20:40:35 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-10 20:40:35 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-02-10 20:40:05 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:40:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:40:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:39:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:39:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:39:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:39:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:39:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-10 20:39:53 4-Error C401.0 DCC-ACK not received
2013-02-10 20:39:53 7-Information C203.0 DCC arrive new
2013-02-10 20:39:53 7-Information C203.0 DCC arrive new
2013-02-10 20:39:52 7-Information C203.0 DCC arrive new
2013-02-10 20:39:52 7-Information C203.0 DCC arrive new
2013-02-10 20:39:51 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 20:39:50 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 20:39:49 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-10 20:39:48 7-Information C202.0 DCC depart old
2013-02-10 20:38:51 7-Information C203.0 DCC arrive new
2013-02-10 20:38:46 7-Information C202.0 DCC depart old
2013-02-10 20:29:32 7-Information C203.0 DCC arrive new
2013-02-10 20:29:27 7-Information C202.0 DCC depart old
2013-02-10 20:20:45 7-Information C203.0 DCC arrive new
2013-02-10 20:20:40 7-Information C202.0 DCC depart old
2013-02-10 18:17:26 7-Information C203.0 DCC arrive new
2013-02-10 18:17:21 7-Information C202.0 DCC depart old
2013-02-10 18:06:09 7-Information C203.0 DCC arrive new
What's a coax and a splitter? |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to Alan A
2013-02-11 14:39:24 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-11 14:39:23 7-Information B401.0 Authorized
2013-02-11 14:39:21 5-Warning C04.1 rgstToD request sent - Response received
2013-02-11 14:39:12 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:39:02 3-Critical U01.0 No UCD's Received - Timeout
2013-02-11 14:38:39 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-11 14:38:39 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-02-11 14:38:09 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:38:08 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:38:05 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:38:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:38:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:38:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:37:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:37:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-11 14:37:57 4-Error C401.0 DCC-ACK not received
2013-02-11 14:37:57 7-Information C203.0 DCC arrive new
2013-02-11 14:37:57 7-Information C203.0 DCC arrive new
2013-02-11 14:37:56 7-Information C203.0 DCC arrive new
2013-02-11 14:37:56 7-Information C203.0 DCC arrive new
2013-02-11 14:37:55 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-11 14:37:54 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-11 14:37:53 3-Critical R05.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2013-02-11 14:37:52 7-Information C202.0 DCC depart old
2013-02-11 14:35:54 7-Information C203.0 DCC arrive new
2013-02-11 14:35:49 7-Information C202.0 DCC depart old
2013-02-11 14:32:50 7-Information C203.0 DCC arrive new
2013-02-11 14:32:45 7-Information C202.0 DCC depart old
2013-02-11 14:31:48 7-Information C203.0 DCC arrive new
2013-02-11 14:31:43 7-Information C202.0 DCC depart old
2013-02-11 14:30:47 7-Information C203.0 DCC arrive new
2013-02-11 14:30:42 7-Information C202.0 DCC depart old
2013-02-11 14:29:46 7-Information C203.0 DCC arrive new
2013-02-11 14:29:41 7-Information C202.0 DCC depart old
2013-02-11 14:28:44 7-Information C203.0 DCC arrive new
2013-02-11 14:28:39 7-Information C202.0 DCC depart old
2013-02-11 14:27:43 7-Information C203.0 DCC arrive new
2013-02-11 14:27:38 7-Information C202.0 DCC depart old |
|
| reply to Alan A
said by Alan A:What's a coax and a splitter?
Coax is the wire that cable signals run on.
»en.wikipedia.org/wiki/Coaxial_cable
A splitter splits that cable signal for multiple devices...
»www.ellies.co.za/assets/images/T···_out.jpg
Google is your friend! |
|
1 edit | reply to Alan A
Yeah, I've recently been given the "it must be your hardware inside the house.. it's not us" line by "Christopher" at Cox Support.
I'm guessing Cox is having trouble with the upstream my neighborhood is given, and as it is intermittent and mostly daytime. Amazing how those cable crimps keep such regular hours, huh?
Without their assistance, and despite the misdirection, I've noted:
the Docsis 3.0 cable modem tries to communicate with CMTS (10.65.0.1) with a MAC of MAC=64:00:f1:40:38:6a, it craps out.. but almost only between 11am and 8pm.
Here's what today has been like. What a joy...
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:16 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:16 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:16 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:01 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:01 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:01 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:06:01 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:03:10 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 10:12:37 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 09:51:26 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 09:49:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 09:38:55 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:56 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from GUI/Configuration page ;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 09:37:09 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
My guess is the CMTS is failing and rebooting, or the filter built into the CMTS is improperly functioning. |
|
 CoxTech1VIP
join:2002-04-25
Chesapeake, VA
kudos:72 | Probably not a CMTS issue otherwise many thousands of others would be experiencing problems. Upstream ingress/noise is a more likely explanation although a failed modem is also possible. A technician would be able to help determine what could be going on. |
|
Alan A
join:2012-10-24
Las Vegas, NV | reply to Alan A
2013-02-17 14:50:56 7-Information C203.0 DCC arrive new
2013-02-17 14:50:51 7-Information C202.0 DCC depart old
2013-02-17 14:50:32 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-17 14:50:31 7-Information B401.0 Authorized
2013-02-17 14:50:29 5-Warning C04.1 rgstToD request sent - Response received
2013-02-17 14:50:14 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-17 14:50:14 3-Critical U02.0 UCD invalid or channel unusable
2013-02-17 14:50:07 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 14:49:44 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 14:49:39 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 14:49:33 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 14:49:20 7-Information C202.0 DCC depart old
2013-02-17 12:18:45 7-Information C203.0 DCC arrive new
2013-02-17 12:18:40 7-Information C202.0 DCC depart old
2013-02-17 12:10:59 7-Information B401.0 Authorized
2013-02-17 12:10:49 6-Notice I401.0 TLV-11 - unrecognized OID
2013-02-17 12:10:46 5-Warning C04.1 rgstToD request sent - Response received
2013-02-17 12:10:33 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 12:10:22 3-Critical U02.0 UCD invalid or channel unusable
2013-02-17 12:10:13 3-Critical C206.0 DCC aborted unable to communicate on new upstream channel
2013-02-17 12:10:13 3-Critical R04.0 Received Response to Broadcast Maintenance Request, but no Unicast Maintenance opportunities received - T4 timeout
2013-02-17 12:09:43 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 12:09:42 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 12:09:39 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 12:09:36 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 12:09:34 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 12:09:33 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 12:09:32 3-Critical R02.0 No Ranging Response received - T3 time-out
2013-02-17 12:09:32 3-Critical R02.0 No Ranging Response received - T3 time-out
Still happening. |
|
