onderwerp Re: Na vervangen modem nog steeds instabiele verbinding in Internet

Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Fri, 08 May 2020 09:15:43 GMT

nadat ik ondekte dat mijn IPv6 tunnel wel heel erg traag was en hier op het community forum er een topic over zag staan, heb ik de UBC1318ZG (waar ik overigens ook zeer blij mee ben!)

enkel is het nog steeds niet stabiel! nu 2 dagen de UBEE, en op beide dagen klapte rond 16:00u de verbinding er helemaal uit. (met de witte CB kwam deze naar x minuten terug, nu niet!)

s'nachts gebeurt er ook van alles...

helaas kan ik niet heel veel info uit de UBEE vissen, maar ga ervan uit de de medewerkers bij Ziggo dit wel kunnen 😉

tevens staat de UBEE grotendeels van de dag in: "internet (Verbonden (partial bonding US))"

misschien komt dat omdat de UBEE een DOCSIS 3.1 is en de wijk nog DOCSIS 3.0 is???

hierbij wat gegevens en screenshots (bijlage):

Standard Specification Compliant    DOCSIS 3.1
Hardware Version        2.73.1
Software Version        12.5.3208
Cable Modem MAC Address    XX:XX:XX:C7:E7:CB
Cable Modem Serial Number    U1318XXXXXXX
CM certificate    Installed

CM IP Prov Mode: Honor MDD
Ethernet WAN Mode:
Bidirectional Forwarding Detection:
Current System Time: Fri May 8 11:03:34 2020

Startup Procedure
Procedure           Status   Comment
Acquire Downstream Channel   850000000   Locked
Connectivity State       OK   Operational
Boot State           OK   Operational
Configuration File       OK   soho11_nowifi_v4.bin
Security           Enabled   BPI+

CM Downstream Channel Info
Channel   Lock Status   Channel Type   Channel ID   Frequency   Width   Power   SNR   Modulation Profile ID   Correctables   Uncorrectables
1   Locked   SC-QAM Downstream   32   850000000 Hz   8000000 Hz   6.2 dBmV   38.9 dB   QAM256   369   201
2   Locked   SC-QAM Downstream   1   602000000 Hz   8000000 Hz   9.8 dBmV   40.5 dB   QAM256   722   229
3   Locked   SC-QAM Downstream   2   610000000 Hz   8000000 Hz   9.6 dBmV   40.7 dB   QAM256   712   220
4   Locked   SC-QAM Downstream   3   618000000 Hz   8000000 Hz   9.5 dBmV   40.6 dB   QAM256   581   183
5   Locked   SC-QAM Downstream   4   626000000 Hz   8000000 Hz   10 dBmV       40.8 dB   QAM256   460   216
6   Locked   SC-QAM Downstream   5   634000000 Hz   8000000 Hz   10.1 dBmV   40.7 dB   QAM256   477   216
7   Locked   SC-QAM Downstream   6   642000000 Hz   8000000 Hz   10.1 dBmV   40.5 dB   QAM256   483   208
8   Locked   SC-QAM Downstream   7   650000000 Hz   8000000 Hz   10.2 dBmV   40.7 dB   QAM256   398   217
9   Locked   SC-QAM Downstream   8   658000000 Hz   8000000 Hz   10 dBmV       40.6 dB   QAM256   453   186
10   Locked   SC-QAM Downstream   9   666000000 Hz   8000000 Hz   10.1 dBmV   40.6 dB   QAM256   310   226
11   Locked   SC-QAM Downstream   10   674000000 Hz   8000000 Hz   9.4 dBmV   40.3 dB   QAM256   613   244
12   Locked   SC-QAM Downstream   11   682000000 Hz   8000000 Hz   8.8 dBmV   40.1 dB   QAM256   678   267
13   Locked   SC-QAM Downstream   12   690000000 Hz   8000000 Hz   8.7 dBmV   40.1 dB   QAM256   893   255
14   Locked   SC-QAM Downstream   13   698000000 Hz   8000000 Hz   9.2 dBmV   40.3 dB   QAM256   451   236
15   Locked   SC-QAM Downstream   14   706000000 Hz   8000000 Hz   8.9 dBmV   40.1 dB   QAM256   515   271
16   Locked   SC-QAM Downstream   15   714000000 Hz   8000000 Hz   8.5 dBmV   39.9 dB   QAM256   793   293
17   Locked   SC-QAM Downstream   16   722000000 Hz   8000000 Hz   7.9 dBmV   39.4 dB   QAM256   1053   248
18   Locked   SC-QAM Downstream   17   730000000 Hz   8000000 Hz   8 dBmV       39.6 dB   QAM256   1046   207
19   Locked   SC-QAM Downstream   18   738000000 Hz   8000000 Hz   8.3 dBmV   39.8 dB   QAM256   552   266
20   Locked   SC-QAM Downstream   19   746000000 Hz   8000000 Hz   8.2 dBmV   39.8 dB   QAM256   562   184
21   Locked   SC-QAM Downstream   20   754000000 Hz   8000000 Hz   8.1 dBmV   40 dB   QAM256   562   171
22   Locked   SC-QAM Downstream   21   762000000 Hz   8000000 Hz   7.9 dBmV   39.8 dB   QAM256   617   137
23   Locked   SC-QAM Downstream   22   770000000 Hz   8000000 Hz   7.6 dBmV   39.3 dB   QAM256   870   107
24   Locked   SC-QAM Downstream   23   778000000 Hz   8000000 Hz   7.8 dBmV   39.6 dB   QAM256   404   97
25   Locked   SC-QAM Downstream   24   786000000 Hz   8000000 Hz   7.8 dBmV   39.8 dB   QAM256   467   83
26   Locked   SC-QAM Downstream   25   794000000 Hz   8000000 Hz   7.8 dBmV   39.7 dB   QAM256   280   116
27   Locked   SC-QAM Downstream   26   802000000 Hz   8000000 Hz   7.8 dBmV   39.8 dB   QAM256   263   125
28   Locked   SC-QAM Downstream   27   810000000 Hz   8000000 Hz   7.2 dBmV   39.6 dB   QAM256   446   145
29   Locked   SC-QAM Downstream   28   818000000 Hz   8000000 Hz   7.8 dBmV   40 dB   QAM256   300   149
30   Locked   SC-QAM Downstream   29   826000000 Hz   8000000 Hz   7.3 dBmV   39.6 dB   QAM256   283   181
31   Locked   SC-QAM Downstream   30   834000000 Hz   8000000 Hz   7.2 dBmV   39.5 dB   QAM256   266   183
32   Locked   SC-QAM Downstream   31   842000000 Hz   8000000 Hz   6.8 dBmV   39.1 dB   QAM256   329   200

