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

Login with username, password and session length
Advanced search  

News:

Pages: [1] 2

Author Topic: Vigor 130 Woes  (Read 9864 times)

highpriest

  • Reg Member
  • ***
  • Posts: 285
Vigor 130 Woes
« on: June 09, 2016, 10:27:54 PM »

First time poster here  :)

So I purchased a Vigor 130 recently with the intention of replacing my BT HH5B with a three device setup; the Vigor 130, an EdgeRouter and a Ubiquiti UniFi AP (and a computer running the UniFi Controller software).

It all went well, but in just over 2 days, the sync speed dropped from pretty much full speed to 73999. My IP profile was lowered to 71.55 Mbps (cab is a Huawei).

Day 1

Code: [Select]
> show adsl
  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 79997000 bps   US Actual Rate       : 19999000 bps
   DS Attainable Rate      : 88255748 bps   US Attainable Rate   : 22444000 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        1       US Interleave Depth  :        1
   NE Current Attenuation  :       14 dB    Cur SNR Margin       :        8  dB
   DS actual PSD           :     2. 0 dB    US actual PSD        :    14. 1  dB
   NE CRC Count            :        0       FE CRC Count         :    33834
   NE ES Count             :        2       FE  ES Count         :    26392
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        1
   ITU Version[0]          : b5004946       ITU Version[1]       : 544e0000
   VDSL Firmware Version   : 05-07-04-03-00-07   [with Vectoring support]
   Power Management Mode   : DSL_G997_PMS_L0
   Test Mode               : DISABLE
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :       13 dB    Far SNR Margin       :        7  dB
   CO ITU Version[0]       : b5004244       CO ITU Version[1]    : 434da459
   DSLAM CHIPSET VENDOR    : < BDCM >

Day 3

Code: [Select]
> vdsl status
  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 73999000 bps   US Actual Rate       : 19999000 bps
   DS Attainable Rate      : 88291792 bps   US Attainable Rate   : 22182000 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        1       US Interleave Depth  :        1
   NE Current Attenuation  :       14 dB    Cur SNR Margin       :        9  dB
   DS actual PSD           :     2. 1 dB    US actual PSD        :    14. 1  dB
   NE CRC Count            :        0       FE CRC Count         :    34303
   NE ES Count             :        0       FE  ES Count         :    26813
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        1
   ITU Version[0]          : b5004946       ITU Version[1]       : 544e0000
   VDSL Firmware Version   : 05-07-06-0D-01-07   [with Vectoring support]
   Power Management Mode   : DSL_G997_PMS_L0
   Test Mode               : DISABLE
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :       14 dB    Far SNR Margin       :        6  dB
   CO ITU Version[0]       : b5004244       CO ITU Version[1]    : 434da459
   DSLAM CHIPSET VENDOR    : < BDCM >

That was just after a restart (the second set of stats). Before the restart, the 'Xdsl Link Times' field was showing 8 suggesting that the device reset the VDSL connection 8 times in a 2 days period. Whatever it was, DLM lowered my IP profile.

Unplugged it all, plugged the HH5B back in. Unfortunately, despite it being online for over 13.5 days, it is stuck at 74000 and refuses to go back up to 79999 (which I got consistently for 4 years).

Code: [Select]
current linestatus
state: UP
mode: VDSL2
mod type: Profile 17a
snr margin down: 107
snr margin up: 69
latn down: 143
latn up: 138
satn down: 0
satn up: 0
output power down: 19
output power up: 140
rate down: 74000
rate up: 19999
attainable rate down: 91610000
attainable rate up: 22869000
chantype: fast

Should I restart the HH5B to force a resync or just leave it alone for a few more days? I want my old speed back! Thanks :)
Logged
Zen | Zyxel VMG8324-B10A (with RFC4638 patch) | EdgeRouter PoE | UniFi AP AC Pro + Lite

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Vigor 130 Woes
« Reply #1 on: June 09, 2016, 10:50:27 PM »

