Chrisy Luke wrote: | Paul G. Donner wrote (on Oct 13): | > If BGP rides on TCP, how are the TCP sessions built if BGP itself is used | > as the IGP? | | Same way as it does when you take next-hops from any other IGP. The fact | that one already has a route to ones' directly attached networks. In other words, the interior routing protocol is either static or a combination of statically configured routes and the likes of ARP/ES-IS/other neighbour discovery protocols. The key point is that, in a router talking iBGP, the route to the NEXT_HOP received by an iBGP neighbour *MUST* be known through means other than BGP. This is not to say that the route need be dynamic -- a static default route would do just fine. Sean.
Sean M. Doran wrote (on Oct 14):
The key point is that, in a router talking iBGP, the route to the NEXT_HOP received by an iBGP neighbour *MUST* be known through means other than BGP. This is not to say that the route need be dynamic -- a static default route would do just fine.
Not necessarily. You just get a more pronounced stepping effect when you learn routes whose next-hops are in the same protocol. I don't recommend it in a large network though. It gets very messy. Chris. -- == chris@easynet.net, chrisy@flix.net, chrisy@flirble.org == Systems Manager for Easynet, part of Easynet Group PLC.
At 11:04 1998-10-14 , Chrisy Luke wrote:
Sean M. Doran wrote (on Oct 14):
The key point is that, in a router talking iBGP, the route to the NEXT_HOP received by an iBGP neighbour *MUST* be known through means other than BGP. This is not to say that the route need be dynamic -- a static default route would do just fine.
Not necessarily. You just get a more pronounced stepping effect when you learn routes whose next-hops are in the same protocol.
Either you have to configure next-hop-self or use static or use other IGP, otherwise you'll end up with flapping routes in your network. BGP cannot use a route for next-hop-self address derived by itself, as far as I know. /Hakan
Hakan Hansson wrote (on Oct 14):
Either you have to configure next-hop-self or use static or use other IGP, otherwise you'll end up with flapping routes in your network. BGP cannot use a route for next-hop-self address derived by itself, as far as I know.
Well it does and can. But then I suppose it depends on the arbitrary restrictions certain vendors place on you. Chris. -- == chris@easynet.net, chrisy@flix.net, chrisy@flirble.org == Systems Manager for Easynet, part of Easynet Group PLC.
Hakan Hansson wrote (on Oct 14):
Either you have to configure next-hop-self or use static or use other IGP, otherwise you'll end up with flapping routes in your network. BGP cannot use a route for next-hop-self address derived by itself, as far as I know.
Well it does and can. But then I suppose it depends on the arbitrary restrictions certain vendors place on you.
GateD can with group type internal, IOS can't. GateD with group type routing requires an IGP running. In this instance you aren't running BGP as your IGP you are running ARP and static routes as an IGP. Regards, Neil. -- Neil J. McRae. Alive and Kicking. Domino: In the glow of the night. neil@DOMINO.ORG NetBSD/sparc: 100% SpF (Solaris protection Factor) Free the daemon in your <A HREF="http://www.NetBSD.ORG/">computer!</A>
participants (4)
-
Chrisy Luke -
Hakan Hansson -
Neil J. McRae -
Sean M. Doran