Print

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

[dandnsmith]

I have a problem, as in title - through the last week of december and all of january I was getting successful monitoring of upstream and downstream, could see tone values etc.
Most of february I was away, and the monitoring machine and process were shutdown, while the router remained up.
In march, after my return, all looked normal for a short period, and then it was only registering upstream traffic, and could not display tones etc. This was without any changes (to my knowledge) to the setup up monitoring or the router, and I was using version 5.3
I tried downloading 5.4 and running that, but it failed to show traffic up or down or statistics ...
Any hints as to where I should look, and for what?

---
edit by admin - topic title.

[roseway]

Welcome to the forum.

Are there any error messages displayed in the DSLstats event log?

Can you login to the modem by telnet? If so, does the command adsl info expand=enabled produce a normal response?

Apart from these points I do vaguely remember a discussion of some issues with this model, and I'll try to find them.

[dandnsmith]

Thanks for the prompt response.
Going with my originally installed version:
No errors shown in event log
Can log in normally to an account I created with admin privileges
However, that command 'adsl info expand=enabled' says 'unknown command'
I did a bit of experimenting when I first got the router, but haven't looked yet to see what the results were (but I found commands to show various bits) - I'll try to find out what I found previously.
With this older version, I am getting some results shown on the tabs for all except Traffic and possibly errors, but have no idea whether they are believable,or are, like the Traffic, erroneous (doesn't show any upstream traffic at all)

[roseway]

I'm sorry, the command should have been xdsl info expand=enabled

[dandnsmith]

That does the trick, and I then get:

Code: [Select]

Physical Layer Statistics:

  Modem state:                                   up
  Up time (Days hh:mm:ss):                       10 days, 5:19:27
  xDSL Standard:                                 ITU-T G.993.2 Annex B (VDSL2)
  Channel Mode:                                  Interleaved

  Number of reset:                               10

  Chipset Vendor info (G.994.1):                 Local          Remote
    Country code:                                B500           B500
    ID:                                          BDCM           BDCM
    Specific:                                    0000           A44F

  System Vendor info (showtime):                 Local          Remote
    Country code:                                0F00           0000
    ID:                                          TMMB           ----
    Specific:                                    3C61           0000

  Bearers generic info                           DS             US
    Payload rate [kbps]:                         22400          1999
    Attenuation [dB]:                            24.4           10.8
    Margins [dB]:                                8.8            6.2
    Output power [dBm]:                          11.0           6.9

    Number of bearers:                           1
    Bearer 0                                     DS             US
      INP [DMT symbols]:                         51.00          51.00
      Delay [ms]:                                0.00           0.00
      Depth []:                                  2              0.00
      R:                                         10             0

G.997.1 Statistics (Current):

  Failures:
    Line failures                                Near end
      Loss of signal (LOS):                      10
      Loss of frame (LOF):                       68
      Loss of power (LPR):                       0

  Performance monitoring:
    Line PM:                                     Near end
      Error second (ES):                         16654

    Channel PM:                                  Near end       Far end
      Bearer 0:
        Code Violation (CV):                     1929           0
        FEC:                                     5999799        5371

    ATM data path PM:                            Near end       Far end
      Bearer 0:
        HEC violation count (HEC):               0              N/A

G.997.1 Statistics (last 15 minutes):

  Failures:
    Line failures                                Near end
      Loss of signal (LOS):                      0
      Loss of frame (LOF):                       0
      Loss of power (LPR):                       0

  Performance monitoring:
    Line PM:                                     Near end
      Error second (ES):                         0

    Channel PM:                                  Near end       Far end
      Bearer 0:
        Code Violation (CV):                     1929           0
        FEC:                                     5999799        5371

    ATM data path PM:                            Near end       Far end
      Bearer 0:
        HEC violation count (HEC):               0              N/A

G.997.1 Statistics (last 24 hours):

  Failures:
    Line failures                                Near end
      Loss of signal (LOS):                      0
      Loss of frame (LOF):                       0
      Loss of power (LPR):                       0

  Performance monitoring:
    Line PM:                                     Near end
      Error second (ES):                         3

    Channel PM:                                  Near end       Far end
      Bearer 0:
        Code Violation (CV):                     1929           0
        FEC:                                     5999799        5371

    ATM data path PM:                            Near end       Far end
      Bearer 0:
        HEC violation count (HEC):               0              N/A

{Monitor}=>


[burakkucat]

Just making this post so that I can edit the subject line . . .

From: DSTStats problem with TG589vn v3

To:     DSLStats problem with TG589vn v3

 


-----
Note from admin
Thanks b*cat - also edited the topic title.

[roseway]

I see you have a VDSL2 connection, and there are some issues with the format of the stats output which will cause DSLstats to misbehave with this model on VDSL2. It requires some rewriting, and unfortunately I'm unable to take this on at present for health reasons.

[dandnsmith]

@roseway -
thanks for your effort, I appreciate it and won't worry that nothing can be done at present.
I saw the comment about VDSL2 format somewhere, even before I first installed it, so was prepared to accept any results offered.
The things which puzzled me were:
a) why the results suddenly not longer showed downstream transmission figures (with no changes to DSLStats or the router setup
b) why the same ini file, used by the newer version, gave not results at all
However that is really just (repeated) comment.

[SimonZerafa]

Hi,

Has anyone heard further news on any possible fixes for this router when in VDSL2 mode?

There doesn't seem to be any other packages out there which even work correctly with this model of router and it would be great to get it working with DSLstats.

