From: Cameron, John (johcamer@cisco.com)
Date: Fri May 09 2003 - 01:09:03 GMT-3
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