cancel
Showing results for 
Search instead for 
Did you mean: 

T3 Timeout, Sync Timing Failure and trips to 1970

PaulR96
Tuning in

For the past month I've had a steadily worsening connection. It went from solid to a few stutters and then hours of downtime multiple times a day with nothing changing at my side. After trying to get help or even just acknowledgement from the Twitter 'help' I called. Had an engineer out on Saturday who took my old Hub 3, unneeded splitter and incorrect mains supply and replaced it with a Hub 4.

I had no problems on Saturday aside from what I thought were to do with the switch out. Unfortunately, Sunday and today I've had a steady series of brief connection drops that show up with lots of the following although mostly the first two.

"No Ranging Response received - T3 time-out"
"SYNC Timing Synchronization failure - Loss of Sync"
"Missing Mandatory MDD TLV on primary DS Channel"
"Unicast Ranging Received Abort Response - initializing MAC"
"CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A"
"Unicast Maintenance Ranging attempted - No response - Retries exhausted"

I can't understand why I'm getting this and I know I have zero hope of getting support before going crazy via phone.
"Have you tried turning it off then waiting a minute and turning it back on? Are the cables connected?"
I just can't do it. I know some people have simple issues, I'd love for it to be a simple issue but these errors tell me there's a pretty big problem. Can someone please help? I know there are support peeps around here.

12 REPLIES 12

PaulR96
Tuning in

hub4.pngI forgot to set this up until today for the new IP. I did this around 1pm and this is how it's been since.

Can you post your Hub status and logs?
Someone should be spot if there is a problem
Navigate to http://192.168.0.1 (or http://192.168.100.1 - if in modem mode)
Don't log in!
Click on 'router status'
Copy/paste the data from each of the tabs as text into a 'REPLY' as opposed to 'QUICK REPLY'. The forum software will remove the MAC addresses for you (If you get an error - just click the 'post' button again).




------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

Doing this in a few parts because it keeps giving me errors about it being over 20k character when I know it isn't.

Item
Status
Comments
Cable Modem Status
Online
DOCSIS 3.1
Primary downstream channel
Locked
SC-QAM
Channel OverviewDownstreamUpstream
DOCSIS 3.0 channels
31
5
DOCSIS 3.1 channels
1
1

 

3.0 Downstream channels

ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
41627500005.30000340.366287QAM2564
11387500005.59999840.946209QAM2561
21467500005.50000040.366287QAM2562
31547500005.59999840.366287QAM2563
51707500005.00000040.366287QAM2565
61787500005.00000040.366287QAM2566
71867500004.69999740.366287QAM2567
81947500004.09999840.366287QAM2568
92027500003.79999940.366287QAM2569
102107500003.70000140.366287QAM25610
112187500003.59999840.366287QAM25611
122267500003.40000240.366287QAM25612
132347500003.09999840.366287QAM25613
142427500002.79999938.983261QAM25614
152507500002.40000238.983261QAM25615
162587500002.29999938.983261QAM25616
172667500002.09999838.983261QAM25617
182747500001.59999838.983261QAM25618
192827500002.20000138.983261QAM25619
202907500002.79999938.983261QAM25620
212987500003.29999938.983261QAM25621
223067500004.09999838.983261QAM25622
233147500004.80000340.366287QAM25623
243227500005.00000040.366287QAM25624
253307500004.69999740.366287QAM25625
263387500004.50000040.366287QAM25626
273467500004.59999840.366287QAM25627
283547500004.80000340.366287QAM25628
293627500004.59999840.946209QAM25629
303707500004.40000238.983261QAM25630
313787500004.00000038.983261QAM25631



3.0 Downstream channels

ChannelLock StatusRxMER (dB)Pre RS ErrorsPost RS Errors
4Locked40.36628700
1Locked40.94620900
2Locked40.36628700
3Locked40.36628700
5Locked40.36628700
6Locked40.36628700
7Locked40.36628700
8Locked40.36628700
9Locked40.36628700
10Locked40.36628700
11Locked40.36628700
12Locked40.36628700
13Locked40.36628700
14Locked38.98326100
15Locked38.98326100
16Locked38.98326100
17Locked38.98326100
18Locked38.98326100
19Locked38.98326100
20Locked38.98326100
21Locked38.98326100
22Locked38.98326100
23Locked40.36628700
24Locked40.36628700
25Locked40.36628700
26Locked40.36628700
27Locked40.36628700
28Locked40.36628700
29Locked40.94620900
30Locked38.98326100
31Locked38.98326100



3.1 Downstream channels

ChannelChannel Width (MHz)FFT TypeNumber of Active SubcarriersModulation (Active Profile)First Active Subcarrier (Hz)
159944K1800QAM4096424


3.1 Downstream channels

Channel IDLock StatusRxMER Data (dB)PLC Power (dBmV)Correcteds (Active Profile)Uncorrectables (Active Profile)
159Locked423.23625081890
 

3.0 Upstream channels

 

ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
12360000040.2705995120 KSym/sec64QAM13
23010000040.2705995120 KSym/sec64QAM12
33660000040.7705995120 KSym/sec64QAM11
44310000041.2705995120 KSym/sec64QAM10
54960000041.7705995120 KSym/sec64QAM9



3.0 Upstream channels

ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1US_TYPE_ATDMA0000
2US_TYPE_ATDMA0000
3US_TYPE_ATDMA0000
4US_TYPE_ATDMA0000
5US_TYPE_ATDMA0000



3.1 Upstream channels

ChannelChannel Width (MHz)Power (dBmV)FFT TypeModulation
1410.036.22KQAM128


3.1 Upstream channels

ChannelChannel TypeNumber of Active SubcarriersFirst Active Subcarrier (Hz)T3 TimeoutsT4 Timeouts
14OFDMA20053.900

General Configuration

Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
kfoA,.iyewrkldJKDHSUBsgvca698



Primary Downstream Service Flow

SFID
24085
Max Traffic Rate
143750047
Max Traffic Burst
42600
Min Traffic Rate
0



Primary Upstream Service Flow

SFID
24342
Max Traffic Rate
22000047
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
42600
Scheduling Type
bestEffort

Network Log

TimePriorityDescription
Tue Apr
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
5DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6US profile assignment change. US Chan ID: 14; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
4Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
4Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan
3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
3SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Apr
6CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Just noting the Thursday was the brief trip to 1970. There was also a lot of this on Sunday. Nothing (yet) since the big outage.

This was Sunday's graph from the very moment I set the BQM to the new IP.

Sunday's BQM on Think Broadband 

wed.jpgFor an update after the big outage I'm still seeing huge latency spikes. I did try calling about this and was essentially told they saw nothing wrong with it because it hadn't dropped (yet) today / Wednesday. 

To me, that looks rather like over-utilisation!

That doesn't tend to get fixed quickly unfortunately!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7