First time poster here  :)

<snip>

Should I restart the HH5B to force a resync or just leave it alone for a few more days? I want my old speed back! Thanks :)

Welcome to the Kitz forum.  :)

I doubt that a resynchronisation event will achieve any positive effect . . . It might induce the DLM to take (what it thinks to be) even more "corrective action". I would advise leaving the HH5B alone and just use the circuit. If you must monitor the statistics, just do so at the same time each day.

In all seriousness, would you have noticed the difference in actual synchronisation speed from normal usage of the circuit?  :-\
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.

highpriest

  • Reg Member
  • ***
  • Posts: 285
Re: Vigor 130 Woes
« Reply #2 on: June 10, 2016, 12:20:41 AM »

Welcome to the Kitz forum.  :)

Thank you :)

Code: [Select]
I doubt that a resynchronisation event will achieve any positive effect . . . It might induce the DLM to take (what it thinks to be) even more "corrective action". I would advise leaving the HH5B alone and just use the circuit. If you must monitor the statistics, just do so at the same time each day.
Fair point. I'll leave it well alone for a few more days (weeks?). Why is the damn DLM thing so touchy?

Code: [Select]
In all seriousness, would you have noticed the difference in actual synchronisation speed from normal usage of the circuit?  :-\
Not under normal usage, no. I still get sub 10 ms pings and the line works absolutely fine. But that's not the point - I want the speed that I know my line is capable of achieving ;D
Logged
Zen | Zyxel VMG8324-B10A (with RFC4638 patch) | EdgeRouter PoE | UniFi AP AC Pro + Lite

gt94sss2

  • Kitizen
  • ****
  • Posts: 1281
Re: Vigor 130 Woes
« Reply #3 on: June 10, 2016, 12:49:05 AM »

I think the Vigor 130 has a Laniq chipset - unlike the HH5B and the Huawei cabinet which both have Broadcom. There is a theory that it's beneficial to match chipsets for better performance.
Logged

highpriest

  • Reg Member
  • ***
  • Posts: 285
Re: Vigor 130 Woes
« Reply #4 on: June 10, 2016, 12:52:09 AM »

I think the Vigor 130 has a Laniq chipset - unlike the HH5B and the Huawei cabinet which both have Broadcom. There is a theory that it's beneficial to match chipsets for better performance.

Yes, been reading up on these very forums. I'm on the lookout for a Billion or ZyXel router I can run in bridge mode :)
Logged
Zen | Zyxel VMG8324-B10A (with RFC4638 patch) | EdgeRouter PoE | UniFi AP AC Pro + Lite

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Vigor 130 Woes
« Reply #5 on: June 10, 2016, 03:53:43 PM »

Fair point. I'll leave it well alone for a few more days (weeks?). Why is the damn DLM thing so touchy?

If only we knew.  :(

Quote from: highpriest
I want the speed that I know my line is capable of achieving ;D

Acknowledged and understood.

I think the Vigor 130 has a Laniq chipset - unlike the HH5B and the Huawei cabinet which both have Broadcom.

I am fairly certain (> 99%) that is correct . . . but let's return the missing t to the name!  ;)

Lantiq, a subsidiary of Intel.
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.

vipermk2

  • Just arrived
  • *
  • Posts: 2
Re: Vigor 130 Woes
« Reply #6 on: February 27, 2017, 07:12:09 PM »

First time poster here  :)

So I purchased a Vigor 130 recently with the intention of replacing my BT HH5B with a three device setup; the Vigor 130, an EdgeRouter and a Ubiquiti UniFi AP (and a computer running the UniFi Controller software).

It all went well, but in just over 2 days, the sync speed dropped from pretty much full speed to 73999. My IP profile was lowered to 71.55 Mbps (cab is a Huawei).

Day 1

