Print

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

[ktz392837]

Does anyone know why some zyxel 8324 do not upload attenuation figures to MDWS? Eg roseway kitz etc

[roseway]

In my case, using the VMG8324 in bridge mode, the modem doesn't report any values for overall attenuation, up or down.

[j0hn]

It does for most using it, no idea why it doesn't for others.
see: angrymonkey, ronski, skyeci, longstaff, samwise78.
5 out of 6 listed as using the 8924 (including me) are showing correctly.

I don't think BCM modems give upstream attenuation over telnet on vdsl2. All the users on MDWS who show upstream attenuation are on ADSL. The exception is 1 vdsl2 user who is showing as using a Thom/Tech TG589vn v3.

There's 1 user, hypericum, listed as using a Billion 8800NL with 0 down attn but I'd throw a guess they simply haven't updated their modem on their MDWS profile.
It's hard to get exact figures as roughly 25% of users don't identify which modem they use.

I wonder if it might be firmware related? what firmware version are you using roseway?

edit: corrected incorrect auto-correct

[LordFox]

I use the VMG8324 in bridge mode, firmware 1.00(AAKL.14)C0. It's set in MDWS (same username). The modem shows the downstream and upstream total attenuations in its GUI, but the upstream is missing from the telnet data gathered by DSLstats...

The modem's GUI shows, (down/up):
Total Attenuation:       15.7 dB           15.0 dB

In the Stats and Telnet Data/Connection Stats windows of DSLstats 5.8 it shows
Attn(dB):        15.3            0.0

And of course there's a flat zero line for the upstream attenuation in MDWS.

So, there seems to be a discrepancy between the modem's GUI and what it says by telnet.

[roseway]

I wonder if it might be firmware related? what firmware version are you using roseway?

Yes, this occurred to me as I was reading your post. I'm using the 6b1 firmware, and I'm fairly sure that Kitz does too, for the same reason - it's the last firmware version in which multiple telnet logins were possible. Since that version, only a single telnet login has been allowed at any one time (and I wonder if this restriction may be indirectly responsible in some way for the periodic telnet timeout errors which some users report).

[skyeci]

Never had a timeout (due to the modem) on my v14 8324 in Bridge mode using hg612 stats on windows 10

[broadstairs]

If you are using the 8324 as modem only then I'm not entirely surprised since the device has significantly less work to do in that mode, if you have it behind a modem then again less work to do and therefore less chance of it being busy.

Stuart

[skyeci]

We also spent a lot of time (be & myself) trying to get the 8924 I had to not miss minutes in Bridge mode. No matter what we tried it would skip 5 minutes at around 1hr and 47 mins... we tried all sorts. I know there are others with no issues on the 8924 but there we go..

[kitz]

I'm using the 6b1 firmware, and I'm fairly sure that Kitz does too,

Yes, I'm using 6b1.   
Total attenuation is not reported via telnet. But it does in the GUI.


From the web GUI

Code: [Select]

============================================================================
    VDSL Training Status:   Showtime
                    Mode:   VDSL2 Annex B
            VDSL Profile:   Profile 17a
            Traffic Type:   PTM Mode
             Link Uptime:   6 days: 1 hour: 51 minutes
============================================================================
       VDSL Port Details       Upstream         Downstream
               Line Rate:     20.202 Mbps       80.103 Mbps
    Actual Net Data Rate:     20.000 Mbps       79.987 Mbps
          Trellis Coding:         ON                ON
              SNR Margin:       12.6 dB            7.1 dB
            Actual Delay:          0 ms              0 ms
          Transmit Power:        5.9 dBm           5.9 dBm
           Receive Power:       -6.3 dBm           1.4 dBm
              Actual INP:        0.0 symbols       0.0 symbols
       Total Attenuation:       12.2 dB           12.8 dB
Attainable Net Data Rate:     30.423 Mbps       84.461 Mbps
============================================================================
      VDSL Band Status    U0      U1      U2      U3      D1      D2      D3
  Line Attenuation(dB):  0.7    18.2    27.7     N/A    10.9    24.2    38.0   
Signal Attenuation(dB):  0.5    18.1    27.7     N/A    10.6    24.0    38.0   
        SNR Margin(dB): 14.6    13.2    12.3     N/A     7.1     7.1     7.1   
   Transmit Power(dBm):- 6.0   -25.9     5.6     N/A    12.0     7.4     7.4   
============================================================================

via telnet

Code: [Select]

> adsl info --show
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 30437 Kbps, Downstream rate = 84465 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 79987 Kbps

Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        7.1             12.6
Attn(dB):        0.0             0.0
Pwr(dBm):        5.9             5.9

[skyeci]

on my v14

 the modem gui shows both up and down values
hg612 stats only shows down and not up
telnet only shows the down figure ....

strange...

[ktz392837]

If using a firmware with no total attenuation do you think failover to a best guess combination of the band figures would be an idea? 

A change in attenuation is a useful diagnostic so it would be better than nothing.

I dare to suggest   if separate bands are available could a graph be added perhaps one for d and one for u bands?

Thanks

[kitz]

DSL stats does provide this info.
Unless you have some sort of line fault, attenuation shouldn't really change much from week to week.

However I can see what you mean re a diagnostic basis on MDWS.  ie if you are wanting to look at others stats with a similar attenuation to see what speeds they get.

[roseway]

My feeling is that an attenuation graph would be OTT for something which normally changes little over time, as Kitz says. But I quite like the idea of calculating a best guess for those modems which don't report overall attenuation values but do report attenuation values per band. We should be able to formulate an algorithm to convert the per band figures to overall figures, and check that the calculated results match the values reported by the modem (only in the GUI in the case of the VMG8324).

We tend to talk loosely about "attenuation" but of course line attenuation and signal attenuation are different things. Line attenuation rarely changes at all unless there's a fault (or a change of modem) but signal attenuation changes continuously by small amounts. I think we're talking about line attenuation here, because few if any modems report overall signal attenuation values for VDSL2 connections.

So if anyone wants to propose a conversion algorithm I'll be very interested. It will presumably be some sort of weighted average, but how it's weighted I have no idea.

[ktz392837]

I have been trying to work out a formulae but no success yet.

 Taking a download band example from above:

10.9, 24.2, 38.0 = 12.2

1/3, 1/6, 1/9 = about 12

May be close but unsure? I wonder how Zyxel do it?

If we do find an acceptable formula perhaps need to indicate the figure is best guess in MDWS by changing background colour of appropriate areas.

[roseway]

I'm not sure that the figures in the Zyxel GUI can be relied on. I've noticed in mine that the upstream figure for total attenuation is higher than the downstream, although the per-band figures don't seem to agree.