Connect Box T3 time-outs

Als LAN en/of Wifi regelmatig wegvallen heb je wel een probleem.
Ik weet uit ervaring dat het heel vervelend is als je internet radio er meerdere malen per dag mee ophoudt. Om maar eens een voorbeeld te noemen. Daarom heb ik nu een TC7210.
 
Die internet radio is het minste probleem het steeds opnieuw moeten inloggen op je Horizon sessie van het werk is veel erger en irritanter.
Vandaag monteur langs geweest die heeft een modem omgewisseld echter ook dit is niet de oplossing (haal de snelheid niet en meerdere disconnects van die Horizon client).
Ben benieuwd hoe dit gaat aflopen.
 
Code:
System up time 15day(s)3h:9m:44s

18-05-2018 08:48:17    notice    TLV-11 - unrecognized OID;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:48:12    warning    MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:48:03    critical    No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:47:49    warning    B-INIT-RNG Failure - Retries exceeded;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:47:47    critical    No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:47:18    warning    B-INIT-RNG Failure - Retries exceeded;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:47:16    critical    No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:46:52    warning    B-INIT-RNG Failure - Retries exceeded;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:46:50    critical    No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:46:21    warning    B-INIT-RNG Failure - Retries exceeded;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:46:18    critical    No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:45:52    warning    B-INIT-RNG Failure - Retries exceeded;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:45:51    critical    No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:45:25    warning    B-INIT-RNG Failure - Retries exceeded;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:45:25    critical    No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:44:57    warning    B-INIT-RNG Failure - Retries exceeded;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:44:53    critical    No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
18-05-2018 08:44:25    warning    B-INIT-RNG Failure - Retries exceeded;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
 
Upstream bonded channels
ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
12.000260
22.000380
32.000450
42.000350
52.000380
62.000340


TimePriorityDescription

19-02-2019 14:37:25criticalNo Ranging Response received - T3 time-out;CM-MAC=8:43:7d:24:05:fa;CMTS-MAC=00:17:7:1b;CM-QOS=1.1;CM-VER=3.0;
19-02-2019 09:21:18criticalNo Ranging Response received - T3 time-out;CM-MAC=8:43:7d:24:05:fa;CMTS-MAC=00:17:17:1b;CM-QOS=1.1;CM-VER=3.0;
19-02-2019 04:38:27criticalNo Ranging Response received - T3 time-out;CM-MAC=8:43:7d:24:05:fa;CMTS-MAC=00:17:17:1b;CM-QOS=1.1;CM-VER=3.0;
18-02-2019 20:02:26criticalNo Ranging Response received - T3 time-out;CM-MAC=8:43:7d:24:05:fa;CMTS-MAC=00:17:17:1b;CM-QOS=1.1;CM-VER=3.0;
18-02-2019 18:50:10criticalNo Ranging Response received - T3 time-out;CM-MAC=8:43:7d:24:05:fa;CMTS-MAC=00:17:17:1b;CM-QOS=1.1;CM-VER=3.0;
18-02-2019 09:24:59criticalNo Ranging Response received - T3 time-out;CM-MAC=8:43:7d:24:05:fa;CMTS-MAC=00:17:17:1b;CM-QOS=1.1;CM-VER=3.0;
18-02-2019 03:07:18criticalNo Ranging Response received - T3 time-out;CM-MAC=8:43:7d:24:05:fa;CMTS-MAC=00:17:17:1b;CM-QOS=1.1;CM-VER=3.0;
17-02-2019 19:09:12criticalNo Ranging Response received - T3 time-out;CM-MAC=8:43:7d:24:05:fa;CMTS-MAC=00:17:17:1b;CM-QOS=1.1;CM-VER=3.0;
 
Code:
20-02-2019 10:37:33	critical	No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:07:59	notice	TLV-11 - unrecognized OID;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:07:55	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:07:37	critical	No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:07:35	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:07:19	warning	Lost MDD Timeout;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:07:17	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:07:13	critical	No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:05:34	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:05:15	warning	Lost MDD Timeout;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:05:09	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:05:01	notice	TLV-11 - unrecognized OID;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:04:56	warning	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:04:41	critical	No Ranging Response received - T3 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:04:33	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;
20-02-2019 09:03:58	warning	Lost MDD Timeout;CM-MAC=54:67:51:cf:c7:30;CMTS-MAC=00:17:10:95:41:a7;CM-QOS=1.1;CM-VER=3.0;[/code
 
En zonuist weer. Ditmaal wel met de errors en een herstart van het modem.

11-03-2019 21:25:23criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 21:25:02warningLost MDD Timeout;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 21:24:56criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 18:19:41criticalNo Ranging Response received - T3 time-out;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 17:34:48criticalNo Ranging Response received - T3 time-out;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 16:55:21criticalNo Ranging Response received - T3 time-out;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 10:17:29criticalNo Ranging Response received - T3 time-out;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 06:36:30criticalNo Ranging Response received - T3 time-out;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 06:22:55criticalNo Ranging Response received - T3 time-out;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
11-03-2019 01:04:58criticalNo Ranging Response received - T3 time-out;CM-MAC=38:43:7d:24:05:fa;CMTS-MAC=00:17:10:91:67:1b;CM-QOS=1.1;CM-VER=3.0;
 
Hier ook, vanaf het moment dat de TC7200 vervangen is door een TG2492, meerdere T3-timouts per dag. Dus regelmatig een wegvallende internetverbinding, welke soms niet uit zich zelf terug opkomt.

Komt volgende week een monteur langs, dus we gaan het zien...
 
Laatst bewerkt:
Is dit normaal in me modem ?


09-06-2019 01:25:39
noticeIllegal - Dropped INPUT packet: SRC=172.217.20.98 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
09-06-2019 01:24:03criticalNo Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
09-06-2019 01:23:49noticeIllegal - Dropped INPUT packet: SRC=52.114.132.74 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
09-06-2019 01:11:24noticeGUI Login Status - Login Sucess from LAN interface; client ip=[192.168.178.87];CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
09-06-2019 01:05:48noticeIllegal - Dropped INPUT packet: SRC=145.58.29.114 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 21:16:26noticeFragmented IP - SRC=185.64.189.110 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 21:16:00noticeIllegal - Dropped INPUT packet: SRC=144.43.254.33 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 20:27:41criticalNo Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 20:19:40noticeIllegal - Dropped INPUT packet: SRC=193.110.74.229 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 16:30:53criticalNo Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 16:29:53noticeIllegal - Dropped INPUT packet: SRC=52.114.128.8 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 15:34:05noticePort Scan - UDP: SRC=192.168.178.150 MAC=78:BD:BC:01:BE:B1;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 15:33:23noticeIllegal - Dropped INPUT packet: SRC=52.210.97.28 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 13:03:26criticalNo Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 13:02:40noticeIllegal - Dropped INPUT packet: SRC=13.86.126.129 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 11:55:08criticalNo Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 11:54:48noticeIllegal - Dropped INPUT packet: SRC=13.86.126.129 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 10:34:05criticalNo Ranging Response received - T3 time-out;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
08-06-2019 10:33:00noticeIllegal - Dropped INPUT packet: SRC=35.186.224.53 MAC=00:17:10:91:51:87;CM-MAC=dc:53:7c:b5:39:a4;CMTS-MAC=00:17:10:91:51:87;CM-QOS=1.1;CM-VER=3.0;
 
lijkt wel of mijn conectie door vodafoon ilegaal word gebruikt wij hebben geen vodafoon mobiels
gamen heb ik laaste tijd ook veel errors
 
Terug
Bovenaan