Hi!
Today I was labbing something similar to this and I found you post. I know you created this topic about three years ago. Possibly you've resolved the issues in the mean time. Hopefully this message finds you well if you get a chance to read it in the future!
I have some remarks, I don't have your configurations / full topology available here so I cannot give 100% solid solutions and my own lab was not complete with enough equipment to even fully verify my own goals.
1)
You wrote regarding unusable next-hop on P5-RR:
[quote]
---> it shows the next-hop as unsuable even though there is a route in inet.0
[/quote]
By default in JUNOS the next-hop for BGP VPN routes are resolved using RIB inet.3 . If not route is there, the VPN route becomes a Hidden route. How to resolve it? There are few options:
- run MPLS with e.g. LDP / RSVP. Active MPLS LSPs put a route in the RIB inet.3 so the route resolution succeeds
- configure static route in rib inet.3 (as you did)
- change the resolution ribs
- change MPLS route lookup
I think you're building an EVPN-VXLAN network, so it would be overkill to configure LDP / RSVP to create the inet.3 routes. Instead, on the RR (P5 router) you configured a static route in RIB inet.3 to resolve the unusable next-hops for RIB bgp.evpn.0. You can also configure a Discard next-hop instead of pointing it to "10.0.0.6 resolve". Or even simpler:
- set routing-options rib inet.3 static route 0/0 discard
You can see the behavior with:
###################################
user@qfx-leaf> show route resolution table bgp.evpn.0
Tree Index: 1, Nodes 0, Reference Count 4
Contributing routing tables: inet.3
###################################
Alternatively you can change the route resolution for inet.3 using:
- set routing-options resolution rib bgp.evpn.0 resolution-ribs [ inet.0 inet.3 ]
The above command should then show:
###################################
Contributing routing tables: inet.0 inet.3
###################################
Or delete dependence on inet.3 for route resolution and [ move all routes from inet.3 into inet.0 / depend on routes in inet.0 ]:
- set protocols mpls traffic-engineering bgp-igp
2)
Regarding the issue with RouteTarget routes on QFX51:
> lab@QFX51> show route advertising-protocol bgp 10.0.0.5
> bgp.rtarget.0: 6 destinations, 7 routes (1 active, 0 holddown, 6 hidden)
There is one active route, and it is being advertised to the P5-RR.
There are also 6x Hidden routes there. You can resolve them using the same solutions as in my remark #1. In my lab I noticed that the routes then move from Hidden state into the bgp.rtarget.0 RIB. I suspect that once they are not hidden anymore, the QFX51 learns membership for the EVPN route-targets from P5-RR and it should then advertise the EVPN routes (they were not being sent in your example) to P5-RR.
You can also specify on P5-RR to send a "default" RTF route (family route-target advertise-default) and it will tell PE devices (QFX51) to send all routes to the P5-RR.
As a closing remark, I don't think you hit a few bugs but just a few missing knobs in the configuration. JUNOS can be complicated at times 🙂