Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 3 4 [5]

Author Topic: Hollow curve disease even after modem swap-out, and occasional DSL instability  (Read 7593 times)

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project

b*cat nods his head in agreement.
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick

For the first time in a couple of months we see:

     Summary of DSL links’ wellbeing and error counts
     ────────────────────────────────────

* There are 3 modems in total. They are:     #1, #2 and #4
* The active, contactable modems are:        #1, #2 and #4
* The modems successfully queried are:       #1, #2 and #4

  ──────────────────────────────────────────
  ***                                                                         ***
  ***  All is well ! No errors or problems detected.  ✅   ***
  ***                                                                         ***
  ──────────────────────────────────────────

      
                                              ◅ ◅ ◅◊▻ ▻ ▻
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick

Normality restored.

Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project

Purrfect.  :)
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick

                Status of each modem
              ───────────────────

* There are 3 modems in total. They are:     #1, #2 and #4
* The active, contactable modems are:        #1, #2 and #4
* The modems successfully queried are:       #1, #2 and #4

--
   Link #1  sync rate: downstream:   2.783 Mbps at SNRM 2.9 dB; upstream: 653 kbps at SNRM 5.9 dB
--
   Link #2 sync rate: downstream:   2.854 Mbps at SNRM 3.2 dB; upstream: 525 kbps at SNRM 5.8 dB
--
   Link #4 sync rate: downstream:   2.876 Mbps at SNRM 2.9 dB; upstream: 386 kbps at SNRM 5.9 dB

                                              ◅ ◅ ◅◊▻ ▻ ▻



As discussed in an earlier thread, note how the downstream sync values are 100k - 300kbps less than in the depths of winter, so over 10% speed loss downstream!



OR engineer’s notes:

BT Fault 5-887769895622 Right When Tested; End User Equipment;All BT tests completed ok, diagnostics show no fault condition
Did all the connections, extensions and DSL filters meet the minimum standards ?: Yes
Have you conducted a sync test (modem light on) ?: Yes
Did you complete the Frames module ?: No
Did you complete the Base module ?: Yes
Did you complete the end customer Premises Wiring Module ?: No
Did you complete the end customer Premises Equipment Module ?: No
What was the result of the initial pair quality test ?: Fail
Did you complete the Network module ?: Yes
Have you successfully demonstrated connectivity to the NTE ?: Yes

2022-05-05 18:05:07      Engineer: The engineer has now completed the visit.   BT
2022-05-05 18:01:16   Yesterday 18:01:46   BT Fault 5-887769895622 Right When Tested; End User Equipment;All BT tests completed ok, diagnostics show no fault condition
What did the end customer describe as the primary issue ?: 3762.03-Customer Report: End customer informed us that broadband is not stable / intermittent.
Where did you perform the initial PQT ?: 3743.01-

Initial test results: PQT test performed at NTE back plate.
What was the result ?: 3763.02-The test passed with amber parameters on 2022-05-05T16:15:47.
Have you identified any other issue(s) in the OR network ?: 6357.03-

What was found: The line was noisy.
Where was the fault located ?: 743.01-

Actions to resolve: Fault located in the D side overhead network.
What did you do to fix it ?: 745.21-Resolved by re-terminating drop wire at external block.
Have you given any general advice to EC ?: 6159.07-

Advice given to end customer: Stop changing SNR to 6dB. Line too long for this setting. .
Please specify: 6160.01-
Where did you perform the final PQT ?: 3835.01-

Final test results: Final PQT performed at the NTE back plate.
What was the result ?: 3836.02-The test passed with amber parameters on 2022-05-05T16:20:59.
What was your final test ?: 3417.03-Final FastTest completed.
What was the result ?: 4000.01-The test passed on 05/05/2022 17:55:33.


A few remarks:
  • Recent OR engineers have been obsessed with downstream SNRM, whilst having absolutely zero clue about it.
  • What is this engineer thinking when he made these notes about 6dB? "Stop changing SNR to 6dB. Line too long for this setting."
  • He said no such thing to us, I had done no such thing,
  • nor was it at 6dB downstream, it was at 10-11dB with a target of 12dB as a desperation measure.
  • The line is usually set to 3dB downstream.



What on earth are the numbers that are sprinkled throughout the report? eg: 3417.03

I asked AA, who said ‘no idea’ and ‘presumably some BT thing’.
« Last Edit: May 07, 2022, 11:16:10 AM by Weaver »
Logged
Pages: 1 ... 3 4 [5]