Code: [Select]
> show adsl
  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 79997000 bps   US Actual Rate       : 19999000 bps
   DS Attainable Rate      : 88255748 bps   US Attainable Rate   : 22444000 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        1       US Interleave Depth  :        1
   NE Current Attenuation  :       14 dB    Cur SNR Margin       :        8  dB
   DS actual PSD           :     2. 0 dB    US actual PSD        :    14. 1  dB
   NE CRC Count            :        0       FE CRC Count         :    33834
   NE ES Count             :        2       FE  ES Count         :    26392
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        1
   ITU Version[0]          : b5004946       ITU Version[1]       : 544e0000
   VDSL Firmware Version   : 05-07-04-03-00-07   [with Vectoring support]
   Power Management Mode   : DSL_G997_PMS_L0
   Test Mode               : DISABLE
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :       13 dB    Far SNR Margin       :        7  dB
   CO ITU Version[0]       : b5004244       CO ITU Version[1]    : 434da459
   DSLAM CHIPSET VENDOR    : < BDCM >

Day 3

Code: [Select]
> vdsl status
  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 73999000 bps   US Actual Rate       : 19999000 bps
   DS Attainable Rate      : 88291792 bps   US Attainable Rate   : 22182000 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        1       US Interleave Depth  :        1
   NE Current Attenuation  :       14 dB    Cur SNR Margin       :        9  dB
   DS actual PSD           :     2. 1 dB    US actual PSD        :    14. 1  dB
   NE CRC Count            :        0       FE CRC Count         :    34303
   NE ES Count             :        0       FE  ES Count         :    26813
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        1
   ITU Version[0]          : b5004946       ITU Version[1]       : 544e0000
   VDSL Firmware Version   : 05-07-06-0D-01-07   [with Vectoring support]
   Power Management Mode   : DSL_G997_PMS_L0
   Test Mode               : DISABLE
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :       14 dB    Far SNR Margin       :        6  dB
   CO ITU Version[0]       : b5004244       CO ITU Version[1]    : 434da459
   DSLAM CHIPSET VENDOR    : < BDCM >

That was just after a restart (the second set of stats). Before the restart, the 'Xdsl Link Times' field was showing 8 suggesting that the device reset the VDSL connection 8 times in a 2 days period. Whatever it was, DLM lowered my IP profile.

Unplugged it all, plugged the HH5B back in. Unfortunately, despite it being online for over 13.5 days, it is stuck at 74000 and refuses to go back up to 79999 (which I got consistently for 4 years).

Code: [Select]
current linestatus
state: UP
mode: VDSL2
mod type: Profile 17a
snr margin down: 107
snr margin up: 69
latn down: 143
latn up: 138
satn down: 0
satn up: 0
output power down: 19
output power up: 140
rate down: 74000
rate up: 19999
attainable rate down: 91610000
attainable rate up: 22869000
chantype: fast

Should I restart the HH5B to force a resync or just leave it alone for a few more days? I want my old speed back! Thanks :)

Did you manage to get this sorted as I have the same problem
Logged

highpriest

  • Reg Member
  • ***
  • Posts: 285
Re: Vigor 130 Woes
« Reply #7 on: February 27, 2017, 10:01:44 PM »

Did you manage to get this sorted as I have the same problem

Nope, got rid of it, switched to a ZyXel VMG8324 and have had no problems since. I switched ISPs last year and during the migration, a reset was performed. It has since been syncing at the full speed.

Based on my experience, I would not recommend a Vigor 130 if your line is connected to a Huawei cab.
Logged
Zen | Zyxel VMG8324-B10A (with RFC4638 patch) | EdgeRouter PoE | UniFi AP AC Pro + Lite

vipermk2

  • Just arrived
  • *
  • Posts: 2
Re: Vigor 130 Woes
« Reply #8 on: February 27, 2017, 10:46:26 PM »

Cheers for the response, not sure what cab I have outside, I can see it from the window but it's too dark to make out, it's only 50m away so I'll look tomorrow.

