Community Forum

Is my event log normal? This is just one day.

New Poster

Is my event log normal? This is just one day.

I currently have an SB6183 Modem.  In the past few weeks I have been having Xfinity consistently drop my signal.  I called Comcast today and other days.  Today Eve told me that I need to contact motorola for an update. My modem is from Arris and they state on thier website that only Comcast can do updates.  So where do I go from here?

 

I have included my event log for just today.  I pretty much looks the same for yesterday.

 

Sun Aug 25 06:46:45 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 06:46:45 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 06:46:45 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 06:47:17 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 06:47:17 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 06:47:17 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 06:53:57 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 06:53:57 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 06:53:57 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 07:35:13 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 07:39:33 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Aug 25 07:47:46 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 07:47:46 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 07:47:46 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 07:53:01 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 07:53:01 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 07:53:01 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:20:38 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:20:38 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:20:38 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:23:40 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:29:56 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:29:56 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:29:56 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:43:55 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:48:08 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:49:44 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:50:17 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:51:40 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 08:55:58 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:00:18 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:13:50 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:13:50 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:13:50 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:29:21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:36:39 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:38:35 2019 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 25 09:40:54 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:40:54 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:40:54 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 09:54:09 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 14:29:03 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 14:33:23 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 14:37:08 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Aug 25 14:41:28 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:9b:7e:ce;CMTS-MAC=00:01:5c:63:04:6b;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Is my event log normal? This is just one day.

Please also post the signal stat figures. Post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.




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!
New Poster

Re: Is my event log normal? This is just one day.

Is this what you are looking for?

 

 

Acquire Downstream Channel

  Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK  
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed  

 

 

 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 17 579000000 Hz -4.4 dBmV 38.2 dB 37 72
2 Locked QAM256 18 585000000 Hz -4.5 dBmV 38.2 dB 38 72
3 Locked QAM256 19 591000000 Hz -4.7 dBmV 38.1 dB 55 76
4 Locked QAM256 20 597000000 Hz -4.8 dBmV 38.2 dB 30 95
5 Locked QAM256 21 603000000 Hz -4.9 dBmV 38.2 dB 29 89
6 Locked QAM256 22 609000000 Hz -5.0 dBmV 38.2 dB 18 73
7 Locked QAM256 23 615000000 Hz -5.2 dBmV 38.2 dB 54 95
8 Locked QAM256 24 621000000 Hz -5.4 dBmV 38.1 dB 26 93
9 Locked QAM256 25 627000000 Hz -6.0 dBmV 37.9 dB 26 75
10 Locked QAM256 26 633000000 Hz -6.6 dBmV 37.6 dB 6 70
11 Locked QAM256 27 639000000 Hz -6.9 dBmV 37.3 dB 12 73
12 Locked QAM256 28 645000000 Hz -4.8 dBmV 38.2 dB 44 31
13 Locked QAM256 29 651000000 Hz -4.6 dBmV 38.2 dB 41 73
14 Locked QAM256 30 657000000 Hz -5.1 dBmV 37.9 dB 11 73
15 Locked QAM256 31 663000000 Hz -5.7 dBmV 37.6 dB 33 28
16 Locked QAM256 32 669000000 Hz -6.5 dBmV 37.2 dB 48 104

 

 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 17 5120 Ksym/sec 34900000 Hz 41.5 dBmV
2 Locked ATDMA 18 5120 Ksym/sec 28500000 Hz 41.5 dBmV
3 Locked ATDMA 19 5120 Ksym/sec 22100000 Hz 41.5 dBmV
4 Locked ATDMA 20 5120 Ksym/sec 15700000 Hz 31.8 dBmV
Expert

Re: Is my event log normal? This is just one day.

Yes. Not certain that this is the root of the problem, but the downstream power is on the weak side and it may be intermittently fluctuating even lower to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, and latency problems.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct. Good luck !



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!