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]

Author Topic: New cabinet / DSLAM - will local lines be moved?  (Read 6257 times)

adslmax

  • Kitizen
  • ****
  • Posts: 1937
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #30 on: April 04, 2019, 11:16:34 AM »

@ Bobsta why capped the line at 69999K when u were previous has a lovely 79999K on the line? Don't understand why your line start off high ReTx for a new connection service 80/20?
Logged

Bobsta

  • Member
  • **
  • Posts: 22
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #31 on: April 04, 2019, 03:10:54 PM »

@ Bobsta why capped the line at 69999K when u were previous has a lovely 79999K on the line?
To get Retx low/off. Then I'll remove the cap. It's worth a shot.

Quote
Don't understand why your line start off high ReTx for a new connection service 80/20?
Me neither! I'm hoping someone can explain.
Logged

Bobsta

  • Member
  • **
  • Posts: 22
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #32 on: April 12, 2019, 08:47:10 AM »

Well, it took a week.... but this morning it resyncd without ReTx.

Code: [Select]
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 31887 Kbps, Downstream rate = 92212 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 70000 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.8 15.5
Attn(dB): 9.0 0.0
Pwr(dBm): 13.1 -7.2
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.1110 0.3781
L: 18307 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 57 0
TxQueue: 19 0
G.INP Framing: 18 0
G.INP lookback: 19 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 0
I: 32 0
N: 32 0
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 1631799
OHFErr: 0 10
RS: 834717088 1161540
RSCorr: 14 39
RSUnCorr: 0 0
Bearer 1
OHF: 1447719 0
OHFErr: 0 0
RS: 14476576 0
RSCorr: 4 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 1056 0
rtx_c: 822 0
rtx_uc: 300124 0

G.INP Counters
LEFTRS: 40 0
minEFTR: 70007 0
errFreeBits: 1112223313 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3130288857 0
Data Cells: 1056084 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: 52 656
SES: 52 0
UAS: 243 191
AS: 23254

Bearer 0
INP: 49.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 70071.29 20063.54

Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01

Bitswap: 14232/14232 14/14

Total time = 1 days 22 hours 48 min 18 sec
FEC: 50949 36785
CRC: 8461 786
ES: 52 656
SES: 52 0
UAS: 243 191
LOS: 5 0
LOF: 25 0
LOM: 0 0
Latest 15 minutes time = 3 min 18 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
Previous 15 minutes time = 15 min 0 sec
FEC: 0 4
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 = 22 hours 48 min 18 sec
FEC: 2670 139
CRC: 554 30
ES: 11 27
SES: 11 0
UAS: 37 26
LOS: 1 0
LOF: 7 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 77 7519
CRC: 0 21
ES: 0 19
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 6 hours 27 min 33 sec
FEC: 14 39
CRC: 0 10
ES: 0 9
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
From: http://home.bobsta.com/fullstats.htm

One thing I can’t work out is what “Total time” is. Before this morning’s resync that section listed a smaller time than “Since Link time” - and contains lots more errors. What is it?
Logged

tiffy

  • Kitizen
  • ****
  • Posts: 1319
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #33 on: April 12, 2019, 11:39:37 AM »

Quote
Well, it took a week.... but this morning it resyncd without ReTx.

Just to clarify, you still have DS Re-Tx (G.Inp) applied, low profile, positively confirmed by:

Code: [Select]
Bearer 0
INP: 49.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 70071.29 20063.54

Bearer 0 INPRein = 0  (Is "1" when on Re-Tx high profile)

Without fully reading the rest of the thread I assume you were on DS Re-Tx high profile before the capping exercise.

Edit:
Purely by observation of the systems I monitor and going back to when MDWS was still active, Bearer 0 INP is usually less than 50 on Re-Tx low profile and 50 or more when on Re-Tx high profile, however, Bearer 0 INPRein "0 or 1" state has been proven to be the best positive indication of Re-Tx profile.
« Last Edit: April 12, 2019, 12:02:21 PM by tiffy »
Logged
BT FTTP 150/30, BT Smart Hub 2

Bobsta

  • Member
  • **
  • Posts: 22
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #34 on: April 12, 2019, 02:01:24 PM »

tiffy, you’re spot on. I meant ReTx “low” rather than off (or not high). My mistake.

BRAS profile is now much closer to sync speed (92%) rather than the 88% it was before.

In a few days I’ll remove the cap and hopefully this %age improvement will remain.
Logged

tiffy

  • Kitizen
  • ****
  • Posts: 1319
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #35 on: April 12, 2019, 02:20:47 PM »

Good result, the capping certainly does appear to work in most cases with respect to changing DS Re-Tx profile to low.
Logged
BT FTTP 150/30, BT Smart Hub 2

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: New cabinet / DSLAM - will local lines be moved?
« Reply #36 on: April 13, 2019, 03:19:43 PM »

Minor update... earlier today I noticed my internet connection drop and my phone line went dead. I wandered down to the street to the new cabinet to see if anything was going on. Sure enough this chap was in a trench surrounded by bundles of copper pairs:



I said hello and he apologised for the service interruption saying he was connecting us to the new cabinet for "fast Internet" and we should be reconnected in a couple of minutes. I mentioned that I thought that wasn't happening until May and he said "nope, it's happening now!". So I merrily wandered back to my house.

By the time I got home my connection was active again ... but alas, still at the old sync speed. So my assumption is this is only the first step of the connection in that our pairs are now going through the cabinet's IDC connections - but aren't connected to the DSLAM yet. Is that vaguely right?

Nothing's changed on the BTW ADSLchecker (still says Cab 7). So I guess I just sit tight until one day the magic happens.


I know its an old post now, but excellent news. :)
Logged
Pages: 1 2 [3]
 

anything