Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) Dynamic Bandwidth Allocation on Pipeline 75

It's not you, Jerry.  I'm having the same trouble!

I've been emailing Ascend Support for a while with no resolution.  I
understand Ethernet->ConnectionProfile->Encaps->DBAMonitor=
Transmit-Recv to mean that my P75 controls the addition of the second
channel during both transmit AND receive.  

The real rub is that this feature used to work prior to me loading 5.1A
and now it is broken. I'm really interested in some kind of
acknowledgement that this is a defect, and that Ascend intends to fix
it.  I thought I had the acknowledgement a while back when Ascend
Support told me they'd opened a problem log, but now they're singing a
different tune.

Here is a snippet from the email I got from Ascend Suuport back on 10/8.
> >>>I have done some testing with the Dynamic Bandwidth Allocation on 5.1A.
> Based on this testing, I have opened a TR (bug report)  with Engineering.
> We will contact you when this TR is fixed.  Basically, the Pipeline is not
> now controlling the adding of channels.  If the MAX is changed to match
> your desired settings, the 2nd channel will be added based on what the MAX
> sees for ALU.  This would be the workaround until this TR is fixed.  You
> can call/mail on the ticket number above to check on the status of this TR.

I won't rule out that my ISP changed their MAX configuration at the same
time I loaded 5.1A, but that seems like a big coincidence.  

At a minimum, it would be nice to see a detailed explanation of how DBA
works under the conditions you described below, and under what
conditions the Pipe uses the MAX DBA parameters instead of its own
settings, especially in the case where DBAMonitor= Transmit-Recv.

Jerry Gardner wrote:
> 
> Has anyone successfully gotten DBA to work on a Pipeline 75?
> 
> I have the latest firmware (5.1A) and DBA works fine when I'm transmitting
> data, but not when I'm receiving data.
> 
> If I read the Ascend manual correctly, the Pipeline should add a second B
> channel when the average utilization stays above the value set in the
> "Util" parameter for "Add pers" seconds. I have "Util" set to 80% and "Add
> pers" set to 90 seconds. The Pipeline always adds the second B channel as
> soon as the utilization reaches 80%; it does not wait 90 seconds as
> specified by "Add pers".
> 
> Strangely, DBA works fine when I'm sending data. The second B channel is
> added when the utilization is above 80% for 90 seconds. I'm using the
> quadratic algorithm and have it set to average over 15 seconds. It's set to
> monitor DBA on both transmit and receive. The Answer parameters related to
> DBA are set to the same values as in my connection profile.
> 
> Ascend tech support claims that the parameters of the ISDN router on the
> other end of the connection must be set to the same values as my Pipeline.
> Trouble is, I'm dialing into an ISP and they don't want to (rightly!)
> modify their router parameters because it might affect their other users.
> 
> Is DBA broken in v5.1A, or is it something I'm (or my ISP is) doing wrong?
> My ISP is dnai.com, in case any of you are in Northern California and have
> experience with their ISDN service. They claim to be using Ascend MAX 4000
> and 4048 routers.
> 
> --
> Jerry Gardner               | Periphonics Corporation
> Senior Project Manager      | email: jgardner@peri.com
> 
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:   <http://www.nealis.net/ascend/faq>


-- 
Mark Hilbush

Everything should be made as simple as possible, but not simpler.
        -- Albert Einstein
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>
Follow-Ups: References: