05-19-2016 10:31 AM
Hi,
Our multiple sites are connected by MPLS coming from 1 ISP provider. We will be adding another site but our current provider does not have local carrier available so we have to use a different ISP. The new circuit is already provisioned and according to the vendor our BGP AS# will propagate on their end. I'm concerned about the config for the new router/site. Would this be the same config like our existing MPLS sites? Will I be using the same BGP config like below but with just a different neighbor IP or is there an additional config I need to add in order for the new site to communicate with our existing MPLS? Any help is appreciated. Thanks
Our current MPLS:
router bgp 11111
no synchronization
bgp log-neighbor-changes
network 10.240.25.0 mask 255.255.255.0
network 172.18.83.0 mask 255.255.255.0
network 172.18.85.0 mask 255.255.255.0
redistribute connected
neighbor x.x.x.x remote-as 2222
neighbor x.x.x.x soft-reconfiguration inbound
no auto-summary
05-20-2016 04:13 AM
Hi Jan,
I believe, the above config template should do as long as the BGP session comes up.
make sure neighbor x.x.x.x remote-as 2222, the AS number here is the new ISP AS number.
And if you are using same local AS number across sites, ISP must enable as-override at PE END.
Rest all, It is ISP's headache to built NNI for your particular VRF and make sure all the routes are exchanged up and down and relayed over to CPE.
Hope this helps.
Sheshu.
05-20-2016 12:21 PM
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