From: Daniel Cisco Group Study (danielcgs@imc.net.au)
Date: Sun Jun 08 2003 - 03:36:18 GMT-3
This whole issue is very unclear in my mind. The docos say the following:
"When the cumulative load of all UP links (a number n) exceeds the load threshold the dialer adds an extra link and when the cumulative load of all UP links minus one (n - 1) is at or below load threshold then the dialer can bring down that one link. The dialer will make additional calls or drop links as necessary but will never interrupt an existing call to another destination"
I would like to work on a couple of examples with those who are interested.
(1) Say I use the following:
int bri 0
ppp multilink
dialer load-threshold 64 either
I think that we would all agree that the 2nd B channel comes up when the load in either direction on the active (1st) B channel reaches 16kbps. (64k x [64/255]).
Now, when does it come back down ???? The doco tries to explain it, but its all very muddy in my mind.... I don't know what its trying to say.
(2) Let's take this one step further.
We have an E1 PRI service (30 channels + 1D) - placing calls to the same destination:
int s0/0:15
ppp multilink
dialer load-threshold 64 either
We would agree that if we already have 5 B channels up, the 6th one comes up when the combined bandwidth of all 5 B channels is 80k (5 x 64 x [64/255]). Correct ?????
Now we have 6 B channels for a combined total available bandwidth of 384k. When does one of the B channels drop?
Daniel
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:54 GMT-3