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

WAN stability has much improved since the cable has been replaced and the previously observed noise decreased drastically.

But critical t3 and t4 are still observed.

 

System up time : 2day(s)22h:12m:0s

 

10-12-2021 08:52: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;
09-12-2021 05:55:58 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;
09-12-2021 05:55:51 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;
09-12-2021 05:55: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;
09-12-2021 05:55:05 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;
09-12-2021 05:51:05 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;

 

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

 

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 3313996747 38
2 Locked 37.636 3312897877 53
3 Locked 38.605 3312898082 27
4 Locked 37.356 3312897817 52
5 Locked 37.356 3312898235 56
6 Locked 37.636 3312898108 43
7 Locked 37.356 3312896538 42
8 Locked 37.636 3312898050 33
9 Locked 38.605 3312895833 21
10 Locked 37.636 3312897733 26
11 Locked 37.636 3312893437 37
12 Locked 37.636 3312895974 51
13 Locked 37.356 3312897827 63
14 Locked 37.636 3312898642 40
15 Locked 37.356 3312898429 59
16 Locked 37.356 3312898964 45
17 Locked 37.356 3312897137 67
18 Locked 37.356 3312892528 65
19 Locked 36.610 3312892019 61
20 Locked 36.610 3312898041 39
21 Locked 36.610 3312894783 39
22 Locked 37.356 3312897662 69
23 Locked 36.610 3312898117 99
24 Locked 36.610 3312899042 47

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

WAN stability has much improved since the cable has been replaced and the previously observed noise decreased drastically.

But critical t3 and t4 are still observed.

 

System up time : 2day(s)22h:12m:0s

 

10-12-2021 08:52: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;
09-12-2021 05:55:58 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;
09-12-2021 05:55:51 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;
09-12-2021 05:55: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;
09-12-2021 05:55:05 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;
09-12-2021 05:51:05 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;

 

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

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

System up time : 4day(s)1h:51m:35s

 

11-12-2021 00:58:57 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;
10-12-2021 08:52: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;
09-12-2021 05:55:58 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;
09-12-2021 05:55:51 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;
09-12-2021 05:55: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;
09-12-2021 05:55:05 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;
09-12-2021 05:51:05 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;

 

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

 

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 6706326518 58
2 Locked 37.636 6705227691 65
3 Locked 38.605 6705227856 39
4 Locked 37.636 6705227638 66
5 Locked 37.636 6705228150 73
6 Locked 37.636 6705228036 66
7 Locked 37.356 6705226497 55
8 Locked 37.356 6705228050 46
9 Locked 37.636 6705225850 27
10 Locked 37.636 6705227752 30
11 Locked 37.636 6705223441 57
12 Locked 37.636 6705225988 72
13 Locked 37.356 6705227840 89
14 Locked 37.356 6705228760 49
15 Locked 37.356 6705228514 89
16 Locked 37.356 6705229078 56
17 Locked 36.610 6705228848 102
18 Locked 37.356 6705224258 98
19 Locked 36.610 6705222369 90
20 Locked 36.610 6705228357 66
21 Locked 36.610 6705225097 61
22 Locked 37.356 6705228012 88
23 Locked 36.610 6705228446 153
24 Locked 36.610 6705229324 79

tobiastheebe

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

On December 9, the modem restarted its cable interface at 5:55 due to a T4 timeout. No CMTS connection could be established for approximately 30 seconds. Without having available the DS/US signal data, present before the restart, it is difficult to determine if DS noise occurred temporarily or if there was another trigger for the T4 timeout. A moderator might be able to shed more light on this by looking at the historical signal data.

 

While only a single T3 timeout was logged between the re-registration on December 9 and December 10, 8:52, 17 additional T3 timeouts were logged from December 10, 8:52, until December 11, 0:58. This implies approximately one T3 timeout every hour during above timespan, which is not acceptable.

 

The accumulated unerrored/correctable RS errors, valid from December 9, 5:55, are looking good. Ideally though, the MER values would be slightly higher (around 38 dB on all channels).

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

@vgarot Thanks you very much for sharing this new data. I had a look at the connection, and the signal itself seems to be all right. What are your own findings in regards to the internetconnection (apart from the T3/T4 notification in the modemlog), at the times you're using it?

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

