vgarot

Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

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;

86 Reacties 86
vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

Several T3 and T4 Timeouts in less than 12 hours after direct connection of the modem to the AOP with the 1,5m coax cable  :

17-11-2021 02:34: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;
17-11-2021 00:47:01 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;
17-11-2021 00:46:54 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;
17-11-2021 00:46: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;
17-11-2021 00:46: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;
17-11-2021 00:42: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;
17-11-2021 00:42: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;
17-11-2021 00:42: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;
17-11-2021 00:42: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;
17-11-2021 00:41:16 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;
17-11-2021 00:41:16 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;
17-11-2021 00:40:53 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;
17-11-2021 00:40:53 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;
17-11-2021 00:40: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;

Now we made clear the issue is not the coax cable from the AOP to the modem, nor the modem itself, what's the next step ?

tobiastheebe
Super Expert
Super Expert
  • 5697Posts
  • 319Oplossingen
  • 1892Likes

A specialized (network) technician should verify the cable feed from AOP to EV (street cabinet). Earlier I noticed that the outdoor cable has been extended with an indoor cable, somewhere inside your house. This needs specific attention.

 

The moderators have been notified and one of them will reply within 24 hours.

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

Thanks @tobiastheebe 
I'm working from home and have to rely on my mobile connection. When I have to download/upload a lot of data I end up hitting my phone provider daily data limit, which basically screws me for the rest of the day.
This issue is starting to get really frustrating.

Latest status, 2 disconnect in less than 30 mins :

17-11-2021 12:43: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;
17-11-2021 12:43:44 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;
17-11-2021 12:43:44 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;
17-11-2021 12:43:44 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;
17-11-2021 12:43: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;
17-11-2021 12:43: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;
17-11-2021 12:43:29 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;
17-11-2021 12:42:41 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;
17-11-2021 12:42:41 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;
17-11-2021 12:42:16 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;
17-11-2021 12:26:02 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;
17-11-2021 12:25:53 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;
17-11-2021 12:25: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;
17-11-2021 12:25:08 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;
17-11-2021 12:21: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;
17-11-2021 12:20:42 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;
17-11-2021 12:20:42 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;
17-11-2021 12:20:42 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;

Item Status Comments
Acquired Downstream Channel(Hz) 634000000 Locked
Ranged Upstream Channel(Hz) 0 Ranged
Provisioning State Partial Service (US only) Operational


Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 45189062 26
2 Locked 37.636 44267081 30
3 Locked 38.605 44267945 29
4 Locked 38.605 44266812 28
5 Locked 38.605 44267633 30
6 Locked 37.636 44268447 34
7 Locked 37.356 44268308 25
8 Locked 37.636 44265714 25
9 Locked 37.356 44268922 21
10 Locked 37.636 44268730 28
11 Locked 37.356 44267883 27
12 Locked 37.356 44268616 108
13 Locked 37.636 44267662 1542
14 Locked 37.636 44270015 36
15 Locked 37.356 44269877 35
16 Locked 37.636 44264025 34
17 Locked 37.356 44270025 19
18 Locked 37.356 44270182 20
19 Locked 37.356 44270331 29
20 Locked 36.387 44261868 25
21 Locked 36.610 44270011 20
22 Locked 36.387 44267392 39
23 Locked 36.610 44270310 33
24 Locked 36.610 44270421 74

 

Jacob
Community Moderator
Community Moderator
  • 930Posts
  • 47Oplossingen
  • 151Likes

@vgarot thanks for the explanation. You're right, this requires extra attention.

That is why I schedule a technician again with these specific data from your measurement. This will be Thursday, November 18 between 12:00-18:00.

Doesn't this fit? In a few hours you can adjust the appointment yourself via your My Ziggo account. Can you please let us know what the mechanic's conclusion is? 

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

