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

@Jiri The modem is connected directly to the AOP since 16-11-2021 18:33. This hasn't changed.
The signal quality is unacceptable. At this point I'm getting several disconnections per day.

The mechanic during the second visit told me he observed from his laptop the other house in my street are also getting a noisy signal. I took the time to pull the modem logs from my direct neighbor, stats were even worst than mine as per @tobiastheebe. I don't understand why you report a different information. Have you spoke to this mechanic ?

This mechanic also told me Ziggo would send someone to check the EV. As this been performed ?? If yes, this issue is definitively not fixed.

@Jiri @Maud @Jacob @Jamyla  what's Ziggo's next step here ??


Posting stats once again ...

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

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 1706194074 43664
2 Locked 37.636 1709654481 53749
3 Locked 38.605 1595013530 52844
4 Locked 37.636 1584779087 46105
5 Locked 38.605 1602863466 27921
6 Locked 37.356 1709685199 24507
7 Locked 37.636 1709684161 26056
8 Locked 37.636 1709679461 29368
9 Locked 37.636 1709677472 32284
10 Locked 37.356 1709677792 32732
11 Locked 37.356 1709673405 37989
12 Locked 37.356 1559895283 35113
13 Locked 37.356 1595272023 47267
14 Locked 37.356 1501650270 29477
15 Locked 37.356 1531892694 13436
16 Locked 37.356 1709686571 18939
17 Locked 37.356 1606233734 18057
18 Locked 36.610 1709684592 26999
19 Locked 36.610 1709682141 23041
20 Locked 36.610 1709677330 25784
21 Locked 36.387 1500513941 50998
22 Locked 36.610 1593647944 25782
23 Locked 36.610 1709696050 15317
24 Locked 36.387 1709697986 11703

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

And WAN connection got reset again ....

23-11-2021 12:13:11 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;
23-11-2021 12:13:03 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;
23-11-2021 12:12:15 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;
23-11-2021 12:08: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;

 

Any update / action plan ???

Paul
Community Moderator
Community Moderator
  • 9810Posts
  • 837Oplossingen
  • 2347Likes

@vgarot Too bad that the problem still persists even after the networkticket has been resolved! I've reported your findings back to our networkdepartment to determine the next steps for a permanent solution to the problem. I'll let you know as soon as I have an update for you. 

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

@Paul @Jiri @Maud @Jacob Any news on this please ?

Latest status :

 

25-11-2021 05:19: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;
24-11-2021 08:09: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;
24-11-2021 03:01: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-11-2021 03:00:40 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 3 0
2 2.0 0 0 252 0
3 2.0 0 0 0 0
4 2.0 0 0 395 0


Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.605 3960074489 280
2 Locked 37.636 3959805789 816
3 Locked 38.605 3959805593 876
4 Locked 38.605 3959805712 850
5 Locked 37.636 3959805356 899
6 Locked 37.356 3959806233 835
7 Locked 37.636 3959806304 614
8 Locked 37.636 3959806690 446
9 Locked 37.636 3959497461 436
10 Locked 37.636 3959807703 430
11 Locked 37.356 3959807480 487
12 Locked 37.636 3959808313 542
13 Locked 37.356 3959808000 652
14 Locked 37.636 3959806455 668
15 Locked 37.356 3959804247 3482
16 Locked 37.356 3959805474 2383
17 Locked 37.356 3959807664 655
18 Locked 37.356 3959805495 610
19 Locked 37.356 3959807546 449
20 Locked 37.356 3959808439 416
21 Locked 36.610 3959808278 452
22 Locked 36.610 3959808578 671
23 Locked 36.610 3959804263 3476
24 Locked 36.610 3959805986 3040

Paul
Community Moderator
Community Moderator
  • 9810Posts
  • 837Oplossingen
  • 2347Likes

