Visitor
•
5 Messages
Netgear Orbi CBR750 modem's download speed drops from 600Mbps to < 3Mbps every time "DS profile config update" event occurs (every 3 days)
Hi everyone,
I'm noticing a clear pattern here and need help troubleshooting. Every time my modem's event log shows a DS profile config update event occurred, soon after we'll use the internet and notice our download speeds have dropped from our normal 600 Mbps down to less than 3 Mbps. I'm running the speed test directly on the modem via the Netgear Orbi iOS app. Lately the DS profile config update event is occurring every 3 days. The issue seems to never resolve on its own and requires a reset of the modem in order to resolve the issue. A Comcast technician was here two days ago and wasn't able to identify root cause and resolve the issue. His hypothesis was occasional signal strength or connectivity issues, but reported while here our signal strength looks good. His hypothesis also doesn't make sense given the issue occurs every 3 days. I showed him the event log but he said he wasn't knowledgable about it.
What is the root cause of this issue, and how can I resolve it?
Below is a cable diagnostic and event logs from the modem I saved today at Thu Feb 23 08:34:16 2023:
Cable Diagnostic
Status: Poor
Internet Access: Good
Downstream Status: Poor
Downstream Power Level: Poor
Downstream power is poor (10.4dBmV). The recommended level is between -10dBmV to 10dBmV.
Downstream SNR: Good
Upstream Status: Good
Upstream Power Level: Good
Current time: Thu Feb 23 08:34:16 2023
Startup Procedure
Acquire Downstream Channel: 537000000 Hz Locked
Connectivity State: Ok Operational
Boot State: Ok Operational
Security: Enabled BPI+
IP Provisioning Mode: Honor MDD honorMdd(4)
Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM 256 1 417000000 Hz 8.5 37.3 6412 64
2 Locked QAM 256 2 423000000 Hz 8.5 37.3 13083 59
3 Locked QAM 256 3 429000000 Hz 8.8 37.3 9663 1030
4 Locked QAM 256 4 435000000 Hz 8.9 37.3 798843 51
5 Locked QAM 256 5 441000000 Hz 8.9 37.3 12550 85
6 Locked QAM 256 6 447000000 Hz 9.0 37.3 10693 52
7 Locked QAM 256 7 453000000 Hz 9.1 37.3 13126 38
8 Locked QAM 256 8 459000000 Hz 9.4 37.3 11483 58
9 Locked QAM 256 9 465000000 Hz 9.5 37.6 12293 27
10 Locked QAM 256 10 471000000 Hz 9.5 37.6 13119 50
11 Locked QAM 256 11 477000000 Hz 9.6 37.6 10941 939
12 Locked QAM 256 12 483000000 Hz 9.8 37.6 10509 1136
13 Locked QAM 256 13 489000000 Hz 9.9 37.6 9011 33
14 Locked QAM 256 14 495000000 Hz 10.0 37.6 8974 54
15 Locked QAM 256 15 507000000 Hz 10.0 38.6 6216 21
16 Locked QAM 256 16 513000000 Hz 10.1 37.6 5896 29
17 Locked QAM 256 17 519000000 Hz 10.1 37.3 2596 30
18 Locked QAM 256 18 525000000 Hz 10.3 38.6 2420 24
19 Locked QAM 256 19 531000000 Hz 10.3 37.6 2501 27
20 Locked QAM 256 20 537000000 Hz 10.3 38.6 2806 120
21 Locked QAM 256 21 543000000 Hz 10.3 37.6 2142 17
22 Locked QAM 256 22 549000000 Hz 10.1 38.6 2407 0
23 Locked QAM 256 23 555000000 Hz 10.4 38.6 2047 0
24 Locked QAM 256 24 561000000 Hz 10.4 38.6 1795 27
25 Locked QAM 256 25 567000000 Hz 10.3 38.9 1937 0
26 Locked QAM 256 26 573000000 Hz 10.4 38.6 1570 0
27 Locked QAM 256 27 579000000 Hz 10.1 38.6 1940 0
28 Locked QAM 256 28 585000000 Hz 10.1 38.6 2690 0
29 Locked QAM 256 29 591000000 Hz 10.3 38.6 1312 7
30 Locked QAM 256 30 597000000 Hz 10.1 38.6 1182 0
31 Locked QAM 256 31 603000000 Hz 10.3 38.6 1134 0
32 Locked QAM 256 32 609000000 Hz 10.1 38.6 1354 0
Upstream Bonded Channels
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 22 2560 10400000 Hz 40.8
2 Locked ATDMA 17 5120 16400000 Hz 40.3
3 Locked ATDMA 18 5120 22800000 Hz 41.0
4 Locked ATDMA 19 5120 29200000 Hz 41.3
5 Locked ATDMA 20 5120 35600000 Hz 41.3
6 Locked ATDMA 21 2560 40400000 Hz 41.8
7 Not Locked N/A 0 0 0 Hz 0.0
8 Not Locked N/A 0 0 0 Hz 0.0
Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 3 193 850000000 Hz 12.0 dBmV 40.0 dB 1108~2987 0 0 0
2 Not Locked 0 0 0 Hz 0.0 dBmV 0.0 dB 0~4095 0 0 0
Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Not Locked 0 0 0 Hz 0.0 dBmV
2 Not Locked 0 0 0 Hz 0.0 dBmV
Event log
Feb 12 2023 10:57:43 | Alert (2) | CM Certificate Error |
Feb 12 2023 17:18:31 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 12 2023 21:49:47 | Notice (6) | CM-STATUS message sent. Event Type Code: 5 |
Feb 12 2023 21:56:32 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 13 2023 10:57:41 | Alert (2) | CM Certificate Error |
Feb 13 2023 12:28:15 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 14 2023 10:57:29 | Alert (2) | CM Certificate Error |
Feb 14 2023 14:09:26 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 14 2023 14:32:48 | Notice (6) | CM-STATUS message sent. Event Type Code: 5 |
Feb 14 2023 14:32:55 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 14 2023 15:12:22 | Notice (6) | CM-STATUS message sent. Event Type Code: 5 |
Feb 14 2023 15:13:33 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 14 2023 18:08:19 | Notice (6) | DS profile config update. DS Chan ID: 193. |
Feb 14 2023 18:25:43 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 14 2023 18:31:28 | Alert (2) | CM Certificate Error |
Speed test run directly on modem via Orbi iOS app. 0.81 down, 9.46 up. restart modem and issue resolves. | ||
Feb 14 2023 19:40:02 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Feb 14 2023 19:40:02 | Notice (6) | TLV-11 - unrecognized OID |
Feb 14 2023 19:40:02 | Critical (3) | Config File Rejected due to Invalid or Unexpected TLV 11 |
Feb 14 2023 19:40:07 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW |
Feb 14 2023 19:40:08 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 14 2023 19:40:19 | Alert (2) | CM Certificate Error |
Feb 15 2023 0:13:31 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 15 2023 10:56:08 | Alert (2) | CM Certificate Error |
Feb 15 2023 11:47:39 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 16 2023 10:56:01 | Alert (2) | CM Certificate Error |
Feb 16 2023 11:56:30 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 17 2023 10:35:54 | Notice (6) | DS profile config update. DS Chan ID: 193. |
Feb 17 2023 10:55:19 | Alert (2) | CM Certificate Error |
Speed test run directly on modem via Orbi iOS app. 0.0 down, 0.0 up. restart modem and issue resolves. | ||
Feb 17 2023 11:20:21 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Feb 17 2023 11:20:21 | Notice (6) | TLV-11 - unrecognized OID |
Feb 17 2023 11:20:21 | Critical (3) | Config File Rejected due to Invalid or Unexpected TLV 11 |
Feb 17 2023 11:20:26 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW |
Feb 17 2023 11:20:26 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 17 2023 11:20:44 | Alert (2) | CM Certificate Error |
Feb 17 2023 11:38:46 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Feb 17 2023 11:38:46 | Notice (6) | TLV-11 - unrecognized OID |
Feb 17 2023 11:38:46 | Critical (3) | Config File Rejected due to Invalid or Unexpected TLV 11 |
Feb 17 2023 11:38:56 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW |
Feb 17 2023 11:38:56 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 17 2023 11:39:13 | Alert (2) | CM Certificate Error |
Feb 17 2023 11:55:03 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 17 2023 14:03:20 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Feb 17 2023 14:03:20 | Notice (6) | TLV-11 - unrecognized OID |
Feb 17 2023 14:03:20 | Critical (3) | Config File Rejected due to Invalid or Unexpected TLV 11 |
Feb 17 2023 14:03:26 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW |
Feb 17 2023 14:03:35 | Alert (2) | CM Certificate Error |
Feb 17 2023 14:42:01 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 18 2023 10:55:42 | Alert (2) | CM Certificate Error |
Feb 18 2023 12:16:52 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 19 2023 10:55:37 | Alert (2) | CM Certificate Error |
Feb 19 2023 12:28:21 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 20 2023 4:49:51 | Notice (6) | DS profile config update. DS Chan ID: 193. |
Feb 20 2023 5:29:14 | Critical (3) | No Ranging Response received - T3 time-out |
Wife texts me that the internet is not working all morning. She restarts the modem and issue resolves. | ||
Feb 20 2023 9:11:58 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Feb 20 2023 9:11:58 | Notice (6) | TLV-11 - unrecognized OID |
Feb 20 2023 9:11:58 | Critical (3) | Config File Rejected due to Invalid or Unexpected TLV 11 |
Feb 20 2023 9:12:08 | Warning (5) | RCS Partial Service |
Feb 20 2023 9:12:08 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW |
Feb 20 2023 9:12:09 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 20 2023 9:12:20 | Alert (2) | CM Certificate Error |
Feb 20 2023 9:12:23 | Notice (6) | CM-STATUS message sent. Event Type Code: 4 |
Feb 20 2023 10:55:30 | Alert (2) | CM Certificate Error |
Feb 20 2023 13:32:53 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 21 2023 10:55:02 | Alert (2) | CM Certificate Error |
Feb 21 2023 13:32:27 | Notice (6) | CM-STATUS message sent. Event Type Code: 24 |
Feb 21 2023 13:32:27 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Feb 21 2023 13:32:30 | Notice (6) | CM-STATUS message sent. Event Type Code: 17 |
Feb 21 2023 13:32:38 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Feb 21 2023 13:32:40 | Notice (6) | CM-STATUS message sent. Event Type Code: 2 |
Feb 21 2023 13:32:42 | Warning (5) | Lost MDD Timeout |
Feb 21 2023 13:33:13 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
Feb 21 2023 13:38:37 | Critical (3) | SYNC Timing Synchronization failure - Loss of Sync |
Feb 21 2023 13:38:43 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Feb 21 2023 13:38:43 | Notice (6) | TLV-11 - unrecognized OID |
Feb 21 2023 13:38:43 | Critical (3) | Config File Rejected due to Invalid or Unexpected TLV 11 |
Feb 21 2023 13:38:51 | Warning (5) | RCS Partial Service |
Feb 21 2023 13:38:51 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW |
Feb 21 2023 13:39:01 | Alert (2) | CM Certificate Error |
Feb 21 2023 13:39:13 | Notice (6) | CM-STATUS message sent. Event Type Code: 4 |
Feb 21 2023 13:40:04 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 21 2023 15:12:16 | Notice (6) | CM-STATUS message sent. Event Type Code: 5 |
Feb 21 2023 15:17:54 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 21 2023 18:44:42 | Alert (2) | CM Certificate Error |
Feb 21 2023 23:44:47 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 22 2023 10:55:04 | Alert (2) | CM Certificate Error |
Feb 22 2023 11:16:36 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 22 2023 13:06:48 | Notice (6) | CM-STATUS message sent. Event Type Code: 5 |
Feb 22 2023 13:38:11 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 23 2023 3:48:03 | Notice (6) | DS profile config update. DS Chan ID: 193. |
Feb 23 2023 7:06:22 | Critical (3) | No Ranging Response received - T3 time-out |
Speed test run directly on modem via Orbi iOS app. 2.74 down, 11.14 up. restart modem and issue resolves. | ||
Feb 23 2023 8:50:23 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
Feb 23 2023 8:50:23 | Notice (6) | TLV-11 - unrecognized OID |
Feb 23 2023 8:50:23 | Critical (3) | Config File Rejected due to Invalid or Unexpected TLV 11 |
Feb 23 2023 8:50:27 | Warning (5) | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW |
Feb 23 2023 8:50:28 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 23 2023 8:50:39 | Alert (2) | CM Certificate Error |
Feb 23 2023 8:58:01 | Critical (3) | No Ranging Response received - T3 time-out |
Feb 23 2023 10:54:45 | Alert (2) | CM Certificate Error |
Feb 23 2023 11:08:23 | Critical (3) | No Ranging Response received - T3 time-out |


