vgarot

Level 5
  • 61Posts
  • 2Oplossingen
  • 10Likes

WAN connection drops - T3 and T4 errors

Since a malfunction in my area yesterday (3648), my WAN connection has been pretty unstable and random disconnections are still observed

Modem is a Connect Box, in Bridge mode (Mainly because Ziggo do not allow the change of the modem IPv4 address)

Modem logs :

 

09/11/2021 22:31:4 notice LAN login Success;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx:xx;CM-QOS =1.1;CM-VER=3.0;
09/11/2021 21:27:32 Warning! RCS Partial Service;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 20:15:42 critical No Ranging Response received - T3 timeout;CM-MAC=e4:57:40:91:d3:XX;CMTS-MAC=00:01:5c:88:d8 :XX ;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 20:14:46 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00 :01:5c:88:xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 20:10:27 critical No Ranging Response received - T3 timeout;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx :xx ;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 20:07:29 Warning! RCS Partial Service;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 20:04:1 critical No Ranging Response received - T3 timeout;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx :xx ;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 20:03:6 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00 :01:5c:88:xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:59:20 critical No Ranging Response received - T3 timeout;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx :xx ;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:59:19 Warning! RCS Partial Service;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:59:18 critical No Ranging Response received - T3 timeout;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx :xx ;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:59:18 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88: xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:59:17 critical Ranging Request Retries exhausted;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx:xx;CM- QOS=1.1;CM-VER=3.0;
09/11/2021 19:59:17 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88: xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:59:17 critical Ranging Request Retries exhausted;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx:xx;CM- QOS=1.1;CM-VER=3.0;
09/11/2021 19:48:36 critical No Ranging Response received - T3 timeout;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx :xx ;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:47:40 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00 :01:5c:88:xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:43:38 critical No Ranging Response received - T3 timeout;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx :xx ;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:43:37 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88: xx:xx;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 19:43:37 critical Ranging Request Retries exhausted;CM-MAC=e4:57:40:91:xx:xx;CMTS-MAC=00:01:5c:88:xx:xx;CM- QOS=1.1;CM-VER=3.0;

89 Reacties 89
vgarot
Topicstarter
Level 5
  • 61Posts
  • 2Oplossingen
  • 10Likes

Hi @Alex ,

I have been away for a few days and couldn't closely monitor the connection.
From the router logs, less noise is observed. Last T4 was registered the 24th and a single T3 was observed 3 days later. Rebooting the router now to get fresh stats, I'll resume monitoring of the connection and logs during the upcoming days and report back here again.

28-12-2021 21:38:15 warning [38:43:7D:C1:79:C6][DFS] Radar signal detected, DFS sequence applied, channel changed from 112 to 44
27-12-2021 22:02:05 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
27-12-2021 15:02:06 critical No Ranging Response received - T3 time-out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
24-12-2021 10:02:23 notice REGISTRATION COMPLETE - Waiting for Operational status;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
24-12-2021 10:02:15 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
24-12-2021 09:48:51 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
24-12-2021 09:46:13 warning Lost MDD Timeout;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
24-12-2021 09:46:09 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
24-12-2021 09:40:19 notice REGISTRATION COMPLETE - Waiting for Operational status;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
24-12-2021 09:40:11 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
24-12-2021 09:37:19 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;


Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 0 0
2 2.0 0 0 0 0
3 2.0 0 0 1 0
4 2.0 0 0 0 0

 

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.983 15414571921 54
2 Locked 38.605 15413623636 40
3 Locked 38.983 15413628762 47
4 Locked 38.605 15413628537 78
5 Locked 37.636 15413623182 79
6 Locked 38.605 15413623987 73
7 Locked 38.605 15413622403 70
8 Locked 38.605 15413624482 67
9 Locked 38.605 15413624201 56
10 Locked 37.636 15413624680 55
11 Locked 38.605 15413624510 64
12 Locked 38.605 15413625331 93
13 Locked 37.636 15413625119 106
14 Locked 37.636 15413625314 60
15 Locked 37.636 15413626687 144
16 Locked 37.636 15413619842 914
17 Locked 37.636 15413626490 976
18 Locked 37.636 15413625742 165
19 Locked 37.356 15413625920 139
20 Locked 37.356 15413625700 192
21 Locked 36.610 15413625788 264
22 Locked 37.356 15413620154 253
23 Locked 36.610 15413623029 229
24 Locked 36.387 15413624798 336


Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 618000000 5 38 256qam 3
2 602000000 5 38 256qam 1
3 610000000 5 38 256qam 2
4 626000000 4 38 256qam 4
5 634000000 4 37 256qam 5
6 642000000 4 38 256qam 6
7 650000000 5 38 256qam 7
8 658000000 5 38 256qam 8
9 666000000 5 38 256qam 9
10 674000000 5 37 256qam 10
11 682000000 5 38 256qam 11
12 690000000 5 38 256qam 12
13 698000000 4 37 256qam 13
14 706000000 5 37 256qam 14
15 714000000 5 37 256qam 15
16 722000000 5 37 256qam 16
17 730000000 4 37 256qam 17
18 738000000 4 37 256qam 18
19 754000000 4 37 256qam 20
20 770000000 3 37 256qam 22
21 786000000 3 36 256qam 24
22 794000000 3 37 256qam 25
23 802000000 3 36 256qam 26
24 850000000 3 36 256qam 32



