Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 [2]

Author Topic: Upstream target snrm  (Read 1504 times)

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #15 on: September 02, 2018, 12:12:00 AM »

I do hate that large distracting advert, which is really a nuisance.
Logged

jelv

  • Helpful
  • Kitizen
  • *
  • Posts: 1207
Re: Upstream target snrm
« Reply #16 on: September 02, 2018, 10:34:35 AM »

How
Not wishing to hijack this thread with irrelevances, I'll just briefly say that if I use the TBB speedtest utility (yes, logged into the main site) I expect it to give me the result, sensibly, and not be expected to left-click anywhere else.
don't disagree with that!
http://forums.thinkbroadband.com/newsite/t/4599794-speedtest-results-graph-key.html
« Last Edit: September 02, 2018, 10:37:24 AM by jelv »
Logged
Line rental: Pulse8, Broadband: AAISP Home::1 FTTC 80/20, Mobile: id Mobile

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #17 on: September 03, 2018, 07:37:11 AM »

After some sort of funny error episode and a resync, the upstream on line 2 the new line has jumped from 440k to 555kbps. However, no matter what I do with slight rate tweaks, the upstream figure given by the AA speedtester is down at 1.12Mbps.
Logged

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #18 on: September 03, 2018, 10:08:52 AM »

And more oddities. Janet turned modem #2 off for a good long while, and the downstream sync went up by well over a 110 kbps, but aside from that the upstream as reported by the AA speed-tester went up from 1.12 to 1.42 Mbps. I have no idea what that is all about.
Logged

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #19 on: September 05, 2018, 12:50:27 AM »

Now fixed.

After the earlier mistake, Janet turned off the correct modem #3 and left it off for a couple of hours. And this cured the upstream: - #3 upstream went from 318k to 435k sync at 59.dB.

This was AA’s suggestion - one to remember - turning it off for ages really works.
Logged

burakkucat

  • Global Moderator
  • Senior Kitizen
  • *
  • Posts: 24615
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Upstream target snrm
« Reply #20 on: September 05, 2018, 12:57:19 AM »

That is good to know.  :)

Perhaps, as a conclusion of this thread, you would post the aggregate DS & US throughput speeds you now achieve with your four line set-up, please?
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #21 on: September 05, 2018, 04:57:46 AM »

line #1 downstream sync 3037kbps, AA TX rate d/s 2536323
line #2 downstream sync 2880kbps, AA TX rate d/s 2405610
line #3 downstream sync 2891kbps, AA TX rate d/s 2414827
line #4 downstream sync 2924kbps, AA TX rate d/s 2442478

line #1 u/s sync 515kbps [Firebrick rate set to 97%]
line #2 u/s sync 551kbps [Firebrick rate set to 97%]
line #3 u/s sync 435kbps [Firebrick rate set to 97%]
line #4 u/s sync 452kbps [Firebrick rate set to 97%]
Logged

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #22 on: October 10, 2018, 01:01:28 PM »

This upstream problem is back again. It is line #3, again. The upstream sync rate was 442k, not very good compared with the others.

