In reply to a post by partial:

Spliced is just an Americanism for jointed. A lot of American terms have crept in in recent years.

It's interesting.

I would have never thought to use the term splice for joins in copper cabling. In comms I have always associated splicing with fibre. Copper cabling is terminated (or punched-down) at the ends and an intermediate join on a cable run is a joint.

There is also "potting up" - perhaps not of the MJ or Alan Titchmarsh type but of using flowable resin to encase a joint.

For the sailors out there you can splice rope too.

I had another line drop today. After it came back up I took these stats from the modem. Can anyone see anything wrong with this?

Remember, this line was stable at 60Mbps for 4 years and only dropped after the ports were changed by Openreach.

============================================================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
G.Vector: Disable
Traffic Type: PTM Mode
Link Uptime: 0 day: 0 hour: 23 minutes
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 18.500 Mbps 48.418 Mbps
Actual Net Data Rate: 18.476 Mbps 48.337 Mbps
Trellis Coding: ON ON
SNR Margin: 6.1 dB 6.3 dB
Actual Delay: 0 ms 0 ms
Transmit Power: 6.8 dBm 6.9 dBm
Receive Power: -4.7 dBm -2.1 dBm
Actual INP: 0.0 symbols 0.0 symbols
Total Attenuation: 11.5 dB 14.9 dB
Attainable Net Data Rate: 18.640 Mbps 47.939 Mbps
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 0.3 12.2 29.4 N/A 10.7 24.8 39.8
Signal Attenuation(dB): 0.3 12.3 29.2 N/A 11.4 24.6 39.7
SNR Margin(dB): 7.5 6.1 6.1 N/A 6.3 6.3 6.2
Transmit Power(dBm): - 4.5 -23.9 6.5 N/A 9.1 7.9 6.8
============================================================================

VDSL Counters

Downstream Upstream
Since Link time = 23 min 41 sec
FEC: 0 2
CRC: 6 1
ES: 6 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Latest 15 minutes time = 9 min 9 sec
FEC: 0 0
CRC: 3 0
ES: 3 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 0 2
CRC: 3 1
ES: 3 0
SES: 0 0
UAS: 27 27
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
HostInitRetr: N/A
FailedRetr: N/A
Latest 1 day time = 24 min 9 sec
FEC: 0 2
CRC: 6 1
ES: 6 0
SES: 0 0
UAS: 27 27
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 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
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Total time = 24 min 9 sec
FEC: 0 2
CRC: 6 1
ES: 6 0
SES: 0 0
UAS: 27 27
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
============================================================================

In reply to a post by dect:

As a process of elimination putting you back on your original DSLAM port to see if the speed would go back to what it was would be a good start but I don't know what the chances of that would be. Are you sure nothing else was changed during the very first visit.

They probably don't know what ports I was on as it has been changed 5 or 6 times since the original change.

My thought is that the DSLAM is not only faulty but the cabinet is full. They just keep swapping customers ports to try and keep the latest complaint happy. I did discuss this with one engineer who didn't disagree.

In reply to a post by GeoPrice1:

I had another line drop today. After it came back up I took these stats from the modem. Can anyone see anything wrong with this?

Fastpath on a 6dB target.

DLM isn't holding the line back and it's achieving as good as it can (in its current state).

In reply to a post by Pheasant:

For the sailors out there you can splice rope too.

Which would have been happening (using that verb) a long time before any wired technology had been invented and probably before Columbus had made it across the Atlantic.

Edited by GonePostal (Sun 07-Feb-21 12:41:38)

I'd be very surprised if anybody had changed dslam ports 5 or 6 times.

Lest we forget everybody is guessing on the forum. Nobody has had their meters out.

So I'll have a punt that you had a line fault and somebody has swapped you to a different cable pair that has different properties. Any subsequent port change still connects you to the same cablie pair with the same properties.

.

In reply to a post by partial:

I'd be very surprised if anybody had changed dslam ports 5 or 6 times.

Lest we forget everybody is guessing on the forum. Nobody has had their meters out.

So I'll have a punt that you had a line fault and somebody has swapped you to a different cable pair that has different properties. Any subsequent port change still connects you to the same cablie pair with the same properties.

.

The cable pair has not been changed (hopefully) as there was a fault in the original pair some time ago (4 years or more) so the faulty pair were capped or removed. Since having the faulty pair issue fixed 4 years ago I had a stable 60Mbps. None of the engineers have made any changes at the master socket except change the faceplate, so I would guess that I am still using the same cable pair.

In reply to a post by partial:

Spliced is just an Americanism for jointed. A lot of American terms have crept in in recent years.

Thanks for this info, I wasn't aware before but will in the future

DSLAM ports cannot be changed willy nilly. If a port change is required it has to be authorised and the change done centrally as well as at the cab , otherwise the port wont work. They original port will be marked as faulty for investigation. Eventually the ports will run out and the faulty ports checked and repaired.

In reply to a post by witchunt:

DSLAM ports cannot be changed willy nilly. If a port change is required it has to be authorised and the change done centrally as well as at the cab , otherwise the port wont work. They original port will be marked as faulty for investigation. Eventually the ports will run out and the faulty ports checked and repaired.

The engineers have explained that and one even asked if he could move my connection to the other cabinet, which is getting 110Mbps feed, but this was refused.

From what I have been told by some of the engineers, no matter what port they have used since my first port change, the speed they are measuring at the ports in the cabinet is only around 48 - 49Mbps even before it goes any distance down the line.

The fact that they are only getting 48 - 49Mbps at the DSLAM port highlights that the DSLAM is the source of the fault as the speed at the port should be close to the maximum speed. I can only go by what I am told.