NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

bvkiran's avatar
bvkiran
Follower
Feb 17, 2022

CM400 keeps dropping internet

My configuration is a CM400 modem with a TP-Link router. For a past few days it keeps dropping internet. To rule out TP-Link router issues, I tried to swap out my router with a older one but it does not help. Contacted XFinity and after running their tests they say things are fine from their end.
I tried to login to the modem and check the event logs. I see this the below. Please help how to fix this issue.
Firmware Version

V2.01.06
Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel447000000 HzLocked
Connectivity StateOkOperational
Boot StateOkOperational
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDhonorMdd(4)

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUnCorrectables
1LockedQAM 2564405000000 Hz9.7 dBmV34.7 dB1354388504
2LockedQAM 2565411000000 Hz9.3 dBmV36.3 dB44963110851
3LockedQAM 2566417000000 Hz9.6 dBmV36.6 dB45948108370
4LockedQAM 2567423000000 Hz9.6 dBmV37.0 dB48843147507
5LockedQAM 2568429000000 Hz9.5 dBmV37.6 dB44307135525
6LockedQAM 2569435000000 Hz10.1 dBmV37.6 dB44535140135
7LockedQAM 25610441000000 Hz9.6 dBmV37.3 dB50812179820
8LockedQAM 25611447000000 Hz9.4 dBmV37.0 dB45357110663

Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA75120 Ksym/sec16400000 Hz46.3 dBmV
2LockedATDMA85120 Ksym/sec22800000 Hz46.5 dBmV
3LockedATDMA95120 Ksym/sec29200000 Hz47.0 dBmV
4LockedATDMA105120 Ksym/sec35600000 Hz48.0 dBmV

Current System Time: Wed Feb 16 18:45:18 2022
System Up Time: 04:45:55
 
 
 
and the event log says - 
TimePriorityDescription
Feb 16 10:02:39 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:02:48 2022Warning (5)Lost MDD Timeout
Feb 16 10:04:18 2022Critical (3)No Ranging Response received - T3 time-out
Feb 16 10:04:23 2022Warning (5)Lost MDD Timeout
Feb 16 10:07:45 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:07:53 2022Warning (5)Lost MDD Timeout
Feb 16 10:08:03 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:08:04 2022Warning (5)Lost MDD Timeout
Feb 16 10:08:04 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:08:29 2022Warning (5)Lost MDD Timeout
Feb 16 10:08:44 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:09:28 2022Warning (5)Lost MDD Timeout
Feb 16 10:09:48 2022Critical (3)No Ranging Response received - T3 time-out
Feb 16 10:09:53 2022Warning (5)Lost MDD Timeout
Feb 16 10:10:10 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:10:12 2022Warning (5)Lost MDD Timeout
Feb 16 10:12:58 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:13:02 2022Warning (5)Lost MDD Timeout
Feb 16 10:13:07 2022Critical (3)No Ranging Response received - T3 time-out
Feb 16 10:13:13 2022Warning (5)Lost MDD Timeout
Feb 16 10:13:15 2022Critical (3)No Ranging Response received - T3 time-out
Feb 16 10:13:34 2022Warning (5)Lost MDD Timeout
Feb 16 10:13:56 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:14:11 2022Warning (5)Lost MDD Timeout
Feb 16 10:14:25 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:14:35 2022Warning (5)Lost MDD Timeout
Feb 16 10:17:22 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 10:17:28 2022Warning (5)Lost MDD Timeout
Feb 16 10:21:13 2022Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 16 12:55:02 2022Warning (5)Lost MDD Timeout
Feb 16 13:50:57 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync
Feb 16 13:51:01 2022Warning (5)Lost MDD Timeout
Feb 16 13:53:12 2022Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Feb 16 13:53:19 2022Warning (5)Lost MDD Timeout
Feb 16 13:53:49 2022Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Feb 16 13:55:08 2022Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out
Feb 16 13:59:58 2022Warning (5)MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 16 14:05:27 2022Warning (5)Lost MDD Timeout
Feb 16 14:05:35 2022Critical (3)SYNC Timing Synchronization failure - Loss of Sync

1 Reply