tobiastheebe

Level 20
T.E.A.M.
  • 31066Posts
  • 2181Oplossingen
  • 15502Likes

Signal data is looking good from December 24, 10:02 onward. Downstream still exhibits some noise on a number of channels.

vgarot
Topicstarter
Level 5
  • 61Posts
  • 2Oplossingen
  • 10Likes

Connection has been stable for since Dec 30th 09:30 AM.
Noise is increasing on some channels, meanly on the ones with MER values lower than 36.5db

uptime : 4day(s)1h:18m:40s

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.605 11949756397 39
2 Locked 37.636 11948526642 65
3 Locked 38.605 11948526461 63
4 Locked 37.636 11948524950 63
5 Locked 37.636 11948527494 77
6 Locked 38.983 11948529352 50
7 Locked 37.636 11948530902 75
8 Locked 38.605 11948529931 92
9 Locked 38.605 11948531271 58
10 Locked 37.636 11948522554 78
11 Locked 37.636 11948523023 116
12 Locked 37.636 11948532029 133
13 Locked 37.356 11848970805 203
14 Locked 37.356 11948515598 8340
15 Locked 37.356 11844940447 6227
16 Locked 37.356 11948533689 422
17 Locked 37.356 11948533116 267
18 Locked 36.610 11948534267 295
19 Locked 36.387 11948533963 1132
20 Locked 36.610 11948524810 1574
21 Locked 36.387 11948534771 642
22 Locked 36.387 11294721436 292422
23 Locked 36.387 11547632019 336368
24 Locked 36.610 11630990391 63680

A few T3 timeouts are observed, but fortunately not a single T4 :

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 1 0
2 2.0 0 0 1 0
3 2.0 0 0 0 0
4 2.0 0 0 1 0

03-01-2022 04:01:35 critical No Ranging Response received - T3 time-out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
02-01-2022 21:30:11 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
02-01-2022 10:54:58 critical No Ranging Response received - T3 time-out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
30-12-2021 15:53:51 warning [38:43:7D:C1:79:C6][DFS] Radar signal detected, DFS sequence applied, channel changed from 64 to 48
30-12-2021 09:30:28 notice REGISTRATION COMPLETE - Waiting for Operational status;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
30-12-2021 09:30:20 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 01:01:25 notice Cable Modem Reboot - due to power reset;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Monitoring stack has not registered packets loss in that timeframe, with nice ping latencies below 20ms

vgarot_0-1641203926774.png

 

In short : There is noise on some channels but the WAN connection is stable since last intervention in the EV.
I'll provide another update by the end of this week.

Paul
Community Moderator
Community Moderator
  • 19178Posts
  • 1373Oplossingen
  • 7281Likes

@vgarot Thank you very much for the extensive update! What are your own findings when using the internetconnection, apart from the Pre en post RS error notifications ? We look forward to you next update.

vgarot
Topicstarter
Level 5
  • 61Posts
  • 2Oplossingen
  • 10Likes

@Paul . The connection is stable and I've not observed any WAN drop since the HW replacement in the EV.

The noise on the low MER values channels added to the T3s timeouts still observed is s bit concerning, but as stated previously I have not observed any relevant impact on the connection.

 

11day(s)0h:21m:32s

 

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.605 32429304181 80
2 Locked 37.636 32428074404 166
3 Locked 38.605 32428074260 117
4 Locked 37.356 32428072750 156
5 Locked 37.636 32428075284 169
6 Locked 38.983 32428077228 125
7 Locked 37.636 32428078747 183
8 Locked 38.605 32428077732 225
9 Locked 38.605 32428079146 119
10 Locked 37.356 32428070339 158
11 Locked 37.636 32428070746 265
12 Locked 37.356 32428078291 331
13 Locked 37.356 32328517077 333
14 Locked 37.636 32401164296 16574
15 Locked 37.636 32324457891 16128
16 Locked 37.356 32428077708 923
17 Locked 37.356 32428077574 666
18 Locked 36.610 32428078515 839
19 Locked 36.610 32428078224 1659
20 Locked 36.387 32428067464 2071
21 Locked 36.387 32428076919 1651
22 Locked 36.610 31161606369 698478
23 Locked 36.610 31616207259 601087
24 Locked 36.387 31923696369 125250

 

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 3 0
2 2.0 0 0 2 0
3 2.0 0 0 1 0
4 2.0 0 0 1 0

 