Hi @Paul,
So far the WAN connection is stable and I observe less drops (telegraf+influxdb+grafana stack)

vgarot_0-1639400342131.png


I have added some more granular monitoring and will report back here in a few days

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

@vgarot Thanks for your report! Good to read that the findings so far are positive. We are wondering what your findings in regards to the connections from the past days are. 

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

@Paul WAN connection has been solid for 4 days, no interruption of service observed during that timeframe.
Unfortunately I just had new T4s with associated connection lost due to modem resetting itself.
Around 20 mins of disconnection (from 15-12-2021 13:44 till 15-12-2021 14:08)

 

4day(s)0h:38m:36s


Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 11851486340 184
2 Locked 37.636 11850273932 177
3 Locked 37.356 11850284337 238
4 Locked 37.356 11850284195 228
5 Locked 37.636 11850280326 182
6 Locked 37.356 11850275303 236
7 Locked 37.636 11850284305 232
8 Locked 37.636 11850275695 151
9 Locked 37.356 11850284678 189
10 Locked 37.636 11850285159 231
11 Locked 37.636 11850275701 302
12 Locked 37.356 11850286146 266
13 Locked 37.636 11850285238 267
14 Locked 37.356 11850263960 17595
15 Locked 37.356 11764663770 11219
16 Locked 36.387 11850235903 38496
17 Locked 36.610 11850279738 600
18 Locked 36.610 11850286976 373
19 Locked 36.610 11850287447 403
20 Locked 36.610 11850287856 512
21 Locked 36.610 11850274394 537
22 Locked 36.610 11850277833 285
23 Locked 36.610 11850279334 693
24 Locked 36.387 11850276767 11572


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 17 0
2 2.0 0 0 16 0

15-12-2021 14:08:33 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;
15-12-2021 14:08:25 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;
15-12-2021 14:08:08 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;
15-12-2021 14:07:45 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;
15-12-2021 14:07:15 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;
15-12-2021 14:06:35 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;
15-12-2021 14:06:27 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;
15-12-2021 14:05:59 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;
15-12-2021 13:50:23 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;
15-12-2021 13:50:05 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;
15-12-2021 13:49:56 notice GUI Token verify failed; 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;
15-12-2021 13:49:39 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;
15-12-2021 13:45:39 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;
15-12-2021 13:45:13 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
15-12-2021 13:45:13 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
15-12-2021 13:45:12 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;
15-12-2021 13:45:09 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
15-12-2021 13:45:09 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
15-12-2021 13:45:08 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;
15-12-2021 13:45:07 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;

From monitoring perspective (ping every 15 sec)

vgarot_0-1639576601775.png

 



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

@Paul  And just got another outage due to T4. 10 mins span this time
Managed to pull the stats before the cable reset. I'm no expert but noises level seem high for a 20 hours timeframe. 700 post RS average with up to 8k errors on channel 23

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.356 2736627938 659
2 Locked 37.636 2767698330 805
3 Locked 37.636 2767697883 777
4 Locked 37.636 2767698321 808
5 Locked 37.636 2767697445 799
6 Locked 37.636 2767698746 689
7 Locked 37.636 2767698626 753
8 Locked 37.356 2767699194 603
9 Locked 37.356 2767699142 628
10 Locked 37.356 2767699914 623
11 Locked 37.356 2767696767 694
12 Locked 37.636 2767699386 703
13 Locked 37.636 2767699421 710
14 Locked 37.356 2767696210 3630
15 Locked 37.356 2767696922 2827
16 Locked 36.610 2767700405 638
17 Locked 36.610 2767700593 649
18 Locked 36.387 2767695172 683
19 Locked 36.387 2767701677 824
20 Locked 36.387 2767701660 687
21 Locked 36.387 2767701513 901
22 Locked 36.387 2767701540 1392
23 Locked 36.387 2767691410 8807
24 Locked 36.610 2669891975 6313

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 58800000 46 5.120 64qam 4

Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 48 0

