Annoyedviewer's profile

Regular Visitor

 • 

6 Messages

Fri, Jan 1, 2021 6:00 PM

Motorola mb8600 and poor connection

I had some issues with my old arris surfboard dropping connections and as it didn't support higher speed I swapped it out for a Motorola mb8600. But now I'm seeing horrible speed no matter what line in my house I connect it with. I'm seeing reoccurring issues in the log and hoping someone can point me in the direction to make it work.


Time Priority Description
19:40:39
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:40:51
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:41:00
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 7 8 9 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:41:04
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:41:11
Fri Jan 1 2021 Warning (5) MDD message timeout;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:41:16
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:41:20
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:41:33
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 7 8 9 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:44:41
Fri Jan 1 2021 Warning (5) MDD message timeout;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:44:45
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:44:52
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:44:57
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 7 8 9 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:45:12
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:45:17
Fri Jan 1 2021 Warning (5) MDD message timeout;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:45:25
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:45:34
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:45:48
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 7 8 9 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:45:53
Fri Jan 1 2021 Warning (5) MDD message timeout;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:45:57
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:45:57
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 8 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:46:08
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:46:22
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 7 8 9 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:46:23
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:47:39
Fri Jan 1 2021 Warning (5) MDD message timeout;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:47:52
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:48:07
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 7 8 9 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:51:15
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:59:19
Fri Jan 1 2021 Warning (5) MDD message timeout;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:59:23
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 2; Chan ID: 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:59:28
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 8 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:59:39
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 4 5 6 7 8 9 10 11 12 16 17 35 36 39 45; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;
19:59:55
Fri Jan 1 2021 Notice (6) CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 7 8 9 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=00:40:36:73:7f:89;CMTS-MAC=00:01:5c:6f:5c:5c;CM-QOS=1.1;CM-VER=3.1;

Responses

EG

Expert

 • 

87.2K Messages

6 m ago

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


Regular Visitor

 • 

6 Messages

6 m ago

Here you go apologize for formatting is not pasting well

 

 Event Log

Connection

   Startup Sequence     

   Startup Step Status Comment 

 

  

   Acquire Downstream Channel 555000000 Hz Locked 

  

   Upstream Connection OK Operational 

  

   Boot State OK Operational 

 

  

   Configuration File OK  

  

   Security Enabled BPI+ 

  

 

 

   Connection Status     

   System Up Time 2 days 03h:19m:08s   

  

   Network Access Allowed   

  

 

 

   Downstream Bonded Channels    

  

   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected

   1 Locked QAM256 13 555.0 -23.9 29.4 627662 226079

   2 Locked QAM256 1 477.0 -23.9 29.7 889282 12883

   3 Locked QAM256 2 483.0 -24.4 29.2 2089733 18079

   4 Locked QAM256 3 489.0 -23.1 30.4 79213 7697

   5 Not Locked Unknown 4 495.0 -21.7 0.0 76701474 79279594

   6 Not Locked Unknown 5 507.0 -20.1 0.0 54733182 1255540

   7 Locked QAM256 6 513.0 -19.3 27.2 110006914 30931800

   8 Not Locked Unknown 7 519.0 -18.4 0.0 386823967 948676550

   9 Not Locked Unknown 8 525.0 -18.8 0.0 736839767 123155351

   10 Not Locked Unknown 9 531.0 -18.8 0.0 93228741 938036

   11 Not Locked QAM256 10 537.0 -19.8 0.0 3572879 4108837

   12 Locked QAM256 11 543.0 -21.1 27.3 45066486 8109591

   13 Locked QAM256 12 549.0 -22.5 29.3 2004986 2713673

   14 Locked QAM256 14 561.0 -25.0 28.5 9509124 2110235

   15 Locked QAM256 15 567.0 -25.4 27.6 63633860 81522

   16 Not Locked QAM256 16 573.0 -25.7 0.0 235368124 39499230

   17 Locked QAM256 17 579.0 -26.3 26.7 879847764 39254918

   18 Not Locked Unknown 18 585.0 -26.2 0.0 1378480649 568650009

   19 Not Locked Unknown 19 591.0 -26.2 0.0 47507081 60489231

   20 Locked OFDM PLC 33 722.0 -9.1 0.0 0 0

   21 Locked QAM256 34 453.0 -23.2 30.2 8871174 1389304

   22 Locked QAM256 35 459.0 -23.3 28.9 19802469 5091837

   23 Locked QAM256 36 465.0 -23.8 29.9 1759191 83700

   24 Locked QAM256 37 471.0 -23.2 30.3 265358 18399

   25 Locked QAM256 38 429.0 -21.6 31.9 1143332 26547

   26 Locked QAM256 39 435.0 -22.1 31.4 3883129 10330094

   27 Locked QAM256 40 441.0 -22.8 30.8 17089477 66199

   28 Locked QAM256 41 447.0 -23.6 30.0 10048964 2383990

   29 Locked QAM256 42 405.0 -18.2 34.5 35781 4400

   30 Locked QAM256 43 411.0 -19.2 33.6 54007 5375

  •    31 Locked QAM256 44 417.0 -20.3 32.8 91093 7141

   32 Locked QAM256 45 423.0 -21.0 32.3 46669 16574

EG

Expert

 • 

87.2K Messages

6 m ago

That's only the downstream stats, but they are WAY out of spec !!!

 

That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

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.

Regular Visitor

 • 

6 Messages

6 m ago

  Upstream Bonded Channels
 

 

 
 

 


  
   ChannelLock StatusChannel TypeChannel IDSymb. Rate (Ksym/sec)Freq. (MHz)Pwr (dBmV)
   1LockedSC-QAM6512035.655.8
   2LockedSC-QAM7512029.256.3
   3LockedSC-QAM8512022.855.5
   4LockedSC-QAM9512016.455.3
   5LockedSC-QAM10256040.454.8
EG

Expert

 • 

87.2K Messages

6 m ago

It's still way out of spec ! If there is nothing more that you can do, then as stated, you need to get a tech out to investigate / correct the problem.

 

Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home.
Good luck with it !

Official Employee

 • 

328 Messages

5 m ago

I'm sorry to hear this latency is impacting your online experience @Annoyedviewer. We can review your signal quality and help! Please click on my name and use the send message option to send us your name and service address so we can assist in greater detail. 

Regular Visitor

 • 

6 Messages

5 m ago

@EG Expert

I wanted to say thank you for your help.  You were more helpful than anyone from Xfinity and after the tech came out he confirmed a splitter upstream was water logged and fixed my problem, or at least did for a week before it got worse, but that's another story.  Thanks for your time.

EG

Expert

 • 

87.2K Messages

5 m ago

You are quite welcome but I am sorry to hear that you are still having problems.

New to the Community?

Start Here