Cox → T3 Errors and Modem Resetting Intermittently

I am getting T3-time-outs .... intermittently.
I have shown below a sequence from the logs where the modem drops off entirely
with the T3 errors. Needless to say I lose my network whenever this happens and it is quite disruptive for me.
Here are my stats. Can somebody possibly help, perhaps one of the Cox techs that monitor this board. Check the head-end and other things on your side? I greatly appreciate it!

Motorola SB5101U
Serial Number 314158001103194301011033
HFC MAC Address 00:23:ed:8a:fe:5f
CPE USB MAC Address 00:23:ee:fc:32:8a

Downstream Value
Frequency 585000000 Hz
Signal To Noise Ratio 38.0 dB
Power Level 5.4 dBmV
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

Upstream Value
Channel ID 1
Frequency 28670000 Hz
Power 43.7 dBmV

Software Version: SB5101NU-2.1.7.0-GA-00-388-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0

2012-05-23 11:02:59 3-Critical R005.0 Started Unicast Maintenance Ranging - No
Response received - T3 time-out
2012-05-23 05:48:06 4-Error D103.0 DHCP RENEW sent - Invalid DHCP option
2012-05-18 17:56:47 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-18 17:56:45 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-18 17:56:37 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-18 17:56:33 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-18 17:56:15 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-18 17:56:13 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-18 17:55:39 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-05-18 17:55:37 6-Notice M571.4 Ethernet link dormant - not currently active
2012-05-18 17:48:13 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:23 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:00:07 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-04-13 11:53:26 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:31 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:00:28 3-Critical D001.0 DHCP FAILED - Discover sent, no offer
received
1970-01-01 00:00:07 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-02-28 19:44:46 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:23 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:00:10 3-Critical R002.0 No Ranging Response received - T3 time-out
(US 2)
1970-01-01 00:00:07 6-Notice M571.4 Ethernet link dormant - not currently active
2012-02-22 10:02:57 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:20 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:00:07 6-Notice M571.1 Ethernet link up - ready to pass packets
2012-02-18 12:00:35 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:27 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:00:15 3-Critical R002.0 No Ranging Response received - T3 time-out
(US 2)
1970-01-01 00:00:07 6-Notice M571.4 Ethernet link dormant - not currently active
2012-02-14 13:18:16 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:20 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:00:07 6-Notice M571.4 Ethernet link dormant - not currently active
2012-02-14 12:50:11 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:20 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:00:07 6-Notice M571.4 Ethernet link dormant - not currently active
2011-10-25 06:34:08 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:00:22 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:00:11 3-Critical R002.0 No Ranging Response received - T3 time-out
(US 2)
1970-01-01 00:00:07 6-Notice M571.4 Ethernet link dormant - not currently active
2011-10-25 01:44:37 6-Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:11:59 3-Critical D003.0 DHCP FAILED - Requested Info not
supported.
1970-01-01 00:11:55 3-Critical D001.0 DHCP FAILED - Discover sent, no offer
received
1970-01-01 00:11:43 3-Critical R002.0 No Ranging Response received - T3 time-out
(US 2)
1970-01-01 00:11:30 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:11:04 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:11:04 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:10:35 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:10:34 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:09:59 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:09:58 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:09:35 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:09:35 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:09:13 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:09:12 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:09:02 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:09:01 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:08:52 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:08:51 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:08:49 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:08:48 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:08:45 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:08:45 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:08:39 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:08:38 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:08:33 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:08:32 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:08:30 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:08:30 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:08:18 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:08:17 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:07:50 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:07:50 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:07:25 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:07:24 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:07:23 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:07:22 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:55 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:06:54 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:08 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:06:08 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:06:00 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:06:00 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:05:25 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:05:24 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:05:06 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:05:05 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:42 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:04:41 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:39 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:04:38 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:37 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:04:36 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:29 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:04:29 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:23 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:04:23 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:21 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:04:20 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:17 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
1970-01-01 00:03:16 3-Critical T001.0 SYNC Timing Synchronization failure -
Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:50 3-Critical T002.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing

How do your U/S and D/S power levels look?

sorry - I see you already have them in your post. They look fine. I'd suspect noise in the cable plant somewhere.

Hello BDNHSV,

Apparently these issues are simultaneously affecting my neighbors as well.

Any further insight on what it could be if these T3 events effect my neighbors at the same time ....bad Tap in the street or what else can it be? Any other ideas appreciated.

JIm

It sounds like noise to me (impulse noise to be more precise). It can be caused by a myriad of things (a device in someone's home backfeeding into the cable plant, damaged lines allowing extra RF into the plant, bad equipment somewhere in the cable plant). It's something the cable co will have to find and correct. I'd call tech support get to tier 2 or 3 and have them look at your modem history in their CMTS - they should be able to see how many times it has flapped. Once they see that they should escalate the issue internally. It's not something the usual service tech with an RF meter will likely be able to see while at your house - to see it they'll likely have to use a spectrum analyzer at their headend.

Hello bdnhsv,

I have escalated to the CHSI field Lead in Orange County. He found large spikes going through upstream frequency at 28Mhz. When this happens loss of link between modem's and CMTS occur (T 3 errors in my logs).

Systems Operation Center and Plant Maintenance Dept engaged. I hope this can be resolved, not too far into the future

Thanks for your insight and help.

I'm sure they'll get it fixed. Have a great holiday weekend!

FYI.....within a day there was a truck in front of my neighbors house. Apparently a noisy device was there, and filtered out/fixed. I would be curious as to how they isolated which house it was so quickly. Ever since no more T3 errors, and things have been solid. This was the fastest time to resolution I have had at Cox. The saving grace this time is I saved some numbers/names from last escalation to skip the 10 service calls to get to this point. Otherwise I think they would have completely rewired my house, and replaced a cable modem (all unnecessarily as usual, by now). It felt good to get a problem solved fast!

Well it may be time to upgrade that modem of yours to a newer D3 model. But I will say, the modem logging T3's often are a sign of trouble on the upstream(return) path.

lilstone87, will a D3 model offer more rejection from noise issues like this in the future? I am not having performance concerns. I do not know why it would be time to upgrade it. Can you elaborate? Thanks.

Well if speed isn't a concern, then you can nvm the D3 modem. Was more of just mentioning if you plan to swap out the modem at some point. But with knowing how old the type of modem you have, you always have to wonder if the modem could be going bad. Because a bad modem could do many things. Still if the modem isn't the problem, the modem log points to an issue somewhere, appears to be an upstream issue. Still if things haven't been troubleshooted at the residents first, then that needs to be done. To make sure there isn't a wiring problem home side.

The problem was resolved per my earlier comment. All is good.

Well excuse me I was only looking over your first post, and thought it was still an issue. As the post were still adding up, but that is my fault for not reading threw .