Skip to main content

  • Home

  • Getting Started

  • Guidelines

sinan72's profile
sinan72
Conversation Starter
1st Like
1st Reply

Frequent Visitor

 • 

14 Messages

Friday, June 19th, 2020 5:00 PM

Closed

Many service interruption every day

Hi, I have many many service interruption since switching from WOW to Xfinity for better service, Unfortunately, I thought Xinfinity will be better > below you can find the log problem for one day only and there are many uncorrected packets. 

 

I lost the connection several times today. 

 

Downstream Bonded Channels
 

 

  
 

 


  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 17 531.0 5.1 39.9 4223 1091
2 Locked QAM256 18 537.0 5.4 39.4 3651 911
3 Locked QAM256 19 543.0 5.0 39.3 3976 977
4 Locked QAM256 20 549.0 5.2 38.5 3587 888
5 Locked QAM256 21 555.0 5.3 39.4 4105 911
6 Locked QAM256 22 561.0 5.3 39.7 3064 1032
7 Locked QAM256 23 567.0 5.1 39.9 3178 954
8 Locked QAM256 24 573.0 4.9 39.5 2984 979
Total             28768 7743

 

 Fri Jun 19 11:27:37 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 11:27:37 2020    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 11:29:47 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 11:30:01 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.0;CM-VER=3.0; 
 Fri Jun 19 11:30:08 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.0;CM-VER=3.0; 
 Fri Jun 19 11:30:14 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Fri Jun 19 11:30:58 2020    Warning (5)   Unicast DSID PSN startup error 
 Fri Jun 19 17:56:05 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 17:57:00 2020    Critical (3)   Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 17:57:13 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 17:57:13 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 17:57:21 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 17:59:31 2020    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jun 19 17:59:47 2020    Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.0;CM-VER=3.0; 
 Fri Jun 19 17:59:54 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.0;CM-VER=3.0; 
 Fri Jun 19 17:59:59 2020    Notice (6)   Honoring MDD; IP provisioning mode = IPv6 
 Fri Jun 19 18:55:34 2020    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 

Question

 • 

Updated 

4 years ago

1.4K

12

0

0

This conversation is no longer open for comments or replies and is no longer visible to community members.

EG

Expert

 • 

103.5K Messages

4 years ago

The downstream is in spec. What does the upstream power look like ?

0

0

sinan72

Frequent Visitor

 • 

14 Messages

4 years ago

