Beantwoord

Na vervangen modem nog steeds instabiele verbinding

  • 8 mei 2020
  • 34 reacties
  • 820 keer bekeken

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...

icon

Best beantwoord door annoniempjuh 3 september 2020, 20:00

Update:

Inmiddels alweer een tijdje verder, en tot op heden geen enkele problemen meer gehad! (behalve dan met eigen hardware 😉 )

Nogmaals een Dikke Shout-Out naar de betreffende monteur die dit probleem wist te tackelen!

Bekijk origineel

34 Reacties

Zou je de modem waardes kunnen laten zien 🙂?

Ben wel benieuwd hoe het er nu uit ziet!

vrij onveranderd, al zeg ik het zelf:

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 1 602000000 Hz 8000000 Hz 10.4 dBmV 40.4 dB QAM256 5592 74
2 Locked SC-QAM Downstream 2 610000000 Hz 8000000 Hz 10.3 dBmV 40.6 dB QAM256 5104 32
3 Locked SC-QAM Downstream 3 618000000 Hz 8000000 Hz 10.4 dBmV 40.5 dB QAM256 4238 49
4 Locked SC-QAM Downstream 4 626000000 Hz 8000000 Hz 10.8 dBmV 40.8 dB QAM256 3431 23
5 Locked SC-QAM Downstream 5 634000000 Hz 8000000 Hz 10.9 dBmV 40.7 dB QAM256 3475 22
6 Locked SC-QAM Downstream 6 642000000 Hz 8000000 Hz 10.9 dBmV 40.6 dB QAM256 3668 53
7 Locked SC-QAM Downstream 7 650000000 Hz 8000000 Hz 11 dBmV 40.6 dB QAM256 3412 49
8 Locked SC-QAM Downstream 8 658000000 Hz 8000000 Hz 10.9 dBmV 40.6 dB QAM256 3479 22
9 Locked SC-QAM Downstream 9 666000000 Hz 8000000 Hz 11 dBmV 40.6 dB QAM256 2015 57
10 Locked SC-QAM Downstream 10 674000000 Hz 8000000 Hz 10.3 dBmV 40.1 dB QAM256 5551 16
11 Locked SC-QAM Downstream 11 682000000 Hz 8000000 Hz 9.7 dBmV 40.1 dB QAM256 5536 40
12 Locked SC-QAM Downstream 12 690000000 Hz 8000000 Hz 9.6 dBmV 40.1 dB QAM256 8751 44
13 Locked SC-QAM Downstream 13 698000000 Hz 8000000 Hz 10 dBmV 40.2 dB QAM256 3671 64
14 Locked SC-QAM Downstream 14 706000000 Hz 8000000 Hz 9.7 dBmV 40 dB QAM256 4512 24
15 Locked SC-QAM Downstream 15 714000000 Hz 8000000 Hz 9.3 dBmV 39.6 dB QAM256 7951 26
16 Locked SC-QAM Downstream 16 722000000 Hz 8000000 Hz 8.8 dBmV 39.4 dB QAM256 10190 24
17 Locked SC-QAM Downstream 17 730000000 Hz 8000000 Hz 9 dBmV 39.6 dB QAM256 10539 18
18 Locked SC-QAM Downstream 18 738000000 Hz 8000000 Hz 9.4 dBmV 39.8 dB QAM256 5157 60
19 Locked SC-QAM Downstream 19 746000000 Hz 8000000 Hz 9.1 dBmV 39.8 dB QAM256 5824 16
20 Locked SC-QAM Downstream 20 754000000 Hz 8000000 Hz 8.9 dBmV 39.8 dB QAM256 5817 19
21 Locked SC-QAM Downstream 21 762000000 Hz 8000000 Hz 8.4 dBmV 39.7 dB QAM256 7193 49
22 Locked SC-QAM Downstream 22 770000000 Hz 8000000 Hz 7.8 dBmV 39.3 dB QAM256 10331 32
23 Locked SC-QAM Downstream 23 778000000 Hz 8000000 Hz 8.1 dBmV 39.6 dB QAM256 4243 36
24 Locked SC-QAM Downstream 24 786000000 Hz 8000000 Hz 8.3 dBmV 39.7 dB QAM256 4702 16
25 Locked SC-QAM Downstream 25 794000000 Hz 8000000 Hz 8.5 dBmV 39.6 dB QAM256 2411 27
26 Locked SC-QAM Downstream 26 802000000 Hz 8000000 Hz 8.8 dBmV 39.7 dB QAM256 2224 50
27 Locked SC-QAM Downstream 27 810000000 Hz 8000000 Hz 8.4 dBmV 39.6 dB QAM256 4228 48
28 Locked SC-QAM Downstream 28 818000000 Hz 8000000 Hz 8.9 dBmV 39.9 dB QAM256 2402 23
29 Locked SC-QAM Downstream 29 826000000 Hz 8000000 Hz 8.2 dBmV 39.5 dB QAM256 2241 25
30 Locked SC-QAM Downstream 30 834000000 Hz 8000000 Hz 8.1 dBmV 39.4 dB QAM256 2294 17
31 Locked SC-QAM Downstream 31 842000000 Hz 8000000 Hz 7.6 dBmV 39.2 dB QAM256 2908 27
32 Locked SC-QAM Downstream 32 850000000 Hz 8000000 Hz 7.1 dBmV 38.8 dB QAM256 3706 40

 

 

 

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 46 dBmV 2
2 Locked ATDMA 2 50900000 Hz 6400000 Hz 45.3 dBmV 2
3 Locked ATDMA 3 44000000 Hz 6400000 Hz 45 dBmV 2
4 Locked ATDMA 4 37100000 Hz 6400000 Hz 46 dBmV 2
5 Locked ATDMA 5 31800000 Hz 3200000 Hz 45.3 dBmV 2
6 Locked ATDMA 6 28600000 Hz 3200000 Hz 45.8 dBmV 2

 

