NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
My_Username
Nov 17, 2021Apprentice
Extended upstream transmit power - CAX80
Cable diagnostics say I have a poor connection due to upstream power. See diagnostic output below. I see that extended upstream transmit power is checked. I can click on the setting but nothing chan...
olympos1625
Dec 11, 2021NETGEAR Employee Retired
Hi My_Username,
Thank you for reaching out. We are sorry for not being able to get back to you immediately. Are you still having issues with your Upstream? Please send us the event logs of the Cable modem.
https://kb.netgear.com/30008/How-do-I-obtain-the-event-logs-from-a-NETGEAR-cable-modem-modem-router
Please do not hesitate to let me know if you need further assistance.
Regards,
Oliver
Community Team
My_Username
Dec 11, 2021Apprentice
Cable diagnostics still indicate that the connection is poor due to upstream power. Upstream power signal level is currently running between 27.0dBmV and 35.5dBmV. Extended upstream transmit power is enabled and I cannot toggle that setting. I assume that setting is part of Xfinity provisioning.
The system seems to be functioning and the speed test indicates I am getting better than my contract 300Mbps. I am just concerned that modem diagnostics flags the connection as poor due to upstream power.
The modem log follows:
Fri Dec 10 20:01:49 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 10 20:01:16 2021 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 10 20:01:12 2021 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 10 20:00:44 2021 | Notice (6) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:00:55 1970 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Thu Jan 1 00:00:44 1970 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 8 18:42:42 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 5 22:46:23 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 5 17:37:09 2021 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:00:43 1970 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 5 09:48:41 2021 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:02:59 1970 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:00:44 1970 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 3 21:52:16 2021 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3e:88:60;CMTS-MAC=00:90:f0:36:00:00;CM-QOS=1.1;CM-VER=3.1; |