Downstream Blue LED Light Blinking on Motorola MB8611 Impacting Download Speed

Hello,

The blue down arrow on my Motorola MB8611 has recently started blinking. When it happens my internet speed drops by 30-40%. If I power cycle the modem, the light stays up for a while and my speed improves until it starts blinking again.

Connection

Startup Sequence

Startup Step	Status	Comment
Acquire Downstream Channel	651000000 Hz	Locked
Upstream Connection	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+

Connection Status

System Up Time	0 days 13h:11m:19s
Network Access	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	44	651.0	4.9	39.8	12	59
2	Locked	QAM256	17	483.0	3.7	40.2	0	0
3	Locked	QAM256	18	489.0	3.8	40.1	0	0
4	Locked	QAM256	19	495.0	3.9	40.1	0	0
5	Locked	QAM256	20	507.0	4.1	39.8	0	0
6	Locked	QAM256	21	513.0	4.1	40.1	5	0
7	Locked	QAM256	22	519.0	4.1	40.1	28	0
8	Locked	QAM256	23	525.0	4.1	40.1	23	0
9	Locked	QAM256	24	531.0	3.8	39.9	25	0
10	Locked	QAM256	25	537.0	3.8	40.1	17	23
11	Locked	QAM256	26	543.0	4.0	40.0	32	0
12	Locked	QAM256	27	549.0	4.1	39.8	30	1
13	Locked	QAM256	28	555.0	4.4	39.9	49	0
14	Locked	QAM256	29	561.0	4.6	39.9	54	0
15	Locked	QAM256	30	567.0	4.7	39.9	46	18
16	Locked	QAM256	31	573.0	4.6	40.0	35	29
17	Locked	QAM256	32	579.0	4.7	40.1	24	27
18	Locked	QAM256	33	585.0	4.7	40.0	55	9
19	Locked	QAM256	34	591.0	4.7	40.1	9	57
20	Locked	QAM256	35	597.0	5.0	40.0	36	29
21	Locked	QAM256	36	603.0	5.1	40.0	25	44
22	Locked	QAM256	37	609.0	5.1	39.9	13	57
23	Locked	QAM256	38	615.0	5.0	39.9	12	58
24	Locked	QAM256	39	621.0	5.0	39.9	17	51
25	Locked	QAM256	40	627.0	4.7	39.8	37	31
26	Locked	QAM256	41	633.0	4.7	39.8	20	50
27	Locked	QAM256	42	639.0	4.8	39.8	18	54
28	Locked	QAM256	43	645.0	4.8	39.8	16	54
29	Locked	QAM256	45	657.0	4.9	39.8	14	54
30	Locked	QAM256	46	663.0	5.1	39.9	15	59
31	Locked	QAM256	47	669.0	4.9	39.8	15	60
32	Locked	OFDM PLC	48	688.0	5.5	36.7	1043837263	27429664

Upstream Bonded Channels

Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV)
1	Locked	SC-QAM	1	2560	10.4	45.5
2	Locked	SC-QAM	2	5120	16.4	46.3
3	Locked	SC-QAM	3	5120	22.8	46.8
4	Locked	SC-QAM	4	5120	29.2	46.8
5	Locked	SC-QAM	5	5120	35.6	46.8
6	Locked	SC-QAM	11	2560	40.4	47.0

Software

Device Information

Cable Specification Version	DOCSIS 3.1
Hardware Version	V1.0
Software Version	8611-19.2.18

Responses

CCJimmy

Problem Solver

•

492 Messages

2 years ago

Hello @Truth_Finder, thank you for taking the time to reach out to us. We will be happy to help with your connection issue. Is this happening at certain times of the day?

1

0

T

Truth_Finder

Visitor

•

6 Messages

@XfinityJimmy Hi, it does not. Every time it happens I have to restart the mode, and usually a few hours after it starts blinking. It won't clear until I restart the modem again.

2 years ago

0

EG

Expert

•

110K Messages

2 years ago

The stats were in spec at that snapshot in time. Are there any modem RF error log entries being shown ? If so, please post them as well in their entirety (copy and paste them, don't post a screenshot) but redact the CM MAC and the CMTS MAC addresses for your privacy. They are considered to be personal information. The posting of personally identifying information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically.

1

0

T

Truth_Finder

Visitor

•

6 Messages

@EG Please see the following:

Event Log

Time	Priority	Description
19:30:20 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=, CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:30:45 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:31:10 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:31:43 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:32:06 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:32:42 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:33:44 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:34:10 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:34:19 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:34:59 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:35:03 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:35:43 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:36:45 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:36:45 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:37:31 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:37:52 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:38:36 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:39:02 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:40:31 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:41:50 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:43:29 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:44:05 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:45:23 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:46:08 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:47:22 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:47:34 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:49:50 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:50:12 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:50:38 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:50:50 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:51:26 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
19:52:39 Sat May 20 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

(edited)

2 years ago

0

EG

Expert

•

110K Messages

2 years ago

@Truth_Finder

You missed one CM MAC address in the very first line.

6

0

T

Truth_Finder

Visitor

•

6 Messages

@EG removed the address.

2 years ago

0

CCMichelle

Problem Solver

•

788 Messages

@Truth_Finder

I am sorry to hear that the intermittent slow connection issues are persisting. Can you please reach out to us through Direct Message with your first and last name, name on the account if different and service address?

To send a "Direct Message" to Xfinity Support:
Click the "Direct Messaging" icon or https://comca.st/3EqVMu7
Click the "New message" (pencil and paper) icon
The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there
- As you are typing a drop-down list appears. Select "Xfinity Support" from that list
- An "Xfinity Support" graphic replaces the "To:" line
Type your message in the text area near the bottom of the window
Press Enter to send it
See https://comca.st/3KQF8q9 for an example.

I no longer work for Comcast.

2 years ago

0

T

Truth_Finder

Visitor

•

6 Messages

Thanks! Direct message sent.

2 years ago

0

CCVanessa

Contributor

•

234 Messages

Hello Brad, thank you for sending over a DM. Can you confirm your address for me as well, so we can get the account authenticated?

I no longer work for Comcast.

2 years ago

0

T

Truth_Finder

Visitor

•

6 Messages

Hello, I have sent a DM per your instructions, but have not heard back since 6 days ago.

2 years ago

0

EG

Expert

•

110K Messages

2 years ago

OK so even though the signal status values looked OK at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) / an upstream channel / return path impairment somewhere.

There are other signal stat values 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 (The Digital Care Team) who are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check 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 the CMTS for those upstream receive signal stats.

You should get a reply here in your topic. Good luck !

0

Your Home Network

Truth_Finder

Downstream Blue LED Light Blinking on Motorola MB8611 Impacting Download Speed

CCJimmy

Truth_Finder

EG

Truth_Finder

EG

Truth_Finder

CCMichelle

Truth_Finder

CCVanessa

Truth_Finder

EG

New to the Community?