Thank you EG for your reply, I just want to tell you that the technician came to my house and change the coaxial cable with a new one from the pole to the house and they changed all the old connections also ( I don't have any splitter connected to the line ), maybe this information will help. 

0

0

EG

Expert

 • 

103.5K Messages

4 years ago

O/k. Please send that private message to .@ComcastMorgan.

0

0

sinan72

Frequent Visitor

 • 

14 Messages

4 years ago

Another service interruption   

 

Mon Jun 22 11:06:24 2020 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 11:08:39 2020 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
     
Mon Jun 22 11:11:28 2020 6 TLV-11 - unrecognized OID;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;

 

 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked 256QAM 37 651.00 MHz 5.40 dBmV 37.36 dB 302 3030
2 Locked 256QAM 9 477.00 MHz 5.20 dBmV 38.98 dB 21 96
3 Locked 256QAM 10 483.00 MHz 5.20 dBmV 38.61 dB 30 86
4 Locked 256QAM 11 489.00 MHz 4.90 dBmV 37.36 dB 42 87
5 Locked 256QAM 12 495.00 MHz 4.70 dBmV 38.98 dB 88 1163
6 Locked 256QAM 13 507.00 MHz 4.40 dBmV 37.36 dB 129 1113
7 Locked 256QAM 14 513.00 MHz 4.60 dBmV 36.61 dB 23 91
8 Locked 256QAM 15 519.00 MHz 4.70 dBmV 37.64 dB 38 101
9 Locked 256QAM 16 525.00 MHz 4.40 dBmV 38.26 dB 26 97
10 Locked 256QAM 17 531.00 MHz 4.30 dBmV 37.36 dB 300 2174
11 Locked 256QAM 18 537.00 MHz 4.60 dBmV 37.36 dB 160 1186
12 Locked 256QAM 19 543.00 MHz 4.30 dBmV 37.36 dB 31 98
13 Locked 256QAM 20 549.00 MHz 4.20 dBmV 36.39 dB 21 101
14 Locked 256QAM 21 555.00 MHz 4.30 dBmV 37.36 dB 508 744
15 Locked 256QAM 22 561.00 MHz 4.20 dBmV 37.64 dB 145 994
16 Locked 256QAM 23 567.00 MHz 4.10 dBmV 37.64 dB 20 89
17 Locked 256QAM 24 573.00 MHz 3.80 dBmV 37.36 dB 111 1159
18 Locked 256QAM 25 579.00 MHz 3.90 dBmV 36.39 dB 169 1133
19 Locked 256QAM 26 585.00 MHz 4.10 dBmV 36.61 dB 113 961
20 Locked 256QAM 27 591.00 MHz 4.20 dBmV 37.36 dB 245 834
21 Locked 256QAM 28 597.00 MHz 4.40 dBmV 37.64 dB 143 1143
22 Locked 256QAM 29 603.00 MHz 4.40 dBmV 37.64 dB 293 1979
23 Locked 256QAM 30 609.00 MHz 4.70 dBmV 37.36 dB 206 2141
24 Locked 256QAM 31 615.00 MHz 4.90 dBmV 37.36 dB 122 978
25 Locked 256QAM 32 621.00 MHz 4.90 dBmV 37.60 dB 18 712
26 Locked 256QAM 33 627.00 MHz 5.30 dBmV 37.60 dB 9 734
27 Locked 256QAM 34 633.00 MHz 5.30 dBmV 37.30 dB 13 638
28 Locked 256QAM 35 639.00 MHz 5.50 dBmV 37.30 dB 23 678
29 Locked 256QAM 36 645.00 MHz 5.30 dBmV 37.60 dB 16 636
30 Locked 256QAM 38 657.00 MHz 5.70 dBmV 37.30 dB 16 635
31 Locked 256QAM 39 663.00 MHz 5.50 dBmV 36.90 dB 9 640
32 Locked 256QAM 40 669.00 MHz 5.70 dBmV 37.30 dB 12 680

 

 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 kSym/s 35.80 MHz 46.00 dBmV
2 Locked ATDMA 4 5120 kSym/s 16.60 MHz 45.00 dBmV
3 Locked ATDMA 3 5120 kSym/s 23.00 MHz 45.00 dBmV
4 Locked ATDMA 2 5120 kSym/s 29.40 MHz 46.50 dBmV

0

0

EG

Expert

 • 

103.5K Messages

4 years ago

The upstream power is also in spec. 

Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.

 

There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.


I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.

0

0

CCMorgan

Gold Problem Solver

 • 

3.3K Messages

4 years ago

Hi there sinan72. Sorry to hear about the troubles you're experiencing with your connection. I would like to take a look at a few more diagnostics. To get started, please send me a PM with your first and last name. We will go from there. 

 

To send a private message, please click my name "ComcastMorgan" then select "Send a Message" on the right side.

 

Thanks. 🙂

0

sinan72

Frequent Visitor

 • 

14 Messages

4 years ago

Before 2 days I replaced the modem with a new one and I still facing the same problems, I think the problem from the top or from the node,  you can find below the modem reading for yesterday and today 

 

Event Log 

 

Time Priority Description
Sun Jun 21 00:27:12 2020 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 21 02:10:57 2020 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 01 00:01:43 1970 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 21 02:13:43 2020 6 TLV-11 - unrecognized OID;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 21 14:53:52 2020 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 10:17:05 2020 5 RCS Partial Service;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 10:17:06 2020 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 10:19:20 2020 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 01 00:01:47 1970 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 10:22:03 2020 6 TLV-11 - unrecognized OID;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;

 

 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked 256QAM 9 477.00 MHz 7.40 dBmV 38.98 dB 10 0
2 Locked 256QAM 1 429.00 MHz 6.90 dBmV 38.98 dB 0 0
3 Locked 256QAM 2 435.00 MHz 7.00 dBmV 38.98 dB 13 0
4 Locked 256QAM 3 441.00 MHz 7.40 dBmV 38.98 dB 0 0
5 Locked 256QAM 4 447.00 MHz 7.30 dBmV 38.61 dB 0 0
6 Locked 256QAM 5 453.00 MHz 7.60 dBmV 38.61 dB 0 0
7 Locked 256QAM 6 459.00 MHz 7.60 dBmV 38.61 dB 0 0
8 Locked 256QAM 7 465.00 MHz 7.60 dBmV 38.61 dB 0 0
9 Locked 256QAM 8 471.00 MHz 7.40 dBmV 38.61 dB 12 0
10 Locked 256QAM 10 483.00 MHz 7.20 dBmV 38.61 dB 1 0
11 Locked 256QAM 11 489.00 MHz 6.90 dBmV 37.64 dB 7 0
12 Locked 256QAM 12 495.00 MHz 6.70 dBmV 38.61 dB 10 0
13 Locked 256QAM 13 507.00 MHz 6.40 dBmV 37.64 dB 0 0
14 Locked 256QAM 14 513.00 MHz 6.60 dBmV 37.64 dB 0 0
15 Locked 256QAM 15 519.00 MHz 6.70 dBmV 37.64 dB 6 0
16 Locked 256QAM 16 525.00 MHz 6.50 dBmV 38.61 dB 17 0
17 Locked 256QAM 17 531.00 MHz 6.40 dBmV 37.64 dB 13 0
18 Locked 256QAM 18 537.00 MHz 6.50 dBmV 37.64 dB 2 0
19 Locked 256QAM 19 543.00 MHz 6.30 dBmV 37.36 dB 0 0
20 Locked 256QAM 20 549.00 MHz 6.30 dBmV 36.61 dB 2 0
21 Locked 256QAM 21 555.00 MHz 6.30 dBmV 37.64 dB 0 0
22 Locked 256QAM 22 561.00 MHz 6.00 dBmV 37.36 dB 0 0
23 Locked 256QAM 23 567.00 MHz 6.00 dBmV 37.64 dB 1 0
24 Locked 256QAM 24 573.00 MHz 5.70 dBmV 37.36 dB 5 0
25 Locked 256QAM 25 579.00 MHz 5.80 dBmV 36.40 dB 2 0
26 Locked 256QAM 26 585.00 MHz 5.80 dBmV 36.90 dB 2 0
27 Locked 256QAM 27 591.00 MHz 6.10 dBmV 38.20 dB 1 0
28 Locked 256QAM 28 597.00 MHz 6.20 dBmV 37.60 dB 0 0
29 Locked 256QAM 29 603.00 MHz 6.10 dBmV 37.90 dB 0 0
30 Locked 256QAM 30 609.00 MHz 6.40 dBmV 37.60 dB 4 0
31 Locked 256QAM 31 615.00 MHz 6.60 dBmV 37.60 dB 6 0
32 Locked 256QAM 32 621.00 MHz 6.60 dBmV 37.60 dB 1 0

 

 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 kSym/s 35.80 MHz 44.00 dBmV
2 Locked ATDMA 4 5120 kSym/s 16.60 MHz 43.50 dBmV
3 Locked ATDMA 3 5120 kSym/s 23.00 MHz 43.50 dBmV
4 Locked ATDMA 2 5120 kSym/s 29.40 MHz 43.50 dBmV

0

0

sinan72

Frequent Visitor

 • 

14 Messages

4 years ago

I sent the PM 

0

0

sinan72

Frequent Visitor

 • 

14 Messages

4 years ago

Again, many interruptions today, I am really  thinking to return back to WOW 

Time Priority Description
Mon Jun 22 14:40:58 2020 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 19:39:35 2020 4 Service Change Response rejected - Invalid transaction ID;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 19:43:01 2020 5 RCS Partial Service;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 19:43:10 2020 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 20:00:09 2020 3 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 20:00:09 2020 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 20:01:58 2020 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 01 00:01:46 1970 3 No Ranging Response received - T3 time-out;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 20:04:43 2020 6 TLV-11 - unrecognized OID;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 22 20:25:12 2020 5 RCS Partial Service;CM-MAC=70:54:25:46:6d:e9;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0;

 

 

0

0

sinan72

Frequent Visitor

 • 

14 Messages

4 years ago

Today I return back to wow with the highest speed there is no problem with service till now, all event log empty no uncorrected pockets. 👍

 

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked 256QAM 13 651.00 MHz 7.00 dBmV 38.61 dB 6 0
2 Locked 256QAM 12 561.00 MHz 8.10 dBmV 38.61 dB 7 0
3 Locked 256QAM 11 567.00 MHz 7.90 dBmV 38.98 dB 0 0
4 Locked 256QAM 10 573.00 MHz 7.90 dBmV 38.61 dB 0 0
5 Locked 256QAM 9 579.00 MHz 7.90 dBmV 38.98 dB 0 0
6 Locked 256QAM 8 585.00 MHz 7.40 dBmV 38.61 dB 0 0
7 Locked 256QAM 7 591.00 MHz 7.70 dBmV 38.98 dB 0 0
8 Locked 256QAM 6 597.00 MHz 7.60 dBmV 38.61 dB 0 0
9 Locked 256QAM 5 603.00 MHz 7.40 dBmV 38.98 dB 0 0
10 Locked 256QAM 1 609.00 MHz 7.60 dBmV 38.98 dB 0 0
11 Locked 256QAM 2 615.00 MHz 7.40 dBmV 38.61 dB 0 0
12 Locked 256QAM 3 621.00 MHz 7.40 dBmV 38.98 dB 0 0
13 Locked 256QAM 4 627.00 MHz 7.20 dBmV 38.61 dB 0 0
14 Locked 256QAM 30 633.00 MHz 7.30 dBmV 38.61 dB 0 0
15 Locked 256QAM 31 639.00 MHz 7.30 dBmV 38.61 dB 0 0
16 Locked 256QAM 32 645.00 MHz 6.80 dBmV 38.61 dB 0 0
17 Locked 256QAM 14 657.00 MHz 6.40 dBmV 38.61 dB 0 0
18 Locked 256QAM 15 663.00 MHz 6.60 dBmV 38.61 dB 0 0
19 Locked 256QAM 16 669.00 MHz 6.80 dBmV 38.61 dB 0 0
20 Locked 256QAM 17 681.00 MHz 6.60 dBmV 37.64 dB 0 0
21 Locked 256QAM 18 687.00 MHz 6.90 dBmV 38.98 dB 0 0
22 Locked 256QAM 19 693.00 MHz 7.00 dBmV 38.26 dB 0 0
23 Locked 256QAM 20 699.00 MHz 7.20 dBmV 38.61 dB 0 0
24 Locked 256QAM 21 705.00 MHz 7.40 dBmV 38.61 dB 0 0
25 Locked 256QAM 22 711.00 MHz 7.50 dBmV 38.60 dB 0 0
26 Locked 256QAM 23 717.00 MHz 7.60 dBmV 38.60 dB 0 0
27 Locked 256QAM 24 723.00 MHz 7.30 dBmV 38.60 dB 0 0
28 Locked 256QAM 25 729.00 MHz 7.50 dBmV 38.60 dB 0 0
29 Locked 256QAM 26 735.00 MHz 7.10 dBmV 37.30 dB 0 0
30 Locked 256QAM 27 741.00 MHz 7.40 dBmV 38.20 dB 0 0
31 Locked 256QAM 28 747.00 MHz 6.90 dBmV 38.20 dB 8 0

 

Event Log

The table below contains the log of events that the SB6190 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

Time Priority Description
CM Events List Empty

0

idolgov

Frequent Visitor

 • 

9 Messages

4 years ago

So, what could have changed to get you back on track?

0

0

sinan72

Frequent Visitor

 • 

14 Messages

4 years ago

Hi, I faced service interruptions for 2 times from WOW service before switching to comcast , that's happend when them fiberoptic has cut through when there was some construction work beside I-75 ,so I decied to switch to comcast , I keept my service with comcast to use it as backup internet , today I bought 2 WAN input router and connect the both ISP provider to my new router , unfortuntly the comcast problem still excist , all comcast technicians aunable to address the problem and you can find the Event Log for today .

 

I saw couple vedio in youtube showing that the technicians using many type of testing meters to address , which is not available with comcast technician 

 

 

 

Event Log
   Log
 

 

 
 

 


  
 Time  Priority  Description 
 Mon Sep 21 19:04:30 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:25:10 2020   Warning (5)  Dynamic Range Window violation 
 Mon Sep 21 19:26:12 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:26:12 2020   Warning (5)  Dynamic Range Window violation 
 Mon Sep 21 19:27:13 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:27:13 2020   Warning (5)  Dynamic Range Window violation 
 Mon Sep 21 19:30:01 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:30:01 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:30:28 2020   Warning (5)  Dynamic Range Window violation 
 Mon Sep 21 19:31:06 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:33:21 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:33:21 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:35:31 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:35:46 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.0;CM-VER=3.0; 
 Mon Sep 21 19:35:51 2020   Notice (6)  Honoring MDD; IP provisioning mode = IPv6 
 Mon Sep 21 19:36:06 2020   Critical (3)  REG RSP not received;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:40:07 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:40:07 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:42:19 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:42:38 2020   Notice (6)  Honoring MDD; IP provisioning mode = IPv6 
 Mon Sep 21 19:42:52 2020   Critical (3)  REG RSP not received;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:47:34 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:52:32 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:52:45 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:53:01 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:53:05 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:53:12 2020   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:53:32 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:55:42 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 
 Mon Sep 21 19:55:56 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.0;CM-VER=3.0; 
 Mon Sep 21 19:56:02 2020   Notice (6)  Honoring MDD; IP provisioning mode = IPv6 
 Mon Sep 21 19:56:16 2020   Critical (3)  REG RSP not received;CM-MAC=00:40:36:44:5d:92;CMTS-MAC=04:2a:e2:c6:cc:ef;CM-QOS=1.1;CM-VER=3.0; 

0

0

forum icon

New to the Community?

Start Here