Hello, I recently upgraded from the SB6141 to the SB8200. I have never had firmware issues with the SB6141 but my brand new SB8200 wont update.
I am currently on the 600Mpbs/15 plan but bought the SB8200 for two specific things: upgrading to gigabit service and LACP/LAG using Pfsense.
Here is what the modem is reporting:
Current Firmware: D31CM-PEREGRINE-1.0.0.2-GA-01-NOSH
Log:
8-29-2020, 15:16:23 Warning(5) "MDD message timeout;CM-MAC=2c:58:4f:fd:fe:5d;CMTS-MAC=00:01:5c:65:42:72;CM-QOS=1.1;CM-VER=3.1;"8-29-2020, 12:19:7 Error(4) "SW upgrade Failed after download - Incompatible SW file"8-29-2020, 12:19:5 Notice(6) "SW Download INIT - Via Config file d11_m_sb8200_extremeproplus_c01.cm"1-1-1970, 0:2:19 Notice(6) "Honoring MDD; IP provisioning mode = IPv6"1-1-1970, 0:2:15 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=2c:58:4f:fd:fe:5d;CMTS-MAC=00:01:5c:65:42:72;CM-QOS=1.1;CM-VER=3.1;"1-1-1970, 0:2:9 Warning(5) "Lost MDD Timeout;CM-MAC=2c:58:4f:fd:fe:5d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"1-1-1970, 0:2:2 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:58:4f:fd:fe:5d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"1-1-1970, 0:2:1 Warning(5) "Lost MDD Timeout;CM-MAC=2c:58:4f:fd:fe:5d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"1-1-1970, 0:1:54 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:58:4f:fd:fe:5d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"1-1-1970, 0:1:27 Warning(5) "Lost MDD Timeout;CM-MAC=2c:58:4f:fd:fe:5d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"1-1-1970, 0:0:28 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=2c:58:4f:fd:fe:5d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
Thoughts. I have spoke with Xfinity tech support, the config file is correct but I've been told there is nothing they can do about the firmware other than it updates automatically when the modem power-resets.
Any other ways to have this manually corrected? It seems like there might be an intermediate firmware I need to go to first and update from there?
↧