I'm thinking of moving over to Zen, just need to bide my time until the years line rental runs out.
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Vigor 130 Woes
« Reply #9 on: February 27, 2017, 11:02:26 PM »

. . . not sure what cab I have outside, I can see it from the window but it's too dark to make out, it's only 50m away so I'll look tomorrow.

Just take a look at the statistics that are available from the Vigor 130. At the bottom of the examples highpriest has shown, above, there is a line which reads --

DSLAM CHIPSET VENDOR    : < BDCM >

The BDCM is an abbreviation for Broadcom and knowing the chipset vendor, we can identify the cabinet based DSLAM.

A Broadcom chipset implies a Huawei manufactured DSLAM, whilst an Infineon chipset implies an ECI manufactured DSLAM.
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.

psychopomp1

  • Reg Member
  • ***
  • Posts: 311
Re: Vigor 130 Woes
« Reply #10 on: February 28, 2017, 04:18:28 AM »

Based on my experience, I would not recommend a Vigor 130 if your line is connected to a Huawei cab.

Sorry to hear of your woes but my experience with the Vigor 130 has been excellent - I'm also on an Huawei cab. Whilst the max attainable is a meg or two lower on the 130 versus the HG612, the 130 still syncs at the full 80/20 on my TalkTalk connection and pings are slightly lower v HG612.

Anyway I've got FTTP On Demand on order from Fluidone so in a few months time all this FTTC cab brand, modem chipset, SNR margins, DLM malarkey etc will be a thing of the past. My only dilemma on FTTP will be which router to use...Asus RT-AC5300 or Netgear R9000  :)
Logged

highpriest

  • Reg Member
  • ***
  • Posts: 285
Re: Vigor 130 Woes
« Reply #11 on: March 01, 2017, 11:25:47 AM »

Sorry to hear of your woes but my experience with the Vigor 130 has been excellent - I'm also on an Huawei cab. Whilst the max attainable is a meg or two lower on the 130 versus the HG612, the 130 still syncs at the full 80/20 on my TalkTalk connection and pings are slightly lower v HG612.

That's good to know. Speeds were fine, the attainable was broadly the same as the HH5B. But it all went horribly wrong very quickly for me. Within 3 days, my line got permanently banded (74000 kbps); this is a line that synced at a solid 80/20 for, well, since they rolled out 17A many years back.

OK, I could have had a faulty unit, but others here have had similar experiences.

Quote
Anyway I've got FTTP On Demand on order from Fluidone so in a few months time all this FTTC cab brand, modem chipset, SNR margins, DLM malarkey etc will be a thing of the past. My only dilemma on FTTP will be which router to use...Asus RT-AC5300 or Netgear R9000  :)

Wow, nice :) I dread to ask how much that cost ;)
Logged
Zen | Zyxel VMG8324-B10A (with RFC4638 patch) | EdgeRouter PoE | UniFi AP AC Pro + Lite

psychopomp1

  • Reg Member
  • ***
  • Posts: 311
Re: Vigor 130 Woes
« Reply #12 on: March 02, 2017, 04:15:20 AM »

Wow, nice :) I dread to ask how much that cost ;)

FTTPoD cost me £3700 in setup (construction) charges and then £300 per month on a 3 year contract :sob:

Obviously not cheap but I see it as a worthwhile investment.
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Vigor 130 Woes
« Reply #13 on: March 02, 2017, 05:08:51 PM »

Psychopomp1 - good for you. I would love to know how you get on, not to hijack this thread though.
Logged

highpriest

  • Reg Member
  • ***
  • Posts: 285
Re: Vigor 130 Woes
« Reply #14 on: March 02, 2017, 05:18:38 PM »

Psychopomp1 - good for you. I would love to know how you get on, not to hijack this thread though.

+1 :)
Logged
Zen | Zyxel VMG8324-B10A (with RFC4638 patch) | EdgeRouter PoE | UniFi AP AC Pro + Lite
Pages: [1] 2
 

anything