Reputatie 6
Badge +10

Zou je de modem waardes kunnen laten zien 🙂?

Ben wel benieuwd hoe het er nu uit ziet!

Update:

Inmiddels alweer een tijdje verder, en tot op heden geen enkele problemen meer gehad! (behalve dan met eigen hardware ;) )

Nogmaals een Dikke Shout-Out naar de betreffende monteur die dit probleem wist te tackelen!

Ah, dat zijn mooie berichten @annoniempjuh.  Bedankt voor deze update. Mocht er al iets zijn, dan weet je ons te vinden! We staan met zijn allen voor je klaar. 

update:

Monteur is vanochtend mooi op tijd geweest.

heeft een aantal werkzaamheden verricht meeste in de straatkast.

Ook vertelde die mij dat ie de komende dagen ook actief gaat mee kijken en als het nodig is ook actie ondernemen. kortom, hartstikke tevreden!

Uiteraard ga ik ook de boel in de gaten houden en post ik zo nodig nog een update.

Top, ik heb hem aanstaande woensdagochtend voor je ingepland. Tussen 08:00 en 13:00. Je ontvangt ook een bevestiging per mail. Laat je weten hoe het is gegaan?

@Alex Ziggo  volgende week heb ik op vrijdag na, genoeg ruimte leeg voor actie,

Ik hoor graag wanneer er een monteur beschikbaar is.

Hi @annoniempjuh,

Het is inderdaad waardeloos dat dit al zo lang speelt. En wat het extra irritant is, is dat het met golven soms opeens weer goed gaat. Dat zagen we vorige keer ook terug, waarbij ik echt de hoop had dat de ellende voorbij was. Ik ben opnieuw je modem ingedoken maar ‘helaas’ zie ik geen gekke signaalwaardes. Wel op enkele dagen inderdaad een hele bult T3 en T4 meldingen. Dit gaat eigenlijk precies zoals jij aangeeft; lange tijd niets en opeens weer flink raak. De periode tussen 18 juli en 22 juli ging het stabiel, maar daarna weer mis. Dat komt ook overeen met je laatste bericht. Normaal gesproken hoeft een dergelijke melding niet altijd voor problemen te zorgen, maar je ervaart duidelijk uitval geef je aan.

Dit is niet iets wat ik op afstand kan oplossen en wil in dat geval dan een monteursafspraak met je maken. Heb je daar volgende week ruimte voor?

gisteren en vandaag is het weer raak, helaas krijg ik de buurman niet te pakken.