CM Upstream Channel Info
Channel   Lock Status   Channel Type   Channel ID   Frequency   Width   Power   Modulation/Profile ID
1   Locked   ATDMA   1   57800000 Hz   6400000 Hz   43.8 dBmV   2
2   Locked   ATDMA   2   50900000 Hz   6400000 Hz   44.3 dBmV   2
3   Locked   ATDMA   3   44000000 Hz   6400000 Hz   43 dBmV       2
4   Locked   ATDMA   4   37100000 Hz   6400000 Hz   43.3 dBmV   2
5   Locked   ATDMA   5   31800000 Hz   3200000 Hz   44.3 dBmV   2
6   Locked   ATDMA   6   28600000 Hz   3200000 Hz   44.5 dBmV   2

valt mij op dat de T3 errors (en een paar T4) allemaal lijden naar de CMTS (iets wat buitenshuis is)…

wat is hier aan de hand?

ik ga vandaag om 16:00u er weer klaar voor zitten dat de boel eruit klapt...

Re: Na vervangen modem nog steeds instabiele verbinding

Jan F. — Fri, 08 May 2020 09:49:07 GMT

Heeft u de modem via een versterker aangesloten?

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Fri, 08 May 2020 09:59:10 GMT

nee, enkel de door ziggo geleverde splitter zit tussen de AOP en de UBEE. (en nee, ik ga niet weer dagen zonder TV zitten, splitter ertussen uit gaf toen met de witte CB geen verbetering)

Re: Na vervangen modem nog steeds instabiele verbinding

Jan F. — Fri, 08 May 2020 10:06:11 GMT

annoniempjuh wrote:

…….. (en nee, ik ga niet weer dagen zonder TV zitten, splitter ertussen uit gaf toen met de witte CB geen verbetering)

Nee, die mag van mij blijven zitten. Ik stelde de vraag omdat ik het downstream signaal hoog vind. Dat kan tot problemen leiden. Het upstream signaal ziet er normaal uit. Misschien een idee voor Ziggo om de sterkte van uw signaal in de straatkast wat terug te schroeven.

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Fri, 08 May 2020 10:30:16 GMT

