U

Visitor

 • 

1 Message

Thu, Sep 15, 2022 2:11 AM

Motorola MB8611 Disconnects

Another person chiming in with disconnects on this modem. I have swapped out the router as I thought that was the cause but after having a new one for 2 days, I noticed the issue did not go away and suspected the modem. Here are the error logs and status. 

Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 13 519.0 2.5 43.9 0 0
   2 Locked QAM256 1 441.0 2.7 43.9 1 0
   3 Locked QAM256 2 453.0 2.2 43.6 1 0
   4 Locked QAM256 3 459.0 2.1 43.5 8 0
   5 Locked QAM256 4 465.0 2.1 43.7 1 0
   6 Locked QAM256 5 471.0 2.1 43.7 0 0
   7 Locked QAM256 6 477.0 1.9 43.4 1 0
   8 Locked QAM256 7 483.0 2.0 43.6 1 0
   9 Locked QAM256 8 489.0 2.1 43.3 1 0
   10 Locked QAM256 9 495.0 2.2 43.6 1 0
   11 Locked QAM256 10 501.0 2.1 43.6 1 0
   12 Locked QAM256 11 507.0 2.2 43.7 0 0
   13 Locked QAM256 12 513.0 2.2 43.6 0 0
   14 Locked QAM256 14 525.0 2.9 44.0 0 0
   15 Locked QAM256 15 531.0 2.9 43.9 0 0
   16 Locked QAM256 16 537.0 2.5 43.6 0 0
   17 Locked QAM256 17 543.0 3.1 43.9 0 0
   18 Locked QAM256 18 555.0 3.4 43.7 0 0
   19 Locked QAM256 19 561.0 3.3 44.0 0 0
   20 Locked QAM256 20 567.0 3.1 43.7 0 0
   21 Locked QAM256 21 573.0 3.4 43.6 0 0
   22 Locked QAM256 22 579.0 3.9 44.0 0 0
   23 Locked QAM256 23 585.0 3.6 43.8 0 0
   24 Locked QAM256 24 591.0 3.3 43.9 0 0
   25 Locked OFDM PLC 25 693.0 3.0 43.7 11478584 0
   26 Locked QAM256 26 597.0 3.6 44.1 0 0
   27 Locked QAM256 27 603.0 3.9 44.1 0 0
   28 Locked QAM256 28 609.0 3.9 44.2 0 0
   29 Locked QAM256 29 615.0 3.6 44.0 0 0
   30 Locked QAM256 30 621.0 3.6 43.9 0 0
   31 Locked QAM256 31 627.0 3.7 43.9 0 0
   32 Locked QAM256 32 633.0 4.1 44.0 0 0


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 53 5120 16.4 41.0
   2 Locked SC-QAM 54 5120 22.8 42.0
   3 Locked SC-QAM 55 5120 29.2 42.0
   4 Locked SC-QAM 56 5120 35.6 42.8

   Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    20:23:24
Tue Sep 13 2022
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;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-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv6
    20:19:53
Wed Sep 14 2022
  Notice (6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;

Official Employee

 • 

447 Messages

3 months ago

 

 

Could you please send our team a direct message with your full name and full address? Our team can most definitely take a further look at this issue. To send a "Peer to peer" ("Private") message:
Click "Sign In" if necessary
• Click the "Peer to peer chat" icon
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "Xfinity Support" graphic replaces the "To:" line
• Type your message in the text area near the bottom of the window
• Press Enter to send it

 

forum icon

New to the Community?

Start Here