• Welkom op het onafhankelijke Ziggo Gebruikersforum. Een forum voor en door gebruikers van Ziggo.
    Registreer je nu gratis om zelf berichten te kunnen plaatsen!

Connect Box T3 time-outs


robjanssen

Product Tester
Lid geworden
24 jan 2006
Berichten
6.369
Ziggo
Alles in 1
Gebied
fUPC
Wie heeft er nog meer last van T3 time-outs bij de Connect Box?
Wat betekenen deze meldingen precies?
En hoe kan het opgelost worden?

01-06-2016 09:53:57 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:28:b5;CMTS-MAC=00:22:90:c6:b7:74;CM-QOS=1.1;CM-VER=3.0;
01-06-2016 08:27:28 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:28:b5;CMTS-MAC=00:22:90:c6:b7:74;CM-QOS=1.1;CM-VER=3.0;
31-05-2016 19:56:06 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:28:b5;CMTS-MAC=00:22:90:c6:b7:74;CM-QOS=1.1;CM-VER=3.0;
31-05-2016 14:37:02 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:28:b5;CMTS-MAC=00:22:90:c6:b7:74;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 02:18:24 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:28:b5;CMTS-MAC=00:22:90:c6:b7:74;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 01:09:34 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:28:b5;CMTS-MAC=00:22:90:c6:b7:74;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 00:56:11 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:28:b5;CMTS-MAC=00:22:90:c6:b7:74;CM-QOS=1.1;CM-VER=3.0;
29-05-2016 07:59:02 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:28:b5;CMTS-MAC=00:22:90:c6:b7:74;CM-QOS=1.1;CM-VER=3.0;
 

KroontjesPen

Forum Gebruiker
Lid geworden
27 jan 2012
Berichten
1.560
Ziggo
Alles in 1
Gebied
fUPC
Mijn duit in het zakje. ???

31-05-2016 01:56:23 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 07:51:40 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 07:09:06 notice TLV-11 - unrecognized OID;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 07:09:01 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:47 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:47 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:46 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:46 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:45 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:45 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:44 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:44 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:43 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:43 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:42 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
30-05-2016 03:15:42 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=dc:53:7c:b5:a6:6d;CMTS-MAC=00:14:f1:eb:93:54;CM-QOS=1.1;CM-VER=3.0;
 

Anne-Ziggo

Webcare Ziggo
Lid geworden
4 jul 2014
Berichten
1.323
Hoi robjanssen en krootjespen,

Ik heb jullie beide net een PM gestuurd hierover. Als je nog vragen hebt dan hoor ik het graag.
 

Jasperrr

Forum Gebruiker
Lid geworden
30 aug 2010
Berichten
8
hier ook meerdere per dag:
11-06-2016 12:54:26 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:f9:38:99;CMTS-MAC=00:1f:ca:20:12:66;CM-QOS=1.1;CM-VER=3.0;
11-06-2016 11:14:39 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:f9:38:99;CMTS-MAC=00:1f:ca:20:12:66;CM-QOS=1.1;CM-VER=3.0;
11-06-2016 08:36:18 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:f9:38:99;CMTS-MAC=00:1f:ca:20:12:66;CM-QOS=1.1;CM-VER=3.0;
11-06-2016 03:27:36 critical No Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:f9:38:99;CMTS-MAC=00:1f:ca:20:12:66;CM-QOS=1.1;CM-VER=3.0;
 

Dutchy60

Forum Gebruiker
Lid geworden
23 nov 2012
Berichten
3
Ik krijg ook al enkele weken de melding: "Response received - T3 time-out"
Maar de internet snelheid is echter prima 300 Down en 30 Up

Connect Box status
Ingesteld Downstream kanaal (Hz) - 306750000 - Afgestemd
Ingesteld Upstream kanaal (Hz) - 37100000 - Bereik
Provisioning status - Gedeeltelijke service (alleen US) - Werkend

