Skip to main content

  • Home

  • Getting Started

  • Guidelines

U
user_6xyrxc
1st Topic
1st Like

1 Message

Saturday, May 11th, 2024 12:56 AM

Internet connect drops often at times for a couple of seconds.

This issue is really noticeable when making internet calls or gaming online. I am using a Motorola MG8702 and have attached screenshots of the event log and connections. The amount of errors and repeated code 16/24 does not seem right. This is present on both wireless and wired connections.


   Downstream Bonded Channels

 


  

   Channel

Lock Status

Modulation

Channel ID

Freq. (MHz)

Pwr (dBmV)

SNR (dB)

Corrected

Uncorrected

   1

Locked

QAM256

13

549.0

-4.9

41.8

1220

763

   2

Locked

QAM256

10

531.0

-4.7

41.9

1749

826

   3

Locked

QAM256

11

537.0

-4.8

41.9

1748

842

   4

Locked

QAM256

12

543.0

-4.8

41.9

1696

834

   5

Locked

QAM256

14

555.0

-4.7

41.8

608

781

   6

Locked

QAM256

15

579.0

-4.6

41.8

628

778

   7

Locked

QAM256

16

585.0

-4.8

41.7

1593

719

   8

Locked

QAM256

17

591.0

-5.1

41.5

4054

707

   9

Locked

QAM256

18

597.0

-5.1

41.5

6102

798

   10

Locked

QAM256

19

603.0

-5.2

41.0

8467

692

   11

Locked

QAM256

20

609.0

-5.2

41.6

9921

801

   12

Locked

QAM256

21

615.0

-5.3

41.6

12619

686

   13

Locked

QAM256

22

621.0

-5.3

41.3

14578

686

   14

Locked

QAM256

23

627.0

-5.4

41.4

13911

710

   15

Locked

QAM256

24

633.0

-5.4

41.3

11727

723

   16

Locked

QAM256

25

645.0

-5.5

41.3

20171

720

   17

Locked

QAM256

26

651.0

-5.9

41.0

56476

662

   18

Locked

QAM256

27

657.0

-6.0

40.8

108741

717

   19

Locked

QAM256

28

663.0

-6.1

40.8

230523

679

   20

Locked

QAM256

29

669.0

-6.2

40.9

374079

728

   21

Locked

QAM256

30

675.0

-6.3

40.1

781806

920

   22

Locked

QAM256

31

681.0

-6.1

40.9

1355400

1660

   23

Locked

QAM256

32

687.0

-5.8

41.1

1453450

2624

   24

Locked

QAM256

33

693.0

-5.5

41.3

10899737

193791

   25

Locked

QAM256

34

699.0

-5.4

41.3

67487410

4244989

   26

Locked

QAM256

35

705.0

-5.5

40.9

183038876

36697859

   27

Locked

QAM256

36

711.0

-5.8

41.0

751115975

242692840

   28

Locked

QAM256

37

717.0

-5.8

41.0

892306144

535024846

   29

Locked

QAM256

38

723.0

-5.9

41.0

1223359276

894600522

   30

Locked

QAM256

39

729.0

-5.9

40.8

1173162791

1026334244

   31

Locked

QAM256

40

735.0

-6.0

40.3

1290672169

1288262075

   32

Locked

OFDM PLC

41

762.0

-4.9

40.9

1716222139

367365015

 

  Upstream Bonded Channels

 


  

 

   Channel

Lock Status

Channel Type

Channel ID

Symb. Rate (Ksym/sec)

Freq. (MHz)

Pwr (dBmV)

   1

Locked

SC-QAM

1

5120

35.6

50.5

   2

Locked

SC-QAM

2

5120

29.2

50.3

   3

Locked

SC-QAM

3

5120

22.8

50.0

   4

Locked

SC-QAM

7

5120

16.4

50.0

   5

Locked

SC-QAM

9

2560

40.4

50.5

   Log

 


  

   

Time 

 

Priority 

 

Description 

   

18:45:56
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:47:30
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:49:04
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:49:25
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:50:02
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:50:33
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:50:57
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:51:26
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:52:38
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:53:38
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:53:48
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

18:54:15
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:26:45
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:27:11
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:39:55
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:40:41
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:45:18
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:45:41
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:46:40
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:47:16
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:48:32
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:49:16
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:49:18
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:49:56
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:50:05
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:51:00
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:51:07
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:51:14
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:51:48
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:51:55
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:51:55
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

   

19:54:07
Fri May 10 2024

 

Notice (6)

 

CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=[Edited: “Personal Information”];CMTS-MAC=[Edited: “Personal Information”];CM-QOS=1.1;CM-VER=3.1;

 

Question

 • 

Updated 

22 days ago

 • Edited

20

3

EG

Expert

 • 

103.9K Messages

25 days ago

@user_6xyrxc 

Please redact all of the CM MAC and the CMTS MAC addresses from your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publicly. It flagged your post as "Private".

That said. The upstream power is too high / marginal and it may be intermittently fluctuating even higher to out of spec levels. The downstream power is on the weak side as well. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are 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 from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

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 with it !

0

0

XfinityTony

Official Employee

 • 

639 Messages

23 days ago

@user_6xyrxc Thank you for the detailed post! How often are you seeing these drops in connection? Also, are they happening at a certain time, or is it random?

0

0

EG

Expert

 • 

103.9K Messages

22 days ago

@user_6xyrxc 

Have you had a chance to see if any of those tips that I gave you apply ?

0

0

forum icon

New to the Community?

Start Here