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: Something has gone wonkey.  (Read 7663 times)

MrBelter

  • Member
  • **
  • Posts: 35
Something has gone wonkey.
« on: March 12, 2016, 10:18:56 AM »

HH5 Type A to an ECI cab, apart from the 14 day reboots with the HH5 the connection has been rock solid since 2011 through a HH3, HH4 and HH5 Type A.

However Openreach recently carried out work on my cab i noticed my max attainable has altered and problems have started.

My upstream has dropped to 26000 from over 33000
My downstream has increased from 102000 to 108000 but my actual sync dropped to 78000 from 80000

That in its self isnt a problem i guess but now my HH5 is rebooting 4 or 5 times a day which clearly is a problem.

I have done a quiet line test and the line is quiet.

Any ideas?
Logged

William Grimsley

  • Kitizen
  • ****
  • Posts: 1489
    • Newton Poppleford Weather
Re: Something has gone wonkey.
« Reply #1 on: March 12, 2016, 10:57:41 AM »

Hi MrBelter,

Please can you post your line stats: http://192.168.1.254 - Troubleshooting - Helpdesk.

This could well be due to a customer being connected to your cabinet who is very close to you and could be a major "crosstalker".
« Last Edit: March 12, 2016, 11:02:48 AM by William Grimsley »
Logged

MrBelter

  • Member
  • **
  • Posts: 35
Re: Something has gone wonkey.
« Reply #2 on: March 12, 2016, 11:15:09 AM »

Its all altered slightly since i posted but as you can see it still not the 33000/102000 it was

4. Board version:   BT Hub 5A
5. DSL uptime:   0 days, 03:10:26
6. Data rate:   19999 / 78639
7. Maximum data rate:   26668 / 107997
8. Noise margin:   9.6 / 13.5
9. Line attenuation:   4.4 / 5.7
10. Signal attenuation:   4.3 / 5.7

Ive noticed over the last 2 days the TR069 log has gone mental as well.

