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 ... 3 4 [5] 6 7

Author Topic: Stat check on my line please  (Read 15229 times)

michty_me

  • Reg Member
  • ***
  • Posts: 631
Re: Stat check on my line please
« Reply #60 on: June 24, 2018, 06:34:00 PM »

It is already looking a lot better with far fewer errors. So now I shall leave for stability.

Code: [Select]
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:    0
Last initialization procedure status:   0
Max:    Upstream rate = 17279 Kbps, Downstream rate = 61982 Kbps
Bearer: 0, Upstream rate = 16964 Kbps, Downstream rate = 48997 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State:       L0
Mode:                   VDSL2 Annex B
VDSL2 Profile:          Profile 17a
TPS-TC:                 PTM Mode(0x0)
Trellis:                U:ON /D:ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        9.4             6.0
Attn(dB):        17.8            0.0
Pwr(dBm):        13.6            7.6

                        VDSL2 framing
                        Bearer 0
MSGc:           -6              -6
B:              195             162
M:              1               1
T:              0               0
R:              12              12
S:              0.0000          0.0000
L:              13117           4585
D:              4               4
I:              208             175
N:              208             175
Q:              4               4
V:              2               0
RxQueue:                135             55
TxQueue:                27              11
G.INP Framing:          18              18
G.INP lookback:         27              11
RRC bits:               24              24
                        Bearer 1
MSGc:           122             58
B:              0               0
M:              2               2
T:              2               2
R:              16              16
S:              8.0000          16.0000
L:              32              16
D:              1               1
I:              32              32
N:              32              32
Q:              0               0
V:              0               0
RxQueue:                0               0
TxQueue:                0               0
G.INP Framing:          0               0
G.INP lookback:         0               0
RRC bits:               0               0

                        Counters
                        Bearer 0
OHF:            0               0
OHFErr:         0               0
RS:             391696156               187778
RSCorr:         157             6100
RSUnCorr:       0               0
                        Bearer 1
OHF:            776466          779563
OHFErr:         0               0
RS:             6211237         3118254
RSCorr:         1               1647
RSUnCorr:       0               0

                        Retransmit Counters
rtx_tx:         9965749         4105
rtx_c:          89              90270
rtx_uc:         0               408952

                        G.INP Counters
LEFTRS:         0               446
minEFTR:        48999           16961
errFreeBits:    9316575         1962069651

                        Bearer 0
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    1175153637              0
Data Cells:     4641139         0
Drop Cells:     0
Bit Errors:     0               0

                        Bearer 1
HEC:            0               0
OCD:            0               0
LCD:            0               0
Total Cells:    0               0
Data Cells:     0               0
Drop Cells:     0
Bit Errors:     0               0

ES:             0               0
SES:            0               0
UAS:            28              28
AS:             12474

                        Bearer 0
INP:            54.00           52.00
INPRein:        1.00            1.00
delay:          0               0
PER:            0.00            0.00
OR:             0.01            0.01
AgR:            49248.62        17015.93

                        Bearer 1
INP:            2.00            4.00
INPRein:        2.00            4.00
delay:          0               0
PER:            16.06           16.06
OR:             63.75           31.87
AgR:            63.75   31.87

Bitswap:        13/13           339/339

Total time = 3 hours 28 min 22 sec
FEC:            157             6100
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            28              28
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 15 minutes time = 13 min 22 sec
FEC:            8               391
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            0               432
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Latest 1 day time = 3 hours 28 min 22 sec
FEC:            157             6100
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            28              28
LOS:            0               0
LOF:            0               0
LOM:            0               0
Previous 1 day time = 0 sec
FEC:            0               0
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
Since Link time = 3 hours 27 min 53 sec
FEC:            157             6100
CRC:            0               0
ES:             0               0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
LOM:            0               0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
 >

I still haven't got DSLstats running correctly and currently accessing it through a long ethernet cable to my PC. I did find a post about checking to make sure that the DHCP server in the default LAN setup was disabled. It was not but is now. I would imagine that I require to reboot it but will get some stability on the line first before rebooting things, And making adjustments etc.
Logged

