From: Rob Barton (robbarto@xxxxxxxxx)
Date: Tue Dec 05 2000 - 10:12:12 GMT-3
You would want to prevent BGP information from bringing up the line by
making the BGP traffic uninteresting. BGP sessions are established with TCP
port 179, so just write a dialer-list to make this kind of traffic
uninteresting.
Cheers, Rob.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Steve Clubb
Sent: Monday, December 04, 2000 4:39 PM
To: ccielab@groupstudy.com
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:59 GMT-3