Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[plexy]

Hi all,
Just wondering why DSLstats (same version as always) has now started reporting US SNRM per tone, HLOG US and US QLN? It never used to...

[roseway]

If DSLstats wasn't reporting those ranges before, then I presume that the router wasn't reporting them. Did you by any chance keep a copy of the raw telnet data for the earlier period?

[plexy]

Hi Roseway
Thanks for the reply, I have emailed you both old telnet data and current telnet data. All the best!

[ryant704]

The US will be reported if the DLM made a change, if a user resets the modem these will not be reported until the DLM forces a re-sync again. (ECI cabinets)

[plexy]

The US will be reported if the DLM made a change, if a user resets the modem these will not be reported until the DLM forces a re-sync again. (ECI cabinets)

Thanks for the explanation, appreciated.

[Bald_Eagle1]

However, this is a connection from a Huawei DSLAM.

Has your band plan changed at all, as spotted by one other Kitz forum user?

The usual Huawei plan from pbParams is/was:-

Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3959)

[plexy]

slightly different from what you posted, but not far off

Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3971)
Medley Phase (Final) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3971)

[Bald_Eagle1]

slightly different from what you posted, but not far off

Discovery Phase (Initial) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3971)
Medley Phase (Final) Band Plan
US: (0,95) (868,1207) (1972,2783)
DS: (32,859) (1216,1963) (2792,3971)

So, it has changed (highlighted in red text in your example).
Your connection was still as per the example I posted in the montage you had posted in another thread (line_stats-P-20130926-0800.png)

The other user saw exactly the same slight change which also coincided with him seeing US data for the first time from his Huawei DSLAM.


AFAIK, there has been no official mention of this via BTOR, just as when it also wasn't mentioned at the previous change from the highest tone discovered of 3939 to 3959.


This may be a DSLAM update or an automated modem update.
I presume it must have actually changed during a resync?


From the modem's GUI 'Device' page, have any of these details changed at all:-

Product type  EchoLife HG612   
Hardware version  VER.B 
Software version  V100R001C01B028SP10 
Firmware version  A2pv6C030b.d22g 
Batch number      BC1P10.028.A2pv6C030b.d22g 
System up time    15 days 6 hours 58 minutes 4 seconds 


I wonder if BS is able to shed any light on these changes for us?

[plexy]

Interesting. The plot thickens! Last night my modem dropped for a good 15 mins till I rebooted it ("No signal" shown in Device->WAN->XDSL report) . Today there were two OR vans by the cab - one was a cable layer/workshop van with reels on a towbar at the back). Saw no contractor stickers on either van. The US reporting changed late in the afternoon today.

I presume it must have actually changed during a resync?

I did a modem reboot in the afternoon evening today also, so yes that's highly probable.

Product type   EchoLife HG612 
Device ID   10C61F-<redacted>
Hardware version   VER.B
Software version   V100R001C01B028SP10
Firmware version   A2pv6C030b.d22g
Batch number   BC1P10.028.A2pv6C030b.d22g
System up time   0 days 5 hours 19 minutes 22 seconds

[ryant704]

Interesting. The plot thickens! Last night my modem dropped for a good 15 mins till I rebooted it ("No signal" shown in Device->WAN->XDSL report) . Today there were two OR vans by the cab - one was a cable layer/workshop van with reels on a towbar at the back). Saw no contractor stickers on either van. The US reporting changed late in the afternoon today.

MSAN Firmware update I Would imagine, seems like they are adding a few more tones available for the DLM to use.

You can contact your ISP if there was any planned work, doubt level 1 will be able to get that Information so might not be worth the hassle as there is nothing really wrong with your service.

[roseway]

Hi Roseway
Thanks for the reply, I have emailed you both old telnet data and current telnet data. All the best!

As far as I can see, there's no material difference between those two text files, so they don't explain your observation. From my own experience of using the HG612 on an ADSL2+ connection, the reporting of upstream SNR is intermittent, but I don't know if the same applies on VDSL2.

[plexy]

Hi Roseway
Thanks for the reply, I have emailed you both old telnet data and current telnet data. All the best!

As far as I can see, there's no material difference between those two text files

Odd, I definitely see a difference. Snippet for comparison

test2.txt

Tone number      SNR
   0      0.0000
   1      0.0000
   2      0.0000
   3      0.0000
   4      0.0000
   5      0.0000
   6      0.0000
   7      0.0000
   8      26.0000
   9      26.0000
   10      26.0000
   11      26.0000
   12      26.0000
   13      26.0000
   14      26.0000
   15      26.0000
   16      41.0000
   17      41.0000
   18      41.0000
   19      41.0000
   20      41.0000
   21      41.0000

whereas test.txt

Tone number      SNR
   0      0.0000
   1      0.0000
   2      0.0000
   3      0.0000
   4      0.0000
   5      0.0000
   6      0.0000
   7      0.0000
   8      0.0000
   9      0.0000
   10      0.0000
   11      0.0000
   12      0.0000
   13      0.0000
   14      0.0000
   15      0.0000
   16      0.0000
   17      0.0000
   18      0.0000

[roseway]

The text files I received only contained bitloading data. Maybe that's an issue with my email program.

But in any event, the snippets above show what I was assuming to be the case, namely that for some reason the router doesn't always report all the SNR data. I don't know the reason for that.