spring

  • Reg Member
  • ***
  • Posts: 342
Re: Stat check on my line please
« Reply #61 on: June 24, 2018, 06:55:54 PM »

You just need to reboot the other devices, as DHCP assigns to another device and the origin is unaffected. [I think]
ZyXEL is able to change most settings on the fly unlike some devices.

Edit: Forgot to say, I'll keep using x1 for as long as I want, be it a few hours or a week, but I've lost any hope in it  :-\  Having no DLM, I wish DLM wasn't enforced on other people.
« Last Edit: June 24, 2018, 07:28:55 PM by spring »
Logged
No one knows what is the taste of the void.

michty_me

  • Reg Member
  • ***
  • Posts: 631
Re: Stat check on my line please
« Reply #62 on: June 24, 2018, 07:31:29 PM »

My line was already banded due to a fault with my previous equipment so I'm not too worried that it has been impacted further.
If it stays at 48mbps I've a better chance of getting a reset (assuming I am now staying stable)

As for dslstats. I'll create a new thread for that. I think I'm just thick!!
Logged

spring

  • Reg Member
  • ***
  • Posts: 342
Re: Stat check on my line please
« Reply #63 on: June 24, 2018, 07:36:03 PM »

If it stays at 48mbps I've a better chance of getting a reset (assuming I am now staying stable)
:blush: Not so bad then  :-[
Logged
No one knows what is the taste of the void.

michty_me

  • Reg Member
  • ***
  • Posts: 631
Re: Stat check on my line please
« Reply #64 on: June 24, 2018, 07:41:31 PM »

I want to see stability for probably a week or two and then I will request it.
Logged

spring

  • Reg Member
  • ***
  • Posts: 342
Re: Stat check on my line please
« Reply #65 on: June 24, 2018, 08:09:09 PM »

Yeah after 14 days
Logged
No one knows what is the taste of the void.

spring

  • Reg Member
  • ***
  • Posts: 342
Re: Stat check on my line please
« Reply #66 on: June 27, 2018, 09:32:51 AM »

if you have sync drops you need SRA, if you don't have any drops whatsoever, it's better without [well, if you ever speak with your ISP, you can ask them to check if your line has SRA. can also enable it and see, but it should be on only if there are drops (if the ISP supports SRA and the modem has it disabled, I don't think it's a negative impact - will search about that)].

edit: it can be off in the modem even if the DSLAM supports it, without side effects (at least, it very much seems so).

edit2: what I recommend is that if you happen to find out from your ISP that it's supported & enabled, to turn it on and benefit from sync rate adaptation to noise and possible saves from sync drops [the profile rate remains the same].
« Last Edit: June 27, 2018, 09:54:04 AM by spring »
Logged
No one knows what is the taste of the void.

michty_me

  • Reg Member
  • ***
  • Posts: 631
Re: Stat check on my line please
« Reply #67 on: June 27, 2018, 09:58:52 AM »

I haven't had an drops what so ever.
I think I'm approaching the 3 day mark and have 0 errors for all CRC, ES and SES.
Logged

spring

  • Reg Member
  • ***
  • Posts: 342
Re: Stat check on my line please
« Reply #68 on: June 27, 2018, 10:11:19 AM »

FEC's count too but the longer you let it run until the DLM reset, the better it will re-sync after the reset

however if there is something "stuck" or not improving as it should over the first week & bitloading graph also shows it then a resync would be better: of course, if it's not the case then it's detrimental to do that. in general V doesn't need any resyncs anywhere from 3 months to 1 year [or 2 years... xD], depends. the recommendation I've read & support is every 3 months to turn off the device, so 4 resyncs per year. or every 4 months, 3 per year. whichever fits more.

you can PM me your bitloading graph and --stats whenever
« Last Edit: June 27, 2018, 10:14:07 AM by spring »
Logged
No one knows what is the taste of the void.

johnson

  • Reg Member
  • ***
  • Posts: 838
Re: Stat check on my line please
« Reply #69 on: June 27, 2018, 10:14:38 AM »

FEC's count too but the longer you let it run until the DLM reset, the better it will re-sync after the reset

FECs do not count towards DLM, they are corrected errors.
Logged

spring

  • Reg Member
  • ***
  • Posts: 342
Re: Stat check on my line please
« Reply #70 on: June 27, 2018, 10:25:50 AM »

FECs do not count towards DLM, they are corrected errors.
that's not what i meant..............

it was about the ongoing sync and whether it benefits a re-sync

nothing about DLM
« Last Edit: June 27, 2018, 10:28:29 AM by spring »
Logged
No one knows what is the taste of the void.

michty_me

  • Reg Member
  • ***
  • Posts: 631
Re: Stat check on my line please
« Reply #71 on: June 27, 2018, 10:39:31 AM »

The line seems happy just now at its current level anyway.
I'm wondering if when I started the thread, If the latest lockup of the D7000 caused enough errors for the DLM to kick in and increase my SNR again or if it was using the X1 firmware. Something I'll never find out anyway.

I noticed prior to last weekw lockout, DLM would appear to make an alteration every 6-7 days or so.
Logged

spring

  • Reg Member
  • ***
  • Posts: 342
Re: Stat check on my line please
« Reply #72 on: June 27, 2018, 10:43:26 AM »

x1 dropped your speed from 55 to 48 and i know from experience it can increase errors on the line from 5 to 15 times more, in your case caused a drop of sync & all the error types

is there something irreversible about it? assuming not, it's good right?

how to trigger DLM: flash to x1 and let it run for 4 days, done [after the first 4 days its actually been fine for me xD]
« Last Edit: June 27, 2018, 10:57:51 AM by spring »
Logged
No one knows what is the taste of the void.

johnson

  • Reg Member
  • ***
  • Posts: 838
Re: Stat check on my line please
« Reply #73 on: June 27, 2018, 10:59:07 AM »

I honestly think you are being over dramatic spring. I have been running the x1 adsl_phy on my line for weeks, with if anything reduced errors.

Weaver and j0hn have also used it, and all they saw was very slightly reduced sync speed.

You have spent a lot of time looking at your line stats and making some strange assumptions. You have a line with an attainable over twice that of your sync speed, and you take interest in things like FECs in the tens. Many perfectly stable lines have millions of FEC errors a day...

I honestly have no idea what to make of your input about the various adsl_phy, or why you feel the need to talk about it the way you do.
Logged

spring

  • Reg Member
  • ***
  • Posts: 342
Re: Stat check on my line please
« Reply #74 on: June 27, 2018, 11:01:45 AM »

I honestly think you are being over dramatic spring. I have been running the x1 adsl_phy on my line for weeks, with if anything reduced errors.

Weaver and j0hn have also used it, and all they saw was very slightly reduced sync speed.

You have spent a lot of time looking at your line stats and making some strange assumptions. You have a like with an attainable over twice that of your sync speed, and you take interest in things like FECs in the tens. Many perfectly stable lines have millions of FEC errors a day...

I honestly have no idea what to make of your input about the various adsl_phy, or why you feel the need to talk about it the way you do.
where did this come from just now

im going to ignore this post and yes, 10 times the average FEC that had been stable for months with V means i need to leave x1 running for longer before I can justify using it as so far it has been nothing but buggy

by the way, j0hn said it performed worse for him

also, talk about it the way I do? first you said it's nice I'm providing information, now it's somehow meaningless? I wouldn't have gone back to x1, don't want to constantly watch my line.

my line doesn't have vectoring like yours

the reason I'm leaving x1 to run is because it has days with reduced errors, I'm just trying to see how it behaves. when did I say it's going to be like that for everyone? the reason I'm being dramatic is some people have DLM.

and this information doesn't apply to ADSL , weaver is using ADSL.

and what about missing upstream bits?

btw the triggering DLM line was written as a joke not a fact
« Last Edit: June 27, 2018, 11:17:08 AM by spring »
Logged
No one knows what is the taste of the void.
Pages: 1 ... 3 4 [5] 6 7