dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1143
share rss forum feed


Dinosauro

@cox.net

1 edit

[LA] [LA] Recurring nightly modem T4 timeouts

Baton Rouge, LA 70808

For about the last two weeks I've been having nightly disconnects with the following repeating entries in the CM log. The modem will continually cycle through these, periodically coming back online then rebooting due to T4 timeout. I can, sometimes, fix this with a manual reboot, but if left alone, it will continue to cycle through the same process. I attempted to see if this was an isolated issue, or more widespread, but the rep I spoke to on the phone was unable to provide me with any info other than "your signal levels look good" and would/could not put in a ticket with the next tier to check the CMTS. Resultant from this I purchased a new SB6141, but the problem persists. I would appreciate any help on the matter

Here are the logs from the modem:

Oct 04 2012 09:19:03 5-Warning T07.0 RCS Partial Service;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Oct 04 2012 09:19:01 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Oct 04 2012 09:19:01 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:27 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 4-Error T201.0 Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Signal Levels:

Power Level
-3 dBmV -4 dBmV -5 dBmV -5 dBmV
Upstream Bonding Channel Value
Channel ID 1 2 3 4
Frequency 37600000 Hz 31200000 Hz 25400000 Hz 22200000 Hz
Ranging Service ID 6722 6722 6722 6722
Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec
Power Level 45 dBmV 45 dBmV 43 dBmV 42 dBmV



Dinosauro

@cox.net

Nuts, I left one of the CM MACs in there....



No_Strings
Premium,MVM,Ex-Mod 2008-13
join:2001-11-22
The OC
kudos:6

I see nothing.



Dinosauro

@cox.net

Thank you sir.



Dinosauro

@cox.net
reply to Dinosauro

Now a T3 timeout as well:

Oct 05 2012 00:19:24 5-Warning T07.0 RCS Partial Service;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Oct 05 2012 00:19:23 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Oct 05 2012 00:19:23 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:29 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 4-Error T201.0 Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 05 2012 00:18:37 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxx;CMTS-MAC=64:00:f1:40:14:75;CM-QOS=1.1;CM-VER=3.0;


SlashG42

join:2002-02-13
Metairie, LA
Reviews:
·Cox HSI
·AT&T Southeast
reply to Dinosauro

Look through these forums, specifically Cox LA. T3/T4 timeouts are a recurring topic. Every time, it is "Your signal levels look good." Customer buys a new modem, problem persists with no solution. I've been dealing with this since March. Cox won't fix it since they know the only other game in town is AT&T with slow DSL.

You can change isp's and maybe get more stability, but Cox isn't interested in addressing a system-wide issue to keep the couple dozen customers who notice their computer's apparent poor performance is being caused by cox's poorly maintained/configured network.


lilstone87

join:2009-04-09
Portsmouth, VA
kudos:3
Reviews:
·Cox HSI

Sounds like the dreaded upstream noise problem, that can be just a pain in the ass. When it is happening on, and off, which makes it hard to track down, and correct whatever the source of the problem is. Trust me I feel for you guys dealing with these T3/T4's timeout's, I have dealt with the same kind of issue on, and off for a while. You really just hope the problem stays to a minimum sadly.