From: Cameron, John (johcamer@cisco.com)
Date: Fri May 09 2003 - 08:51:38 GMT-3
Based on the comments made in the Config guide that should not happen and
R1 should only initiate a call:
*****In this case, the secondary line will not be activated when the primary
goes down. The secondary line will be activated when the load on the primary
line is greater than 75 percent of the bandwidth of the primary line*****
Maybe you can share your configurations and that may help us spot the issue.
JDC
-----Original Message-----
From: Seonghui [mailto:Seonghui@vads.com]
Sent: Friday, May 09, 2003 2:50 AM
To: Cameron, John
Cc: ccielab@groupstudy.com
Subject: RE: Bandwidth on Demand issue
Hi Cameron,
Thanks. But the problem that I am facing now is primary link backup should
be originated from R2 while bandwidth on demand (BOD) should be originated
from R1. Both routers will use the same PRI line and E1 interface to
accomplish both BOD and dialbackup.
LAN---R1 -----point to point serial--------R2-------------ISP
\ /
\ /
-----ISDN PRI------------------
If I use different dialer profiles for BOD (originate from R1) and
dialbackup (originate from R2), how should the configuration be? One problem
that I am experiencing is when ptp serial is down, both R1 and R2 will start
dialing due to 'backup interface dialer 1' command. How can I stop R1 from
initiating ISDN call when serial is detected down? R1 is suppose to initiate
call if and only utilization touches 75% (backup load 75 5).
Can anyone help?
Thanks and regards,
Mark
-----Original Message-----
From: Cameron, John [mailto:johcamer@cisco.com]
Sent: Friday, May 09, 2003 12:09 PM
To: 'Seonghui'; ccielab@groupstudy.com
Subject: RE: Bandwidth on Demand issue
Dial Backup Service When the Primary Line Reaches Threshold Example:
The following example configures the secondary line (serial 1) to be
activated
only when the load of the primary line reaches a certain threshold:
interface serial 0
backup interface serial 1
backup load 75 5
*****In this case, the secondary line will not be activated when the primary
goes down. The secondary line will be activated when the load on the primary
line is greater than 75 percent of the bandwidth of the primary line. The
secondary line will then be brought down when the aggregate load between the
primary and secondary lines fits within 5 percent of the primary bandwidth.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fdia
l_c/fnsprt6/dcdbaks.htm
HTH
JDC
-----Original Message-----
From: Seonghui [mailto:Seonghui@vads.com]
Sent: Thursday, May 08, 2003 6:52 AM
To: ccielab@groupstudy.com
Subject: Bandwidth on Demand issue
Hi,
My scenerio is as below:
LAN--- R1 -----point to point serial--------R2-------------ISP
\ /
\ /
------ISDN PRI---------------------
1. Serial will be the primary link
2. When serial link goes down, R2 will originate ISDN call
3. When Serial link utilization reaches 70%, R1 originate ISDN call for
Bandwidth on Demand (BOD)
Task no. 2 can be done easily. But for task 2 and 3 to work together, can
someone give me some clues how to go about it? The problem that I am facing
is that task 2 and task 3 are originated from 2 different routers. If I
configure 'backup load 70 30' on R1 serial interface for BOD, when serial
link goes down, R1 will also generate ISDN call to R2 which conflict with
task 2...meaning R1 and R2 also generating ISDN call for backup. R1 is
suppose to call only when serial int reaches 70%, not when serial link is
down. R2 is only suppose to kick in when serial link is down.
Please assist.
Thanks and regards,
Mark
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:39 GMT-3