16-12-2021 12:44:00 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;
16-12-2021 12:43:52 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;
16-12-2021 12:43:31 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;
16-12-2021 12:43:03 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;
16-12-2021 12:39:03 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;
16-12-2021 12:38:32 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 12:38:32 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 12:38:30 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 12:38:30 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 12:38:09 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 12:38:09 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 12:38:07 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;
16-12-2021 09:59:47 warning [38:43:7D:C1:79:C6][DFS] Radar signal detected, DFS sequence applied, channel changed from 100 to 36
16-12-2021 07:05:28 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;

 

vgarot_0-1639655389332.png


The mechanic replaced around 5m of cable, with a armored on. It definitively helped decreased the noise but not totally. Maybe the cable from the EV is damaged a bit further.
@tobiastheebe what's your insights on this please ? Thanks.

tobiastheebe

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

It appears that the excess downstream noise has partially returned. No more than ~50 correctable codewords per channel should be accumulated after a 20-hour uptime. For reference, my modem's per-channel correctable codewords are 91 on average, after a 48-day uptime. Furthermore, the modem has dropped all but one of the upstream channels. The data you posted yesterday shows 2/4 US channels missing.

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

@Paul . Another 10 mins outage with T4.
30 mins apart from the previous one ....
This issue is 1 month old already !! This is no acceptable

 

Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 69 0


16-12-2021 13:21:52 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;
16-12-2021 13:21:44 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;
16-12-2021 13:21:26 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;
16-12-2021 13:20:59 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;
16-12-2021 13:16:59 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;
16-12-2021 13:16:56 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:16:56 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:16:55 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;
16-12-2021 13:16:27 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:16:27 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:16: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;
16-12-2021 13:15:52 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:15:52 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:15:51 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;


Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 76529415 23
2 Locked 37.356 75491917 27
3 Locked 38.605 75488990 18
4 Locked 37.356 75492549 26
5 Locked 37.636 75490306 21
6 Locked 38.605 75489471 20
7 Locked 37.356 75490297 35
8 Locked 37.636 75490471 23
9 Locked 37.636 75490250 15
10 Locked 37.636 75490967 15
11 Locked 37.356 75486731 16
12 Locked 37.636 75490615 15
13 Locked 37.356 75491412 21
14 Locked 37.356 75485109 10
15 Locked 36.610 75489688 24
16 Locked 36.610 75485075 15
17 Locked 36.610 75491335 14
18 Locked 36.387 75490476 13
19 Locked 36.387 75490217 29
20 Locked 36.387 75482866 40
21 Locked 36.387 75488817 40
22 Locked 36.610 75479573 45
23 Locked 36.387 75484613 36
24 Locked 36.610 75489281 11


10 mins after reset ... 1 T3, 50 post RS average ... :

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


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.356 10377159 69
2 Locked 37.636 9413580 56
3 Locked 37.636 9412750 51
4 Locked 37.356 9413146 33
5 Locked 37.636 9412914 37
6 Locked 37.356 9413700 43
7 Locked 37.636 9411137 43
8 Locked 37.356 9413990 42
9 Locked 37.356 9413791 49
10 Locked 36.387 9414571 54
11 Locked 36.387 9414395 58
12 Locked 36.387 9415230 44
13 Locked 36.610 9409956 50
14 Locked 36.387 9414862 43
15 Locked 36.387 9415537 58
16 Locked 36.610 9410209 43
17 Locked 36.387 9415168 59
18 Locked 36.387 9415971 38
19 Locked 36.387 9415811 65
20 Locked 35.780 9416645 67
21 Locked 35.973 9416528 43
22 Locked 36.387 9407120 82
23 Locked 36.387 9418534 76
24 Locked 36.387 9419040 42

cc @tobiastheebe 

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

@vgarot I'm very sorry that the problem still persists! I've reported your findings back to our network department for further investigation. I'll let you know as soon as I have an update about the next steps. 

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

