dslreports logo
 
    All Forums Hot Topics Gallery
spc

spacer

Search Topic:
uniqs
5194
share rss forum feed

r8er4ever

join:2011-04-02

SMC3GN

Can someone tell me if these readings are ok? I keep getting disconnects and really slow internet issue's. Also am wondering if the fact that I have 2 Ethernet connections for Direct-TV video on demand plugged into the router if that's the issue. But not definite cause these were not present on the old G band router.
HISTORY
PROBLEM -->REPAIR
Old G band router same issue-->Got N band router
Thought maybe net card issue-->Got 2 new net cards
Thought maybe computer issue-->Got 2 new computer's
Thought maybe Bandwidth issue-->Increased 8 -->15 megs

Downstream Channel ID 0 1 2 3
Downstream Frequency 699.000000 MHz 693.000000 MHz
705.000000 MHz 711.000000 MHz
Lock Status Locked Locked Locked Locked
Modulation 256 QAM 256 QAM 256 QAM 256 QAM
Symbol Rate 5.360537Msym/sec 5.360537Msym/sec 5.360537Msym/sec 5.360537Msym/sec
Downstream Power -1.911771 dBmV -1.699815 dBmV -2.370104 dBmV -3.155623 dBmV
SNR 37.935909 dB 37.935909 dB 38.257755 dB 37.935909 dB

Upstream Channel ID 0 1 2 3
Upstream Frequency 32496000 Hz
Lock Status Locked Not locked Not locked Not locked
Modulation 64QAM
Symbol Rate 2560 sym/sec
Upstream Power 41.0000 dBmV
Channel ID 3

Cable Modem System Event Log

Time:03/22/11 05:10:07, Level:warning, Content:Lost MDD Timeout;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:10:31, Level:warning, Content:MDD message timeout;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:10:31, Level:warning, Content:Lost MDD Timeout;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:10:35, Level:critical, Content:SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:13:56, Level:critical, Content:No Ranging Response received - T3 time-out;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:14:50, Level:critical, Content:Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:15:04, Level:critical, Content:SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:15:07, Level:warning, Content:Lost MDD Timeout;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:20:06, Level:critical, Content:No Ranging Response received - T3 time-out;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:22:12, Level:critical, Content:DHCP FAILED - Discover sent, no offer received;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:22:37, Level:critical, Content:No Ranging Response received - T3 time-out;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:25:03, Level:critical, Content:DHCP FAILED - Discover sent, no offer received;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:25:50, Level:critical, Content:No Ranging Response received - T3 time-out;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/22/11 05:27:57, Level:critical, Content:DHCP FAILED - Discover sent, no offer received;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:01/01/70 00:00:02, Level:warning, Content:ToD request sent - No Response received;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/28/11 05:48:45, Level:critical, Content:No Ranging Response received - T3 time-out;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:01/01/70 00:00:01, Level:warning, Content:ToD request sent - No Response received;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:03/29/11 10:57:39, Level:critical, Content:No Ranging Response received - T3 time-out;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:01/01/70 00:00:02, Level:warning, Content:ToD request sent - No Response received;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;
Time:04/02/11 17:27:08, Level:critical, Content:No Ranging Response received - T3 time-out;CM-MAC=00:26:f3:18:3b:55;CMTS-MAC=00:13:5f:04:b9:a8;CM-QOS=1.1;CM-VER=3.0;

r8er4ever

join:2011-04-02
Just a update had the Charter Cable tech out here once again. He found a couple slightly lose connections outside the house, and swore that would fix it. Guess what still have the same intermitte issue. Also looking over the log I posted above, there is 3 dates I find rather strange (01/01/70) is that normal anyone know?

r8er4ever

join:2011-04-02
reply to r8er4ever
Had another tech( supposedly a field supervisor or so he claimed)out 04-09-11, he also tried using the "OOHHH, here it is this connection is lose"(keep in mind the tech only a couple days prior, went over every connection and torqued them...lol). So then he took reading at the drop, and the junction box(side of house), and then at the plug to back of router. And then started to explain that he was noticing some MINOR packet loss occurring. His fix-(and this really cracks me up) replaced the router. Now I'm a auto-mech not a electronics tech, but common sense tells me that if the input to something has issues replacing the item after the input isn't gonna solve the problem. But hey give the guy credit cause it all was working fine till today 04-13-11. Woke up 6AM and no internet then slow then normal then ect ect ect...Same issue.On the phone again, this time (and I hadn't noticed this but up till now all the so-called tech's were actually sub-contractors...Learned today that only charter employee's drive vehicle's with the charter name on them. So no charter name on vehicle means not charter employee) anyways today got a real life charter tech to come check things and of course every thing was running fine when he showed up. But where I caught a break this time is that the tech today was also 1 of the tech's that had been here when we were having cable TV issue's, so he kinda knew that something isn't right somewhere. But his only option is that even tho he doubt's it is the issue. He is coming out next week to replace all the lines from the main drop to thru-out the entire house. That way he feels when the issue occurs again he can tell the maintance guy's without a doubt that it is a pole issue. So I guess this kinda explains the weird readings on the modem log and GOD!!!! I hope that maybe after the next week or so I will finally be getting the high-speed internet I have been paying for over the past couple years.


HFCNUT82

join:2007-12-13
reply to r8er4ever
Someone needs to start looking further back from a node or upstream perspective based on your logs.

The T3 indicates that the modem is not receiving a RNG-RSP from the CMTS and if its not receiving one, there is a good chance the CMTS is not receiving the modems RNG-REQ when it solicits its SID during the station maintenance interval. If this is happening, the CMTS should a good amount of misses and flaps if its looked at. More than likely the issue is effecting the feeder segment or whole node itself.

The MDD indicates that the modem is actually dropping the MAC Domain Descriptor used in DOCSIS 3.0 channel bonding. Normally if the modem drops one or all of its non primary RF channels used in bonding it wont force it to reboot or reinitialize its MAC layer and they will be corrected during a RNG-RSP interval from the CMTS. In your case, the RF was bad enough for the CMTS to force the modem to reinitialize its MAC layer.(Reboot)

You need tech support or a local Charter tech to investigate the upstream port from the CMTS. They will need to investigate the flap counts, station maintenance exhaust & abort info.

Hope this helps


HFCNUT82

join:2007-12-13
reply to r8er4ever
Oh ya....the (01/01/70) date you see is because the device has no sync to a TOD (Time of Day) server.

Content:ToD request sent - No Response received

TOD is part of the modem registration process when obtaining its config file

If it has no TOD the device will have a fall back date...Iv seen different devices use different dates. The logic behind gets into UTC time stamps based on seconds from that date noted.

Its normal operation when trying to obtain TOD parameters so now worries


HFCNUT82

join:2007-12-13
reply to r8er4ever
r8er4ever, You ever get a resolution at all?

r8er4ever

join:2011-04-02
Sorry it took so long to get back, but since charters last visit all has been pretty good. He came out and replaced all the lines from the drop thru the house. And in the process found up the pole on the feed line in between the pole in my backyard and the pole 2 doors down in they're backyard, there is some sort of box that the drop originates from, well it not only had my drop to house but apparently when they replaced the drop long ago all they did was cut the old one and tie it up around the main cable(so this box had a cable to my house and about 10ft unshielded open ended old piece of cable plugged together) so he was thinking it was working as like a 10ft antenna picking up all kinds of stray crap and feeding it into my line. Now he could be just feeding me a line of crap or not IDK but hell it's working great so I'm not going to argue...lol