Quantcast
Channel: All Routing posts
Viewing all articles
Browse latest Browse all 8688

Route advertized through BGP, not seen in received routes on the neighbouring router

$
0
0

Hello everyone. Gotta an issue I've been struggling with. I have this iBGP peering taking place between a QFX5100 and a MX104. Goal is to grab IX routes from one of my POPs, get them into VRF, export routes to be able to import directly into other VRF enabled POPs, and finally inject into my MX routers in another city. I'm stuck with a VR on the MXs for another 6 months, else I'd be running into VRF on those as well and would only have to import the target communities... I dabbled with rib groups but it's not doing it for me for many reasons, so I went for the iBGP peeing instead.

 

QFX: Peering taking place from inside VRF

MX: PEering taking place from insidei VR

QFX is advertizing a route to MX and we can see it's sent, but MX doesn't see the route coming in from QFX even in hidden route.

 

==============================

 

#run show route advertising-protocol bgp 50.21.165.2 detail

TORIX.inet.0: 167 destinations, 169 routes (167 active, 0 holddown, 0 hidden)
* 1.0.4.0/24 (2 entries, 1 announced)
BGP group BGP-BLENDED type Internal
Nexthop: Self
Flags: Nexthop Change
Localpref: 100
AS path: [65401] 29909 11670 6939 4826 38803 38803 38803 38803 56203 I (Originator)
Cluster list: 10.24.0.5 10.25.0.1
Originator ID: 10.25.0.4
Communities: 65401:11670 target:65401:11670 target:65401:11674 target:65401:11677

 

==================================

 

# ... bgp 50.21.165.3 table BGP-BLENDED.inet.0 hidden extensive

BGP-BLENDED.inet.0: 681709 destinations, 3409260 routes (681700 active, 0 holddown, 139 hidden)
50.21.165.2/31 (2 entries, 1 announced)
Nexthop: 50.21.165.3
Localpref: 100
AS path: I
Hidden reason: rejected by import policy

206.108.34.0/23 (1 entry, 0 announced)
Nexthop: 50.21.165.3
Localpref: 100
AS path: I (Originator)
Cluster list: 10.24.0.5 10.25.0.1
Originator ID: 10.25.0.4
Communities: target:65401:11670 target:65401:11672
Hidden reason: rejected by import policy

 

=========

 

I know why the two routes on there are rejected by MX, but that's ok. What I want to know if why MX isn't seeing the 1.0.4.0/24 route, which is clearly sent.

 

So, what can I show you to check this out. I was hoping I wouldn't have to open another ticket with tac, giving it a shot here.

 

Thanks.


Viewing all articles
Browse latest Browse all 8688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>