[c-nsp] next-hop-self under address-family vpnv4 also?

[Waris Sagheer (waris)]

BGP PIC Edge would be recommended but if it is not supported, use different RDs even for the same VPN. This would allow second best path to be installed for the same prefix.


Best Regards,

[http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg]

Waris Sagheer
Technical Marketing Manager
Service Provider Access Group (SPAG)
waris at cisco.com<mailto:waris at cisco.com>
Phone: +1 408 853 6682
Mobile: +1 408 835 1389

CCIE - 19901


<http://www.cisco.com/>



This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

For corporate legal information go to:http://www.cisco.com/web/about/doing_business/legal/cri/index.html




From: CiscoNSP List <cisconsp_list at hotmail.com<mailto:cisconsp_list at hotmail.com>>
Date: Friday, September 19, 2014 at 3:23 PM
To: adam vitkovsky <adam.vitkovsky at swan.sk<mailto:adam.vitkovsky at swan.sk>>, Will Tardy <will.tardy at vocus.com.au<mailto:will.tardy at vocus.com.au>>, "cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>" <cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>>
Subject: Re: [c-nsp] next-hop-self under address-family vpnv4 also?

Thanks very much Adam.

From: adam.vitkovsky at swan.sk<mailto:adam.vitkovsky at swan.sk>
To: cisconsp_list at hotmail.com<mailto:cisconsp_list at hotmail.com>; will.tardy at vocus.com.au<mailto:will.tardy at vocus.com.au>; cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
Subject: RE: [c-nsp] next-hop-self under address-family vpnv4 also?
Date: Fri, 19 Sep 2014 07:50:04 +0000
Next-hop-self is enabled automatically under vpnvX AF.
If the code supports it I'd recommend:
address-family vpnv4
   bgp advertise-best-external  <-- enables best-external + pic(if supported).
   no bgp recursion host <--disables recursive lookup for BGP NHs.
   bgp nexthop route-map BGP_NHT <--specifies which prefixes qualify as BGP NHs.
   bgp nexthop trigger delay 0 <--allows BGP to act on IGP events immediately(enable if FRR backup is available for the BGP NH).
route-map BGP_NHT permit 10
  match ip address prefix-list PE_LOOPBACKS
  match source-protocol "igp" <--if you are using hierarchical MPLS you need to add BGP there as well.
route-map BGP_NHT permit 20
  match source-protocol connected
adam
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> CiscoNSP List
> Sent: Friday, September 19, 2014 3:32 AM
> To: Will Tardy; cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> Subject: Re: [c-nsp] next-hop-self under address-family vpnv4 also?
>
> Cheers.
>
> Any other "tweaks" to default config you recommend?  i.e. timers etc?
>
>
> > From: will.tardy at vocus.com.au<mailto:will.tardy at vocus.com.au>
> > To: cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> > Date: Fri, 19 Sep 2014 00:42:23 +0000
> > Subject: Re: [c-nsp] next-hop-self under address-family vpnv4 also?
> >
> > It¹s not needed.
> >
> >
> > "address-family vpnv4" section is used to define which routers
> > participate in the VPNv4.  The underlying MPLS network will forward
> > labels between the
> > VPNv4 end-point CE's. Next-hop-self isn¹t required. All that¹s
> > required is MPLS and IGP reachability between the CE¹s participating
> > in the vpnv4 domain.
> >
> > On 19/09/2014 10:31 am, "CiscoNSP List" <cisconsp_list at hotmail.com<mailto:cisconsp_list at hotmail.com>>
> wrote:
> >
> > >Is it recommended to add it under vpnv4 also?
> > >
> > >i.e.
> > >
> > >router bgp xxxxxx
> > >...
> > >neighbor iBGP-IPv4-PEERS update-source Loopback0 neighbor
> > >iBGP-IPv4-PEERS next-hop-self neighbor xxx.xxx.xxx.xxx peer-group
> > >iBGP-IPv4-PEERS...
> > >address-family vpnv4
> > >  bgp redistribute-internal
> > >  neighbor  iBGP-IPv4-PEERS send-community extended
> > >  neighbor iBGP-IPv4-PEERS next-hop-self
> > >  neighbor xxx.xxx.xxx.xxx activate
> > >
> > >Cheers.
> > >
> > >
> > >
> > >_______________________________________________
> > >cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> > >https://puck.nether.net/mailman/listinfo/cisco-nsp
> > >archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/