«

Hi

I hava a question about BGP next-hop-self.
There is a topology below.

R1------------R2--------------R3
(AS100) (AS100) (AS200)
30.1.1.1 30.2.2.2 30.3.3.3

R1 and R2 have AS100 ,
R3 has AS200.
R1,R2 and R3 interfaces are set in OSPF.
30.1.1.1 30.2.2.2 30.3.3.3 are not in OSPF,
but those are advertised from R3 in BGP.

R1 can see 30.1.1.1 30.2.2.2 30.3.3.3 in BGP
but R1 cannot ping those.

next,
"neighbor R1 next-hop-self" is set on R2,
R1 can ping those.

I think that next-hop-self is no need since R1 can see those routes.

Please anyone can say the advise if i mistake something about it.

Thanks.

"COM3" <> wrote in message
news:05fc49cd-ac8e-4a4b-a60e-...
> Hi
>
> I hava a question about BGP next-hop-self.
> There is a topology below.
>
> R1------------R2--------------R3
> (AS100) (AS100) (AS200)
> 30.1.1.1 30.2.2.2 30.3.3.3
>
> R1 and R2 have AS100 ,
> R3 has AS200.
> R1,R2 and R3 interfaces are set in OSPF.
> 30.1.1.1 30.2.2.2 30.3.3.3 are not in OSPF,
> but those are advertised from R3 in BGP.
>
> R1 can see 30.1.1.1 30.2.2.2 30.3.3.3 in BGP
> but R1 cannot ping those.
>
> next,
> "neighbor R1 next-hop-self" is set on R2,
> R1 can ping those.
>
> I think that next-hop-self is no need since R1 can see those routes.
>
> Please anyone can say the advise if i mistake something about it.
>
> Thanks.



1) R1 needs a valid route to the next-hop-address,
and
2) because 30.1.1.1, 30.2.2.2, and 30.3.3.3
are not in R1's OSPF, R1 requires the command "no synch" under bgp.