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

Author Topic: High Interleaving  (Read 11140 times)

mbb

  • Member
  • **
  • Posts: 33
Re: High Interleaving
« Reply #45 on: February 13, 2018, 12:05:11 AM »

mdws username is markb. currently top and middle left light is amber. bottom left light is red??. rest are green

heres my current stats after lifting the cap on my line

xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason:   1
Last initialization procedure status:   0
Max:   Upstream rate = 7991 Kbps, Downstream rate = 37900 Kbps
Bearer:   0, Upstream rate = 7991 Kbps, Downstream rate = 38029 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):    6.1       6.1
Attn(dB):    23.7       0.0
Pwr(dBm):    12.4      -0.9
         VDSL2 framing
         Bearer 0
MSGc:      19      26
B:      239      239
M:      1      1
T:      64      42
R:      0      0
S:      0.2008      0.9543
L:      9560      2012
D:      1      1
I:      240      120
N:      240      240
         Counters
         Bearer 0
OHF:      34764425      1146335
OHFErr:      21304      81
RS:      0      1865191
RSCorr:      0      0
RSUnCorr:   0      0

         Bearer 0
HEC:      30764      0
OCD:      1878      0
LCD:      1878      0
Total Cells:   3883081190      0
Data Cells:   233826399      0
Drop Cells:   0
Bit Errors:   0      0

ES:      2179      316
SES:      95      0
UAS:      148      137
AS:      112149

         Bearer 0
INP:      0.00      0.00
INPRein:   0.00      0.00
delay:      0      0
PER:      3.22      10.05
OR:      61.99      25.44
AgR:      38091.20   8016.68

Bitswap:   82501/82502      50/50

Total time = 1 days 6 hours 26 min 52 sec
FEC:      1037      92
CRC:      21415      100
ES:      2179      316
SES:      95      0
UAS:      148      137
LOS:      1      0
LOF:      8      0
LOM:      0      0
Latest 15 minutes time = 11 min 52 sec
FEC:      0      0
CRC:      824      0
ES:      51      0
SES:      3      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 15 minutes time = 15 min 0 sec
FEC:      0      0
CRC:      255      0
ES:      21      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 6 hours 26 min 52 sec
FEC:      0      0
CRC:      8372      31
ES:      634      24
SES:      31      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      0      0
CRC:      12550      48
ES:      1134      38
SES:      40      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 1 days 7 hours 9 min 9 sec
FEC:      0      0
CRC:      21304      81
ES:      1813      64
SES:      73      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
#
« Last Edit: February 13, 2018, 12:08:32 AM by mbb »
Logged

dgilbert2

  • Member
  • **
  • Posts: 27
Re: High Interleaving
« Reply #46 on: February 13, 2018, 10:09:16 PM »

@mbb I'm not sure of the significance of your MDWS stats reporting "G.Inp Inactive" and mine saying nothing at all!? Is that because at some point G.Inp WAS active?
« Last Edit: February 13, 2018, 10:13:34 PM by dgilbert2 »
Logged

mbb

  • Member
  • **
  • Posts: 33
Re: High Interleaving
« Reply #47 on: February 14, 2018, 08:50:38 AM »

@mbb I'm not sure of the significance of your MDWS stats reporting "G.Inp Inactive" and mine saying nothing at all!? Is that because at some point G.Inp WAS active?

Yes sir. that is from my old property when G.INP was activated.

Mark
Logged

mbb

  • Member
  • **
  • Posts: 33
Re: High Interleaving
« Reply #48 on: February 22, 2018, 12:53:01 PM »

7 days 21 hours 43 min 0 sec scince interleaving was re-applied to my line and no sign of G.INP  :'( One thing ive noticed is my upload snr is fluctuating between 6 and 4db. its been on 4 for the past few days

Could it be my line is classed as a 'new' line having only just moved here in December that it needs a good few months before G.INP is applied

im also gettin daily dropouts around the same time everyday for a couple of minutes. the homehub stays in sync (blue light) but i lose all connection for approx 1-2 minutes with the bt splash page breifly appearing. any ideas what this could be?. it hasn't really bothered me that much compared to having an interleaved line. but my net has dropped in the middle of playing online games last couple of nights and could it possibly be the cause of no G.INP?

mark
Logged

KingJ

  • Member
  • **
  • Posts: 44
  • ¯\_(ツ)_/¯
    • Miscellaneous Knowledge
Re: High Interleaving
« Reply #49 on: February 24, 2018, 11:14:56 AM »

Just a bit of an update here.

Since the DLM resync to 3dB, my line had been stable - no resycns, no drops just lovely fast speeds.

However, on Thursday (22nd) evening at 22:45, my line resynced due to Remote Defect/DLM. Looking at my stats around that time, since around 19:30 my Bitswaps/min on the downstream went to 0 and remained there til the resync. Consequently, this caused G-Retransmit Corrections to go from their usual low level to over 100,000 a minute.

I'm not quite sure why Bitswaps/min dropped to 0 like that, but clearly DLM was doing its job by resyncing the line and correcting the issue. After the resync, I gained a tiny bit extra on the downstream and now sync at the full 79999/19999. Interestingly, the modem's measured attainable sync post-resync increased by 1.5mbit on the downstream, and decreased by 1.5mbit on the upstream.
Logged

ejs

  • Kitizen
  • ****
  • Posts: 2078
Re: High Interleaving
« Reply #50 on: February 24, 2018, 11:32:19 AM »

clearly DLM was doing its job by resyncing the line and correcting the issue.

I don't think it's clear at all that it was the DLM instigating the resync. Why couldn't it simply be one or other end of the connection determining that it can no longer maintain the connection due to whatever was going on causing the lack of bitswaps and/or large amounts of retransmission?
Logged

KingJ

  • Member
  • **
  • Posts: 44
  • ¯\_(ツ)_/¯
    • Miscellaneous Knowledge
Re: High Interleaving
« Reply #51 on: February 24, 2018, 11:41:52 AM »

I don't think it's clear at all that it was the DLM instigating the resync. Why couldn't it simply be one or other end of the connection determining that it can no longer maintain the connection due to whatever was going on causing the lack of bitswaps and/or large amounts of retransmission?

Ah my bad for wording it like that. I meant moreso that the resync was initiated by an automated process. It is indeed unlike to be DLM as it wouldn't react this quickly from what I understand? (Given the daily batch nature of it).

My modem could have initiated it, but I don't know how to tell for sure - unfortunately I have no logs. Can the cab trigger resyncs if it notices abnormal line conditions?

The resync cause according to MDWS was "1 Remote Defect Indicator/DLM".
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: High Interleaving
« Reply #52 on: February 24, 2018, 03:34:22 PM »

Can the cab trigger resyncs if it notices abnormal line conditions?

Yes. At the level of your connection, the cabinet based DSLAM is just the modem at the other end of the G.993.2 link which is paired with your modem. Either modem may initiate a circuit re-train.
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.
Pages: 1 2 3 [4]
 

anything