Another T4 10 mins outage. 
This mins 3 outage in 90 mins, downtime cumulative during this period is 40 mins ....

 

 

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 57918760 469
2 Locked 37.636 56955322 381
3 Locked 37.636 51920439 246
4 Locked 37.356 56955101 265
5 Locked 37.356 56954868 317
6 Locked 37.356 56955686 309
7 Locked 37.636 56953174 319
8 Locked 37.356 56956021 329
9 Locked 37.636 56955874 304
10 Locked 36.610 56956740 313
11 Locked 36.610 56956491 302
12 Locked 36.610 56957421 253
13 Locked 36.610 56952181 238
14 Locked 36.387 56957065 220
15 Locked 36.610 56957839 238
16 Locked 36.387 56952538 231
17 Locked 36.387 56957283 270
18 Locked 36.387 56958181 247
19 Locked 36.610 56957986 288
20 Locked 36.387 56958760 316
21 Locked 36.387 56958588 251
22 Locked 36.387 56949211 320
23 Locked 36.610 56960619 276
24 Locked 36.387 56961177 208

Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 89 0

16-12-2021 13:53:35 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;
16-12-2021 13:53:27 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;
16-12-2021 13:53:08 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;
16-12-2021 13:52:41 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;
16-12-2021 13:48:41 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;
16-12-2021 13:48:37 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:48:37 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:48:37 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;
16-12-2021 13:48:03 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:48:03 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:48:02 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;
16-12-2021 13:47:40 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:47:40 critical Ranging Request Retries exhausted;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
16-12-2021 13:47:38 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;

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

- Last cable reset at 16-12-2021 14:24:41:

16-12-2021 14:24:41 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;

- Noise on all channels :

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.356 2362057722 66127
2 Locked 37.636 2360931425 81482
3 Locked 37.356 2360933251 79408
4 Locked 37.636 2360934521 77888
5 Locked 37.636 2360936981 75413
6 Locked 37.636 2360964400 47968
7 Locked 37.356 2357630288 39079
8 Locked 37.356 2359959909 30575
9 Locked 37.356 2360967439 45068
10 Locked 37.356 2360957050 56258
11 Locked 36.610 2360963159 50514
12 Locked 36.387 2360987954 25618
13 Locked 36.610 2360987689 26093
14 Locked 36.610 2360991392 23186
15 Locked 36.387 2360983373 30027
16 Locked 36.387 2360984439 30718
17 Locked 36.610 2360972861 41777
18 Locked 36.387 2360975123 40635
19 Locked 36.387 2360967243 48268
20 Locked 36.387 2360967692 49376
21 Locked 36.387 2360964068 48619
22 Locked 36.387 2360959850 47148
23 Locked 36.387 2360980687 32002
24 Locked 36.387 2360999191 16737

- T3 observed on 3 channels out of 4 :

Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 23 0
2 2.0 0 0 132 0
3 2.0 0 0 138 0
4 2.0 0 0 0 0

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

@vgarot I've discussed the problem with our network engineers. We still notice issues with the signal on your connection. To resolve this I've planned a new appointment with a network engineer on the 20th of December 2021 between 8 and 13.  I've provided the engineer's receipt with an extensive report containing my findings in regards to the signalissues. In case the appointment doesn't suite you on this date, you can change the appointment via My Ziggo. 

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

@vgarot Unfortunately something went wrong with the planned appointment! Therefore I'm very sorry. I've planned a new appointment with a senior engineer on the 23rd of December between 12 and 18 o 'clock. You can reschedule the appointment via My Ziggo in case it doesn't suite you. I've also included the extensive report containing my findings in regards to the signal. This way it should be easier for the engineer to pinpoint the problem. 

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

Thanks @Paul.

The new date is fine. I thought the first one was cancelled due to lockdown

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

@Paul Today's FE findings:
- Internal house cabling is good but he observed some noise on the line at the AOP level. Decided to replace the socket again, didn't improve.
- He checked the EV in the street and has observed some signal issues there if measuring for a while (apparently not detected doing a short measurement).
- He will open a new ticket so someone can check/fix the EV again (That would be the third time ... )
- He also said the main cable might be damaged

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

@vgarot Thank you very much for your extensive report back to us. I see that the engineer raised a networkticket with ticketnumber TTS693556 for further investigation of our network. Depening on what the specialists find this may result in a Cabledamage ticket towards one of the contractors in the area. I suggest we'll wait for the outcome. Hopefully the problem will be resolved soon.

Alex
Community Moderator
Community Moderator
  • 8992Posts
  • 1059Oplossingen
  • 4003Likes

Hi @vgarot,

 

The networkticket was solved this week by replacing hardware in the EV. How's your connection at the moment?

Uitgelicht topic