aan de andere kant, Ziggo kan vanuit hun systeem hier in verder kijken, Zij kunnen meer zien dan dat ik kan…

Ziggo moet zich wel gaan realiseren dat ze hier bezig zijn met glasvezel en dit "probleem" mij wel richting glasvezel aan het duwen is…

Ik blijf erbij, ik geloof voor geen cent dan router modus en bridge modus invloed hebben op de T3 en T4 errors…

Helaas is Ziggo wel heel erg passief bezig, dit "probleem" speelt al vanaf maart!!!

Reputatie 7
Badge +8

@annoniempjuh kun je bij de buurman de up- en downstream plaatjes krijgen?

@annoniempjuh

Kun je de downstreams nog eens volledig hier posten? En wat de uptime is van het modem als je deze tabel hier post?

Hebben je buren ook Internet van Ziggo en dezelfde klachten? Zo ja: Hebben zij een Connectbox en wat laat de downstream daar zien?

Heb de Ubee 1318ZG, uptime is op het moment van schrijven 10 dagen 22uur 24 minuten.

 

 

 

CM IP Prov Mode: Honor MDD
Ethernet WAN Mode: 
Bidirectional Forwarding Detection: 
Current System Time: Sun Jul 19 10:23:03 2020

 

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 618000000 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 3 618000000 Hz 8000000 Hz 8.9 dBmV 40.1 dB QAM256 1371 446
2 Locked SC-QAM Downstream 1 602000000 Hz 8000000 Hz 9 dBmV 40.4 dB QAM256 3478 331
3 Locked SC-QAM Downstream 2 610000000 Hz 8000000 Hz 8.8 dBmV 40.5 dB QAM256 3047 272
4 Locked SC-QAM Downstream 4 626000000 Hz 8000000 Hz 9.3 dBmV 40.6 dB QAM256 2557 314
5 Locked SC-QAM Downstream 5 634000000 Hz 8000000 Hz 9.4 dBmV 40.6 dB QAM256 2093 353
6 Locked SC-QAM Downstream 6 642000000 Hz 8000000 Hz 9.4 dBmV 40.5 dB QAM256 2124 292
7 Locked SC-QAM Downstream 7 650000000 Hz 8000000 Hz 9.5 dBmV 40.5 dB QAM256 2116 324
8 Locked SC-QAM Downstream 8 658000000 Hz 8000000 Hz 9.4 dBmV 40.4 dB QAM256 2099 381
9 Locked SC-QAM Downstream 9 666000000 Hz 8000000 Hz 9.5 dBmV 40.5 dB QAM256 2008 389
10 Locked SC-QAM Downstream 10 674000000 Hz 8000000 Hz 8.8 dBmV 40.2 dB QAM256 1413 349
11 Locked SC-QAM Downstream 11 682000000 Hz 8000000 Hz 8.2 dBmV 40 dB QAM256 2981 354
12 Locked SC-QAM Downstream 12 690000000 Hz 8000000 Hz 8.1 dBmV 39.9 dB QAM256 3134 375
13 Locked SC-QAM Downstream 13 698000000 Hz 8000000 Hz 8.5 dBmV 40 dB QAM256 4404 335
14 Locked SC-QAM Downstream 14 706000000 Hz 8000000 Hz 8.2 dBmV 39.9 dB QAM256 2087 253
15 Locked SC-QAM Downstream 15 714000000 Hz 8000000 Hz 7.7 dBmV 39.8 dB QAM256 2337 263
16 Locked SC-QAM Downstream 16 722000000 Hz 8000000 Hz 7.3 dBmV 39.4 dB QAM256 3769 420
17 Locked SC-QAM Downstream 17 730000000 Hz 8000000 Hz 7.5 dBmV 39.5 dB QAM256 4769 360
18 Locked SC-QAM Downstream 18 738000000 Hz 8000000 Hz 7.8 dBmV 39.7 dB QAM256 4817 331
19 Locked SC-QAM Downstream 19 746000000 Hz 8000000 Hz 7.6 dBmV 39.6 dB QAM256 2455 227
20 Locked SC-QAM Downstream 20 754000000 Hz 8000000 Hz 7.5 dBmV 39.8 dB QAM256 2642 203
21 Locked SC-QAM Downstream 21 762000000 Hz 8000000 Hz 7.1 dBmV 39.6 dB QAM256 2490 236
22 Locked SC-QAM Downstream 22 770000000 Hz 8000000 Hz 6.6 dBmV 39.3 dB QAM256 3032 196
23 Locked SC-QAM Downstream 23 778000000 Hz 8000000 Hz 6.9 dBmV 39.5 dB QAM256 4090 185
24 Locked SC-QAM Downstream 24 786000000 Hz 8000000 Hz 7 dBmV 39.6 dB QAM256 1775 212
25 Locked SC-QAM Downstream 25 794000000 Hz 8000000 Hz 7.1 dBmV 39.6 dB QAM256 1866 176
26 Locked SC-QAM Downstream 26 802000000 Hz 8000000 Hz 7.2 dBmV 39.7 dB QAM256 1102 216
27 Locked SC-QAM Downstream 27 810000000 Hz 8000000 Hz 6.6 dBmV 39.6 dB QAM256 1126 216
28 Locked SC-QAM Downstream 28 818000000 Hz 8000000 Hz 7.1 dBmV 39.7 dB QAM256 1891 212
29 Locked SC-QAM Downstream 29 826000000 Hz 8000000 Hz 6.5 dBmV 39.5 dB QAM256 1218 220
30 Locked SC-QAM Downstream 30 834000000 Hz 8000000 Hz 6.3 dBmV 39.4 dB QAM256 1163 252
31 Locked SC-QAM Downstream 31 842000000 Hz 8000000 Hz 6 dBmV 39.2 dB QAM256 1107 369
32 Locked SC-QAM Downstream 32 850000000 Hz 8000000 Hz 5.6 dBmV 38.9 dB QAM256 1574 331

 

 

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 47 dBmV 2
2 Locked ATDMA 2 50900000 Hz 6400000 Hz 46.5 dBmV 2
3 Locked ATDMA 3 44000000 Hz 6400000 Hz 46 dBmV 2
4 Locked ATDMA 4 37100000 Hz 6400000 Hz 46.5 dBmV 2
5 Locked ATDMA 5 31800000 Hz 3200000 Hz 47 dBmV 2
6 Locked ATDMA 6 28600000 Hz 3200000 Hz 47.5 dBmV 2

 