More than happy to help with testing, if that helps any? 

Kind Regards

Simon

[burakkucat]

Hello Simon and welcome to the Kitz forum.

As you will see from the above, Eric is having to limit the time he can spend on various tasks. However I am sure that when he is able to port the code to the hardware your services will then be called upon. 

[roseway]

Thank you for that, B*cat.

Simon: I'm on the mend, and I do have some time available now. Could you log into the TG589vn by telnet, and send the command xdsl info --stats then post the result here, please?

[burakkucat]

I'm on the mend . . .

I'm pleased to read that. 

[SimonZerafa]

Hi Eric,

Good to hear you are on the mend. Hopefully that will continue

Apologies for taking my time to reply but the command you suggested doesn't seem to work on this device.

The following command: xdsl info expand=enabled produces the following output:


Physical Layer Statistics:

  Modem state:                                   up
  Up time (Days hh:mm:ss):                       17 days, 14:20:55
  xDSL Standard:                                 ITU-T G.993.2 Annex B (VDSL2)
  Channel Mode:                                  Interleaved

  Number of reset:                               2

  Chipset Vendor info (G.994.1):                 Local          Remote
    Country code:                                B500           B500
    ID:                                          BDCM           BDCM
    Specific:                                    0000           A48C

  System Vendor info (showtime):                 Local          Remote
    Country code:                                0F00           0000
    ID:                                          TMMB           ----
    Specific:                                    3C61           0000

  Bearers generic info                           DS             US
    Payload rate [kbps]:                         74000          20000
    Attenuation [dB]:                            9.8            5.5
    Margins [dB]:                                6.9            13.6
    Output power [dBm]:                          13.3           6.7

    Number of bearers:                           1
    Bearer 0                                     DS             US
      INP [DMT symbols]:                         49.00          47.00
      Delay [ms]:                                0.00           0.00
      Depth []:                                  16             0.00
      R:                                         8              0

G.997.1 Statistics (Current):

  Failures:
    Line failures                                Near end
      Loss of signal (LOS):                      2
      Loss of frame (LOF):                       12
      Loss of power (LPR):                       0

  Performance monitoring:
    Line PM:                                     Near end
      Error second (ES):                         24

    Channel PM:                                  Near end       Far end
      Bearer 0:
        Code Violation (CV):                     11             0
        FEC:                                     2887902        51636

    ATM data path PM:                            Near end       Far end
      Bearer 0:
        HEC violation count (HEC):               0              N/A

G.997.1 Statistics (last 15 minutes):

  Failures:
    Line failures                                Near end
      Loss of signal (LOS):                      0
      Loss of frame (LOF):                       0
      Loss of power (LPR):                       0

  Performance monitoring:
    Line PM:                                     Near end
      Error second (ES):                         0

    Channel PM:                                  Near end       Far end
      Bearer 0:
        Code Violation (CV):                     11             0
        FEC:                                     2887902        51636

    ATM data path PM:                            Near end       Far end
      Bearer 0:
        HEC violation count (HEC):               0              N/A

G.997.1 Statistics (last 24 hours):

  Failures:
    Line failures                                Near end
      Loss of signal (LOS):                      0
      Loss of frame (LOF):                       0
      Loss of power (LPR):                       0

  Performance monitoring:
    Line PM:                                     Near end
      Error second (ES):                         0

    Channel PM:                                  Near end       Far end
      Bearer 0:
        Code Violation (CV):                     11             0
        FEC:                                     2887902        51636

    ATM data path PM:                            Near end       Far end
      Bearer 0:
        HEC violation count (HEC):               0              N/A

{Administrator}[xdsl]=>

Hopefully that might be useful information for you. If not or if you need further information please let me know.

Kind Regards

Simon Zerafa
--
@SimonZerafa
simon.zerafa[at]gmail.com

[Moderator edited to remove an excess of blank lines at the end of this post.]

[roseway]

Thank you for your good wishes.

Yes, of course, it's a Technicolor model, so it uses the command you mentioned. At present, DSLstats has no VDSL2 support for Technicolor modems, but it should be possible to add it. I'll come back to you concerning any extra information that's needed.

Those stats are interesting in themselves. The figures in the first Bearer 0 section look very much like the figures we see with connections which have G.INP enabled, but there's no mention of Bearer 1 in the stats. Perhaps this model needs a firmware update to fully support G.INP.

[SimonZerafa]

Hi Eric,

Yes this modem should already support G.INP and here are the stats for that via:

 xdsl info ginp=yes


G.INP Info:

  Status:                                        12

  Framing Info:                                  Near end       Far end
    Q:                                           8              16
    V:                                           2              3
    RxQueue:                                     39             42
    TxQueue:                                     13             14
    G.INP Framing:                               18             18
    G.INP lookback:                              13             14
    RRC bits:                                    24             24

  Retransmit counters:                           Near end       Far end
    rtx_tx:                                      12695          12695
    rtx_c:                                       15590          15590
    rtx_uc:                                      62821          62821

  G.INP Counters:                                Near end       Far end
    LEFTRS:                                      205            8
    minEFTR:                                     74006          74006
    errFreeBits:                                 3383378879     466586844


The CLI on this device also seems to have other options for Impulse Noise Monitoring, Vectoring and other items, many which are currently meaningless ;-)

All in all it seems to be a very capable single box solution for VSDL2 and can often be picked up on eBay quite inexpensively. My unit was initially shipped by Zen but I'm using it on Plusnet with no issues.

Kind Regards

Simon