Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: roseway on October 09, 2017, 09:03:37 AM
-
At about 00:26 this morning my connection went down for nearly half an hour. When it returned it connected at 79999/20000 (previously 76221/19999) with the same DS SNRM of 3.3 dB, but a considerably increased US SNRM. Very quickly the DS SNRM dropped to 2 dB and the US SNRM dropped a little, but still a lot higher that it was before.
These are typical symptoms of a power cut, but there was no power cut. I guess there was some overnight work being done in the cabinet.
-
Also your U/S Power has risen from ~1.8dB to 4.7dB and Attenuation increased by 0.3dB.... And you have a load of FECs you never had before presumably due to the lower SNRM but little change in CRCs
-
It certainly bears all the hallmarks of the DSLAM being "taken down" . . . either by local action at the cabinet or remotely by entities at the NOC.
-
Just a thought is there any change in the firmware version being reported by the DSLAM
-
Good suggestion, you're quite right:
Yesterday: DSLAM/MSAN type: BDCM:0xa48c / v0xa48c
Today: DSLAM/MSAN type: BDCM:0xb12d / v0xb12d
-
My BDCM firmware is still the same as your original, I wonder if the change in modem has triggered a DSLAM firmware upgrade or coincidence?
-
. . . I wonder if the change in modem has triggered a DSLAM firmware upgrade . . .
I seriously doubt it.
. . . or coincidence?
That would be more like it.
Perhaps all members, those connected via Huawei equipped cabinets, should keep a close watch for any such updates on their own circuits.
-
Thanks for highlighting this. Our line went down at just before midnight on 1 October for a similar period of time - and after trying adsl info --vendor on the 8924 just now shows I am also on 0xb12d *
A few days after that I started benefiting from the xdB changes
(*I have set DSLStats to monitor DSLAM firmware version but can't see it in the telnet data its showing this!)
-
*I have set DSLStats to monitor DSLAM firmware version but can't see it in the telnet data its showing this!
Under the Stats tab, at the top. It shows as not monitored if unchecked.
I'm sure the XdB changes starting right after the DSLAM firmware changing was a big coincidence. I'm still on BDCM:0xa48c at the moment.
-
Under the Stats tab, at the top. It shows as not monitored if unchecked.
???
It's checked, I just can't see it in the telnet data ???
-
It's not shown under the telnet data tab. I didn't think it was worth adding another tab there just to show the same information as is recorded on the Stats tab.
-
???
It's checked, I just can't see it in the telnet data ???
adsl info --vendor
-
I impatiently wait for firmware update. For a few years I have BDCM:0xa48d.
-
It's not shown under the telnet data tab. I didn't think it was worth adding another tab there just to show the same information as is recorded on the Stats tab.
Thanks - I knew it was there somewhere as I had seen it before.. just not the other day :-[
-
Similar thread. Somebody has also new DSLAM firmware. DSLAM/MSAN type: BDCM:0xb12d / v0xb12d
https://community.bt.com/t5/BT-Infinity-Speed-Connection/down-speed-is-now-half/td-p/1777532
-
Bit of an old thread but my DSLAM just went down for 15 mins at midnight and the result was....
DSLAM/MSAN type: BDCM:0xb12d / v0xb12d
I've seen DSLAM firmware release notes in the past. Do they ever release this?
-
Still on 48c here.
Stats recorded 16 Mar 2018 02:16:25
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
-
Just to avoid any confusion, it's not 48c, it's a4, 8c. That's a pair of hexadecimal numbers whose decimal equivalents are 164 and 140.
j0hn's new figures are b1, 2d - decimal equivalents 177 and 45.
-
Am I right in thinking that if you are still on a48c you will not get xdB, and for that you need to be on b10d?
Would explain why I’ve never yet been moved to xdB.
-
Am I right in thinking that if you are still on a48c you will not get xdB, and for that you need to be on b10d?
Would explain why I’ve never yet been moved to xdB.
No, DLM profiles are unrelated to DSLAM firmware for the most part.
The exception being DSLAM firmware might need updating for things like G.INP to work. All Huawei cabinet firmwares are capable of G.INP/Vectoring already.
I was on a 3dB snrm target before the DSLAM firmware update(0xa48c), and still am after the update(0xb12d).
-
On my line, DSLstats reports:
DSLAM type / SW version: BDCM:0xa48c (164.140) / v0xa48c
Downstream Upstream
G.INP: Enabled Not enabled
Vectoring status: 1 (VECT_FULL)