cancel
Showing results for 
Search instead for 
Did you mean: 

Intermittent very slow download, normal upload

disruptive
Up to speed
The results are in...

We're all done measuring - here's how your broadband speed stacks up.

2.8Mbps average download speed
10.0Mbps average upload speed
 
Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
12030000002.730256 qam9
21390000004.330256 qam1
31470000003.728256 qam2
41550000003.528256 qam3
51630000002.928256 qam4
61710000003.727256 qam5
71790000002.528256 qam6
81870000002.731256 qam7
91950000001.930256 qam8
102110000001.427256 qam10
112190000002.530256 qam11
122270000001.433256 qam12
13235000000235256 qam13
142430000001.237256 qam14
152510000002.737256 qam15
162590000001.937256 qam16
172670000002.538256 qam17
182750000001.537256 qam18
192830000002.237256 qam19
20291000000134256 qam20
212990000002.235256 qam21
223070000001.536256 qam22
233150000002.237256 qam23
243230000001.937256 qam24


Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked31.1521532186159
2Locked31.61387298239231832881
3Locked29.91864202562702605983
4Locked29.8-1960977560152587190
5Locked29.41588295711377713
6Locked28.7194198113819003182
7Locked30.2111788303621268
8Locked33.361100365102
9Locked31.619239347891
10Locked28-2065419403198897718
11Locked31.11888078974130307
12Locked33.353537067112
13Locked36.312991177
14Locked37.682449
15Locked38.253969
16Locked38.63380
17Locked38.640817
18Locked38.65340
19Locked37.34410
20Locked34.9369470
21Locked35313171
22Locked37.34010
23Locked37.64270
24Locked37.33040

 

Rebooted a couple of days ago. Post RS Errors increasing a lot.

 

1 ACCEPTED SOLUTION

Accepted Solutions

lotharmat
Community elder
Wow - the RxMER (A measure of Signal to noise) is too low on some channels giving the PostRS errors -

VM need ot book an engineer to fix this.

In the meantime - set a clean slate:

1. Power off your hub and leave off for 5 minusyres
2. Check that all connections are 'finger tight'
3. Power back on the hub
4. Give it 5 minutes to settle
5. Re post the logs!

Let's see if that has any effect on the RxMER



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

See where this Helpful Answer was posted

6 REPLIES 6

lotharmat
Community elder
Wow - the RxMER (A measure of Signal to noise) is too low on some channels giving the PostRS errors -

VM need ot book an engineer to fix this.

In the meantime - set a clean slate:

1. Power off your hub and leave off for 5 minusyres
2. Check that all connections are 'finger tight'
3. Power back on the hub
4. Give it 5 minutes to settle
5. Re post the logs!

Let's see if that has any effect on the RxMER



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

SNR/RxMER all 38+, speedtest giving expected speeds, only a small number of Pre RS errors and no Post RS ones.

Only fly in the ointment is that I ran a speedtest just prior to performing your suggested actions and also got the expected speed. As per the title, this is intermittent 😞

OK, afternoon chore is to automate this data gathering.

 

Also, set up a 'Broadband Quality Monitor'. This will monitor the state of your connection and record any network dropouts etc - You can do this at ThinkBroadband (https://www.thinkbroadband.com/broadband/monitoring/quality)
Give it a while to gather data and then click 'Share Live graph' and paste the 'Direct Link' into the forum!

I'd suggest keeping a log of these levels (excel or something similar) this will help when the engineer is inevitably booked!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

The one good thing about this is that I've looked into monitoring the status of the CM. Thanks to other pages on this board I know that

http://192.168.0.1/walk?oids=1.3.6.1.2.1.10.127.1.1.4.1.4

gives the Post RS Errors in JSON format:

{
"1.3.6.1.2.1.10.127.1.1.4.1.4.3":"59",
"1.3.6.1.2.1.10.127.1.1.4.1.4.48":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.49":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.50":"2",
"1.3.6.1.2.1.10.127.1.1.4.1.4.51":"14",
"1.3.6.1.2.1.10.127.1.1.4.1.4.52":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.53":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.54":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.55":"26",
"1.3.6.1.2.1.10.127.1.1.4.1.4.56":"1",
"1.3.6.1.2.1.10.127.1.1.4.1.4.57":"47",
"1.3.6.1.2.1.10.127.1.1.4.1.4.58":"45",
"1.3.6.1.2.1.10.127.1.1.4.1.4.59":"121",
"1.3.6.1.2.1.10.127.1.1.4.1.4.60":"48",
"1.3.6.1.2.1.10.127.1.1.4.1.4.61":"75",
"1.3.6.1.2.1.10.127.1.1.4.1.4.62":"25",
"1.3.6.1.2.1.10.127.1.1.4.1.4.63":"22",
"1.3.6.1.2.1.10.127.1.1.4.1.4.64":"28",
"1.3.6.1.2.1.10.127.1.1.4.1.4.65":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.66":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.67":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.68":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.69":"0",
"1.3.6.1.2.1.10.127.1.1.4.1.4.70":"0",
"1":"Finish"
}

 

at the minute. http://192.168.0.1/walk?oids=1.3.6.1.2.1.10.127.1.1.4.1.5 appears to be the SNR:

{
"1.3.6.1.2.1.10.127.1.1.4.1.5.3":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.48":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.49":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.50":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.51":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.52":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.53":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.54":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.55":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.56":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.57":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.58":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.59":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.60":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.61":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.62":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.63":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.64":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.65":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.66":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.67":"389",
"1.3.6.1.2.1.10.127.1.1.4.1.5.68":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.69":"386",
"1.3.6.1.2.1.10.127.1.1.4.1.5.70":"386",
"1":"Finish"
}

 which is still looking good.

Running the following hacky line is good enough at the moment:

echo -n $(date -u +%Y-%m-%d,%T,) >> error_count.csv; wget -q -O - http://192.168.0.1/walk?oids=1.3.6.1.2.1.10.127.1.1.4.1.4 | grep "1.3.6.1.2.1.10.127.1.1.4.1.4"| sed 's/1.3.6.1.2.1.10.127.1.1.4.1.4.//;s/:/,/'| sort | xargs >> error_count.csv

The only thing I don't understand is why this reboot worked (with the 5min+ gap) and the one I did previously (with only a few seconds between turning off and on) didn't.

Anyway all fine so far 🙂

 

Nice!! - Love the coding!! - I'm so nicking that

I *think* leaving it off for 5 minutes causes the modem to fully re-establish a connection to the CMTS and possibly grab different channel frequencies etc.



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

Still fine so I'm happy to call that fixed.

Lots of stuff on GitHub to do various things with the Hub3. Didn't realise the SNMP stuff was exposed by the web interface. In case it helps others, the device-specific MIBs are here:

https://mibs.observium.org/mib/ARRIS-CM-DEVICE-MIB/

https://mibs.observium.org/mib/ARRIS-ROUTER-DEVICE-MIB/

Values can be set through that interface too, but that seems a little too dodgy for this forum 🙂