Check your service statusCable National
Ask a question
Reply
Brainbox
GMAN73
Posts: 160
Registered: ‎31-05-2011

T3 and T4 timeouts

[ Edited ]

Okay I posted this on another thread that I have going, not sure if its related to high utilisation.

 

Can someone explain what these error messages are in my Superhub log.

 

Date Time Error Number Error Description
25/09/2012 22:05:06 2436694074 CMTS DCC 291000000 MHz
25/09/2012 22:04:58 2436694078 TOD established
25/09/2012 22:03:34 68000600 TFTP failed - configuration file NOT FOUND;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0;
25/09/2012 22:03:27 2436694077 TOD server unavailable
25/09/2012 22:03:27 2436694080 TOD resynchronisation failure
25/09/2012 22:02:20 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/09/2012 13:40:48 82000500 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/09/2012 13:08:18 2436694074 CMTS DCC 315000000 MHz
22/09/2012 18:28:54 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0;
22/09/2012 18:28:42 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0;
22/09/2012 18:27:02 84000100 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0;
22/09/2012 18:26:58 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0;
22/09/2012 18:26:11 68000500 TFTP failed - Request sent - No Response;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0;
22/09/2012 18:26:11 68001101 TFTP Request Retries exceeded, CM unable to register
22/09/2012 18:24:45 82000100 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0;

 

Network Log- " Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; " happen in time Tue Sep 25 11:35:30 2012
 
 Network Log- " Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; " happen in time Wed Sep 26 01:18:03 2012
 
Network Log- " Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; " happen in time Wed Sep 26 12:54:59 2012
 
Network Log- " Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**:**CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; " happen in time Thu Sep 27 00:21:33 2012
 
In just over a day and a half Ive had 4 T3 timeout, now is this related to F002100299 or is there something else sinister going on with my shoddy broadband service.

 

Please use plain text.
Brainbox
GMAN73
Posts: 160
Registered: ‎31-05-2011

Re: T3 and T4 timeouts

 28/09/2012   02:58:04   68000300   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 
 28/09/2012   02:58:04   2436694078   TOD established 
 28/09/2012   02:57:48   82000200   No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:57:40   2436694074   CMTS DCC 315000000 MHz 
 28/09/2012   02:57:12   82000400   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:41:55   68000600   TFTP failed - configuration file NOT FOUND;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:41:46   68000300   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:41:25   84000100   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:40:25   84000200   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:39:36   68000500   TFTP failed - Request sent - No Response;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:39:36   68001101   TFTP Request Retries exceeded, CM unable to register  
 28/09/2012   02:39:36   68000401   ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:38:37   68000100   DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**1;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:35:26   84020200   Lost MDD Timeout;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:35:15   82000200   No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:31:38   84000200   SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:24:00   68000300   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:22:00   68000300   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:20:58   68000100   DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:12:46   68000401   ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   02:12:44   82000400   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   01:59:51   68000300   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   01:59:04   2436694077   TOD server unavailable 
 28/09/2012   01:59:04   2436694080   TOD resynchronisation failure 
 28/09/2012   01:49:57   68000300   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   01:48:05   68000300   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 28/09/2012   01:19:32   82000400   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 
 28/09/2012   01:19:32   84000100   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 
 28/09/2012   01:19:15   84020300   MDD message timeout;CM-MAC=**:**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 

Please use plain text.
The Sorter
Darren_G
Posts: 1,077
Registered: ‎05-12-2011

Re: T3 and T4 timeouts

Hi GMAN73, We are sorry to see you are having issues with your connection, I have sent you a Private Message. We'll be happy to progress things for you once we have received your reply.


Darren_G
Help & Support Forum Team

Seen a useful post?Problem Solved?Fault with your service?

Please use plain text.
Brainbox
GMAN73
Posts: 160
Registered: ‎31-05-2011

Re: T3 and T4 timeouts

[ Edited ]

Thanks Darren, never knew my downstream powerlevels were high.  Ive replied to the PM.

 

Downstream

Lock Status Channel ID Frequency     Modulation  Rx Power  SNR Pre RS Errors Post RS Errors
Locked         38          315000000 Hz   QAM256     0.0 dBmV  41.5 dB  58546      16
Locked         35          291000000 Hz   QAM256     0.4 dBmV  40.9 dB  70619      38
Locked         36          299000000 Hz   QAM256     0.3 dBmV  41.9 dB  63550      20
Locked         37          307000000 Hz   QAM256     0.2 dBmV  42.4 dB  52672       0

 

Upstream
Lock Status Channel ID Frequency    Modulation  Tx Power      Mode    Channel Bandwidth  Symbol Rate
Locked        33              45800000 Hz  ATDMA     40.8 dBmV  16QAM  6 400000           20480 Kbits/sec

Please use plain text.
Brainbox
GMAN73
Posts: 160
Registered: ‎31-05-2011

Re: T3 and T4 timeouts

[ Edited ]

Richie the VM engineer came out, did various checks etc.  He noticed that my powerlevels were near 0.  He decided to swap over the Superhub as per advice from the controller due to the timeouts, but when doing so he noticed that I had the wrong type of Power Supply (this was the one I got supplied with when I got my Superhub over a year ago), he supplied the correct type of power supply, he activated the modem and did some tests.

 

So far its looking great.  One thing I would always get is egg timers with various sites that I visit a lot, sometime they would not load or would get page cannot be displayed, but the I would refresh and they woul load up, but now they are loading up a lot faster.  Especially forums.Xbox.com which would take 10-15 seconds to load each section.

 

Will see how it goes, hopefully F002100299  will be sorted soon.

 

Ive been very critical of VM, but Richie today has restored my faith.  Now maybe I will get on the phone and try and blag a free upgrade to 60mbs.

Please use plain text.