I've a few RRs that are "out of path" and not running LDP. I'm exchanging inet and inet-vpn address families and also have inet.3 resolution set to inet.0:
routing-options {
forwarding-table {
export no-fib;
}
resolution {
rib bgp.l3vpn.0 {
resolution-ribs inet.0;
}
}
}
That (I think) should allow reflection of vpn routes but it still doesn't work:
> show route table bgp.l3vpn.0
bgp.l3vpn.0: 889 destinations, 1601 routes (0 active, 0 holddown, 1601 hidden)
An example (next hop unusable):
x.x.x.x:1:a.b.c.d/24 (3 entries, 0 announced)
BGP Preference: 170/-101
Route Distinguisher: x.x.x.x:1
Next hop type: Unusable, Next hop index: 0
Address: 0x278d15c
Next-hop reference count: 139697
State: <Hidden Int Ext ProtectionPath ProtectionCand>
Local AS: 1111 Peer AS: 1111
Age: 2d 0:04:55
Validation State: unverified
MED-plus-IGP: 0
Task: BGP_1111.x.x.x.x
AS path: I (Originator)
Cluster list: a.b.c.d x.y.z.v
Originator ID: x.x.x.x
Communities: target:11111:1
Accepted
VPN Label: 17
Localpref: 100
Router ID: x.x.x.x
Does anybody have any idea why? Next hop is in inet.0 table (via OSPF) so it should be "usable"...
Thanks,