Re: VPNv4 next-hop-self

In VPNv4 routes u need a label for the next-hop..... in case of ebgp
the next-hop does not change wen passing the route to IBGP.....u dont
have a label for the next-hop for the neighboring AS.....so one
solution is to use the next-hop self command .....

On Mon, Jun 29, 2009 at 3:02 PM, NN Kumar<nagendra.cisco_at_gmail.com> wrote:
> Hi,
>
> One good reason, I can remember is Inter-AS VPN option B-2a.
>
> CE1-----PE1---------ASBR1------------ASBR2------------PE2-------------CE2
> |-------As100----| |-------As200------|
>
> With Option B, you will advertise VPNv4 prefixes to eBGP neighbor which will
> be the ASBR of neighboring AS. As next-hop attribute will not be changed
> when the update is sent to iBGP, you either:
>
> 1. have to set "next-hop-self" in ASBR (Option B-2a) or
> 2. You can redistribute the host route (/32 route entry) for directly
> connected ASBR which will be created automatically and installed in your
> routing table. (Option B-2b)
>
> Regards,
> Nagendra
>
>
>
> On Mon, Jun 29, 2009 at 4:40 PM, Splinter <splinter330_at_gmail.com> wrote:
>
>> Hi All,
>>
>> please can anyone help me understand when to use the next-hop-self under
>> the
>> vpnv4 process and why this is needed.
>> any good examples are welcome to get a better understanding.
>>
>> thank you
>>
>> Splinter
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Mon Jun 29 2009 - 17:01:12 ART