Further to my own email, this link may be of use - it discusses the difference between backup interfaces, floating static routes, and dialer watch...
http://www.cisco.com/warp/public/123/backup-main.html JMcL ----- Forwarded by Jenny Mcleod/NSO/CSDA on 26/11/2001 04:53 pm ----- "jenny.mcleod@centreli nk.gov.au" To: [EMAIL PROTECTED] <jenny.mcleod cc: Sent by: Subject: problem in router config ? [7:27288] [EMAIL PROTECTED] 26/11/2001 04:01 pm Please respond to "jenny.mcleod@centreli nk.gov.au" I haven't played with it much personally, but I believe using the 'backup interface' command on frame relay interfaces can be problematical, because it is quite possible for the PVC to be down but the interface itself (i.e. the local connection to the frame relay 'cloud') to be up and working. When you say 'the ISDN will not activate', I assume you mean it doesn't even attempt to dial - if it tries to dial but fails to bring up the ISDN link properly, you have a different problem. But if it's not even attempting to dial (debug dialer can be a useful command here), it's probably because your frame relay interface isn't recognised as down. To get around this, you can use floating static routes instead - create a static route for the routes at the remote side, and give it a higher administrative distance than the IGRP route. Point the static route at the dialer interface. That way, if the PVC drops out (even if the local cloud is still visible), the route known by IGRP disappears, and the static route (pointing to the dialer interface) kicks in, directing traffic over the ISDN. This is a very flexible way of configuring backup connections - you can also use it to configure a backup ISDN interface on a separate router to your frame relay interface. However I am not aware of any way of getting the equivalent functionality of the 'backup delay' command, because all the work is done through the routing protocol. If anyone has any thoughts on this I'd be interested to hear them. Hope that helps... JMcL ----- Forwarded by Jenny Mcleod/NSO/CSDA on 26/11/2001 03:52 pm ----- "Anthony Toh" cc: Sent by: Subject: problem in router config ? [7:27288] nobody@groups tudy.com 26/11/2001 01:52 pm Please respond to "Anthony Toh" Hi,I am trying to configure two 2600 series routers to run in a Frame Relay network with an ISDN dial line as backup operation. The Frame Relay configuration is working alright but the ISDN is not. With reference to the figure below : R1---S1----Frame Relay----S0---R2 \---Bri0-----ISDN------Bri0---/ The problem is with reference to R2 being the sender : - if serial link of both routers are brought down, the ISDN will activate. - if only 1 serial link of either router is brought down, the ISDN will not activate. The same case happen with R1 being the sender. I am struck with this for weeks, really appreciate very much if you can help to chk my router config. My configurations of both routers are as below : R1 configuration : ! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname R1 ! username R2 password 0 cisco ! no ip domain-lookup ! isdn switch-type basic-ni ! interface FastEthernet0/0 ip address 172.16.32.1 255.255.240.0 ! interface Serial0/1 backup delay 10 40 backup interface Dialer1 ip address 172.16.96.1 255.255.240.0 encapsulation frame-relay cdp enable frame-relay map ip 172.16.96.1 17 ! interface BRI0/0 no ip address no ip directed-broadcast encapsulation ppp dialer pool-member 5 isdn switch-type basic-ni isdn spid1 51055512340001 5551234 isdn spid2 51055512350001 5551235 ! interface Dialer1 ip address 172.16.16.1 255.255.240.0 no ip directed-broadcast encapsulation ppp dialer remote-name R1 dialer idle-timeout 300 dialer string 5554000 dialer string 5554001 dialer load-threshold 128 either dialer pool 5 dialer-group 1 ppp authentication chap ppp multilink ! router igrp 100 passive-interface Dialer1 network 172.16.0.0 ! ip classless ip route 0.0.0.0 0.0.0.0 172.16.96.2 ip route 0.0.0.0 0.0.0.0 172.16.16.2 200 no ip http server ! dialer-list 1 protocol ip permit ! line con 0 transport input none line aux 0 line vty 0 4 password project login ! end R2 configuration: ! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname R2 ! username R1 password 0 cisco ! no ip domain-lookup ! isdn switch-type basic-ni ! process-max-time 200 ! interface FastEthernet0/0 ip address 172.16.48.1 255.255.240.0 no ip directed-broadcast ! interface BRI0/0 no ip address no ip directed-broadcast encapsulation ppp dialer pool-member 1 isdn switch-type basic-ni isdn spid1 51055540000001 5554000 isdn spid2 51055540010001 5554001 ! interface Serial0/0 backup delay 10 40 backup interface Dialer1 ip address 172.16.96.2 255.255.240.0 no ip directed-broadcast encapsulation frame-relay frame-relay map ip 172.16.96.2 16 ! interface Dialer1 ip address 172.16.16.2 255.255.240.0 no ip directed-broadcast encapsulation ppp dialer remote-name R2 dialer idle-timeout 300 dialer string 5551234 dialer string 5551235 dialer load-threshold 128 either dialer pool 1 dialer-group 1 ppp authentication chap ppp multilink ! router igrp 100 passive-interface Dialer1 network 172.16.0.0 ! ip classless ip route 172.16.32.0 255.255.240.0 172.16.96.1 ip route 172.16.32.0 255.255.240.0 172.16.16.1 200 no ip http server ! dialer-list 1 protocol ip permit ! line con 0 transport input none line aux 0 line vty 0 4 password project login ! end Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=27298&t=27288 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