@vgarot We've investigated the problem and it seems that the signal issue on both the down- and upstream frequencies only occurs on your connection. Based on the findings from my colleagues from our netwerkdepartment I've planned an appointment with an engineer on Monday the 29th of november between 8 and 18 o'clock to resolve the problem. In case this doesn't suite you, you can reschedule the appointment via Mijn Ziggo > Mijn Gegevens > Mijn Monteursafspraken. Please read the guidelines regarding the Corona measures before the appointment with the engineer. This way we can keep the appointment safe for everyone.  I can offer 50 GB data if you have a Vodafone mobile subscription. so you can still use the internet until the technician has visited. Let me know if I need to arrange this for you. 

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

Thanks @Paul 
Please provide the action plan details for this intervention. As this will be the third engineer coming onsite, and to not delay resolution any further, I would just like to make sure he exactly knows what he has to do during the visit.
I'm on a different mobile provider.
Regards.

Paul
Community Moderator
Community Moderator
  • 9810Posts
  • 837Oplossingen
  • 2347Likes

@vgarot You're welcome. I've provided the details and my findings in regards to the signal issue to our engineer. 

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

@Paul I would love to get those too 😉
Thanks

Paul
Community Moderator
Community Moderator
  • 9810Posts
  • 837Oplossingen
  • 2347Likes

@vgarot On both the up and downstream signal I noticed noise on the signal. This is also visible for the engineer which I have scheduled for you. If you are interested you can always ask the engineer if you can have a look on the data on his measurement equipment. 

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

Paul,

Field Engineer came in around Nov 29th 11:30 AM. He thought the issue was due to the connector within the AOP which model is apparently known for getting sensible to noise interferences. He replaced it with another model he brought, and left. 

vgarot_0-1638190574806.jpeg


UNFORTUNATELY this didn't helped ! @Paul What's the next step please ?

Standard specification compliant : DOCSIS 3.0
Hardware version : 5.01
Software version : CH7465LG-NCIP-6.15.31p1-NOSH
Cable MAC address : 38:43:7D:CD:CE:99
Cable modem serial number : DEAP8118041D
System up time : 0day(s)0h:41m:58s
Network access : Allowed


Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 37.636 33794274 1016
2 Locked 37.356 32867544 2616
3 Locked 37.356 32867582 2390
4 Locked 37.636 32868442 2394
5 Locked 37.356 32872670 2315
6 Locked 37.636 32868331 2141
7 Locked 38.258 32861651 1627
8 Locked 37.356 32861755 1234
9 Locked 37.636 32870179 892
10 Locked 37.356 32870191 739
11 Locked 37.636 32871022 662
12 Locked 37.636 32870563 778
13 Locked 37.636 32871150 859
14 Locked 37.356 32864187 871
15 Locked 36.610 32865107 947
16 Locked 36.610 32870003 619
17 Locked 36.610 32870504 751
18 Locked 36.610 32870806 570
19 Locked 36.610 32862664 649
20 Locked 35.780 32857375 6647
21 Locked 36.610 32869880 624
22 Locked 36.610 13519304 20
23 Locked 36.387 32870059 499
24 Locked 36.610 32858503 390

 

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 17 0
4 2.0 0 0 0 0

29-11-2021 13:37:14 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;
29-11-2021 13:36:31 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;
29-11-2021 13:36: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;
29-11-2021 13:36: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;
29-11-2021 13:35: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;
29-11-2021 13:31: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;
29-11-2021 13:31:00 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;
29-11-2021 13:31:00 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;
29-11-2021 13:30: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;
29-11-2021 13:30: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;
29-11-2021 13:30:34 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;
29-11-2021 13:12:27 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;
29-11-2021 13:12: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;
29-11-2021 13:09:44 notice Cable Modem Reboot - CBN WebSrv Info: system reboot;CM-MAC=38:43:7d:cd:ce:99;CMTS-MAC=00:01:5c:88:d8:55;CM-QOS=1.1;CM-VER=3.0;
29-11-2021 13:00:26 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;
29-11-2021 13:00:18 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;
29-11-2021 12:59: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;


@tobiastheebe ^

