Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: Bobsta on January 15, 2019, 10:42:00 PM
-
I've posted before about how I'm in the unfortunate position of living approximately 1.2km from my cabinet - with a line length of 1485m (as reported by GEA test).
However, today I noticed what appears to be some very good news - a report of a new cabinet being installed less than 100m from my house - https://roadworks.org/?111974693
(my current cabinet - #7 - is located by the golf club to the bottom-left of the map)
I'd appreciate your collective wisdom on whether this really is what I hope it is from the description ("HARTLEY WINTNEY 10 - DSLAM 597996 - STREET CABINET and POWER INSTALLATION. Excavate to lay approx 2m BT ducts, Lay concrete plinth, Stand cab.")... and also, whether it would be Openreach standard practice to migrate over local lines to this DSLAM once installed. There are no new properties being built in the area so I'm hopeful.
Edited to add: Checking here, it looks positive that this could be cabinet P10 - https://www.telecom-tariffs.co.uk/codelook.htm?xid=343802&cabinets=12373
Many thanks,
Bobsta
-
I'd appreciate your collective wisdom on whether this really is what I hope it is from the description ("HARTLEY WINTNEY 10 - DSLAM 597996 - STREET CABINET and POWER INSTALLATION. Excavate to lay approx 2m BT ducts, Lay concrete plinth, Stand cab.")...
Yes, it is. :)
Could it be an in-fill cabinet? :shrug2:
Edited to add: Checking here, it looks positive that this could be cabinet P10 - https://www.telecom-tariffs.co.uk/codelook.htm?xid=343802&cabinets=12373
Yes, it could be. I prescribe a walk around the area, taking a close interest in any spray-paint markings on the ground, etc.
-
Due to be completed May 2019.
If it is an infill cabinet then it needs a live-to-live migration of all the lines on the old cabinet to the new cabinet.
This needs coordinated with every ISP who has a customer being moved so can take many weeks/months.
They all need moved at the same time or the 2 competing signals/power levels from different FTTC cabinets can cause problems.
As to what specific properties are likely to be connected to this new cabinet I have no idea.
There are members on ThinkBroadband who are sometimes kind enough to look up info from sources not available to the public.
MrSaffron is also often very helpful in attempting to work out which streets are likely to be moved to new cabinets by looking through their coverage database.
It might be worth posting this over there on the Fibre Broadband section and asking if anyone can provide any info. The exchange name, the 2 cabinet numbers and the roadworks.org link should be enough to go on.
Without knowing the current cable routes that the copper takes and spending a considerable time looking up estimates for properties in the area, I would not be able to say with any certainty what lines are likely to be moved.
The roadworks page makes no mention of dimensions to establish the cabinet type, but the mention of only 1 plinth suggests an All In One cabinet.
-
Thanks for the replies.
This evening I noticed the cones had been cleared away to reveal a shiny new All-In-One cabinet:
(https://www.dropbox.com/s/oxs26mzzk25ljox/2019-01-16%2018.40.21%20copy.jpg?raw=1)
It's placed right by some existing below-ground junction boxes (I've seen Openreach engineers working in these in the past - I believe it's where overhead pole-strung lines are joined to lines in underground ducting into the village)
(https://www.dropbox.com/s/i95jc1i22m14t1n/2019-01-16%2018.41.25%20copy.jpg?raw=1)
There are also additional works listed on roadworks.org planned for April: "HARTLEY WINTNEY 10 - DSLAM 591270 - Overlay – Lay approx 50m of Duct 54/56 in VERGE to link existing BT Boxes to facilitate spine cabling works."
https://roadworks.org/?111855989
https://roadworks.org/?111855588
https://roadworks.org/?111855991
I estimate there are approximately 40-50 properties which could be served by this cabinet, all of which have existed for 50+ years... and there are no new developments on the horizon.
Looking up our postcode on hampshiresuperfastbroadband.com gives the result:
The cabinet which serves this address has been upgraded to fibre by the Hampshire Superfast Broadband Programme.
You may therefore be able to get superfast broadband.
Our records indicate that once the upgrade has been completed, some properties will be too far away from the upgraded infrastructure to access superfast services.
Hampshire County Council is awaiting further information from Government about how to address this issue.
Appreciate the input folks. I'll head over to TBB to see if anyone's able to shed any light on whether our lines will be migrated or I'll be needing to play the game of ordering a second line in order to get served by this new cab.
-
That all looks to be quite positive. :)
Thank you for sharing that update.
-
Appreciate the input folks. I'll head over to TBB to see if anyone's able to shed any light on whether our lines will be migrated or I'll be needing to play the game of ordering a second line in order to get served by this new cab.
Just a heads up that that isn't a possibility.
Either your line will be part of those being moved or it won't. Ordering a 2nd line would see it served by the same cabinet as OpenReach have designated to your address.
It's not possible to have a 2nd line from a different cabinet.
With what you have said above it seems extremely unlikely this cabinet wouldn't cover your property.
It would need the live-to-live migration I described above as the new cabinet cannot be activated for new lines until the existing FTTC lines have been transferred first.
-
Either your line will be part of those being moved or it won't. Offering a 2nd line would see it served by the same cabinet as OpenReach have designated to your address.
It's not possible to have a 2nd line from a different cabinet.
Ah OK, thanks for the info - that's definitely worth knowing (albeit rather annoying!).
With what you have said above it seems extremely unlikely this cabinet wouldn't cover your property.
It would need the live-to-live migration I described above as the new cabinet cannot be activated for new lines until the existing FTTC line have been transferred first.
Thanks - fingers crossed. I guess I just need to sit tight (whilst keeping a lookout for Openreach vans ;))
-
If you work out the most likely route your line takes from home to your existing fibre cab does it pass the new cabinet, if so then its highly likely you will be transferred to it. If your between the new cab and the old cab then it is much less likely you'll be on the new cab.
Basically they cut the lines that pass the new cab and join them into the new cab, so if your before that point you will be out of luck, after that point and your line will be fed from the new cab.
-
Thanks Ronski, makes sense. Fortunately my house is about 50m past the new cab, and I know my line goes (overhead) another 80m up the road before going underground and then coming back pretty much under the new cab. Total line length is probably under 250m to the new cab, so that's positive. ;D
-
Sounds very promising then, keep an eye on the wholesale checker, at some point your cabinet number and estimate should change.
-
What he says ^^^
It often changes before any migration work has been done so don't jump the gun and try order anything!
The move of cabinets will be automatic, you may not even be informed.
It will give confirmation your line is being moved before it happens though.
-
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:
(https://www.dropbox.com/s/2j8ube2dh0m6uj1/2019-01-22%2012.00.22.jpg?raw=1)
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.
-
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?
Yes, correct. You should not have suffered a disconnection or noticed any aspect of the teeing and re-jumpering. Hence I am able to say that an unfortunate "mishap" had occurred. ::)
Nothing's changed on the BTW ADSLchecker (still says Cab 7). So I guess I just sit tight until one day the magic happens.
Yes, once again.
-
Sounds like you're now physically connected to the new cabinet.
The engineer seems unaware of the process for migrating lines on infill cabinets, unless it has changed very recently.
AFAIK it will still require the live-to-live migration discussed earlier in the thread.
-
I avoided posting blow-by-blow updates to this thread... but to cut a long story short, everything proceeded in an orderly fashion;
- On 29 Jan the broadband availability checker was updated to show my line was served by Cabinet 10 (not 7, as previously) - but with no VDSL info
- In early February further roadworks took place to put in extra trenches to (I assume) bring a handful of other local properties' lines to the cabinet.
- On 17 Feb the availability checker was updates showing VDSL availability with an 80/20 estimate
- On 4 March I was emailed by Plusnet advising me that upgrade work was scheduled for 15 March with an estimated 1-2hr outage and they apologised for any inconvenience. ::)
- On 4 March the CodeLook DB was updated to show Cab 10 going live "by March" rather than the previous "by May"
- This week I've seen a significant Openreach presence - which kinda made me nervous - but today, bang on schedule, my line went offline for 90 mins whilst the live-to-live migration took place.
Currently syncing at 40/10 due to the package I'm on but with 82/33 showing as my max sync. Interleaving is at 1283! - I'm hoping DLM will bring that down on its own so leaving everything to settle.
One very happy punter here. ;D - thanks for all the excellent info from others on this thread. Hopefully this update proves helpful to anyone else going through a similar experience in future. I'm pretty impressed that everything was achieved in just over 2 months from cabinet footing being put in to users live.
-
That's good to hear, thanks for updating us.
Are you going to upgrade to 80/20?
The interleaving will be removed soon, hopefully in a few days but possibly longer.
-
Should switch from Interleaving to ReTx in 2 days.
Glad to hear everything went well. :congrats: :yay: :clap: :thumbs:
-
That's good to hear, thanks for updating us.
Are you going to upgrade to 80/20?
Yes, absolutely. Plusnet's tools currently won't let me order the 80/20 package which they believe is because the cabinet isn't officially open for orders. They're going to keep an eye on things and hopefully in the next week or two when databases are updated I can be bumped up.
-
There is just one thing that puzzles me . . .
In reply #3 you show two images of the new AIO cabinet.
In reply #11 you mention walking to the new cabinet, as your telephone and broadband services had been disrupted, and showed another image. This latter image does not match either of the two images in reply #3.
???
-
It does, it's just end on, you can see the same wooden fence in both and also see the same white sign post in both.
-
It does, it's just end on, you can see the same wooden fence in both and also see the same white sign post in both.
Correct. I agree that the first two pics show the verge looking quite maintained versus the one in post 11... but I can assure you it's definitely the same cab. In fact the OR engineer is down in the trench/pit which you can see the covers for in the second pic (lower right corner).
Maybe this'll help (although I'm sure we've all seen enough green cabinet pics):
(https://www.dropbox.com/s/jkjrkibkcg8bwo9/2019-01-31%2009.09.02%20copy.jpg?raw=1)
-
Ah, ha. Thank you. The curious kitteh now understands the physical layout. :)
-
How does it show max sync at 82?
I though they were all capped at 80 or 40, package dependant?
-
The modem shows what it considers to be the maximum attainable speed given no imposed limits, that is the speed he stated. It should be noted that if interleaving is applied then this figure will be incorrect and higher than it should be, it probably also doesn't take into account lower SNR targets, so maximum attainable speed would be higher if the SNR target was lowered.
-
Ah ok, so it is capped at 80 before transmission?
-
The max attainable rate will take into account whatever value the target SNRM is.
-
Ah ok, so it is capped at 80 before transmission?
All 80/20 lines are capped at 80Mb, even though the max attainable may be 99Mb.
If there wasn't an 80Mb cap then that 99Mb would be roughly where the line would sync.
The max attainable shows what they line would sync at if there was no cap at all, wether it was a 40Mb/55Mb/80Mb cap.
The way Interleaving/INP is applied on FTTC makes the max attainable over estimate.
-
I actually have an interesting comparison having been on Digital Region.
I used to get a max attainable of 130Mbit and actual sync of 99.9Mbit, but once I switched to BT its never been that high. I suspect something to do with the band plans.
Its quite depressing seeing my line syncing at 76Mbit these days though, my new second line is only hitting 63Mbit. :(
Don't get me wrong, I appreciate that other people have it WAY worse, but its never good to see things going backwards.
-
You folks were spot on... after ~36hrs active, at around 1am Sunday the modem resync'd, enabling G.INP and lowering the interleave depth from 1283 to 16 (resulting in my latency halving).
Reported max rates are now 81424 down / 29128 up.
Have ordered Plusnet Fibre Extra (80/20) which should go live overnight, so fingers crossed. :fingers:
-
Continuing the story... my 80/20 service went live as expected. Initially at:
Downstream Upstream
Line attenuation (dB): 9.0 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 71119 19999
SNR margin (dB): 6.2 15.4
Power (dBm): 13.0 -7.2
Interleave depth: 1391 1
INP: 3.00 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0008 0.0350
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 1.28
Then after 48hrs G.INP kicked in and interleaving dropped:
Downstream Upstream
Line attenuation (dB): 9.1 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 79999 19999
SNR margin (dB): 6.6 15.7
Power (dBm): 13.1 -7.2
Interleave depth: 8 1
INP: 52.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0001 0.0375
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 2.17
It's remained sync'd like that for 12 days but I've noticed that my BRAS profile is pretty poor, given my 79999 sync:
The current Downstream BRAS rate is: 70.61 Mbps
The current Upstream BRAS rate is: 20 Mbps
... by my maths, that's 88.26%
This is all with a stable downstream SnR of 6.5 dB - but with the dreaded ReTx High.
Here are my Connection Stats and G.INP stats taken earlier today:
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 32023 Kbps, Downstream rate = 85064 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79999 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): 6.5 15.6
Attn(dB): 9.1 0.0
Pwr(dBm): 13.1 -7.2
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 162 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0647 0.3781
L: 21128 5374
D: 8 1
I: 171 127
N: 171 254
Q: 8 0
V: 2 0
RxQueue: 136 0
TxQueue: 34 0
G.INP Framing: 18 0
G.INP lookback: 31 0
RRC bits: 0 24
Bearer 1
MSGc: 186 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 5.3333 0.0000
L: 48 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 1722291
OHFErr: 0 513
RS: 1204843304 3148605
RSCorr: 4129 4287
RSUnCorr: 0 0
Bearer 1
OHF: 62051486 0
OHFErr: 0 0
RS: 744617090 0
RSCorr: 22 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 659 0
rtx_c: 561 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 80011 0
errFreeBits: 1215976899 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3012210997 0
Data Cells: 405054493 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: 10 449
SES: 10 0
UAS: 65 55
AS: 996691
Bearer 0
INP: 52.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80244.76 20063.54
Bearer 1
INP: 4.00 0.00
INPRein: 4.00 0.00
delay: 3 0
PER: 16.06 0.01
OR: 95.62 0.01
AgR: 95.62 0.01
Bitswap: 598693/598693 2819/2820
Total time = 1 days 10 hours 45 min 35 sec
FEC: 39925 7052
CRC: 6241 559
ES: 10 449
SES: 10 0
UAS: 65 55
LOS: 1 0
LOF: 3 0
LOM: 0 0
Latest 15 minutes time = 35 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 0
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 = 10 hours 45 min 35 sec
FEC: 152 59
CRC: 0 13
ES: 0 13
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 322 170
CRC: 0 24
ES: 0 23
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 11 days 12 hours 51 min 31 sec
FEC: 4129 4287
CRC: 0 513
ES: 0 413
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
Downstream Upstream
General
rtx_tx 674 0
rtx_c 576 0
rtx_uc 0 0
LEFTRS 0 0
minEFTR 80001 0
errFreeBits 1226737302 0
Bearer 0
RxQueue 136 0
TxQueue 34 0
G.INP Framing 18 0
G.INP Lookback 31 0
RRC Bits 0 24
Interleave depth 8 1
INP 52.00 0.00
INPRein 1.00 0.00
Delay 0 0
Bearer 1
Interleave depth 3 0
INP 4.00 0.00
INPRein 4.00 0.00
Delay 3 0
I've now capped the line at 70000 20000 to try to get ReTx low to kick in. I'm a bit fuzzy on why I wouldn't get ReTx set to low anyway, given the >6dB SNR margin and relatively low error rates. Is someone able to explain that please?
Now it's syncing at 70000 20000 the SNRM is nice and high. I'll post the G.INP stats tomorrow as I know j0hn has been tracking them. Fingers crossed that the 70000 cap is low enough - I may not have been heavy-handed enough, so let's see.
Stats are now:
xdslcmd info --stats
xdslcmd: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 31816 Kbps, Downstream rate = 85324 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 69999 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.3 15.2
Attn(dB): 9.0 0.0
Pwr(dBm): 13.0 -7.2
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 138 237
M: 1 1
T: 0 42
R: 8 16
S: 0.0629 0.3781
L: 18697 5374
D: 8 1
I: 147 127
N: 147 254
Q: 8 0
V: 5 0
RxQueue: 140 0
TxQueue: 35 0
G.INP Framing: 18 0
G.INP lookback: 31 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 460862
OHFErr: 0 0
RS: 115799768 2167821
RSCorr: 0 2
RSUnCorr: 0 0
Bearer 1
OHF: 113867 0
OHFErr: 0 0
RS: 1138054 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 810 0
rtx_c: 576 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 70007 0
errFreeBits: 2460334364 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 246175195 0
Data Cells: 848106 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: 10 456
SES: 10 0
UAS: 96 86
AS: 1829
Bearer 0
INP: 52.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 70442.73 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: 908/908 0/0
Total time = 1 days 14 hours 17 min 5 sec
FEC: 39947 7068
CRC: 6241 566
ES: 10 456
SES: 10 0
UAS: 96 86
LOS: 1 0
LOF: 3 0
LOM: 0 0
Latest 15 minutes time = 2 min 5 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 2
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 = 14 hours 17 min 5 sec
FEC: 174 75
CRC: 0 20
ES: 0 20
SES: 0 0
UAS: 31 31
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 322 170
CRC: 0 24
ES: 0 23
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 30 min 29 sec
FEC: 0 2
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
#
-
@ 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?
-
@ 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.
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.
-
Well, it took a week.... but this morning it resyncd without ReTx.
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?
-
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:
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.
-
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.
-
Good result, the capping certainly does appear to work in most cases with respect to changing DS Re-Tx profile to low.
-
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:
(https://www.dropbox.com/s/2j8ube2dh0m6uj1/2019-01-22%2012.00.22.jpg?raw=1)
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. :)