Highlighted
Observer

T3 timeouts several times a day.

SB6183
 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel Locked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+
DOCSIS Network Access EnabledAllowed 

 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1LockedQAM2567501000000 Hz9.2 dBmV43.4 dB7328
2LockedQAM2562471000000 Hz9.9 dBmV44.1 dB9330
3LockedQAM2563477000000 Hz9.7 dBmV43.9 dB7628
4LockedQAM2564483000000 Hz9.6 dBmV43.8 dB9237
5LockedQAM2565489000000 Hz9.5 dBmV43.6 dB6732
6LockedQAM2566495000000 Hz9.4 dBmV43.7 dB6336
7LockedQAM2561465000000 Hz10.1 dBmV44.2 dB6928
8LockedQAM2568507000000 Hz8.9 dBmV41.8 dB6269
9LockedQAM2569513000000 Hz8.8 dBmV42.8 dB5446
10LockedQAM25610519000000 Hz8.5 dBmV42.2 dB5532
11LockedQAM25611525000000 Hz8.6 dBmV42.6 dB4848
12LockedQAM25612531000000 Hz8.4 dBmV42.5 dB3170
13LockedQAM25613537000000 Hz8.1 dBmV42.1 dB5050
14LockedQAM25614543000000 Hz8.0 dBmV41.9 dB4355
15LockedQAM25615549000000 Hz7.9 dBmV41.8 dB7976
16LockedQAM25616555000000 Hz7.6 dBmV41.3 dB8532

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA25120 Ksym/sec23900000 Hz42.0 dBmV
2LockedTDMA12560 Ksym/sec19000000 Hz40.0 dBmV
3LockedATDMA35120 Ksym/sec30400000 Hz42.8 dBmV
4LockedATDMA45120 Ksym/sec36900000 Hz43.3 dBmV

Current System Time: Wed May 17 19:15:52 2017

 
Wed May 17 17:40:53 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:28:39 2017Notice (6)TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:28:39 2017Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:28:39 2017Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:28:25 2017Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Wed May 17 17:28:16 2017Notice (6)TLV-11 - unrecognized OID;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:28:16 2017Notice (6)Provisioning Mode Changed - Reinitialize MAC...
Wed May 17 17:28:15 2017Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:28:15 2017Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedWarning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.0;CM-VER=3.0;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv4
Wed May 17 17:27:34 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:27:02 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:13:49 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:13:16 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:05:41 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 17:05:08 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 16:53:43 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 16:53:10 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 13:08:12 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 13:07:39 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 11:25:49 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Wed May 17 11:25:16 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Tue May 16 21:03:20 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Tue May 16 21:02:48 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Tue May 16 20:12:52 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Tue May 16 20:12:19 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Mon May 15 18:10:10 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Mon May 15 18:09:38 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Mon May 15 17:54:20 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Mon May 15 17:53:48 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Mon May 15 17:48:41 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Mon May 15 17:48:09 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Mon May 15 12:43:45 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Mon May 15 12:43:12 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 18:56:38 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 18:56:05 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 18:26:41 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 18:26:08 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 17:56:05 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 17:55:33 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 17:40:37 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 17:40:05 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 15:09:37 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 15:09:04 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 14:47:50 2017Critical (3)Resetting the cable modem due to docsDevResetNow
Sun May 14 14:44:24 2017Critical (3)Resetting the cable modem due to docsDevResetNow
Sun May 14 13:35:02 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 13:34:29 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 10:58:11 2017Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sun May 14 10:57:38 2017Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:ed:4a:cc;CMTS-MAC=00:17:10:86:c4:16;CM-QOS=1.1;CM-VER=3.0;
Sat May 13 18:01:42 2017
12 REPLIES
Expert

Re: T3 timeouts several times a day.

points to some sort of upstream issue with noise. Your DS levels are a little high as well- possibly what's causing the correcteds and uncorrecteds. modem needs probably 3-5 dB of attenuation or a 50' piece of cable added.

Something might be corroded or loose, 

 

This line is odd:

 Provisioning Mode Changed - Reinitialize MAC...

Were you on the phone with them?

 

Observer

Re: T3 timeouts several times a day.

I was not on the phone with them.  It does that quite often.

Expert

Re: T3 timeouts several times a day.

What is it, a 6190?

Provisioning should never change unless you change speeds by calling TWC/Spectrum up.

 

Observer

Re: T3 timeouts several times a day.

SB6183

Observer

Re: T3 timeouts several times a day.

I just went and to the troubleshoot modem page and it says its not connected.  But I am typing this using the modem.  LOL.

Expert

Re: T3 timeouts several times a day.

go to the help tab.. What firmware does it have? 2016?

 

Observer

Re: T3 timeouts several times a day.

Software Version D30CM-OSPREY-1.5.2.3-GA-01-NOSH
Spectrum Employee

Re: T3 timeouts several times a day.

Ok so after looking at this for a few moments I really advise you to get a tech out.

 

first, the signals are too high. Your pushing 8-10db on every downstream and those need to come down. Target is 0 and anything inside about +\- 10 is good but at the high end your starting to get out of range. When you are at the top end, you start getting pushed out and the signal deteriorates due to something as simple as the temperature changing or water getting into the system and fluctuations will occur.

 

also, you are getting uncorrected and corrected errros on every channel. This is most likely some sort of signal error or bad fitting in the network that needs to be addressed.

 

that error can be in the house wiring or in the network, and it needs to be found because t3 errors are essentially the modem detecting a problem and attempting a reset to reestablish good service.

I post on my off hours, away from work and any statements made are my opinions, and do not necessarily reflect the views and beliefs of Spectrum Communications.

Observer

Re: T3 timeouts several times a day.

Getting someone out here to actually fix anything would be a miracle.  I ask my neighbors and they had these same issues a few years ago.  TWC would never fix it so they just moved to over to AT&T.  Two techs have been out but they don't really do anything.

 

I've ran experiments where everything was unplugged except the cable modem and still got the same issues.  As soon as they learn its a customer owned modem they just start making excuses.  However, as far as I know,  no one has been up on the pole to make sure its not one of those TV filter trap issues.