From: Mike Flannagan (mflannag@cisco.com)
Date: Sun Jan 02 2005 - 01:29:18 GMT-3
Your question was "for lab purposes" -- so I'll answer in that context:
The lab instructions will make it clear if you're NOT supposed to do
something in a specific way (such as, peering with loopbacks). Otherwise,
you're free to accomplish the designated task in any way that meets the
requirements.
As a follow-up thought: If you know a given method is a "best practice," and
you're allowed to use that method...why wouldn't you?
Mike
#7651
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Rick
Sent: Saturday, January 01, 2005 11:16 PM
To: Cisco certification
Subject: next hop self
I have a question regarding next hop self. When you have a bgp peering
session using loopbacks and updatesource lo0 the next hop of the advertised
routes have the loopback address instead of the interface address. Here is a
where my questions comes from
This example is using interface addresses for all bgp peering and R3 is a
route reflector to R2 and R4:
R1---ebgp----R2----ospf & ibgp-----R3-----ospf & ibgp------R4
The link between R1 and R2 is not advertised in BGP so when R3 receives the
routes it will not install as it can't resolve the next hop. to solve this
problem you just use next-hop-self on R2 to R3 and then R3 will install the
routes and advertise them on to R4
This example is using loopbacks for all ibgp peering and interface addresses
for ebgp(R1-R2) and R3 is a route reflector to R2 and R4:
R1---ebgp----R2----ospf & ibgp-----R3-----ospf & ibgp------R4
The link between R1 and R2 is not advertised in BGP, however R3 gets the
routes with R2's loopback as the next-hop. Now since R3 knows how to get to
the loopback it will install the route and advertise the learned routes on
to R4.
So my questions are should we still use next-hop-self with the second
example even though it isn't needed? For lab purposes is there a reason to
not peer with loopbacks unless of course you are instructed not to?
Rick
This archive was generated by hypermail 2.1.4 : Wed Feb 02 2005 - 22:10:18 GMT-3