Ik heb een buurman die heeft de connecbox (geen idee welke) en die merkt niks, maar die is ook geen power user! (en zit weinig op internet.)

Reputatie 7
Badge +8

@annoniempjuh 

Kun je de downstreams nog eens volledig hier posten? En wat de uptime is van het modem als je deze tabel hier post?

Hebben je buren ook Internet van Ziggo en dezelfde klachten? Zo ja: Hebben zij een Connectbox en wat laat de downstream daar zien?

nou vandaag is het weer raak! meerdere keren een lading T3 en T4 errors!

Helaas niet een aantal "mooie" logboek screenshots kunnen maken maar weet zeker dat aan Ziggo' kant wel een aantal gegevens zijn bewaard…

Ik vraag me nu toch echt af wat dit kan zijn… Wordt er stront  chagrijnig van!

 

Funfact. in de tijd dat er veel problemen waren met cloudflare (17/07 +/-23:00u) heb ik nul problemen gehad!

afgelopen weekend was het heel slecht, TE slecht!

maar nu is het vanaf maandag best oké, merk weinig problemen (lees, heb niks handmatig moeten doen), hoewel de logboek nog wel wat T3/T4 errors voorbij komen…

Maar ja, dit is dus al 3 maanden zo. zo heb ik dagen nul problemen, en zo heb ik dagen een en al allende, Ik kan er geen touw aan vast knopen.

 

Dit probleem is net zoals het weer; Het slaat zo om...

Hi @annoniempjuh,

De meting is afgelopen en ik zie inderdaad de uitval terug ten tijde van je bericht. Ook later die nacht ging het niet helemaal goed. De oorzaak zie ik helaas niet. Echter, daarna is het wel stukken beter gegaan. Klopt dat? Hoe is het gegaan de afgelopen dagen?

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...

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.

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...)

 

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.

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;

 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;

 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...

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

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:

 

 

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

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!

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...

Reageer