Community Forum

T3 time out; CM-MAC and MDD message timeout

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

New Poster

T3 time out; CM-MAC and MDD message timeout

Hello all,

Here is what I have going on. I recently moved my Netgear c6250 modem/router combo to another cable jack in my house. For over a week we didn’t have an issue. Then we started experiencing a drop of WiFi signal on both frequency bands. I reported to tech support who tried a host of things and found that there was a connection issue, and scheduled a tech to come out. Tech came out 2 days later and found a bad section of line from the pole to the first splitter (which looked to be the original time warner) and changed to a barrel connector. He shot the line all the way from the pole to the router, no issues, no noise. I had been working with Netgear whom said connection issue as well. I did a factory reset on the router and cleared the logs which can be seen in the screen shots from the modem as well as the cable connection information. I forwarded the shots to Netgear in hopes they can help as well in the event of a hardware issue.
7E6842F2-AAD7-46DA-A20B-3A766334F05A.jpeg
2694182F-D378-48B0-B909-71C6243B50B7.jpeg
Valued Contributor

Re: T3 time out; CM-MAC and MDD message timeout

T3 time outs are usually associated with ingress on the line.  I would guess your US SNR is probably dipping into the 20s with quite a few errors.  They might need to check out your return levels also, once you start getting up into the 50s you could start to see some problems if the signal fluctuates throughout the day.  

 

I have to question when you said they replaced part of the line since usually if part of a line is bad the entire piece should be replaced and not just barrel spliced together.  I would have them back to dig into it some more.

Expert

Re: T3 time out; CM-MAC and MDD message timeout

@AstrosFan1984

 

I've asked a Comcast employee to help you. You should expect a reply in this thread. 


I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Official Employee

Re: T3 time out; CM-MAC and MDD message timeout

Hello AstrosFan1984. I can assist with troubleshooting your internet connectivity issue. I'd like to start with polling the CMTS for real-time and historical RF signal reports from your modem. I can also check your local Node/Plant for any degradation or error reports. Please reach out to me via private message and include your full name and account primary phone number so I can access your equipment.


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
New Poster

Re: T3 time out; CM-MAC and MDD message timeout

Here is what has happened and where we are currently.

Tech #1: replaced section of cable from pole to back of detached garage, installed 2 barrel ground blocks instead of old splitters.

Tech #2: replaced 3rd section of cable from new ground block to inside home. Found knick in this cable and claimed this was the issue and that indoor cabling would have to be worked by an electrician as not supported by comcast.

Tech #3: Changed a -7db 3 way splitter in the attic, a "clear" barrel connector, which brought the signal on the upstream link down, but raised the downstream.  Installed 2 stacked attenuators to lower this down.

 

Here is the event log after I cleared it from tech #3:

 
 
 
 
Time Priority Description
2018-6-28, 17:24:02 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 17:24:03 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 19:46:06 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 19:46:06 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 19:54:52 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 19:54:52 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 20:17:20 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 20:17:20 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 21:26:56 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 21:26:56 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 21:39:45 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 21:39:45 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 22:20:49 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 22:20:49 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 22:28:15 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-28, 22:28:15 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 00:42:36 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 00:42:36 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 01:25:52 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 01:25:52 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 02:05:54 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 02:05:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 04:32:28 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 04:32:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 05:06:30 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 05:06:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 06:38:31 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 06:38:31 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 06:47:27 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 06:47:28 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 07:04:01 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 07:04:01 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 07:05:50 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 07:05:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 07:50:30 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 07:50:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 08:02:31 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 08:02:31 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 09:04:57 Warning (5) MDD message timeout;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
2018-6-29, 09:04:57 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c0:ff:d4:ea:4d:18;CMTS-MAC=00:01:5c:9d:d6:72;CM-QOS=1.1;CM-VER=3.0;
 
 
Here is the cable connection stats:
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 7 525000000 Hz 8.8 dBmV 39.3 dB 36 0
2 Locked QAM256 8 531000000 Hz 8.8 dBmV 39.2 dB 43 0
3 Locked QAM256 9 537000000 Hz 8.8 dBmV 39.2 dB 44 0
4 Locked QAM256 10 543000000 Hz 8.8 dBmV 39.2 dB 45 0
5 Locked QAM256 11 549000000 Hz 9 dBmV 39.2 dB 33 0
6 Locked QAM256 12 555000000 Hz 8.7 dBmV 39.1 dB 50 0
7 Locked QAM256 13 561000000 Hz 8.5 dBmV 39 dB 62 0
8 Locked QAM256 14 567000000 Hz 8.8 dBmV 39.1 dB 53 0
9 Locked QAM256 16 579000000 Hz 8.6 dBmV 39 dB 48 0
10 Locked QAM256 17 585000000 Hz 8.3 dBmV 38.7 dB 59 0
11 Locked QAM256 18 591000000 Hz 8.3 dBmV 38.8 dB 57 0
12 Locked QAM256 21 609000000 Hz 8.3 dBmV 38.8 dB 51 0
13 Locked QAM256 22 615000000 Hz 8.3 dBmV 38.8 dB 47 0
14 Locked QAM256 23 621000000 Hz 8.2 dBmV 38.7 dB 77 0
15 Locked QAM256 25 633000000 Hz 8.4 dBmV 38.7 dB 40 0
16 Locked QAM256 28 651000000 Hz 8.2 dBmV 38.6 dB 43 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 5 5120 Ksym/sec 36100000 Hz 41.5 dBmV
2 Locked ATDMA 6 5120 Ksym/sec 29600000 Hz 43.3 dBmV
3 Locked ATDMA 8 5120 Ksym/sec 16500000 Hz 44 dBmV
4 Locked ATDMA 7 5120 Ksym/sec 23000000 Hz 43 dBmV