New Poster
•
2 Messages
Netgear CM1000v2 bandwidth dropoff with Gigabit xfinity service
Bandwidth drops with Gigabit service.
Modem: Netgear CM1000v2
Firmware: V7.01.01
Time | Priority | Description |
2021-01-01, 20:27:22 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:26:54 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:26:36 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:26:08 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:25:21 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:24:51 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:23:58 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:23:33 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:23:17 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:23:17 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:22:49 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:22:22 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:22:11 | Notice (6) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:21:51 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:21:46 | Notice (6) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:21:46 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
2021-01-01, 20:21:36 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:01:5c:76:2c:59;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=9c:c9:eb:92:0b:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
CMCCR
New Poster
•
2 Messages
5 years ago
Current System Time: Fri Jan 01 20:37:40 2021System Up Time: 0:16:48
0
0
EG
Expert
•
111.5K Messages
5 years ago
Oth the upstream power and the downstream power are borderline and they may be intermittently fluctuating even farther to out of spec levels. 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.
0
0