14-08-2016 03:34:56 critical No Ranging Response received - T3 time-out;CM-MAC=54:67:51:14:ba:5a;CMTS-MAC=00:01:5c:72:4c:4e;CM-QOS=1.1;CM-VER=3.0;
13-08-2016 08:19:08 critical No Ranging Response received - T3 time-out;CM-MAC=54:67:51:14:ba:5a;CMTS-MAC=00:01:5c:72:4c:4e;CM-QOS=1.1;CM-VER=3.0;
13-08-2016 05:57:19 critical No Ranging Response received - T3 time-out;CM-MAC=54:67:51:14:ba:5a;CMTS-MAC=00:01:5c:72:4c:4e;CM-QOS=1.1;CM-VER=3.0;
12-08-2016 21:04:09 critical No Ranging Response received - T3 time-out;CM-MAC=54:67:51:14:ba:5a;CMTS-MAC=00:01:5c:72:4c:4e;CM-QOS=1.1;CM-VER=3.0;
12-08-2016 05:46:03 critical No Ranging Response received - T3 time-out;CM-MAC=54:67:51:14:ba:5a;CMTS-MAC=00:01:5c:72:4c:4e;CM-QOS=1.1;CM-VER=3.0;
12-08-2016 03:46:24 critical No Ranging Response received - T3 time-out;CM-MAC=54:67:51:14:ba:5a;CMTS-MAC=00:01:5c:72:4c:4e;CM-QOS=1.1;CM-VER=3.0;
12-08-2016 02:12:14 critical No Ranging Response received - T3 time-out;CM-MAC=54:67:51:14:ba:5a;CMTS-MAC=00:01:5c:72:4c:4e;CM-QOS=1.1;CM-VER=3.0;
 

kw3ll0

Forum Gebruiker
Lid geworden
11 jul 2009
Berichten
104
Ziggo
Internet
Gebied
fUPC
2016-07-20 09:16:15: [Major] No Ranging Response received - T3 time-out;CM-MAC=fc:52:8d:17...
2016-07-20 09:15:53: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2016-07-20 09:15:24: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2016-07-20 09:15:14: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2016-07-20 09:15:13: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2016-07-20 09:14:54: [Major] Received Response to Broadcast Maintenance Request, But no Un...
2016-07-20 09:14:54: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2016-07-20 09:13:53: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2016-07-20 09:11:48: [Major] SYNC Timing Synchronization failure - Failed to acquire FEC f...
2016-07-20 09:11:47: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2016-07-20 09:11:23: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
2016-07-20 09:11:16: [Major] SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
 

patrickw

Forum Gebruiker
Lid geworden
2 okt 2010
Berichten
40
Ik heb helemaal geen problemen en heb 1 a 2 keer een t3 timeout om de paar dagen, en maak me ook geen zorgen.
Maar wat me wel opviel is dat ik vandaag terug kwam van vakantie, en in de periode dat ik weg was helemaal geen timeouts heb gehad, kwam rond half 8 's avonds thuis en op dat moment een timeout in de log. Lijkt wel zodra ik met wifi apparaten (telefoons) binnenbereik kom dat dit een t3 uitlokt.
 

Devil-Strike.net

Quality Member
Lid geworden
20 aug 2002
Berichten
16.336
Ziggo
Alles in 1
Gebied
fUPC
Ja die t3's zijn een connectbox eigen ofzo, want met alle andere modems amper tot geen t3's bij connectbox al meer dan ik in 3jaar gehad heb(gelukkig nog geen uitval gehad)

Untitled.jpg
 
Laatst bewerkt door een moderator:

Devil-Strike.net

Quality Member
Lid geworden
20 aug 2002
Berichten
16.336
Ziggo
Alles in 1
Gebied
fUPC
Ah ok, naja iig bij connectbox iig vaker last van t3 dan me ubee en nog oudere tc7200