tobiastheebe
Super Expert
Super Expert
  • 5801Posts
  • 327Oplossingen
  • 1924Likes

I had hoped that a network technician would be sent to check up on the EV.

 

Which type of AOP did the technician install, perhaps a TRISZ-DG300? The btv 1 IEC-NL and btv 01-SET/UPC have been in deployment since a couple of years now, they are very high quality coax sockets and not susceptible to interference whatsoever, provided the cable is properly terminated.

 

Overall downstream signal is still very noisy, resulting in (repetitive) T3/T4 timeouts.

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

@tobiastheebe Got a btv 01-SET.
Quoting the technician : "Cable termination is good, but making it new just to be sure"

WhatsApp Image 2021-11-29 at 15.44.00.jpeg

 

Paul
Community Moderator
Community Moderator
  • 9810Posts
  • 837Oplossingen
  • 2347Likes

@vgarot I'm very sorry that the problem still excists! When I have a look at the signal I still notice noise on both the down- and upstream channels. Due to the fact that the engineer didn't resolve the problem I've escalated the problem to our network department and we scheduled a new appointment with a field engineer on Thursday the 1st of December 2021 between 12 and 18 o'clock. I hope this time and date suits you. Otherwise you can reschedule the appointment via Mijn Ziggo > Mijn Gegevens > Mijn monteursafpraken. 

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

@Paul Thanks for the update. Please share the action plan here once you got an update from your network team. 
And as per @tobiastheebe , has the EV been checked already ? If yes, what are the technician findings please.

Mark
Community Moderator
Community Moderator
  • 5496Posts
  • 639Oplossingen
  • 2081Likes

The plan is quite simple. The mechanic will be tasked to investigate the source of the signal noise we're detecting. He or she will most likely start the investigation from your address and work their way up from there.

No mention of EV checks in the previous mechanics' notes.

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

Issue very likely identified today. Extra old non waterproof coax cable coming from the street (mainly from the original installation long time ago) 
Mechanic should come next Tuesday to replace it. Hurray

vgarot_0-1638454099762.png

 

Paul
Community Moderator
Community Moderator
  • 9810Posts
  • 837Oplossingen
  • 2347Likes

@vgarot Thank you very much for your update! Good to read that the problem has been identified by our technician. I noticed he has planned an appointment with a contractor (ticketnumber: KBSM668580) to replace the cable. Please let us know what your findings are after the cables has been replaces next Tuesday. 

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

Cable replaced. I'll monitor for the rest of the week and update here again but so far it looks very promising. 

 

System up time : 0day(s)0h:23m:19s

 

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.605 47938220 4
2 Locked 37.636 47939786 5
3 Locked 37.636 47940287 5
4 Locked 38.605 47936386 6
5 Locked 38.605 47937116 6
6 Locked 38.605 47940142 5
7 Locked 37.636 47940646 5
8 Locked 37.636 47943183 0
9 Locked 37.636 47944617 6
10 Locked 37.356 47945255 5
11 Locked 37.356 47946701 4
12 Locked 37.356 47947312 5
13 Locked 36.610 47948731 0
14 Locked 37.356 47952094 5
15 Locked 37.356 47952604 0
16 Locked 37.356 47953424 6
17 Locked 36.610 47948748 0
18 Locked 36.387 47950609 5
19 Locked 37.356 47953519 4
20 Locked 36.610 47954041 4
21 Locked 36.387 47955568 6
22 Locked 36.610 47954698 17
23 Locked 36.387 47955916 4
24 Locked 36.610 47948159 0

Paul
Community Moderator
Community Moderator
  • 9810Posts
  • 837Oplossingen
  • 2347Likes

@vgarot Thanks for sharing this update with us. That looks promising indeed. Let's see how it continues to go in the next few days than we can determine if the problem has been resolved. 

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

WAN stability has much improved since cable replacement and noise has drastically decreased.

But still observing critical T3 and T4 events  

 

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

Uitgelicht topic