[c-nsp] MPLS labels with VPNv4 blackholing

[Ross Halliday]

Hi list,

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:

test-lab-c6506#sh bgp vpnv4 uni rd 64723:666 12.34.56.78/32
BGP routing table entry for 64723:666:12.34.56.78/32, version 254
Paths: (1 available, best #1, no table)
  Not advertised to any peer
  Local
    6.6.6.6 from 172.18.96.255 (172.18.96.255)
      Origin IGP, metric 0, localpref 200, valid, internal, best
      Extended Community: RT:64723:666,
      mpls labels in/out nolabel/66

test-lab-c6506#sh bgp vpnv4 uni rd 64723:666 23.45.67.89/32
BGP routing table entry for 64723:666:23.45.67.89/32, version 255
Paths: (1 available, best #1, no table)
  Not advertised to any peer
  Local
    6.6.6.6 from 172.18.96.255 (172.18.96.255)
      Origin IGP, metric 0, localpref 200, valid, internal, best
      Extended Community: RT:64723:666,
      mpls labels in/out nolabel/35

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

Any advice or recommended approaches?

Thanks
Ross