4 Messages
I can no longer access Event and System logs in Gateway tool
I've been experiencing connection issues and trying to troubleshoot it. I was looking for logs a week ago and could access the Event logs, which was throwing DHCP errors with codes 24 and 82 missing option.
Fast forward a week later and I can no longer access the Event logs, only the firewall logs.
My main connection issue is randomly for 30 seconds-2min I experience high packet loss, that quickly subsides but can lead to disconnects and is frustrating. It can make gaming and even simple web browsing tiresome.
I am using ethernet but Wi-Fi interrupts still happen frequently on my home network. While digging through forums to troubleshoot the issue I noticed my upstream power levels to be above spec ranging from 51.02- 56.93
Downstream
|
Channel Bonding Value | |||||||||||||||||||||||||||||||||
Channel ID |
28
|
20
|
36
|
44
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
29
|
30
|
31
|
32
|
33
|
34
|
35
|
37
|
38
|
39
|
40
|
41
|
42
|
43
|
0
|
193
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Lock Status |
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
|
Frequency |
591000000
|
543000000
|
639000000
|
687000000
|
501000000
|
507000000
|
513000000
|
519000000
|
525000000
|
531000000
|
537000000
|
549000000
|
555000000
|
561000000
|
567000000
|
573000000
|
579000000
|
585000000
|
597000000
|
603000000
|
609000000
|
615000000
|
621000000
|
627000000
|
633000000
|
645000000
|
651000000
|
657000000
|
663000000
|
669000000
|
675000000
|
681000000
|
959800000
|
|
SNR |
43.376591
|
44.625977
|
43.376591
|
44.625977
|
43.376591
|
43.376591
|
44.625977
|
43.376591
|
43.376591
|
43.376591
|
43.376591
|
43.376591
|
43.376591
|
44.625977
|
43.376591
|
44.625977
|
43.376591
|
43.376591
|
44.625977
|
43.376591
|
43.376591
|
43.376591
|
44.625977
|
43.376591
|
43.376591
|
40.946209
|
44.625977
|
43.376591
|
43.376591
|
40.366287
|
40.946209
|
43.376591
|
42.60 dB
|
|
Power Level |
7.500000
|
7.500000
|
7.699997
|
6.900002
|
7.699997
|
7.900002
|
7.900002
|
7.699997
|
7.800003
|
7.500000
|
7.699997
|
7.500000
|
7.599998
|
7.500000
|
7.599998
|
7.699997
|
7.599998
|
7.699997
|
7.500000
|
7.699997
|
7.900002
|
7.800003
|
7.500000
|
7.800003
|
7.599998
|
7.500000
|
7.099998
|
7.099998
|
7.099998
|
7.000000
|
7.000000
|
6.800003
|
3.400002 dBmV
|
|
Modulation |
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
QAM256
|
OFDM
|
Upstream
|
Channel Bonding Value | |||||
Channel ID |
3
|
4
|
2
|
1
|
41
|
|
---|---|---|---|---|---|---|
Lock Status |
Locked
|
Locked
|
Locked
|
Locked
|
Locked
|
|
Frequency |
29200000
|
35600000
|
22800000
|
16400000
|
39900000-84275000
|
|
Symbol Rate |
5120 KSym/sec
|
5120 KSym/sec
|
5120 KSym/sec
|
5120 KSym/sec
|
0 KSym/sec
|
|
Power Level |
52.520599
|
51.020599
|
54.520599
|
54.520599
|
56.932629
|
|
Modulation |
64QAM
|
64QAM
|
64QAM
|
64QAM
|
OFDMA
|
|
Channel Type |
US_TYPE_ATDMA
|
US_TYPE_ATDMA
|
US_TYPE_ATDMA
|
US_TYPE_ATDMA
|
US_TYPE_OFDMA
|
CM Error Codewords | |||||||||||||||||||||||||||||||||
Channel ID |
28
|
20
|
36
|
44
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
29
|
30
|
31
|
32
|
33
|
34
|
35
|
37
|
38
|
39
|
40
|
41
|
42
|
43
|
0
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Unerrored Codewords |
1876358164
|
1874991479
|
1874999177
|
1875004081
|
1875023876
|
1875029184
|
1875007230
|
1875009136
|
1875034582
|
1875040948
|
1875037140
|
1875029465
|
1875034165
|
1875056937
|
1874986592
|
1874978539
|
1874975197
|
1874965922
|
1874972336
|
1874977539
|
1874986166
|
1874976871
|
1874951937
|
1874975878
|
1874969383
|
1874972628
|
1875038441
|
1875033637
|
1875007943
|
1875040598
|
1875038127
|
1875065224
|
0
|
Correctable Codewords |
11836
|
9786
|
9580
|
8858
|
6835
|
6203
|
10188
|
7400
|
6875
|
6762
|
7381
|
8919
|
9434
|
8182
|
7217
|
8083
|
10246
|
9863
|
10589
|
8929
|
8843
|
9264
|
13295
|
11129
|
11971
|
8785
|
9372
|
9927
|
11164
|
9960
|
9031
|
7616
|
0
|
Uncorrectable Codewords |
74201
|
61365
|
54020
|
54419
|
35994
|
36449
|
59073
|
41706
|
39479
|
37790
|
45596
|
56520
|
60864
|
40615
|
40120
|
51750
|
57776
|
72128
|
69215
|
52183
|
57067
|
66460
|
87951
|
70588
|
76787
|
52429
|
63020
|
67395
|
76945
|
64966
|
53280
|
47172
|
0
|
It seems I may need to have a tech come to my home to diagnose the problem further, but any help would be greatly appreciated.
train_wreck
Contributor
•
35 Messages
3 months ago
Not sure what device or what method you are using to access it, but if you're using a browser try either clearing the cache or opening up a private window. And of course a reboot of the device, sometimes the management interface daemons running on them crash/lock up. But yes looks like an upstream impairment of some kind, check cable connections and temporarily remove splitters and if you feel up for it try moving the modem closer to where the outside coax comes in. If none of those help yeah you'll probably need to get them to take a look.
1
0
EG
Expert
•
107.1K Messages
3 months ago
@user_59erfv
Yes. The upstream power is too high / out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
Good luck with it !
1
0
EG
Expert
•
107.1K Messages
3 months ago
Yes, it's normal. The upstream power level and the downstream power level work opposite of each other. When the overall line attenuation is reduced by removing a splitter, the upstream power will become lower but the downstream power will become higher / stronger. It's a balancing act between the two.
If the high downstream power now becomes a problem you could try inserting a -6 dB forward path-only attenuator pad such as this one on the coax port on the rear of the modem to knock that power level down and see: https://www.amazon.com/line-Signal-Forward-Attenuator-FPA6-54/dp/B07882H96R
It won't affect the upstream power level.
Channels 1 and 41 are still on the high side. You may want to get a tech out to properly balance the line levels.
(edited)
7
0
EG
Expert
•
107.1K Messages
3 months ago
@user_59erfv @train_wreck
These are the right choice for use in mid-split upgraded areas. They start at 85 MHz;
https://www.multicominc.com/product/multicom-mul-fpa85-forward-path-attenuator/
(edited)
1
EG
Expert
•
107.1K Messages
3 months ago
Whattaya' gonna' do......
0