11:01:34, 12 Mar.   (87417.430000) CWMP: session completed successfully
11:01:34, 12 Mar.   (87417.220000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
11:01:31, 12 Mar.   (87414.510000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
11:01:31, 12 Mar.   (87414.500000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
11:01:31, 12 Mar.   (87414.060000) CWMP: Initializing transaction for event code 4 VALUE CHANGE
09:27:41, 12 Mar.   (81784.490000) CWMP: session completed successfully
09:27:40, 12 Mar.   (81784.290000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
09:27:38, 12 Mar.   (81781.920000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
09:27:38, 12 Mar.   (81781.920000) CWMP: Session start now. Event code(s): '6 CONNECTION REQUEST,4 VALUE CHANGE'
09:27:38, 12 Mar.   (81781.450000) CWMP: Initializing transaction for event code 6 CONNECTION REQUEST
09:21:36, 12 Mar.   (81420.070000) CWMP: session completed successfully
09:21:36, 12 Mar.   (81419.660000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
09:21:33, 12 Mar.   (81417.130000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
09:21:33, 12 Mar.   (81417.120000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
09:21:33, 12 Mar.   (81416.720000) CWMP: Initializing transaction for event code 4 VALUE CHANGE
09:21:24, 12 Mar.   (81407.630000) CWMP: session completed successfully
09:21:20, 12 Mar.   (81404.280000) CWMP: Set Parameter by TR069 Success
09:21:20, 12 Mar.   (81403.470000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
09:21:08, 12 Mar.   (81391.870000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
09:21:08, 12 Mar.   (81391.860000) CWMP: Session start now. Event code(s): '6 CONNECTION REQUEST,4 VALUE CHANGE'
09:21:08, 12 Mar.   (81391.400000) CWMP: Initializing transaction for event code 6 CONNECTION REQUEST
09:17:35, 12 Mar.   (81178.960000) CWMP: session completed successfully
09:17:35, 12 Mar.   (81178.750000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
09:17:32, 12 Mar.   (81175.640000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
09:17:32, 12 Mar.   (81175.630000) CWMP: Session start now. Event code(s): '6 CONNECTION REQUEST,4 VALUE CHANGE'
09:17:31, 12 Mar.   (81174.630000) CWMP: Initializing transaction for event code 6 CONNECTION REQUEST
08:01:58, 12 Mar.   (76642.280000) CWMP: session completed successfully
08:01:58, 12 Mar.   (76641.840000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
08:01:38, 12 Mar.   (76622.060000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
08:01:38, 12 Mar.   (76622.050000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
08:01:12, 12 Mar.   (76595.470000) CWMP: session closed due to error: No response
08:01:09, 12 Mar.   (76592.730000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
08:01:09, 12 Mar.   (76592.720000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
08:00:36, 12 Mar.   (76559.720000) CWMP: session closed due to error: No response
08:00:33, 12 Mar.   (76556.420000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
08:00:33, 12 Mar.   (76556.410000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
08:00:32, 12 Mar.   (76555.980000) CWMP: Initializing transaction for event code 4 VALUE CHANGE
03:28:22, 12 Mar.   (60225.770000) CWMP: session completed successfully
03:28:22, 12 Mar.   (60225.550000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
03:28:19, 12 Mar.   (60222.360000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
03:28:19, 12 Mar.   (60222.350000) CWMP: Session start now. Event code(s): '2 PERIODIC,4 VALUE CHANGE'
03:28:18, 12 Mar.   (60221.960000) CWMP: Initializing transaction for event code 2 PERIODIC
18:15:15, 11 Mar.   (27039.050000) CWMP: session completed successfully
18:15:14, 11 Mar.   (27037.930000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
18:15:00, 11 Mar.   (27023.920000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
18:15:00, 11 Mar.   (27023.910000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
18:13:56, 11 Mar.   (26960.080000) CWMP: session closed due to error: No response
18:13:53, 11 Mar.   (26957.130000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
18:13:53, 11 Mar.   (26957.130000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
18:13:20, 11 Mar.   (26924.130000) CWMP: session closed due to error: No response
18:13:18, 11 Mar.   (26921.680000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
18:13:18, 11 Mar.   (26921.670000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
18:13:17, 11 Mar.   (26921.200000) CWMP: Initializing transaction for event code 4 VALUE CHANGE
10:46:52, 11 Mar.   ( 136.080000) CWMP: session completed successfully
10:46:51, 11 Mar.   ( 135.290000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
11:46:24, 11 Mar.   ( 123.040000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
11:46:24, 11 Mar.   ( 123.030000) CWMP: Session start now. Event code(s): '1 BOOT,4 VALUE CHANGE'
11:46:01, 11 Mar.   ( 99.890000) CWMP: session closed due to error: No response
11:45:52, 11 Mar.   ( 90.920000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
11:45:52, 11 Mar.   ( 90.910000) CWMP: Session start now. Event code(s): '1 BOOT,4 VALUE CHANGE'
11:45:49, 11 Mar.   ( 88.200000) CWMP: Initializing transaction for event code 4 VALUE CHANGE
11:45:22, 11 Mar.   ( 60.520000) CWMP: session closed due to error: No response
11:45:05, 11 Mar.   ( 43.340000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
11:45:05, 11 Mar.   ( 43.330000) CWMP: Session start now. Event code(s): '1 BOOT,4 VALUE CHANGE'
11:45:04, 11 Mar.   ( 42.870000) CWMP: Initializing transaction for event code 1 BOOT
04:52:32, 11 Mar.   (660351.970000) CWMP: session completed successfully
04:52:32, 11 Mar.   (660351.740000) CWMP: HTTP authentication success from https://pbthdm.bt.mo
04:52:14, 11 Mar.   (660333.680000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
04:52:14, 11 Mar.   (660333.670000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
04:51:41, 11 Mar.   (660300.860000) CWMP: session closed due to error: No response
04:51:35, 11 Mar.   (660294.970000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
04:51:35, 11 Mar.   (660294.960000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
04:50:59, 11 Mar.   (660258.930000) CWMP: session closed due to error: No response
04:50:55, 11 Mar.   (660254.860000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
04:50:55, 11 Mar.   (660254.850000) CWMP: Session start now. Event code(s): '4 VALUE CHANGE'
04:50:55, 11 Mar.   (660254.440000) CWMP: Initializing transaction for event code 4 VALUE CHANGE
Logged

MrBelter

  • Member
  • **
  • Posts: 35
Re: Something has gone wonkey.
« Reply #3 on: March 12, 2016, 11:19:02 AM »

This could well be due to a customer being connected to your cabinet who is very close to you and could be a major "crosstalker".

Im assuming the cab is full, when i first got FTTC my max attainable was 130000'ish and over the years it has dropped to 102000'ish but all of a sudden it has jumped up to 108000'ish
Logged

MrBelter

  • Member
  • **
  • Posts: 35
Re: Something has gone wonkey.
« Reply #4 on: March 12, 2016, 11:25:29 AM »

Just had a look and there arent any new SSIDs around, same old same old on that score.
Logged

William Grimsley

  • Kitizen
  • ****
  • Posts: 1489
    • Newton Poppleford Weather
Re: Something has gone wonkey.
« Reply #5 on: March 12, 2016, 11:32:33 AM »

Hmm, interesting. It could be something to do with G.INP being implemented...
Logged

MrBelter

  • Member
  • **
  • Posts: 35
Re: Something has gone wonkey.
« Reply #6 on: March 12, 2016, 11:39:05 AM »

I hope not, its never missed a beat up to them pratting about  :(
Logged

MrBelter

  • Member
  • **
  • Posts: 35
Re: Something has gone wonkey.
« Reply #7 on: March 14, 2016, 10:10:50 AM »

Some stability seems to have come back, its been up over 2 days now but the stats are the same so i am guessing the HH5 was finding its feet after being G.INPed.

Oddly BT offered to send me another Home Hub within about 3 minutes of a live chat and it is normally blood out of a stone with them isn't it. Anyway unless it is a HH5 Type B to try and see what the stats looks like i might as well just send it straight back because i am pretty sure it isn't the hubs fault.

Half wish i had not sold my Huawei modem now  :(
Logged

MrBelter

  • Member
  • **
  • Posts: 35
Re: Something has gone wonkey.
« Reply #8 on: March 16, 2016, 05:50:11 PM »

Its all altered slightly since i posted but as you can see it still not the 33000/102000 it was

4. Board version:   BT Hub 5A
5. DSL uptime:   0 days, 03:10:26
6. Data rate:   19999 / 78639
7. Maximum data rate:   26668 / 107997
8. Noise margin:   9.6 / 13.5
9. Line attenuation:   4.4 / 5.7
10. Signal attenuation:   4.3 / 5.7


The replacement HH5 Type A arrived and unsurprisingly there is very little difference (a couple of Mbit on the upload)

6. Data rate:   20000 / 78639
7. Maximum data rate:   28555 / 107784
8. Noise margin:   9.6 / 13.5
9. Line attenuation:   4.4 / 5.9
10. Signal attenuation:   4.4 / 5.9
Logged

Dray

  • Kitizen
  • ****
  • Posts: 2361
Re: Something has gone wonkey.
« Reply #9 on: March 16, 2016, 05:54:28 PM »

Yes a Huawei modem or a HH5B may get G.INP on your ECI cab.
A HH5A won't :(
Logged

S.Stephenson

  • Reg Member
  • ***
  • Posts: 575
Re: Something has gone wonkey.
« Reply #10 on: March 16, 2016, 09:48:28 PM »

Yes a Huawei modem or a HH5B may get G.INP on your ECI cab.
A HH5A won't :(
A HH5A does support G.INP doesn't it, it was fixed in a firmware update.

Or did it break again?
Logged

Dray

  • Kitizen
  • ****
  • Posts: 2361
Re: Something has gone wonkey.
« Reply #11 on: March 16, 2016, 10:15:53 PM »

No I haven't seen any evidence of the HH5A supporting G.INP on any firmware. The HH5B does though.
Logged

S.Stephenson

  • Reg Member
  • ***
  • Posts: 575
Re: Something has gone wonkey.
« Reply #12 on: March 16, 2016, 10:33:57 PM »

No I haven't seen any evidence of the HH5A supporting G.INP on any firmware. The HH5B does though.

I was under the impression that the HH5a on a Huawei cabinet would work with G.INP on the downstream only, the problem that BT had initially was enabling G.INP on Up and Down by default and the ECI modem and HH5a couldn't handle it, so they just disabled it on the up as a cheap fix.

Logged

Dray

  • Kitizen
  • ****
  • Posts: 2361
Re: Something has gone wonkey.
« Reply #13 on: March 16, 2016, 10:50:37 PM »

A lot of people say that, no evidence though. However, plenty of evidence that the HH5A does not support G.INP and the HH5B does.
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Something has gone wonkey.
« Reply #14 on: March 16, 2016, 11:34:16 PM »

I would just like to make a brief comment and a polite request . . .

Brief comment: There has been a long-running disagreement between various persons in the TBB forum on the subject of the BT HH5A, BT HH5B and G.Inp support.

Polite request: Please don't bring that disagreement here.
« Last Edit: March 17, 2016, 04:45:05 PM by burakkucat »
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.
Pages: [1] 2