Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: adslmax on August 21, 2018, 03:48:56 PM
-
I didn't know PN has booked an engineer to turn up at my door this morning to enter my property and he agree to resetted DLM to open profile and told me to leave it on for two days before G.INP get back but he told me bad news that my FTTC cabinet won't get back to 79999K because the cabinet (pcp8) almost nearly filled up. Lucky PN, as I almost going out for the day. I was surprise PN never informed me of an engineer to turn up today. Anyway I did ask the engineer if G.Fast or FTTP ever come to my area for Cuckoo Oak. He say that my area are supposed to be G.Fast this month but Openreach has decided to withdrawnal it because not enough peoples on FTTC in Telford suggest that peoples using Virgin Media cable. For FTTP, there is no chance for Telford, he say.
Here is full stats of open profile for now:
DLM Resetted (Open Profile for first two days) 21st August 2018 by Openreach Engineer at 11:33am
Connection stats
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 26797 Kbps, Downstream rate = 80556 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 67526 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.2 15.1
Attn(dB): 12.0 0.0
Pwr(dBm): 12.5 0.9
VDSL2 framing
Bearer 0
MSGc: 18 26
B: 51 237
M: 1 1
T: 64 42
R: 12 16
S: 0.0245 0.3781
L: 20896 5374
D: 1321 1
I: 64 127
N: 64 254
Counters
Bearer 0
OHF: 138477 54774
OHFErr: 0 0
RS: 35450023 2299498
RSCorr: 0 0
RSUnCorr: 0 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 28308888 0
Data Cells: 12256 0
Drop Cells: 0
Bit Errors: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
AS: 218
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.57 3.98
OR: 121.96 64.22
AgR: 67647.75 20063.54
Bitswap: 0/0 0/0
Total time = 7 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 15 minutes time = 7 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
Previous 15 minutes 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
Latest 1 day time = 7 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
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 = 7 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
________________________________________________________________________________________
xDSL
Mode VDSL2
Traffic Type PTM
Status Up
Link Power State L0
Downstream Upstream
Line Coding (Trellis) On On
SNR Margin (dB) 6.2 15.1
Attenuation (dB) 12.0 0.0
Output Power (dBm) 12.5 0.9
Attainable Rate (Kbps) 80556 26797
Rate (Kbps) 67526 19999
B (# of bytes in Mux Data Frame) 51 237
M (# of Mux Data Frames in an RS codeword) 1 1
T (# of Mux Data Frames in an OH sub-frame) 64 42
R (# of redundancy bytes in the RS codeword) 12 16
S (# of data symbols over which the RS code word spans) 0.0245 0.3781
L (# of bits transmitted in each data symbol) 20896 5374
D (interleaver depth) 1321 1
I (interleaver block size in bytes) 64 127
N (RS codeword size) 64 254
Delay (msec) 8 0
INP (DMT symbol) 3.00 0.00
OH Frames 217243 85573
OH Frame Errors 0 0
RS Words 55614255 3611371
RS Correctable Errors 0 0
RS Uncorrectable Errors 0 0
HEC Errors 0 0
OCD Errors 0 0
LCD Errors 0 0
Total Cells 44411191 0
Data Cells 14932 0
Bit Errors 0 0
Total ES 0 0
Total SES 0 0
Total UAS 0 0
________________________________________________________________________________________
Stats recorded 21 Aug 2018 11:33:00
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039g1.d24m
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 7 min 0 sec
Resyncs: 0 (since 21 Aug 2018 11:33:00)
Downstream Upstream
Line attenuation (dB): 12.0 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 67526 19999
SNR margin (dB): 6.2 15.1
Power (dBm): 12.5 0.9
Interleave depth: 1321 1
INP: 3.00 0
G.INP: Not enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
RSCorr/RS (%): 0.0000 0.0000
RSUnCorr/RS (%): 0.0000 0.0000
ES/hour: 0 0
_________________________________________________________________________________________
80556 26797 Attainable Rate (Kbps)
67526 19999 Sync Rate (Kbps)
6.2 15.1 SNR Margin (dB)
12.0 0.0 Line Attenuation (dB)
12.5 0.9 Output Power (dBm)
1321 1 Interleave Depth
3.00 0.00 INP
Not enabled Not enabled G.INP
5 (VECT_UNCONFIGURED) Vectoring status
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.57 3.98
OR: 121.96 64.22
AgR: 67647.75 20063.54
Bitswap: 0/0 0/0
For your connection, the acceptable range of speeds is 40 Mbps-65.36 Mbps
Additional Information:
IP Profile for your line is - 65.36 Mbps
-
What did you contact Plusnet about for them to send an engineer?
You had a single resync that was a little lower than usual. Hardly cause for an engineer visit. Not cause to contact your ISP either.
You may get back to 80Mb now though.
DLM should lower your target SNRM to 5dB a few days after applying G.INP.
-
Looks like you have interleaving on with INP of 3 and a delay of 8
That’s not what I think you mean by an “open profile”
-
I never ask Plusnet to send out engineer. They found a fault on the line. They sent off to BT Wholesale yesterday. No one metion me of an engineer to come out or booked in.
-
Looks like you have interleaving on with INP of 3 and a delay of 8
That’s not what I think you mean by an “open profile”
Openreach has resetted DLM open profile on his big tool kit (JS2 something) he spend half an hour to resetted everything on DLM.
-
I can only dream of getting speeds like that from a single line, but at the moment I have two lines bonded while one is flapping a lot because of an intermittent fault which I can't get to clearly register yet so AAISP can pursue it.
Looks like you have interleaving on with INP of 3 and a delay of 8
That’s not what I think you mean by an “open profile”
Temporary traditional interleaving for the downstream is standard for a DLM reset.
-
Looks like interleaving might be the default for new provisions too.
On both ECI and Huawei lines.
-
Temporary traditional interleaving for the downstream is standard for a DLM reset.
I think the verbage open profile threw me.
-
I got a history of last DLM remotely resetted by Plusnet on 29th January 2018 to compared to today DLM resetted by an engineer:
29/01/2018:
Downstream Upstream
Line attenuation (dB): 11.3 0.0
Signal attenuation (dB): Not available on VDSL2
Attenuation rate (kbps): 83026 27648
Connection speed (kbps): 69594 19999 (79999 19999 when enabled G.INP after 3 days)
SNR margin (dB): 6.2 15.2
Power (dBm): 12.5 -1.3
Interleave depth: 1363 1
INP: 3.00 0
G.INP: Not Enabled Not Enabled
21/08/2018
Downstream Upstream
Line attenuation (dB): 12.0 0.0
Signal attenuation (dB): Not available on VDSL2
Attenuation rate (kbps): 80556 26797
Connection speed (kbps): 67526 19999 (76999 19999 when enabled G.INP soon within 3 days - look likely no chance of 79999)
SNR margin (dB): 6.2 15.1
Power (dBm): 12.5 0.9
Interleave depth: 1321 1
INP: 3.00 0
G.INP: Not Enabled Not Enabled
I reckon when G.INP is enabled will only get sync rate around 76999 something like that ?
-
Yes but because you will be under 79,999 this time DLM might lower your SNRM target a couple days after G.INP returns.
It would only need to go to 5dB you get you max sync.
-
was surprise PN never informed me of an engineer to turn up today.
Thats what happened to me last year. An engineer came out even before I agreed to one coming out. Unfortunately that engineer turned up and was sent away by a family member who thought there was nothing wrong with the line.
-
j0hn
What happen if DLM put retx high on bearer 0 (INPRein:1.00) with target SNR 5dB? What to do next? Or leave it alone!
It's would be very interesting now. Because it now open profile after DLM resetted. How long to get G.INP back on? What was Bearer 0 retx are like and how long before target snr 5 next and what the Bearer 0 retx are like, high or low? Only sit back and have to wait and see.
Will updated here when DLM has put G.INP back on
-
Because it now open profile after DLM resetted.
No it's not. It's on Default Profile. See DLM Profiles (https://kitz.co.uk/adsl/retransmission.htm#retransmission-DLM-profiles)
After a DLM reset the initial profile is: -
Downstream: Interleaving (& INP) Low. Upstream: Interleaving Off.
Actual words straight from Ian Lawrence who was Openreach Chief Engineer. (https://kitz.co.uk/adsl/ginp-retransmission.htm)
Downstream
Initially, low interleaving is enabled by default on all retransmission lines. Once DLM has positively identified that the modem supports retransmission then retransmission is enabled. This happens after a few days. If the low level of retransmission is not good enough to correct all errors then the high level is selected by DLM. If the line remains unstable and cannot be adequately managed by DLM with retransmission profile then Interleaving is applied as normal.
This is old news from 3 &1/2 yrs ago now.
Open Profile means No Interleaving, No INP, No G,INP. You very obviously have INP = 3 & Delay=8 which means Low Interleave.
I honestly find it hard to believe that you've been hanging around broadband forums for so long and not know this, nor be able to spot INP=3 and Delay=8 in your stats. :(
-
I am sorry Kitz but I do believe this DLM resetted to open profile is now all changed. Openreach engineer did show me his tool kit Open Profile. I do believe all DLM resetted are now in low interleave depth to stable the line as fast path are no longer in open profile.
-
Open Profile means No Interleaving, No INP, No G,INP. You very obviously have INP = 3 & Delay=8 which means Low Interleave.
I honestly find it hard to believe that you've been hanging around broadband forums for so long and not know this, nor be able to spot INP=3 and Delay=8 in your stats. :(
Billion router and openreach tool kit did showing Non G.INP in Open Profile even in a low interleave depth 1321 INP 3 to stable all FTTC lines for the first connection for first two days. It's 100% definitely open profile.
-
Kitz as I am not being funny with you. But I do think this site: https://kitz.co.uk/adsl/ginp-retransmission.htm are outdated August 2015 and these things has changing now in DLM and Openreach might has adjusted all these now rather than in 2015 interview with Ian Lawrence who was Openreach Chief Engineer. (3 years ago)
-
Point Blank you are NOT on Open Profile.
Your stats prove beyond any doubt that you are on Default Profile of Low Interleave
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
How much clearer can it be?
Open Profile is when there is No G.INP + No INP + No Interleave.
In 2015, the automated DLM system for Huawei cabs started using Default Profile rather than Open Profile. Up until very recently Open Profile was still used on ECI cabs and only Openreach Engineers could actually trigger Open Profile after a DLM reset. With effect from this year even Openreach Engineer DLM resets now put the line into Default Profile.
If the engineer used the term 'Open Profile' then it is him who is perhaps not aware of the changes that took place about 4-5 months ago... or perhaps he just said Open when he meant Default.
-
Kitz as I am not being funny with you. But I do think this site: https://kitz.co.uk/adsl/ginp-retransmission.htm are outdated August 2015 and these things has changing now in DLM and Openreach might has adjusted all these now rather than in 2015 interview with Ian Lawrence who was Openreach Chief Engineer. (3 years ago)
The information in there about DLM is still correct. At that time it just applied to the automated system for G.INP (Huawei) lines. Since this year it applies across the board and even DLM resets for ECI cabs now trigger Default Profile.
-
I am sorry Kitz but I do believe this DLM resetted to open profile is now all changed. Openreach engineer did show me his tool kit Open Profile. I do believe all DLM resetted are now in low interleave depth to stable the line as fast path are no longer in open profile.
His kit may say "open profile" or he may have used those words.
It isn't an open profile though.
"open profile" meant wide open, no error protection, i.e fastpath.
They don't go to fastpath with DLM resets anymore.
Huawei lines haven't for years. ECI lines don't either since recently.
-
Ok fair point taken kitz and j0hn - can mod please change subject Re: Openreach engineer has resetted DLM to default profile on my line
-
Hmmm .... every day's a school day ..... I have to admit that on the odd occasion that I mention it, I too still use the term 'Open Profile' when carrying out a DLM reset. For the most part, I tend to just comment I'm resetting the circuit.
However, great point by kitz noted and I will indeed change my wording from now on, per-chance my next EU is adslmax <shudders>. ;) ;D
-
or even 'has reset' because I don't believe 'has resetted' exists in English, in fact my autocorrect spelling checker is immediately trying to fix it.
--
reset
/riːˈsɛt/
verb
verb: reset; 3rd person present: resets; past tense: reset; past participle: reset; gerund or present participle: resetting
1 set again or differently."I must reset the alarm"
◦ ELECTRONICS
cause (a binary device) to enter the state representing the numeral 0.
-
Ok fair point taken kitz and j0hn - can mod please change subject Re: Openreach engineer has resetted DLM to default profile on my line
I don't think that would be appropriate, because it would make nonsense of half the posts in this thread.
-
The only publicly available documentation about the FTTC DLM would be a small section in SIN 498.
At provision, the line is put on “wide open” VDSL2 line profiles allowing the
upstream and downstream line speeds to run at the upper limit of the product option
selected.
To me, it implies that the openness of a profile refers to the lack of any capped rates (banding) lower than the product selected.
-
It doesn't imply that to me.
I deliberately said earlier...
"open profile" meant wide open, no error protection, i.e fastpath.
The fact that SIN 498 specifically says "wide open" and not just open profile makes me think that even more.
-
My understanding of the phrase in question, from SIN498, is that the circuit is allowed to operate at the maximum that the technology and infrastructure allows. I.e. it "finds its own level".
-
I remembered that the test setup in Annex A of SIN 498 does define and refer to some of the line profiles.
Now reconfigure the DSLAM to use the equivalent open interleaved profile
(O2_1_6_36_3_6_18_1) and repeat steps 4 to 12.
Configure DSLAM to implement an ESEL value of 30dB and the open
retransmission profile O2_3_6_36_3_6_18_3 .
Repeat the above process for the default (i.e. fast) profile.
-
A lot of digging around (waaaaay too much bumph to read) and the only thing I can glean at this point is that if an engineer carries out a DLM reset, this will revert the circuit back to the default profile the EU purchased ...... but that it will also remove all protection a line may have built up.
-
Latest stats:
Since Link time = 1 days 12 hours 5 min 29 sec
FEC: 154360 810
CRC: 0 142
ES: 0 120
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Bearer 0
INP: 3.00 0.00
INPRein: 0.00 0.00
delay: 8 0
PER: 1.57 3.98
OR: 121.96 64.22
AgR: 67647.75 20063.54
Bitswap: 19/19 16/16
-
Updated: DLM has resync @ 01:42
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Modem/router firmware: AnnexA version - A2pv6F039g1.d24m
DSL mode: VDSL2 Profile 17a
Status: Showtime
Uptime: 0 hour 8 min 43 sec
Resyncs: 1
Downstream Upstream
Line attenuation (dB): 12.0 0.0
Signal attenuation (dB): Not available on VDSL2
Connection speed (kbps): 78044 19999
SNR margin (dB): 6.4 15.1
Power (dBm): 12.5 1.3
Interleave depth: 8 1
INP: 49.00 0
G.INP: Enabled Not enabled
Vectoring status: 5 (VECT_UNCONFIGURED)
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: 78124.49 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: 2/2 1/1
-
Still waiting for DLM to target SNR 3dB and low retx. Still no change yet since engineer default reset.
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1 (G.INP Enabled as a result of resync)
Last initialization procedure status: 0
Max: Upstream rate = 26920 Kbps, Downstream rate = 78729 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 78044 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.4 15.1
Attn(dB): 12.0 0.0
Pwr(dBm): 12.5 1.3
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: 78124.49 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: 37/37 89/89
Total time = 5 days 20 hours 49 min 0 sec (Since engineer default reset)
FEC: 177275 3885
CRC: 5925 458
ES: 10 381
SES: 10 0
UAS: 36 26
LOS: 1 0
LOF: 6 0
LOM: 0 0
Since Link time = 4 days 6 hours 43 min 21 sec (after G.INP Enabled)
FEC: 14742 3011
CRC: 0 304
ES: 0 252
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
-
You are on low rtex. I doubt DLM will touch your line to lower SNR given the speed you're synced at.
-
You might have a long wait Max, I've been waiting since January for DLM to lower my DS SNRm from 6.4, only by capping my line I've managed to get it lowered.
Steve
-
My sync rate staying at 78Mbps but I got email alert to say my cabinet is now filled up with waiting list.
[attachment deleted by admin]
-
My cabinet is now back to Available to order
-
My cabinet are now back on the waiting list.
-
Then I guess you'll have to wait if you wanted a second FTTC line.
-
I kept getting email from follow that page that kept changing every 2 days
FTTC - Available
FTTC - Waiting List
FTTC - Available
FTTC - Waiting List
FTTC - Available
FTTC - Now back to waiting list again.
Sound like the 2nd FTTC cabinet might be needing to built soon.
-
I just saw openreach engineer who working at my cabinet asked him what he is doing? He say he just checked everything to preparing for g.fast pod delivering at the cabinet soon this month. Took photo.
Meanwhile DLM has made change to my line just after 1:40am as a result of resync increase to 79.5Meg from 78.0Meg :) and INP change from 49.00 to 48.00 after 27 days since DLM reset to default.
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 27123 Kbps, Downstream rate = 81837 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79509 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.1
Attn(dB): 11.9 0.0
Pwr(dBm): 12.4 0.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0977 0.3781
L: 20794 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 63 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 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 56722
OHFErr: 0 0
RS: 9174104 2381308
RSCorr: 3 3
RSUnCorr: 0 0
Bearer 1
OHF: 14069 0
OHFErr: 0 0
RS: 168093 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 142999 0
rtx_c: 13418 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 39 0
minEFTR: 79491 0
errFreeBits: 929810149 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 34555677 0
Data Cells: 29636 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 1699
SES: 10 0
UAS: 63 53
AS: 227
Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 79590.45 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: 1/1 1/1
IP Profile for your line is - 76.88 Mbps
[attachment deleted by admin]
-
Meanwhile DLM has made change to my line just after 1:40am as a result of resync increase to 79.5Meg from 78.0Meg :) and INP change from 49.00 to 48.00 after 27 days since DLM reset to default.
I don't think that's a DLM change. Looks like just a resync.
-
My line has been resync and now back to 80Mbps :) :)
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 27477 Kbps, Downstream rate = 80703 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.4 15.1
Attn(dB): 11.9 0.0
Pwr(dBm): 12.5 0.9
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0971 0.3781
L: 20922 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 63 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 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 183692
OHFErr: 0 0
RS: 29989112 3416690
RSCorr: 8 0
RSUnCorr: 0 0
Bearer 1
OHF: 45510 0
OHFErr: 0 0
RS: 546117 0
RSCorr: 1 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 144265 0
rtx_c: 4 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 79975 0
errFreeBits: 891822 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 112459016 0
Data Cells: 16603618 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: 0 0
AS: 730
Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80080.38 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: 0/0 0/0
Total time = 12 min 10 sec
FEC: 8 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 12 min 10 sec
FEC: 8 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 = 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 = 12 min 10 sec
FEC: 8 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
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 = 12 min 9 sec
FEC: 8 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
-
Just had resync early yesterday just after 5pm as the 80Meg has dropped again due to crosstalk. Reduced 79999k to 79849k
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 27191 Kbps, Downstream rate = 80576 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79849 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.1
Attn(dB): 11.8 0.0
Pwr(dBm): 12.4 0.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0973 0.3781
L: 20883 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 63 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 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 146941
OHFErr: 0 29
RS: 1397606880 330332
RSCorr: 216 71
RSUnCorr: 0 0
Bearer 1
OHF: 2124949 0
OHFErr: 0 0
RS: 25498646 0
RSCorr: 30 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 146529 0
rtx_c: 125 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 79835 0
errFreeBits: 41572741 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 946207868 0
Data Cells: 37446130 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 24
SES: 0 0
UAS: 28 28
AS: 34138
Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 79931.10 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: 2/2 3/3
Total time = 9 hours 29 min 26 sec
FEC: 216 71
CRC: 0 29
ES: 0 24
SES: 0 0
UAS: 28 28
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 14 min 26 sec
FEC: 0 1
CRC: 0 1
ES: 0 1
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 = 9 hours 29 min 26 sec
FEC: 216 71
CRC: 0 29
ES: 0 24
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 = 9 hours 28 min 57 sec
FEC: 216 71
CRC: 0 29
ES: 0 24
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
IP Profile for your line is 77.21Mbps
-
Wow 150kb. That's tiny.
-
I wish my line would sync at anything even close to that.
My average sync is about 45Mb, but has been known to reach 48Mb on a really good day.
As long as it doesn't change too much I just leave it alone and don't worry about it.
:)
-
Wow 150kb. That's tiny.
Are you inferring that this is something trivial that shouldn't be of any concern? That's a 0.1875% drop! It's going to take adslmax hours of effort, frequent contacts with the ISP including requests for engineer visits and numerous posts on here while he works at getting the sync back to where it should be at 79999!
-
I don't understand the fascination Max has with his sync speed. :hmm:
Steve
-
I have no complaints about sync rate has dropped because I only posted for change in sync for my own record history due to crosstalk.
My cabinet are back in waiting list accordingly to btw dsl checker. :blush:
-
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 26972 Kbps, Downstream rate = 80588 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79945 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.1
Attn(dB): 11.8 0.0
Pwr(dBm): 12.4 0.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0972 0.3781
L: 20908 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 63 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 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 3830109
OHFErr: 0 165
RS: 3373875640 3087660
RSCorr: 833 901
RSUnCorr: 0 0
Bearer 1
OHF: 5123486 0
OHFErr: 0 0
RS: 61481090 0
RSCorr: 71 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 148229 0
rtx_c: 1027 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 5 0
minEFTR: 79944 0
errFreeBits: 690538524 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4062242395 0
Data Cells: 149983217 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 247
SES: 0 0
UAS: 28 28
AS: 82310
Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80026.79 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: 3/3 9/9
Total time = 3 days 11 hours 41 min 34 sec
FEC: 7916 3008
CRC: 0 485
ES: 0 247
SES: 0 0
UAS: 28 28
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 11 min 34 sec
FEC: 0 1
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 = 11 hours 41 min 34 sec
FEC: 298 119
CRC: 0 46
ES: 0 39
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 1235 982
CRC: 0 168
ES: 0 72
SES: 0 0
UAS: 28 28
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 22 hours 51 min 49 sec
FEC: 833 901
CRC: 0 165
ES: 0 75
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
IP Profile for your line is 77.3Mbps
-
Actually, I am intrigued.
If the line is obviously that good, how come there is a 6dB SNR? Are you on a Huawei cab?
-
Yes I am on large Huawei cabinet (288) and there is another cabinet to be built due soon.
FTTC Available from 4th February 2014, being expanded by October 2018. Your area is enabled for Superfast Fibre but demand is high on your cabinet right now. This means you may not be able to order fibre today but we're working to increase capacity. Please check back for an update.
The cabinet is on the waiting list. This PCP has a waiters list for FTTC VDSL services. You may place an order which will be dealt with in turn.
-
The SNRM is still ~6 dB because the connection is already effectively at the maximum speed, so a lower SNRM target would achieve nothing.
-
I get that - so would DLM not try and set the SNR lower?
This implies that there must be some threshold that if a line is over X Mb, it will keep the SNR at 6dB.
-
No, DLM never bother to lower SNR even if max rate drop below 78Meg, don't know why. (maybe to do with low interleave by bearer 0 with INPRein: 0.00)
-
I get that - so would DLM not try and set the SNR lower?
Are you getting SNR and target SNR confused?
The DLM cannot set the actual SNR which varies as the line conditions vary. What it does is set the minimum SNR to be used when resyncing which is the target.
When the sync occurs the modem negotiates the fastest speed possible where the SNR is equal to or above the target and within the profile cap - so if (as in this case) the cap is 80Mbps - it syncs at that and there is 'spare' SNR which is great as it provides a buffer. When it syncs at the maximum speed for the cap you can't tell what the actual target SNR is - all you know is that it must be lower than the SNR immediately after the sync - so it is possible the target is already 3db.
If he changed to the 55/10 product (or lower) the SNR would be way higher, but the target would still be 6.
-
No, I wasn't getting it confused, I think I wasn't explaining myself correctly :)
Of course DLM can't set the SNR - it is, as you say, down to the conditions of the individual line itself.
-
I do wish there is special command to force resync via putty and set SNR at 5dB but there is no way to do this way? The only way to get target SNR 3dB is to cap the line at 54999/19999 and wait for DLM to action in 11 or 12 days but there is risky of Bearer 0 with INPRein: 1.00 with high interleave mean IP Profile will drop to 91% to 92% from 96.69%
-
Mr Max, don't you have Vivid 350 from Virgin Media now? Why the worry about a couple of megabits here and there with the VDSL? :)
Permitting customers to start playing with target SNR margins is a bad idea from the Openreach point of view. Given the stories we've seen here of people degrading their services mucking around it would go against the entire point of DLM, to reduce manual intervention and faults, to allow end users to manipulate it.
VDSL is going to be receiving fewer and fewer interventions from Openreach. It is legacy technology now, has been obsolete for a while and the level of investment going into it is minimal.
Regarding your cabinet the chances are there won't be a second one built but either additional line cards / tie pairs to allow use of 5th and 6th cards or an HD upgrade to move it from 288 lines to 384 capacity. By the end of the month is probably too soon for an entirely new cabinet, the delivery times for those are of the order of several months. Be aware that if there is any room for further impact this upgrade is likely to increase crosstalk.
-
I don't have virgin media anymore. Because the speed has dropped to 125Meg from 388Meg every nights, I have cancelled it because lucky me it was on 30 days rolling on with no contract as already sent the hub 3 back to virgin media. Overall disappointed with virgin media unreliable never get 388Meg 24/7. Will never go back to VM don't believe in their speed 388Meg because thinkbroadband speed test show a drop to 125Meg.
I stay with FTTC for now and upgraded to G.Fast soon (probably will choose 160/30 product because 330/50 seem so expensive from openreach)
-
Damn, 125 from 388 is quite some congestion.
-
Yes it always bad congestion in this area for VM. Awful.
-
Touch wood, and at the risk of going slightly off topic - I've never experienced congestion. Well, I did after ADSL24 started getting too popular back in about 07-08.
Had to go there after Pipex threw me off their "unlimited" ADSLMax service within a month. I'm still particularly proud of that one.
-
Regarding your cabinet the chances are there won't be a second one built but either additional line cards / tie pairs to allow use of 5th and 6th cards or an HD upgrade to move it from 288 lines to 384 capacity
Codelook only gives the cabinet being expanded message for 2nd cabinets. None of the HD extensions I've seen on single cabinets show as expanded on codelook.
His cabinet only serves 354 priorities though so that is extremely unlikely.
FTTC Available from 4th February 2014, being expanded by October 2018. Your area is enabled for Superfast Fibre but demand is high on your cabinet right now. This means you may not be able to order fibre today but we're working to increase capacity. Please check back for an update.
The cabinet is on the waiting list. This PCP has a waiters list for FTTC VDSL services. You may place an order which will be dealt with in turn.
The adslmax magic editing strikes again....
Where on Earth did you get that?? That's like a mashup of 3 different sites. That's a sentence from the BT Wholesale Broadband checker, a part from the OpenReach Where and When page, and a made up line that only shows on codelook.
codelook doesn't show your cabinet as being expanded?
-
jOhn you are correct there. I got the wrong cabinet. Apology for mix up
-
Damn, 125 from 388 is quite some congestion.
VM have a history of testing poorly on the Think Broadband checker but being flawless for other usage so it doesn't really prove anything beyond that VM and the TBB tester don't play well. Telford last time I was made aware was fine having not long received some upgrades and having had Vivid 350 recently released. Indeed there don't appear to be any complaints about speeds in Telford in the past year on the VM forums just a couple of SNR issues causing packet loss / intermittent connection.
C'est la vie.
-
Codelook only gives the cabinet being expanded message for 2nd cabinets. None of the HD extensions I've seen on single cabinets show as expanded on codelook.
His cabinet only serves 354 priorities though so that is extremely unlikely.
Understood. In an area with VM coverage, VM average 30-50% uptake in their passed areas, the odds of a new cabinet being needed are virtually nil so it shouldn't be unavailable for new release for long. Probably just needs tie pairs or a card in that case.
-
VM have a history of testing poorly on the Think Broadband checker but being flawless for other usage so it doesn't really prove anything beyond that VM and the TBB tester don't play well. Telford last time I was made aware was fine having not long received some upgrades and having had Vivid 350 recently released. Indeed there don't appear to be any complaints about speeds in Telford in the past year on the VM forums just a couple of SNR issues causing packet loss / intermittent connection.
C'est la vie.
Yes, in the main I dislike the synthetic tests. Personally I'd rather fire up an SFTP client and start performing some multi-connection transfers. That's the really only sensible way to max out a connection, imo.
-
I noticed my dslstats max rate has a varies below:
Max: Upstream rate = 26587 - 27768 Kbps in varies, Downstream rate = 79601 - 84945 Kbps in varies between 01:34am and 01:55am last night. If the max rate is at 84945 Kbps within 10 seconds and force resync with adsl configure --maxDataRate 90000 20000 100000 in putty and the line sync rate could return to max 79999K from 79945K in tonight because of DLM resync other lines at the time of the night between 01:30am and 2:00am.
Question is why can't Openreach removed line capped @ 79999K / 19999k to get the maximum out of the max rate that the line and cabinet support it?
-
Because the product sold is 80/20!
My line can theoretically support 119/25, but since I have bought 40/10 that's what I get!
-
Because the product sold is 80/20!
My line can theoretically support 119/25, but since I have bought 40/10 that's what I get!
Yes, nail on the head.
-
Permitting customers to start playing with target SNR margins is a bad idea from the Openreach point of view. Given the stories we've seen here of people degrading their services mucking around it would go against the entire point of DLM, to reduce manual intervention and faults, to allow end users to manipulate it.
This ^
BTw had a large moan years ago about people using DMT tool to adjust their target SNRM without knowing what they were doing and messing up their line.
The downside of people getting obsessive rather than using it for diagnostics is that it can ruin things for others. There was an unsubstantiated rumour that BTw put pressure on Thomson/Speedtouch to drop some of the config options on the TG585 v7 after a f/w upgrade. Whoever was behind it obviously had some clout with Thomson and there was a massive outcry at one point when they even removed some of the more vital stats.
I have no objection to people capping their line to give the DLM a nudge for those BCM modems that appear to get stuck, but in days of old you used to see people running their lines at a ridiculous 1 or 2dB margin.
-
Kitz oh blimey I do remember using dmt tool to force my adsl2+ Snr at 3dB and increase my sync rate to 18 Meg and stood there for 13 days before I upgraded to fttc in 2014. :)
Just found my saved screenshot below :)
-
There's nothing technical stopping end users adjusting the target SNRM, it's just that the Broadcom modems can't do it. It's possible to fiddle with the SNRM using other modems.
-
I do remember these miserable contractor men telling me off to stop spying at their work during FTTC built in December 2013. I watched them all day. :)
[attachment deleted by admin]
[attachment deleted by admin]
-
You're lucky you didn't end up in that hole !!!
-
You're lucky you didn't end up in that hole !!!
:-[ if I did fall on this one below!
[attachment deleted by admin]
-
Did force re-sync to get back to maximum sync rate via putty :) at 1:45am as the max rate jump to 89457k and re-sync straight away at 79998K (1K is missing out)
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 27275 Kbps, Downstream rate = 81891 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 79998 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.1
Attn(dB): 11.8 0.0
Pwr(dBm): 12.4 0.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 243 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0971 0.3781
L: 20922 5374
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 63 0
TxQueue: 21 0
G.INP Framing: 18 0
G.INP lookback: 21 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 47148
OHFErr: 0 0
RS: 7671632 1979344
RSCorr: 0 0
RSUnCorr: 0 0
Bearer 1
OHF: 11704 0
OHFErr: 0 0
RS: 139704 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 148962 0
rtx_c: 1380 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 5 0
minEFTR: 79975 0
errFreeBits: 3985498916 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 28922277 0
Data Cells: 1051 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 318
SES: 0 0
UAS: 192 192
AS: 188
Bearer 0
INP: 48.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 3.98
OR: 0.01 64.22
AgR: 80080.38 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: 2/2 1/1
Total time = 4 days 12 hours 23 min 6 sec
FEC: 9402 3267
CRC: 0 567
ES: 0 318
SES: 0 0
UAS: 192 192
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 8 min 6 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 55 55
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 5 2
CRC: 0 2
ES: 0 1
SES: 0 0
UAS: 109 109
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 1 day time = 12 hours 23 min 6 sec
FEC: 900 153
CRC: 0 53
ES: 0 47
SES: 0 0
UAS: 164 164
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 1 day time = 24 hours 0 sec
FEC: 884 225
CRC: 0 75
ES: 0 63
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Since Link time = 3 min 7 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
>
IP Profile for your line is 77.35Mbps :)
-
Now leave it alone. Don't even look at stats for a while unless something service affecting happens.
Just enjoy the fact that you have a full 80Mbps line :)
-
> you used to see people running their lines at a ridiculous 1 or 2dB margin.
mea culpa. This is me :-[
But my links never drop now with these good modems, and even if one does, it doesn’t matter, as the other links take over. Also the changeover is now quicker as I have changed the inter-LCP-test speed in the upstream direction, so the router detects the drop sooner now as well as AA detecting it quickly. I never realised it, but you do get even more speed than you might expect with multiple lines as you can get away with lower target SNRM.
-
Now leave it alone. Don't even look at stats for a while unless something service affecting happens.
Just enjoy the fact that you have a full 80Mbps line :)
Thanks but I will be away on holiday to St Ives for a week break on Monday. :) Should I switch off modem because never know of power cut etc might trigger DLM
-
Just enjoy the fact that you have a full 80Mbps line :)
But it's not full 80 Mbps or 79999 Kbps. It's 79998 Kbps. :D
-
79999K never get full 80Mbps :) :P only if the sync rate get it magic number 80000K :P
-
Thanks but I will be away on holiday to St Ives for a week break on Monday. :)
Enjoy the break.
Should I switch off modem because never know of power cut etc might trigger DLM
Yes, why not? And save the electricity. ;)
-
Enjoy the break.
Yes, why not? And save the electricity. ;)
Thanks will do. I do remember a long while I saw someone post a thread post can't remember if it was at PN forum, TTB forum or BT forum that someone turn off modem and went away on holiday then come back after two weeks away found DLM reduced sync rate from 80Mbps to 60Mbps for no reason because DLM don't like the non-active for more than 7 days? Maybe I shouldn't worry about that?
As for electricity, I wouldn't worry about that, it only cost 35p for 7 days lol
-
. . . can't remember if it was at PN forum, TTB forum or BT forum that someone turn off modem and went away on holiday then come back after two weeks away found DLM reduced sync rate from 80Mbps to 60Mbps for no reason because DLM don't like the non-active for more than 7 days?
That reads like something apocryphal. I've never seen any similar reports.
Maybe I shouldn't worry about that?
In one word: Correct.
-
If there is no or insufficient DLM data then there is no reason for it to act. :)
-
If there is no or insufficient DLM data then there is no reason for it to act. :)
Exactly so.
-
My line has resync to magic number max out at 80000K that never has it before since 2014. SNR also shoot up to 9dB.
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 30290 Kbps, Downstream rate = 92132 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 80000 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.2 16.7
Attn(dB): 11.8 0.0
Pwr(dBm): 12.4 0.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 203 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0809 0.3781
L: 21153 5374
D: 8 1
I: 214 127
N: 214 254
Q: 8 0
V: 5 0
RxQueue: 78 0
TxQueue: 26 0
G.INP Framing: 18 0
G.INP lookback: 26 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 54187
OHFErr: 0 0
RS: 10683032 2274862
RSCorr: 0 0
RSUnCorr: 0 0
Bearer 1
OHF: 13510 0
OHFErr: 0 0
RS: 162116 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 149547 0
rtx_c: 0 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 79983 0
errFreeBits: 264740 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 33384475 0
Data Cells: 2953 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: 0 0
AS: 216
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: 80344.32 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: 11/11 0/0
Total time = 3 min 36 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 15 minutes time = 3 min 36 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 = 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 = 3 min 36 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 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 min 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
>
IP Profile for your line is 77.35Mbps
-
Where have you suddenly found another 10Mb of attainable and some spare dB's from?
Interesting.
-
Where have you suddenly found another 10Mb of attainable and some spare dB's from?
Interesting.
Perhaps a neighbour has gone on holiday and switched off his router.
;)
-
Must be!
-
Any particular reason the previous resync was done via CLI using Putty while this was a power cycle of the modem?
If I were to Google those numbers would they match perfectly a thread I read elsewhere in the past few days where a person remarked they had synced at exactly 80Mb?
-
Here is my latest stats ongoing for 7 hours since this morning resync. This morning I saw the stats on the max rate went over 90Mbps so why not give a resync one go via putty and bingo sync rate changed from 79998K to 80000K and INP has changed from 48 to 49 plus SNR changed from 6dB to 9dB. Look like someone going on holiday turn off the modem to gain more max rate.
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 28271 Kbps, Downstream rate = 91448 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 80000 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.2 16.6
Attn(dB): 11.8 0.0
Pwr(dBm): 12.4 0.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 203 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0809 0.3781
L: 21153 5374
D: 8 1
I: 214 127
N: 214 254
Q: 8 0
V: 5 0
RxQueue: 78 0
TxQueue: 26 0
G.INP Framing: 18 0
G.INP lookback: 26 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 2803930
OHFErr: 0 29
RS: 1373582696 3124667
RSCorr: 311 289
RSUnCorr: 0 0
Bearer 1
OHF: 1737028 0
OHFErr: 0 0
RS: 20844326 0
RSCorr: 28 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 149757 0
rtx_c: 210 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 79996 0
errFreeBits: 34039200 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4292440625 0
Data Cells: 9384108 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 20
SES: 0 0
UAS: 0 0
AS: 27905
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: 80344.32 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: 37/37 3/3
Total time = 7 hours 45 min 5 sec
FEC: 311 289
CRC: 0 29
ES: 0 20
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 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: 6 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 = 7 hours 45 min 5 sec
FEC: 311 289
CRC: 0 29
ES: 0 20
SES: 0 0
UAS: 0 0
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 = 7 hours 45 min 5 sec
FEC: 311 289
CRC: 0 29
ES: 0 20
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
-
I think I have spoken too soon about someone go on holiday cos the max rate has come back down at 81Mbps and snr at 6dB as well but sync rate stayed at 80Mbps.
adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 27286 Kbps, Downstream rate = 81448 Kbps
Bearer: 0, Upstream rate = 19999 Kbps, Downstream rate = 80000 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.2 14.6
Attn(dB): 11.8 0.0
Pwr(dBm): 12.4 0.6
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 203 237
M: 1 1
T: 0 42
R: 10 16
S: 0.0809 0.3781
L: 21153 5374
D: 8 1
I: 214 127
N: 214 254
Q: 8 0
V: 5 0
RxQueue: 78 0
TxQueue: 26 0
G.INP Framing: 18 0
G.INP lookback: 26 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 2914814
OHFErr: 0 30
RS: 1395244152 3484739
RSCorr: 313 291
RSUnCorr: 0 0
Bearer 1
OHF: 1764420 0
OHFErr: 0 0
RS: 21173042 0
RSCorr: 31 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 149769 0
rtx_c: 222 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 79996 0
errFreeBits: 34575999 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 65165054 0
Data Cells: 9396848 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 21
SES: 0 0
UAS: 0 0
AS: 28346
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: 80344.32 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: 37/37 3/3
Total time = 7 hours 52 min 26 sec
FEC: 313 291
CRC: 0 30
ES: 0 21
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Latest 15 minutes time = 7 min 26 sec
FEC: 2 2
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Previous 15 minutes time = 15 min 0 sec
FEC: 6 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 = 7 hours 52 min 26 sec
FEC: 313 291
CRC: 0 30
ES: 0 21
SES: 0 0
UAS: 0 0
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 = 7 hours 52 min 25 sec
FEC: 313 291
CRC: 0 30
ES: 0 21
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
>
Also I have noticed this one:
Signal attenuation (dB) U0 U1 U2 U3 U4 D1 D2 D3
05 Oct 2018 18:18:12 2.5 12.8 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:18:32 2.5 12.7 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:20:11 2.5 12.8 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:20:31 2.5 12.7 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:22:31 2.5 12.8 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:22:50 2.5 12.7 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:23:50 2.5 12.8 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:24:10 2.5 12.7 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:26:31 2.5 12.8 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:26:50 2.5 12.7 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:27:11 2.5 12.8 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:27:30 2.5 12.7 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:29:11 2.5 12.8 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:29:31 2.5 12.7 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:30:11 2.5 12.8 20.3 N/A N/A 9.3 16.4 27.4
05 Oct 2018 18:30:31 2.5 12.7 20.3 N/A N/A 9.3 16.4 27.4
-
Any particular reason the previous resync was done via CLI using Putty while this was a power cycle of the modem?
If I were to Google those numbers would they match perfectly a thread I read elsewhere in the past few days where a person remarked they had synced at exactly 80Mb?
I did resync was done via CLI using Putty while this was a power cycle of the modem 8 times in the space of 8 minutes and waiting to see if DLM put banded on the line or more interleaved (high) on it after 48 hours but it haven't done it. Sound like via putty to get resync are safer things to do rather than power down the modem or wait for 30 minutes to avoid any DLM.
-
Probably a crosstalker somewhere as someone mentioned before. Perhaps there has been a power outage or something and now they're back online?
You have quoted the signal attenuation, which is subject to change (unlike the the line attenuation which is static since sync). As you can see, mine (and, in fact, everyone else's) also deviates by a small margin:
Signal attenuation (dB) U0 U1 U2 U3 U4 D1 D2 D3
05 Oct 2018 16:35:27 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:46:27 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:46:57 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:48:57 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:49:57 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:50:27 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:50:57 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:52:27 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:53:57 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:54:27 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:55:57 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 16:56:27 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 17:01:27 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 17:01:57 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 17:05:27 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 17:05:57 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 17:08:57 3.8 9.2 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 17:09:27 3.8 9.1 12.4 N/A N/A 6.5 11.1 20.0
05 Oct 2018 18:04:27 3.8 8.9 12.3 N/A N/A 6.5 11.1 20.0
05 Oct 2018 18:31:27 3.8 9.0 12.3 N/A N/A 6.5 11.1 20.0
While the actual line attenuation figure:
Line attenuation (dB) U0 U1 U2 U3 U4 D1 D2 D3
01 Oct 2018 01:54:28 3.8 9.7 13.3 N/A N/A 5.2 11.3 20.0
-
Mine is
Line attenuation (dB) U0 U1 U2 U3 U4 D1 D2 D3
05 Oct 2018 18:18:12 2.5 13.7 21.3 N/A N/A 7.1 16.5 27.3
-
Interestingly enough, the modem I am currently using gives a higher attenuation figures for some bands than the 8800AXL R2 (as can be seen below) that I used to use as the AiO device, although the difference is mostly D2 and D3:
VDSL Band Status U0 U1 U2 U3 U4 D1 D2 D3
Line Attenuation(dB): 3.7 9.3 13.5 N/A N/A 5.3 11.1 17.6
And for the signal attenuation:
Signal Attenuation(dB): 3.7 9.0 12.7 N/A N/A 6.3 11.0 17.6
Performance is virtually the same, so it's likely that slight differences in manufacturing are responsible.
Anyway, that was perhaps a little bit off topic so I'll stop it there.
-
Hi everyone. I am now back home from my fab holiday in Turkey. Been on paragliding at 1900m in Mount Babadag at Turkey, love it :)
-
Pleased to know that you had a good time. :)
Checking the calendar, your TBB Forum ban should be lifted in two days. That year has passed quite quickly.
-
I forget about that one. U have to remind that to MrSaffron cos I couldn't message him.
-
I forget about that one. U have to remind that to MrSaffron cos I couldn't message him.
Sure. It won't be timed at 00:00:01 hours on November 1, 2018 but I'll give Saffy a quick prod sometime during the day. ;)
-
:) Cheers and thanks
-
My reminder (http://forums.thinkbroadband.com/fibre/t/4604648-re-done.html) was made on Thu 01-Nov-18 at 00:00:59 according to the TBB Forum time. :)
-
I am now unbanned. :) I better behave myself!
-
I am now unbanned. :)
Quick work by Saffy. ;)
I better behave myself!
Yes, indeed. As a member here, you proved that you could . . . after that initial "mishap".