Time Priority Description
09-01-2022 21:30:05 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
09-01-2022 09:46:42 notice GUI Login Status - Login Sucess from LAN interface; client ip=[80.115.14.173];CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
08-01-2022 23:12:27 critical No Ranging Response received - T3 time-out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
06-01-2022 10:41:46 notice GUI Login Status - Login Sucess from LAN interface; client ip=[80.115.14.173];CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
06-01-2022 09:30:08 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
06-01-2022 02:35:33 critical No Ranging Response received - T3 time-out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
05-01-2022 09:06:40 notice GUI Login Status - Login Sucess from LAN interface; client ip=[80.115.14.173];CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
04-01-2022 02:23:48 critical No Ranging Response received - T3 time-out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
03-01-2022 10:44:29 notice GUI Login Status - Login Sucess from LAN interface; client ip=[80.115.14.173];CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
03-01-2022 04:01:35 critical No Ranging Response received - T3 time-out;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
02-01-2022 21:30:11 error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
30-12-2021 15:53:51 warning [38:43:7D:C1:79:C6][DFS] Radar signal detected, DFS sequence applied, channel changed from 64 to 48
30-12-2021 09:30:28 notice REGISTRATION COMPLETE - Waiting for Operational status;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
01-01-1970 01:01:25 notice Cable Modem Reboot - due to power reset;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

 

vgarot_0-1641805083272.png


@tobiastheebe cc'ing you once again, your technical expertise has been very valuable in all this investigation.

tobiastheebe

Level 20
T.E.A.M.
  • 31066Posts
  • 2181Oplossingen
  • 15502Likes

A number of channels exhibits ingress noise. Uncorrectable errors may be present on C# 13-15 and 22-24, these would be responsible for packet loss.

 

Has the modem still been connected directly to the AOP?

vgarot
Topicstarter
Level 5
  • 61Posts
  • 2Oplossingen
  • 10Likes

@tobiastheebe Modem is connected directly to the AOP but using a longer than recommended cable (10m). 
I'll connect a 1M cable (provided by Ziggo), test again for a few days and report back here.

Paul
Community Moderator
Community Moderator
  • 19178Posts
  • 1373Oplossingen
  • 7281Likes

@vgarot We are very curious in regards to your findings after you've changed the setup by directly connecting the modem to the AOP (1 meter cable). 

vgarot
Topicstarter
Level 5
  • 61Posts
  • 2Oplossingen
  • 10Likes

Hi @Paul , thanks for the follow up.
Connections has been rock solid for a month, not a single wan drop observed. 
Below are the values for 32 days uptime :

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 95236064851 436
2 Locked 37.636 95234834522 978
3 Locked 38.605 95234834630 740
4 Locked 37.356 95234833234 638
5 Locked 37.636 95234835785 621
6 Locked 37.356 95234837741 566
7 Locked 37.636 95234839003 815
8 Locked 37.356 95234837910 995
9 Locked 36.610 95234839380 790
10 Locked 37.636 95234830671 831
11 Locked 37.636 95234830905 1087
12 Locked 37.356 95234839950 1053
13 Locked 37.356 95078811629 1877
14 Locked 37.636 94504926480 85996
15 Locked 37.636 94032309004 76023
16 Locked 36.610 95234839312 2511
17 Locked 36.610 95234839549 2016
18 Locked 36.610 95234840072 2682
19 Locked 36.610 95175403636 644635
20 Locked 36.610 95234539555 294179
21 Locked 36.610 95234838037 5224
22 Locked 36.387 91361838576 1278900
23 Locked 36.387 90532288235 1239823
24 Locked 36.387 91253255139 539721

 

A T3 timeout is registered every 7 to 10 days in the logs, but no impact on the connectivity is observed.

 

I will finally not connect back the modem to the AOP with a 1m cable. I understand this is the recommendation but it doesn't suit my needs. 
In case I would observe new drops in the future, I will connect the 1m cable, analyze the logs and reach out again if needed.

Feel free to mark this as resolved.
Thanks again to anyone involved @tobiastheebe 

Cheers,
Vivien

Paul
Community Moderator
Community Moderator
  • 19178Posts
  • 1373Oplossingen
  • 7281Likes

@vgarot You're welcome! We're glad to read that the problem has been resolved so you can enjoy the internetconnection to the fullest. For the period you couldn't fully utilize our services I've arranged a compensation as described in our terms and conditions. You'll notice the compensation as a deduction on the next invoices. If there's anytthing else we can you with, please let us know. I wish you a very nice day!

Uitgelicht topic