Another BRAS moan

What is the matter with getting BRAS upped? My rate dropped from
months at 8meg to 130K in nothing flat. Router was 130/160. Rebooted
the router which promptly synced at 448/8096 . BT tests says there are
no faults - but it will take 5 *days* to reset BRAS. :-(

What are they smoking?
--
Regards
Dave Saville

NB Remove nospam. for good email address

On Fri, 5 Jun 2009 11:28:04 UTC, "Ato_Zee" <(E-Mail Removed)>
wrote:

>
> On 5-Jun-2009, "Dave Saville" <(E-Mail Removed)> wrote:
>
> > BT tests says there are
> > no faults - but it will take 5 *days* to reset BRAS.
>
> Probably the time trhey think it will take for the automated
> system to react.
>
> > Rebooted
> > the router which promptly synced at 448/8096
>
> So you should be back to your previous speed.
>

my feelings exactly.

> A noise burst, particularly if it repeats, can knock your
> speed back for several days, or even permanently until
> the source is removed.
> Is your router next to the NTE5?

Yes.

> Some modems support DMT tool, which allows you
> to set your target SNR, which can up your speed
> dramatically, but it doesn't cure faults, and can be
> a mixed blessing.

SNR is OK as it is.

--
Regards
Dave Saville

NB Remove nospam. for good email address

"Dave Saville" <(E-Mail Removed)> wrote in message
news:fV45K0OBJxbE-pn2-Zz0bVqewEYmU@localhost...
> What is the matter with getting BRAS upped? My rate dropped from
> months at 8meg to 130K in nothing flat. Router was 130/160. Rebooted
> the router which promptly synced at 448/8096 . BT tests says there are
> no faults - but it will take 5 *days* to reset BRAS. :-(
>
> What are they smoking?

The system was changed a while back. Big swings in IPProfile should cause
the profile to be update rapidly. It shouldn't be more than a few hours
before its back to what you had before.

Of course what everyone would like to know is why can't the IPProfile be
what you sync at rather than something else. Then we wouldn't have to wait.

--

WildCardZero

On Fri, 5 Jun 2009 12:00:11 UTC, "WCZ" <(E-Mail Removed)>
wrote:

> The system was changed a while back. Big swings in IPProfile should cause
> the profile to be update rapidly. It shouldn't be more than a few hours
> before its back to what you had before.

Well so far still 130K and 15 hours since the resync at 448/8096

<quote BT>
15 - NO BTW FAULT-circuit progressing correctly and BRAS Profile is
due to be changed in 118 Hour 50 Minutes.
</quote BT>
--
Regards
Dave Saville

NB Remove nospam. for good email address

"Dave Saville" <(E-Mail Removed)> wrote in message
news:fV45K0OBJxbE-pn2-C52RfIrionKy@localhost...
> On Fri, 5 Jun 2009 12:00:11 UTC, "WCZ" <(E-Mail Removed)>
> wrote:
>
>> The system was changed a while back. Big swings in IPProfile should
>> cause
>> the profile to be update rapidly. It shouldn't be more than a few hours
>> before its back to what you had before.
>
> Well so far still 130K and 15 hours since the resync at 448/8096
>
> <quote BT>
> 15 - NO BTW FAULT-circuit progressing correctly and BRAS Profile is
> due to be changed in 118 Hour 50 Minutes.
> </quote BT>
> --


Jeez, thats awful. I had a low sync event down to 160 from about 1500 about
6 months ago. So a much smaller swing than you've had and it was back to
normal within 12 hours.

BT profile system really is rubbish. Hope it sorts itself out soon for you.

--

WildCardZero

"WCZ" <(E-Mail Removed)> wrote in message
news:h0b3ja$1507$(E-Mail Removed)...
> "Dave Saville" <(E-Mail Removed)> wrote in message
> news:fV45K0OBJxbE-pn2-C52RfIrionKy@localhost...
>> On Fri, 5 Jun 2009 12:00:11 UTC, "WCZ" <(E-Mail Removed)>
>> wrote:
>>
>>> The system was changed a while back. Big swings in IPProfile should
>>> cause
>>> the profile to be update rapidly. It shouldn't be more than a few hours
>>> before its back to what you had before.
>>
>> Well so far still 130K and 15 hours since the resync at 448/8096
>>
>> <quote BT>
>> 15 - NO BTW FAULT-circuit progressing correctly and BRAS Profile is
>> due to be changed in 118 Hour 50 Minutes.
>> </quote BT>
>> --
>
>
> Jeez, thats awful. I had a low sync event down to 160 from about 1500
> about 6 months ago. So a much smaller swing than you've had and it was
> back to normal within 12 hours.
>
> BT profile system really is rubbish. Hope it sorts itself out soon for
> you.
>


Replying to myself, I know. This is what should happen according to
ThinkBroadband

"As of August 2007 a more flexible system has been implemented where large
improvements in the IP Profile may take place with 75 minutes, for example a
jump from 135Kbps up to 7.15Mbps should happen quickly, whereas a small
increment from 3.5Mbps to 4Mbps may take the full 5 days the current system
allows."

http://www.thinkbroadband.com/faq/se...radsl.html#228

--

WildCardZero

Ted wrote:
> On Fri, 5 Jun 2009 13:00:11 +0100 WCZ <(E-Mail Removed)> wrote:
>
>> ....
>>
>> Of course what everyone would like to know is why can't the IPProfile
>> be what you sync at rather than something else. Then we wouldn't
>> have to wait.
>
> I can understand why the IP Profile is always lower than the sync speed, but just
> why must it take "up to x days" to respond to an increase in sync speed, when it
> reacts almost immediately to a drop in sync speed.
>
> I could never see the logic in that.
>

I am not sure it DOES respond instantly to a drop.

The rationale is that the one thing they DO not want, is packets
arriving at an (almost) bufferless DSLAM faster than they are being
downloaded.

>
> I am not sure it DOES respond instantly to a drop.
>

Its ranged from almost instant to several hours for me. I think it depends
on how big the sync swing is.

> The rationale is that the one thing they DO not want, is packets arriving
> at an (almost) bufferless DSLAM faster than they are being downloaded.

True but why can't my IPProfile be (sync speed - overheads) and it gets set
everytime the router syncs with the exchange? BE seem to manage to do
something like that.

--

WildCardZero

Ted wrote:
> On Fri, 5 Jun 2009 13:00:11 +0100 WCZ <(E-Mail Removed)>
> wrote:
>
>> ....
>>
>> Of course what everyone would like to know is why can't the IPProfile
>> be what you sync at rather than something else. Then we wouldn't
>> have to wait.
>
> I can understand why the IP Profile is always lower than the sync
> speed, but just why must it take "up to x days" to respond to an
> increase in sync speed, when it reacts almost immediately to a drop
> in sync speed.
>
> I could never see the logic in that.

You won't get a good answer to that one Ted, I asked the same thing over a
year ago and not got an adequate reply yet. However things have improved a
little since now, as someone mentioned earlier, large drops of IPProfile
usually get upped more qyuickly these days. Last Friday my IPProfile was
dropped to 4500 kbps after an outage droped my synch rate from 7616 kbps to
4992 kbps. The profile was restored to 6500 kbps sometime overnight
Saturday/Sunday, whereas in the past it's usually taken around 3 days.
--
Heard melodies are sweet, but those Unheard are sweeter
(E-Mail Removed) FN 2°°9 +, Mungo Brandybuck of Buckland

WCZ wrote:

> Of course what everyone would like to know is why can't the IPProfile be
> what you sync at rather than something else.

Because the IP throughput is always going to be ~13% less than the sync
speed due to the overheads of the Matryoshka-doll style ADSL + ATM + PPP +
IP stack

> Then we wouldn't have to wait.

Some kind of interface for expert users would be nice. Be offer this. I
selected speed over stability, but haven't seen any loss of stability.

--
<http://ale.cx/> (AIM:troffasky) ((E-Mail Removed))
18:52:50 up 29 days, 23:08, 1 user, load average: 0.10, 0.14, 0.10
A few flakes working together can unleash an avalanche of destruction