[j-nsp] Setting RTBH next-hop at RR for L3VPN routes

[Phil Mayers]

On 09/02/2014 05:34, Mark Tinka wrote:
> On Sunday, February 09, 2014 01:30:20 AM Phil Mayers wrote:
>
>> So, what I'm asking is: how can I override an inet-vpn
>> next-hop at a route-reflector, when the next-hop is not
>> a "real" PE.
>
> I'm guessing this is dedicated route reflector - not running
> MPLS - and you have no problems reflecting regular l3vpn
> routes, yes?

It is a dedicated route-reflector i.e. not in the traffic path, and I 
have no problems reflecting regular l3vpn routes. But it is running MPLS 
(ldp & family mpls on core ifs), as to me this seems marginally cleaner 
than a 0.0.0.0/0 static in inet.3.

This made me wonder if a static for the RTBH next-hop in inet.3 would 
help - no joy. Nor does adding the RTBH next-hop as a secondary on 
loopback, presumably because JunOS isn't allocating a label for it, or a 
couple of different variations of getting the route into inet.3, this 
time with valid labels (advertised by a 3rd router).

Since the error message all along is:

   BGP label allocation failure: protocols mpls not enabled on interface

...I'm wondering what interface it's referring to. MPLS is defintely 
enabled on the core-facing interfaces, so which interface is it 
referring to? Time to break out traceptions methinks.