From: Raj Bahad (raj.bahad@xxxxxxxxxxxxxx)
Date: Tue Aug 27 2002 - 06:37:43 GMT-3
Hi Group,
When presented with scenarios of either using floating static routes or dialer
watch or ospf demand circuits to backup primary links, I have come across many
various scenarios from books and cco where in some cases the IP address
associated with the ISDN interface (physical or logical) is included under the
routing protocol process. For example:
Interface serial 0
ip address 192.168.10.1 255.255.255.0
!
Interface BRI0
ip address 192.168.20.1 255.255.255.252
dialer-map ip 192.168.20.2 broadcast 12345 - used for standard ISDN cal
l.
dialer-map ip x.x.x.x broadcast 12345 - used for dialer watch
dialer-group 1
dialer-watch group 1
!
router eigrp 10
network 192.168.10.0
network 192.168.20.0
no auto-summary
!
access-list 101 deny eigrp any any
access-list 101 permit ip any any
dialer-list 1 protocol ip list 101
dialer-watch list 1 x.x.x.x x.x.x.x
Whereas in other scenarios it is not:
Interface serial 0
ip address 192.168.10.1 255.255.255.0
!
Interface BRI0
ip address 192.168.20.1 255.255.255.252
dialer-group 1
!
router eigrp 10
network 192.168.10.0
no auto-summary
!
access-list 101 permit ip any any
dialer-list 1 protocol ip list 101
ip route 0.0.0.0 0.0.0.0 192.168.20.2 200
Essentially, what i need clarifying is as follows:
If I have not configured the ISDN interface to belong to any routing process
and have either floating static/ip ospf demand circuit/dialer watch configured
to backup the primary link (i.e. frame-relay). If i wish to have the ISDN
backup operate properly (so that other routers within the same domain know of
this alternative route) without actually including the interface under the
routing process:
1. Should I redistribute the ISDN interface (using redistribute connected with
a restrictive access-list permitting only the ISDN interface)?
2. Redistribute the floating static route (if configured) so that other
routers are aware of this alternative path
3. Include the interface in the routing process, but make it passive and/or
define it as un-interesting traffic so that the ISDN link will not keep on
coming up.
I am confused when to include this interface and when not to !
Any clarification will be greatly appreciated.
Thanks in advance,
Raj.
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:48:39 GMT-3