ik snap sowieso niet waarom je de modem zelf nog eens achter een versterker plaatst, zal denk ik aan mij liggen 😉

downstream vind ik ook wel een de hoge kant, de UBEE zelf vind dat volgens mij ook:

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=00:17:XX:XX:XX:8c;CM-QOS=1.1;CM-VER=3.1;

Re: Na vervangen modem nog steeds instabiele verbinding

Henno — Fri, 08 May 2020 10:42:27 GMT

https://volpefirm.com/docsis_timeout_descriptions/

De docsis datastroom met ranging info is een aantal keren niet aangekomen, dit leid tot een T3 fout: verbreken van je verbinding.

Als het voortdurend op hetzelfde tijdstip is dan lijkt de meest voor de hand liggende oorzaak in ruis op de verbinding naar de CMTS.

gr, Henno

Re: Na vervangen modem nog steeds instabiele verbinding

Jan F. — Fri, 08 May 2020 10:52:03 GMT

annoniempjuh wrote:

ik snap sowieso niet waarom je de modem zelf nog eens achter een versterker plaatst, zal denk ik aan mij liggen 😉

Nee, en dat is in het algemeen ook niet nodig, maar ik heb al een heel aantal voorbij zien komen op dit forum.

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Fri, 08 May 2020 12:55:03 GMT

De UBEE zal wel hebben gedacht, "hij zit er klaar voor", verassing! we komen een uurtje eerder!

weer een drop out. verbinding klapte er volledig uit. moest ditmaal zelf de utp kabel tussen UBEE en eigen router verwijderen (waar bij de witte CB dit niet hoefde, had naar x minuten weer verbinding)

ditmaal een aantal T4 errors:

de status van de modem staat nu weer op:

Internet (Verbonden - bridge mode) ← goed dus.

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Fri, 08 May 2020 13:27:03 GMT

net contact gehad met de (zakelijke)klantenservice, hij konden niks zien, waardes staan prima. in overleg ga ik dit weekend de UBEE omzetten naar Router modus en enkel de laptop erop aan data verzamelen (screenshots etc.) de meldingen die ik hier in het bericht boven zag hij (kl. serverice) niet.

Ik gebruik o.a. Vlans, 'even' de OPNsense router ertussen uit betekend 90% van mijn netwerk plat, dus dan maar met enkel met de laptop troubleshooten...

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Thu, 14 May 2020 10:46:06 GMT

even een update,

nadat ik de zaterdag middag de UBEE uit bridge modus haalde, en ik ontdekte dat ik in opnsense even een vinkje weg moest halen bij de WAN interface. kreeg ik opnsense ook werkend achter de ubee in 'NAT' modus.

hier viel mij op dat suricata (IPS/IDS services) in eens de boel blokkeerde, zowel inkomend als uitgaande. dit heeft mij naar de diep liggende logboeken doen leiden en hier viel mij op dat er een rule was die het nodige blokkeerde van en naar 255.255.255.255 (ik zag in de syteem logboek dat er een dhcprequest naar toegestuurd werd)

deze regels uitgeschakeld en nu 5 dagen verder geen problemen meer waargenomen, laatste foutmeldingen in de UBEE is van 11/05.

denk dat een update van de 'rules' de boel sloopte, ik heb suricata behoorlijk streng ingesteld 😉

(of er is achter de schermen bij Ziggo de nodige wijzigingen doorgevoerd nadat ik gebeld had 😛 )

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Thu, 14 May 2020 14:12:53 GMT

