I can't remember but... this also helps

dialer pool-member number [priority priority] [min-link minimum] [max 
link maximum] - Assigns a physical interface to a dialer pool.
priority priority - Sets the priority of the physical interface within 
the dialer pool (from 1 to 255). Interfaces with the highest priorities 
are selected first when dialing out.
min-link minimum - Sets the minimum number of ISDN B channels on an 
interface reserved for this dialer pool (from 1 to 255). Used for dialer 
backup.
max-link maximum - Sets the maximum number of ISDN B channels on an 
interface reserved for this dialer pool (from 1 to 255).


John Neiberger wrote:

>Thanks.  I knew there was a way to set the dialer priority but I just
>wasn't sure how it operated.  I have yet to find a reference on CCO that
>specifies what the priority really accomplishes.  If a dialer with a
>high priority needs to use a line but the line is being used by a dialer
>with a lower priority, does it simply disconnect the existing call and
>take over?
>
>Or, does it make use of the fast idle timer to be a little more fair? 
>I'm still looking on CCO at the moment.  Hopefully, I'll find a link
>that makes this more clear.
>
>Thanks again,
>John
>
>>>>Tshon  2/22/02 3:07:43 PM >>>
>>>>
>Yes this is possible exactly as you discribed.  Hope fully in this 
>scenario you have more than one bri.  But, say you don't
>you have two B channels unless the load exceeds one of the B channels 
>you have no problem.... I believe the last question
>is "is there a priority or preempt command?"  Make a dialer interface 
>and see : - )
>
>John Neiberger wrote:
>
>>I was just talking to a guy I work with about this and I thought it
>>
>was
>
>>an interesting scenario.  It was his idea and my first thought was
>>
>that
>
>>it wasn't possible, but then after a little more pondering I decided
>>that it might be possible.  Note:  'possible' does not mean desirable.
>>
>
>>:-)    Here's the scoop:
>>
>>
>>
>>[A]-----------------[B]
>> |  \        
>> |    \
>> |      \
>> |        \
>> |          \
>> |            \
>> |              \
>>[C] ----------- [D]
>>
>>Site A is connected to B, a disaster recovery facility, via frame
>>relay.  A also has point-to-point connections to sites C and D.   C
>>
>and
>
>>D are connected via frame relay but obviously only use the frame
>>
>relay
>
>>link to reach A if their own primary link goes down.
>>
>>C and D have ISDN connections configured to dial B in case both links
>>to A go away (Dialer Watch).  Now for the twist....  What if you
>>
>wanted
>
>>to configure C to dial D when the load on its primary link reached a
>>certain point, yet still dial B if both point-to-point links went
>>
>down?
>
>>I haven't completely figured out how to do this yet, but here's a
>>start.  You might configure two Dialer profiles, one for each
>>destination.  On the major interface on C you'd configure Dialer0 as
>>your backup interface and configure an appropriate load.  When the
>>
>line
>
>>utilization reaches that load, the router would dial Site D.
>>
>>Then you might configure Dialer Watch on Dialer1 and make it dialer
>>Site B if routes originating from Site A disappear.  The difficulty
>>
>is
>
>>that the Dialer interface that calls Site B would have to have
>>
>absolute
>
>>priority.  If the primary link goes down, because Dialer0 is
>>
>configured
>
>>as a backup it might grab the BRI first.  Even if it does get there
>>first, when Dialer Watch kicks in, we'd have to have a way to clear
>>
>the
>
>>line immediately so Dialer1 could dial out.
>>
>>Is that possible?  Admittedly, I'm a bit weak on DDR of this variety,
>>but this sounded like an interesting brain teaser.
>>
>>Regards,
>>John




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=36283&t=36283
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to