03-06-2019 04:54 PM
Hello All,
We want to redistribute received routes from one provider e.g. SingTel to Telstra. Both been configured as same AS and peered with BGP.
We are receiving route from SingTel e.g. 10.80.128.0/24 (Asia office subnet) and Telstra (Asia office not with Telstra) does not have that route in its BGP table. Both ISP connected to same CE WAN router. We want that route in Telstra BGP table as well. So our remote site can reach singtel routes as well via Telstra gateway.
Both are our MPLS provider.
I have attached diagram of this.
Any ideas for what I might need to do to get this working..?
Any thoughts or suggestions would be greatly appreciated!
Thanks in Advance,
Jeet
Solved! Go to Solution.
03-08-2019 12:34 AM - edited 03-08-2019 04:01 AM
Hello
As I said by default bgp loop prevention will not allow any prefix with its own ASN in the path attitude to be allowed so to negate this try the following:
On the Teltra rtr towards its bgp neighbour facing ASN64800
neighbor xxxx allowas-in
Then do a soft RR (clear ip bgp xxx soft in ) and test again
03-07-2019 01:58 AM - edited 03-07-2019 01:59 AM
Hello,
--> Both ISP connected to same CE WAN router.
Post the full configs of all routers that are under your control...
03-07-2019 01:44 PM
Correct both routers are connected to SAME WAN router.
03-07-2019 02:01 AM
03-07-2019 02:20 PM
Hi ngkin2010,
Those routes already there in Singtel but what I want is other way around.
Those are Singtel received routes , I want to redistribute to Telstra. and Both have same AS number. and both connected to same WAN router.
Jit
03-07-2019 02:18 AM - edited 03-07-2019 02:28 AM
Hello
No so sure I understand - You have a single wan rtr connected to two ISPs and your receiving an ebgp route from one these ISP's that isnt reachable from where - What your topology shows is one router AS64800 (I assume your wan router) connected to two ISP rtrs in the same ASN so why would you want to your wan rtr to be a transit path between two ISP's
You should ONLY advertise locally originated prefixes towards your ISP's NEVER other ISP routes, in fact I doubt they would even allow them in anyway.
Lastly by default bgp wont accept routes originated from its own ASN
03-07-2019 02:18 PM
Hi Paul,
I have added my topology here. We were with Singtel and disconnected all Singtel across APAC region. Singapore where the router is , have Telstra and Singtel as Transit to reach to Asia offices. Offices in Asia still have Singtel not migrating to Telstra.
I still have single link between Melbourne and Singapore that I am going to disconnect. That's where the problem will start, when I will disconnect that I can reach up to Singapore via Telstra as both on Telstra. But I wont be able to reach our offices in Asia from Melbourne.
03-08-2019 12:34 AM - edited 03-08-2019 04:01 AM
Hello
As I said by default bgp loop prevention will not allow any prefix with its own ASN in the path attitude to be allowed so to negate this try the following:
On the Teltra rtr towards its bgp neighbour facing ASN64800
neighbor xxxx allowas-in
Then do a soft RR (clear ip bgp xxx soft in ) and test again
03-12-2019 03:17 PM
Hi Paul,
I will try that and get back to you..
Thanks,
Jit
03-13-2019 06:33 PM
Hi Paul,
This has fixed the issue.
Thank you.
Jit
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide