Many thanks for all the advice on this. I have added track-igp-metric to a backup PE node and this solves my current issue so will add throughout our network.
I will definitely look at getting individual route-distinguishers added as well as I do have 3 routers carrying full table and only two route reflectors so can optimise the routing further with this. Best regards, Paul From: Stuart Howlette [mailto:[email protected]] Sent: 29 April 2016 06:29 To: Ian Tomkins <[email protected]>; Paul Bone <[email protected]>; [email protected] Subject: Re: [uknof] Juniper SRX as PE Node Problem This is my guess, both routes reach the route reflector, but it is making a best path decision before announcing the routes. We run this where I work, and it works a treat. You could get into things like BGP Add Path and the like, but it’s probably complexity you do not need at this stage Stuart From: uknof <[email protected]<mailto:[email protected]>> on behalf of Ian Tomkins <[email protected]<mailto:[email protected]>> Date: Thursday, 28 April 2016 at 17:16 To: Paul Bone <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [uknof] Juniper SRX as PE Node Problem I’m not sure this is relevant to you but I thought I would mention that there is also a trick you can use when running MP-BGP through route reflectors and you still need to see all the versions of a particular route not just the ones the route reflector chose as best route - which is to use a different route-distinguisher on each originating router but the same route-target, this causes the route reflector to see the multiple versions of the same route as different so the route selection process will take place at the point the routes are pushed into your specific VRF. You can also use this to ensure that ECMP works, but it gets more complex because every router that needs to build an LSP to one of your destinations needs to be configured to use multiple routes in the relevant VRF. Cheers, Ian From: uknof [mailto:[email protected]] On Behalf Of Paul Bone Sent: 28 April 2016 10:31 To: [email protected]<mailto:[email protected]> Subject: [uknof] Juniper SRX as PE Node Problem I am using some Juniper SRX240 as PE nodes and running the Internet in VRF. I have two Juniper MX5 MP-BGP route reflectors which also receive the full internet table plus default into VRF and export just my local routes (BGP and direct) and a default route (BGP) into the VRF. The problem I have is that the SRX240 is receiving the default route from both route reflectors but is actually preferring and forwarding traffic to the route reflector with the lowest router ID (show route detail confirms this) and ignoring the underlying IGP metrics from the global OSPF table. This is causing sub-optimal routing of traffic. Has anyone experienced this before? Best regards, Paul Paul Bone | Connectivity Manager office: 01223 755055 | mobile: +44 7713 393621 email: [email protected]<mailto:[email protected]> Thinking of moving services to a Data Centre? Please ask for information on our Colocation services<http://www.bridgefibre.co.uk/colocation-services/> Bridge Fibre Ltd<http://www.bridgefibre.co.uk> | Registered in England 04250873 Jeffreys Building, St John's Innovation Park, Cowley Road, Cambridge, CB4 0DS web: www.bridgefibre.co.uk<http://www.bridgefibre.co.uk> twitter: @bridgefibre<http://twitter.com/@bridgefibre> service desk: 01223 755075 CLARITY • PARTNERSHIP • QUALITY 2015 ISPA Awards Winner - Best Enterprise Broadband<http://www.ispa.org.uk/ispa-awards/> DISCLAIMER NOTICE This message and any files transmitted with it contain privileged and confidential information intended only for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message you are hereby notified that you must not use, disseminate, forward, copy, print or take any action in reliance on it. If you have received this message in error, please notify Bridge Fibre Ltd immediately and delete this email from your computer. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of Bridge Fibre Ltd. Viruses: Although we have taken steps to ensure that this e-mail and any attachments are free from any virus, we cannot be held responsible for any viruses transmitted with this email and any such attachments. Any prices quoted in this email are for indicative purposes only and are subject to further technical appraisal. Additional installation charges may apply. Unless otherwise specified, prices are in GB Pounds and exclude VAT (or equivalent taxes). Pricing valid for 14 days. Acceptance of any proposal contained in this email is subject to formal contract. ________________________________ This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any distribution, copying or use of this communication or the information in it is strictly prohibited. If you have received this communication in error please notify us by email ([email protected]<mailto:[email protected]>) or by telephone +44 (0)203 3716666 and then delete the email from your system together with any copies of it. All communication sent to and from Modrus Limited is subject to monitoring of content. By using this method of communication you give consent to the monitoring of such communications. Any views or opinions are solely those of the author and do not necessarily represent those of the companies listed below unless specifically stated.' Modrus Limited is registered in England and Wales (no. 5022857). The registered office of Modrus Limited is Midland House, 2 Poole Road, Bournemouth, Dorset BH2 5QY.