hmm, te vroeg gejuicht. op het moment dat ik bewust suricata had uitstaan (ik wou 'm nog wat fine-tunen, om te voorkomen dat ie de boel sloopt deed ik het maar even uit), klapte de boel er toch weer uit.

OPNSENSE meld meerdere malen:

dhclient[99496]: DHCPREQUEST on em0 to 255.255.255.255 port 67

UBEE:

Time	Priority	Description
2020-05-14 16:02:10	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 16:02:10	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 16:02:10	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 16:01:24	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 16:01:03	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 16:00:57	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:58	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:53	notice	TLV-11 - unrecognized OID;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:32:52	error	Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:27	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:24	notice	Honoring MDD; IP provisioning mode = IPv4
2020-05-14 15:33:22	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:20	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:10	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:09	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:09	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:06	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:06	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:06	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:06	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:03	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:03	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:03	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-05-14 15:33:02	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:c7:e7:cb;CMTS-MAC=XX:XX:XX:91:50:8c;CM-QOS=1.1;CM-VER=3.1;

ik had hiet beter geen update kunnen plaatsen...

Re: Na vervangen modem nog steeds instabiele verbinding

Alex — Tue, 26 May 2020 07:39:35 GMT

Hi @annoniempjuh, sorry dat een nieuwe reactie wat lang op zich heeft laten wachten. Erg zonde dat je update uiteindelijk toch niet positief was

We zijn inmiddels enige tijd verder; hoe staat het er voor? In de afgelopen dagen ziet het signaal er aan deze kant prima uit. Ik ben benieuwd!

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Tue, 26 May 2020 10:51:50 GMT

Alex Ziggo wrote:

Hi @annoniempjuh, sorry dat een nieuwe reactie wat lang op zich heeft laten wachten. Erg zonde dat je update uiteindelijk toch niet positief was

We zijn inmiddels enige tijd verder; hoe staat het er voor? In de afgelopen dagen ziet het signaal er aan deze kant prima uit. Ik ben benieuwd!

kijkend in de logboek van de UBEE is het al een stuk rustiger, enkel blijven er nog steeds T3 en T4 errors langskomen (Met de Connectbox had ik nagenoeg geen enkele T4 error)

OPNsense is ook een stuk rustiger, heb de afgelopen week geen enkele keer de boel te hoeven herstarten, dus er is verbetering.

enkel kijken in de UBEE logboeken blijven er een aantal meldingen voorbij komen die ik niet helemaal vertrouw:

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Wed, 24 Jun 2020 19:09:08 GMT

Het is sinds gisteren 5:00u weer erg slecht, Ik beging hier nu toch echt wel heel erg moe van te worden. vandaag kreeg ik weer eens geen contact met het thuisnetwerk met mijn mobiel (ik was buitenshuis, dus op mobiele netwerk!), start tijd weet ik niet, nu net weer een utp stekker ontkoppeld terug geduwd.

2020-06-23 15:36:34 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:31 notice  Honoring MDD; IP provisioning mode = IPv4 2020-06-23 15:36:30 critical    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:27 critical    No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:17 critical    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:16 critical    No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:16 critical    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:16 critical    No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:16 critical    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:15 critical    No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:36:15 critical    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:35:29 critical    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:30:18 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:30:13 notice  TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:30:12 error   Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;

T4, T3, T4, T3, T4, T3…. Wauw!

Time    Priority    Description 2020-06-23 15:20:31 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:25 notice  TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:24 error   Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:22 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:19 notice  Honoring MDD; IP provisioning mode = IPv4 2020-06-23 15:20:07 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:07 critical    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:07 critical    No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:07 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:07 critical    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:07 critical    No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:06 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:06 critical    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:06 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:20:02 critical    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:37 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:37 critical    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:36 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:36 critical    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:36 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:36 critical    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:36 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:36 critical    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1; 2020-06-23 15:19:36 critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;

en dan vandaag weer:

Time	Priority	Description
2020-06-24 18:24:53	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 18:24:53	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 18:24:33	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 18:24:27	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 5 8 9 10 12 15 16 17 18 30 31 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 18:24:23	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 18:24:06	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:43	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:38	notice	TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	error	Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:36	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:33	notice	Honoring MDD; IP provisioning mode = IPv4
2020-06-24 16:36:22	notice	CM-STATUS message sent. Event Type Code: 6; Chan ID: 6 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:36:22	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:35:52	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:35:51	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 16:35:36	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 14:59:33	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 14:59:28	notice	TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 14:59:26	error	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 14:59:26	error	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 14:59:26	error	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 14:59:26	error	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 14:59:26	error	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-24 14:59:26	error	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;

Note: ik heb sinds kort een 2e lijn op OPNsense zitten en deze is ECHT Rock Solit.

paar weken terug moest ik voor werkzaamheden de meterkast leegruimen, nadat het klaar was dacht ik van: laat ik die splitter er nu eens tussenuit laten, Nou, die zat er snel weer tussen! ik kwam niet eens online!

tijdens het schrijven van deze bericht staat de UBEE weer in "Verbonden (partial bonding US)"

Terwijl mijn OPNsense bakkie geen enkel fout heeft...

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Thu, 25 Jun 2020 13:34:24 GMT

die T3, T4, T3, T4, T3, T4, T3 dit doet ie nu dagelijks! wederom weer rond 16:00u! dat was een aantal weken geleden ook al, toen was het wat rustiger, maar nu deze week weer erg slecht...

Time	Priority	Description
2020-06-25 15:29:50	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:44	notice	TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:48	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:45	notice	Honoring MDD; IP provisioning mode = IPv4
2020-06-25 15:29:32	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:23	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:21	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:21	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:20	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:20	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:19	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:19	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:19	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:18	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:28:32	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Thu, 25 Jun 2020 13:39:10 GMT

Time	Priority	Description
2020-06-25 15:29:50	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:44	notice	TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:43	error	Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:48	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:45	notice	Honoring MDD; IP provisioning mode = IPv4
2020-06-25 15:29:32	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:23	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:21	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:21	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:20	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:20	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:19	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:19	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:19	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:29:18	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-25 15:28:32	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;

Re: Na vervangen modem nog steeds instabiele verbinding

Alex — Sat, 27 Jun 2020 13:10:52 GMT

Hi @annoniempjuh,

Dat zijn niet bepaald meldingen/logs waar je gelukkig van wordt. Ik ben aan deze kant je signaal ingedoken, maar kan het eigenlijk niet echt rijmen met de zeer afwijkende resultaten in je logboek. Overigens zijn het ook heel veel meldingen binnen één of twee minuten. Hoe lang ligt het er gemiddeld dan uit? En hoe vaak komt dit per dag voor? Op basis van je ervaringen op dit moment, denk ik dat het verstandig is een monteur in te plannen.

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Sat, 27 Jun 2020 13:20:39 GMT

afgelopen week vooral woensdag en donderdag was vreselijk, denk dat ik wel 10x heb moeten ingrijpen. vandaag is ie verdacht rete stabiel (lees: geen merkbare uitval gezien) *klopt af op houten bureau*, OPNsense is de afgelopen weken niks verandert dus die durf ik nog steeds uit te sluiten, en daarbij lijkt mij het zo dat ie niet de T3 en t4 errors kan veroorzaken… (vooral de momenten dat er meerdere direct achterelkaar komen...)

Re: Na vervangen modem nog steeds instabiele verbinding

Alex — Sat, 27 Jun 2020 17:51:17 GMT

Laten we uiteraard hopen dat het een voorbode is op meer goeds! Ik zal ondertussen dan ook even een nauwkeurige meting starten voor 3 dagen om alles nog wat beter in kaart te brengen. Mochten we toch op een monteur uitkomen, dan kan het daar ook bij helpen.

Re: Na vervangen modem nog steeds instabiele verbinding

annoniempjuh — Sat, 27 Jun 2020 20:57:40 GMT

vanmiddag niet hard genoeg afgetikt, het was weer raak, gedeelte van de logboek kunnen kopiëren, hij is 2 maal kort achterelkaar geklapt:

Time	Priority	Description
2020-06-27 22:43:37	notice	TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:33	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:30	notice	Honoring MDD; IP provisioning mode = IPv4
2020-06-27 22:43:24	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:14	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:13	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:13	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:12	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:12	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:05	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:04	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:03	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:03	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:42:19	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:44	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:39	notice	TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:38	error	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:38	error	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:38	error	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:38	error	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:38	error	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:38	error	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:39:38	error	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;

het gaat dus bij de UBEE al fout, opnsense gaf ditmaal ook aan package lose, dit zag ik voor het eerst, vaak was het eigenlijk altijd direct "offline". (ik monitor de WAN zijde met de ingebakken monitor tools) Tijdens het typen van dit bericht klapte de verbinding er nogmaal uit:

Time	Priority	Description
2020-06-27 22:52:05	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:54	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:54	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:54	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:54	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:54	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:53	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:53	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:53	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:52	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:51:06	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:48:54	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:48:53	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:45:12	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:37	notice	TLV-11 - unrecognized OID;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:35	error	Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:33	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:30	notice	Honoring MDD; IP provisioning mode = IPv4
2020-06-27 22:43:24	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:14	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:13	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:13	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:12	critical	No Ranging Response received - T3 time-out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;
2020-06-27 22:43:12	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:32:4b:c7:e7:cb;CMTS-MAC=00:17:10:91:50:8c;CM-QOS=1.1;CM-VER=3.1;

Dit begind echt zwaar vervelend te worden, ben bijna geniegd om m'n hele huishouden naar een 4G abbo te verplaatsen...