user_jb223
Visitor
•
5 Messages
29 days ago
Senior technician scheduled to come out tomorrow afternoon.
My brother in law used to be a Comcast tech for many years. He looked at my event log and cable diagnostics and seems to be concerned about the T3 timeouts and wonders if there's static electricity or noise ingress in the line.
Does anyone know if a DS profile config update could cause a modem to drop downstream speeds like I'm observing?
Do the DS profile config updates occur on a recurring schedule or only when my modem has issues/disruptions/timeouts?
8
0
user_jb223
Visitor
•
5 Messages
14 hours ago
My issue is still unresolved and ongoing!
A senior tech came out on 2/25/23 and investigated. He observed flux and upstream tilt issues impacting my service address and three other services addresses on the same TAP component which is part of the Comcast network infrastructure. He called the network team (maintenance team), reported the flux and upstream tilt findings, and set my expectations that the maintenance team would come investigate the issue within the next 48 hours.
A few days later I speak with support and they say the maintenance team actually has a 10 day SLA to work on my escalated issue. 10 days pass and my issue keeps occurring. Over the last month, I've reach out to support and have been given conflicting status updates about the maintenance team's progress investigating my issue. Several times I was told the maintenance team's ticket number was 640311 and it was still in progress. Now this evening a support rep is telling me she sees no maintenance team ticket and no records that indicate that the maintenance team did any work at all to investigate my escalated issue. She tells me that the ticket 640311 is actually the job number of the senior tech's visit on 2/25/23.
I'm forced to schedule yet another service technician appointment and have requested the same senior tech from 2/25 to come out on 3/28 in a few days. The rep tells me this is the only way I can find out if the flux and upstream tilt issues are still present at my service address and other services addresses on the same TAP. The rep also tells me only the technicians can communicate to the maintenance team, and so if I want to find out if the maintenance team did any work when my issue was escalated, I need a tech to come back here.
I'll post an update after the senior tech visits again on 3/28.
(edited)
0
0