[c-nsp] tag-switching advertise-tags for?

[Aamer Akhter (aakhter)]

> If I understood you correctly, I'll need an extra lo on each 
> PE (one for 
> vpnv4 BGP peering, one for ipv4 peering, twice as many BGP 
> sessions, and 
> will have to set things up so that each session is strictly 
> vpnv4 or ipv4, 
> but not both (or only accepts routes in the appropriate 
> address-family).

Jon,

Just to clarify, there is a way to have single session which shares ipv4 + vpnv4 and a relatively simple config. 

You'll need to have 2 loopbacks: one for ipv4 another for vpnv4. Additionally, you'll need one route-map: to change the next-hop to one of the loopbacks per address-family. The other loopback will be set by default.

hth

-- 
Aamer Akhter / aa at cisco.com
NSITE - cisco Systems 

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jon Lewis
> Sent: Monday, October 24, 2005 6:37 PM
> To: Robert Kiessling
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] tag-switching advertise-tags for?
> 
> On Mon, 24 Oct 2005, Robert Kiessling wrote:
> 
> >> tables or policy routing.  Do all the PE router lo0's have 
> to be advertised 
> >> into TDP/LDP for MPLS-VPN tag switching to work?
> >
> > All your loopbacks that are nexthops for BGP in the vpnv4 address
> > family have to be advertised by LDP, and only those have to.
> >
> >> How/why would traffic to bgp learned non vpnv4 prefixes be 
> label-switched 
> >> if tags for those prefixes were not advertised?
> >
> > If the next hop is label switched, then the prefix itself
> > is too.
> 
> That sucks...so getting our non-MPLS traffic routed instead of 
> tag-switched is actually going to be much more complicated 
> (or at least 
> more work) than just tag-switching advertise-tags for <acl> 
> on all the 
> PEs.
> 
> If I understood you correctly, I'll need an extra lo on each 
> PE (one for 
> vpnv4 BGP peering, one for ipv4 peering, twice as many BGP 
> sessions, and 
> will have to set things up so that each session is strictly 
> vpnv4 or ipv4, 
> but not both (or only accepts routes in the appropriate 
> address-family).
> 
> ----------------------------------------------------------------------
>   Jon Lewis                   |  I route
>   Senior Network Engineer     |  therefore you are
>   Atlantic Net                | 
> _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>