Fw: BGP on demand

From: Wu, Jiang (wujiang@xxxxxxxxx)
Date: Tue Dec 05 2000 - 03:58:03 GMT-3


   
> I think you can change keepalive and holddown timers between the two peers to
 a longer time using "nei ... timers".
>
> HTH,
> Wu
>
> ----- Original Message -----
> From: Steve Clubb <sclubb@cattech.com>
> To: <ccielab@groupstudy.com>
> Sent: Tuesday, December 05, 2000 8:39 AM
> Subject: BGP on demand
>
>
> > I have a ibgp router (route-reflector 'client') that has a primary
> > connection on it's ethernet interface, but also has an isdn link for
> > back-up. If the ethernet link goes down and the bri interface comes up on
> > demand, is there a way to stop the ibgp router from keeping up the back-up
> > link without loosing it's tcp connection with it's peer?
> >
> > r1 and r2 configs relevant to this question:
> >
> > r1
> > interface loopback0
> > ip add 131.10.100.1 255.255.255.0
> > !
> > router bgp 2
> > neighbor 131.10.130.2 remote-as 2
> > neighbor 131.10.130.2 update-source Loopback0
> > neighbor 131.10.130.2 route-reflector-client
> > !
> >
> > r2
> > !
> > interface Loopback0
> > ip address 131.10.130.2 255.255.255.0
> > !
> > interface BRI0
> > ip address 131.10.132.2 255.255.255.0
> > ip ospf demand-circuit
> > isdn spid1 40888830000101
> > isdn spid2 40888830000102
> > dialer map ip 131.10.132.3 name r3 broadcast 8887000
> > dialer-group 1
> > !
> > router bgp 2
> > neighbor 131.10.100.1 remote-as 2
> > neighbor 131.10.100.1 update-source Loopback0
> >
> > ****after the e0 is shut, the link comes up constantly****
> > debug di pack
> >
> > BRI0: sending broadcast to ip 137.20.132.5 -- failed, not connected
> >



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:58 GMT-3