[c-nsp] MPLS labels with VPNv4 blackholing

[Oliver Boehmer (oboehmer)]

> My Google-fu seems to be letting me down. Maybe I haven't had enough
coffee
> yet.
> 
> I'm in the lab playing with finally implementing remote-triggered
black hole
> routes into an MPLS network with BGP VPNv4 prefixes. After I realized
that
> the null-route destination set by BGP as the next hop address had to
be in
> the global table everything's working fine. However I notice that the
route
> reflector I'm sending out the "666" community on is generating
separate
> labels for each prefix:

the RR is not generating any labels, it's the originator (i.e. the PE)
who does. 
 
> I don't plan on sending out thousands of black hole routes that might
> exhaust the label table but all this junk in LDP is annoying me. 

none of these labels will end up in LDP, we're talking about BGP/l3vpn
labels here.

> I looked at
> the "Per-VRF Label" feature but it's only available on the 6500
platform. My
> route reflectors are 7200 boxes.

I guess all of the routes are originated by a specific PE in the
network? You could use per-vrf labels there (and per-vrf labels should
also work on 7600 and ASR1k and others, haven't checked).. but even if
you advertise a per-prefix label, the other PEs shouldn't have any
problems storing these (I remember a 3rd-party device which had problems
storing a lot of different vpnv4 labels, but that's been ages). 

	oli