@Jacob Thanks for the new appointment. The scheduled time works for me.
I understand the technician is requested to check the feed between the AOP and the EV. I'll report his conclusion afterwards.
If possible/allowed by Ziggo I will also have him perform the same check from my 2 neighbors, whom also complained recently about disconnections.

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

As additional info, please find below the modem stats from my neighbor (same street, next house number)

T3 Timeouts and high post rs errors number

vgarot_1-1637168769589.png

 

vgarot_2-1637168799493.png

 

vgarot_3-1637168833523.png

 

 

tobiastheebe
Super Expert
Super Expert
  • 5697Posts
  • 319Oplossingen
  • 1892Likes

Their modem exhibits even more signal problems than yours (weak signal, excessive noise on all DS and US channels). Its overall signal strength and quality are very poor.

 

The network technician should definitely carry out measurements on street level.

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

Mechanic's conclusion is the problem is in the street, in the EV.

He said that :
- My house's cabling is fine.
- From his laptop he could see the neighbors in the street are also getting a bad signal.
- He will arrange for another mechanic to be sent to check/fix the EV.

Note : Rather short intervention, he just took a single reading from my AOP and deemed not necessary take readings from the neighbors' AOP.

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

Would appreciate if Ziggo can inform me (here or email or phone call) once the EV intervention is complete, so I can keep the modem under close monitoring afterwards.

Maud
Community Moderator
Community Moderator
  • 1570Posts
  • 141Oplossingen
  • 241Likes

@vgarot, ah good the read that the technician took action. I see there was an outage yesterday until today. They checked the EV. Can you send the up and downstream details again? Then we can take a look at it. And how is the internet working just now? The signal from here looks fine.

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

Hi @Maud. IF they checked the EV from my end it doesn't look fixed. Just got a T4 timeout 10 mins ago.
From the logs I can't see any service interruption between the technician intervention yesterday 18-11-2021 12:57  till the T3-T4's today 19-11-2021 16:57.
Can't see the outage you're referring too.

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 2.0 0 0 16 0
2 2.0 0 0 16 0

 

19-11-2021 17:03:45 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;
19-11-2021 17:03:37 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;
19-11-2021 17:03:01 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;
19-11-2021 16:59:01 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;
19-11-2021 16:58:01 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;
19-11-2021 16:57: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;
19-11-2021 16:57: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;
19-11-2021 16:57: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;
19-11-2021 16:57: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;
19-11-2021 16:57: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;
18-11-2021 18:38:07 warning [38:43:7D:C1:79:C6][DFS] Radar signal detected, DFS sequence applied, channel changed from 112 to 44
18-11-2021 12:57:51 notice MDD Recovery following MDD Loss;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
18-11-2021 12:57:39 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;
18-11-2021 12:57:32 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;
18-11-2021 12:57:23 notice MDD Recovery following MDD Loss;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
18-11-2021 12:56:45 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;
18-11-2021 12:56:39 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;


Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 4313859870 305
2 Locked 38.605 4312521260 225
3 Locked 38.605 4312520773 237
4 Locked 38.605 4312516529 231
5 Locked 38.983 4312521015 287
6 Locked 37.636 4312517319 286
7 Locked 38.605 4312519768 301
8 Locked 38.605 4312520819 327
9 Locked 37.636 4312521006 308
10 Locked 37.636 4312519910 351
11 Locked 37.636 4312513023 353
12 Locked 37.636 4312519495 295
13 Locked 37.636 4312519694 300
14 Locked 37.636 4312509778 389
15 Locked 37.356 4312513383 3452
16 Locked 37.356 4312512496 4387
17 Locked 37.636 4312510562 6016
18 Locked 37.636 4312511231 296
19 Locked 37.356 4312484047 343
20 Locked 37.356 4312516748 235
21 Locked 37.356 4312484188 290
22 Locked 37.356 4312486223 328
23 Locked 37.356 4312482141 313
24 Locked 37.356 4312483249 433

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 4313859870 305
2 Locked 38.605 4312521260 225
3 Locked 38.605 4312520773 237
4 Locked 38.605 4312516529 231
5 Locked 38.983 4312521015 287
6 Locked 37.636 4312517319 286
7 Locked 38.605 4312519768 301
8 Locked 38.605 4312520819 327
9 Locked 37.636 4312521006 308
10 Locked 37.636 4312519910 351
11 Locked 37.636 4312513023 353
12 Locked 37.636 4312519495 295
13 Locked 37.636 4312519694 300
14 Locked 37.636 4312509778 389
15 Locked 37.356 4312513383 3452
16 Locked 37.356 4312512496 4387
17 Locked 37.636 4312510562 6016
18 Locked 37.636 4312511231 296
19 Locked 37.356 4312484047 343
20 Locked 37.356 4312516748 235
21 Locked 37.356 4312484188 290
22 Locked 37.356 4312486223 328
23 Locked 37.356 4312482141 313
24 Locked 37.356 4312483249 433


Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 44500000 41 5.120 64qam 2
2 58800000 41 5.120 64qam 4
3 36000000 40 5.120 64qam 3
4 52000000 41 5.120 64qam 1

ownstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 634000000 5 37 256qam 5
2 602000000 6 37 256qam 1
3 618000000 5 38 256qam 3
4 626000000 5 37 256qam 4
5 642000000 5 37 256qam 6
6 650000000 5 38 256qam 7
7 658000000 6 38 256qam 8
8 666000000 6 37 256qam 9
9 698000000 5 37 256qam 13
10 706000000 4 37 256qam 14
11 722000000 4 37 256qam 16
12 730000000 4 37 256qam 17
13 738000000 4 37 256qam 18
14 746000000 4 37 256qam 19
15 754000000 5 37 256qam 20
16 762000000 4 37 256qam 21
17 770000000 4 37 256qam 22
18 778000000 4 37 256qam 23
19 786000000 3 36 256qam 24
20 802000000 4 36 256qam 26
21 818000000 4 35 256qam 28
22 826000000 4 36 256qam 29
23 834000000 4 36 256qam 30
24 842000000 4 36 256qam 31

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

Stats taken at 19-11-2021 17:18 (15 mins after the 17:03 T4 timeout modem auto reset)

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 30934411 6
2 Locked 37.636 30133379 7
3 Locked 38.605 30133900 4
4 Locked 37.636 30133715 5
5 Locked 37.636 30132852 8
6 Locked 38.605 30134699 5
7 Locked 38.605 30134510 7
8 Locked 37.636 30134327 6
9 Locked 37.636 30134428 6
10 Locked 37.356 30136310 13
11 Locked 37.356 30136139 5
12 Locked 37.356 30136344 6
13 Locked 37.356 30135116 8
14 Locked 37.356 30137016 1
15 Locked 37.356 30136806 7
16 Locked 37.636 30136991 1
17 Locked 37.356 30137780 7
18 Locked 37.356 30132743 6
19 Locked 36.610 30137721 3
20 Locked 36.610 30133052 7
21 Locked 36.387 30137537 108
22 Locked 36.387 30137470 1
23 Locked 36.610 30137664 6
24 Locked 36.387 30132991 35

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

And disconnection again ... 40 mins later.
This is definitively not fixed. @Maud Are you sure they checked the EV ?

 

19-11-2021 17:48:44 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;
19-11-2021 17:48:36 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;
19-11-2021 17:48:17 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;
19-11-2021 17:47:52 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;
19-11-2021 17:43:52 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;
19-11-2021 17:43:48 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;
19-11-2021 17:43:48 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;
19-11-2021 17:43: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;
19-11-2021 17:43: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;
19-11-2021 17:43: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;
19-11-2021 17:43: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;
19-11-2021 17:42:51 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;
19-11-2021 17:42:51 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;
19-11-2021 17:42:47 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
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

