From: shiran guez (shiranp3@gmail.com)
Date: Wed Oct 31 2007 - 10:03:09 ART
the next-hop-self is not for peering, the next-hop-self is for making sure
that your peers have reachability to the prefix you advertise when you do
not have IGP or Static route to the next hop.
if for example
______
/ R2
BB2 --- > R5 |
\______R1
R5 R1 R2 (AS100) have a full mash peer and R5 is peering with BB2 (EBGP
Neighbor)
R5 R1 and R2 have IGP OSPF between them and R5 is not advertising the link
to BB2 over the IGP and also do not have a static route to BB2 then when R5
receive prefix from BB2 over BGP he will send them to R1 and R2 but because
R1 and R2 will see the next hop as the IP of BB2 and they do not have a
route to it, then they will not consider that as best route and will not put
it into the Routing Table. to fix it you can advertise the link between R5
and BB2 or put a next-hop-self and the next-hop-self will advertise to R1
and R2 the next hop as R5 IP address and then R1 and R2 will be able to
consider the routes as best and inject them to the routing table.
On 10/31/07, Jonny English <redkidneybeans@gmail.com> wrote:
>
> Hi,
>
> can someone please help me out here.
>
> In task 4.1 in the IEWBv4 lab 5 we have to set up a peering between Sw3
> and
> SW4.
>
> Why do we need the neighbor 162.1.109.10 next-hop-self, and
> 162.1.109.9next-hop-self commands?
>
> I got a peering without this extra line of configuration and the switches
> are directly connected.
>
> Thanks,
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Shiran Guez MCSE CCNP NCE1 http://cciep3.blogspot.com http://www.linkedin.com/in/cciep3
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:19 ART