(Janet had got two of the modems (not links) mixed up, in the sense that each has a label on it and has a configuration with a unique, non-clashing admin interface IP address, and the units on links #2 (mux switch port 2, VLAN 102, line #2) and #3 (mux  switch port #3, VLAN 103, line #3) were swapped, so that the FireBrick was trying to talk to a modem at 192.168.2.1 and that modem was listening to 192.168.3.1, thinking ‘I am modem #3’, and the reverse for the modem on link #3. So I asked her to switch them over.)

This involved powering them down, as I always think that is safer from the point of view of DLM. When powered back up, modem on link #3 had now dropped its upstream sync speed from 442k to 347k. So remembering the previous fix, left modem off for 45 mins, back on, no good, now the upstream sync was down to 338kbps.

Last time, I left a modem on this line turned off for several hours. I will try that again at some point. But I still wonder what on earth is going on. Why does this line lose 24% of its upstream sync rate ? And if turning it off for ages works, how long is an age, and why does some particular, greater length of time work?


Another matter - another modem: Much earlier this morning, I did a target SNRM reset on line #2. Unfortunately this dropped the upstream sync rate from 568kbps to 496kbps on this modem too. (But its downstream sync did go up by 67k, so not all bad.) So a total loss of 176k of upstream, which is over 10%, so not a good day for upstream, whilst downstream rates improved. Why is it that I can just lose a fair sized chunk of upstream on these modems ?


AA staff noticed that the upstream side loop loss has increased by 0.3dB on that line. There has been a massive amount of rain, but it is not raining right this minute. Makes me wonder if the line is lying in a lot of water - wonder if that could make a difference at lower frequencies?
« Last Edit: October 10, 2018, 02:00:44 PM by Weaver »
Logged

johnson

  • Reg Member
  • ***
  • Posts: 540
Re: Upstream target snrm
« Reply #23 on: October 11, 2018, 01:16:22 AM »

Not sure how closely you monitor the SNRM of your lines over time Weaver, but I cant help thinking an overview of how it changes over the course of the day might help clear up the reasons for these differences in rates after a resync.

You may remember I was fiddling with a simple server running on VMG1312/8x24s to serve data and some javascript to make it into graphs client side. I finally got around to making the time series data work acceptably today so if you felt like being a guinea pig with one of your modems you could try the simplest possible version that just logs SNRM over a 24 hour period and graphs it. I have it doing more things but am not confident the range detection will work with lines other than VDSL2, its hard to test without a live ADSL/ADSL2+ line, so rather than offer something that might not work I can make one that just has the SNRM logging and graphing.

No problem at all if you don't like the idea of another http server running on your modems or wouldn't be up for the hassle of flashing, testing etc, but let me know if you would.

For example, a resync at half 11 this evening would have probably resulted in suboptimal speed:

Logged

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #24 on: October 11, 2018, 09:54:08 AM »

That’s a very thoughtful and generous offer. You really are a star! A lot of pain, burning and confusion today, so I can’t do much. I will have to return to this when I am rather better.

So to recap, need to get a picture of when is the good / bad time for a resync?

I don’t have any kit that is capable of being set up for monitoring, so your solution would be perfect.

I can however, ask the ISP to tell me some of the basic line stats, and they query the DSLAM etc remotely, reporting back with a current snapshot of the SNRM, sync rate and loop loss etc in both directions. Of course the other way is for me to query the modem directly: using a web browser doesn’t work well because the stupid web UI has Safari-related problems with info being off-screen and scrolling not working. The command line is of course far better.

I can telnet but not SSH for some reason, which might be to do with NATing to the modems through the router (a Firebrick) which rewrites src IP addresses. If I could get SSH to work, I have a tool (in the iOS12 ’Shortcuts’ app) that can launch remote shell commands via SSH and get the response back programmatically so I could hopefully write something nice to query all kinds of status info and handle it in an iPad ’Shortcuts’ program. (Doing the same kind of thing by web ‘scraping’ the modem’s status info web page would be really nasty, having to deal with html tag soup, ugh, and having to work out how to log in, what the right URLs are, all a pain doing it via http meant for humans.)
« Last Edit: October 11, 2018, 10:08:48 AM by Weaver »
Logged

johnson

  • Reg Member
  • ***
  • Posts: 540
Re: Upstream target snrm
« Reply #25 on: October 11, 2018, 10:45:18 AM »

So to recap, need to get a picture of when is the good / bad time for a resync?

I cant speak for your ADSL2+ line, but on my noisy VDSL line the choice of time to resync can cause several mbps of difference in downstream, so a little under 10% on my ~25mbit/s connection. Maybe SNRM doesnt have the same influence on yours, but it seems like something sensible to rule out.

Quote
I can telnet but not SSH for some reason, which might be to do with NATing to the modems through the router (a Firebrick) which rewrites src IP addresses. If I could get SSH to work, I have a tool (in the iOS12 ’Shortcuts’ app) that can launch remote shell commands via SSH and get the response back programmatically so I could hopefully write something nice to query all kinds of status info and handle it in an iPad ’Shortcuts’ program. (Doing the same kind of thing by web ‘scraping’ the modem’s status info web page would be really nasty, having to deal with html tag soup, ugh, and having to work out how to log in, what the right URLs are, all a pain doing it via http meant for humans.)

The mongoose server (written in C and very small ~ 300K) is super basic and as it is just serves files produced by running a shell script on the modem. One GET request to the /getdata URI and the script is run to invoke xdslcmd etc to create files with SNR/bitloading/whathaveyou, then you can fetch them with similarly simple GET requests /SNR /Bits /Hlog etc. So its easy to fetch the data from javascript running on any tablet PC etc and draw graphs, but could be equally simple to summon it using Workflow and the returned files are just plain text which should be easy to parse, no tag soup etc. Also doesn't need any authentication... this may seem worrying, but with no commands passed and interpreted or important things done it doesn't seem like a big deal and simplifies things a lot.

I'l make a VMG1312 firmware with the most basic setup and a more detailed explanation later.

Hope you feel better soon!  :)
Logged

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #26 on: October 11, 2018, 11:38:04 AM »

You’re right about authentication. I can firewall off the modems from inappropriate LAN access anyway.
Logged

johnson

  • Reg Member
  • ***
  • Posts: 540
Re: Upstream target snrm
« Reply #27 on: October 14, 2018, 12:04:55 PM »

Have made a firmware if you feel like testing on one of your modems Weaver:

https://forum.kitz.co.uk/index.php/topic,21685.msg384925.html#msg384925

Again, absolutely no worries if it isn't for you.  ;D
Logged

Weaver

  • Addicted Kitizen
  • *****
  • Posts: 6569
  • Retd sw dev; A&A; 4 × 7km ADSL2; IPv6; Firebrick
Re: Upstream target snrm
« Reply #28 on: October 14, 2018, 10:42:10 PM »

Wow. That is incredibly generous.  ;D  Would anyone reading this give Kitz a donation as a thank you to Johnson, if they are able?
Logged
Pages: 1 [2]
 

anything