Latest T3 ...

 

21-11-2021 18:18:21 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;
21-11-2021 18:17:55 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;
21-11-2021 18:13: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;
21-11-2021 18:13:06 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;
21-11-2021 18:13:06 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;
21-11-2021 18:12:42 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;
21-11-2021 18:11: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;
21-11-2021 18:11: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;
21-11-2021 18:11:24 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;
21-11-2021 18:11:23 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;
21-11-2021 18:11:23 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;
21-11-2021 18:11: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;
21-11-2021 17:55: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;
21-11-2021 17:55:32 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;
21-11-2021 17:55:10 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;
21-11-2021 17:54: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;
21-11-2021 17:50: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;
18-11-2021 18:38:07 warning [38:43:7D:C1:79:C6][DFS] Radar signal detected, DFS sequence applied, channel changed from 112 to 44

tobiastheebe
Super Expert
Super Expert
  • 5697Posts
  • 319Oplossingen
  • 1892Likes

The moderators have been notified, they will reply within 24 hours.

vgarot
topicstarter
Gedreven Liefhebber
  • 50Posts
  • 0Oplossingen
  • 7Likes

This morning status ....

 

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


22-11-2021 08:20: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;
22-11-2021 03:54: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;
22-11-2021 03:54: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;
22-11-2021 03:54: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;
22-11-2021 03:53:42 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;
22-11-2021 03:49:42 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;
22-11-2021 03:49:38 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;
22-11-2021 03:49:38 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;
22-11-2021 03:49: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;
22-11-2021 03:49:10 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;
22-11-2021 03:49:10 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;
22-11-2021 03:49:10 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;
22-11-2021 03:48:36 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;
22-11-2021 03:48:36 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;
22-11-2021 03:48: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;
22-11-2021 03:07:12 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;
22-11-2021 03:07:05 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;
22-11-2021 03:06:17 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;
22-11-2021 03:02:17 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;


Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.356 754509130 33591
2 Locked 37.356 753478555 35520
3 Locked 37.636 638837337 34885
4 Locked 37.356 628599853 31106
5 Locked 37.356 753492114 22390
6 Locked 37.356 753497859 17284
7 Locked 37.356 753497351 18256
8 Locked 37.636 753493754 20455
9 Locked 37.356 753492892 22344
10 Locked 37.356 753493522 22388
11 Locked 36.387 753490650 26114
12 Locked 36.610 753491911 24678
13 Locked 36.387 639098371 28673
14 Locked 36.610 652685135 23166
15 Locked 36.610 681902713 5193
16 Locked 36.387 753498640 13510
17 Locked 36.610 650045598 12709
18 Locked 35.780 753500606 17339
19 Locked 36.610 753495530 16023
20 Locked 36.175 753491558 17960
21 Locked 34.484 650106787 31302
22 Locked 36.387 637462076 18089
23 Locked 36.387 753507219 10563
24 Locked 36.387 753508857 7430

Jiri
Community Moderator
Community Moderator
  • 1207Posts
  • 127Oplossingen
  • 311Likes

Hi @vgarot

It's strange the problems are still not fixed.

I've asked the mechanics who went there and they say the cable is replaced. We can't find any other disturbances in the neighbourhood. We only see this at your connection. Could you please connect the modem directly to the AOP with the short cable, as you did before?

I'm curious if the signals are better then.
Please let us know 🙂

tobiastheebe
Super Expert
Super Expert
  • 5697Posts
  • 319Oplossingen
  • 1892Likes

@Jiri This has already been tested here, the noise problems likely occur somewhere between AOP and EV.

Jiri
Community Moderator
Community Moderator
  • 1207Posts
  • 127Oplossingen
  • 311Likes

I know @tobiastheebe 🙂 This was before the last mechanic came by to fix the cable.
The network should be good now and that's why I want @vgarot to test the modem directly on the AOP. 

Uitgelicht topic