At both the remote site, I've a Cisco 2811 connected to two different MPLS providers..say ProviderA and ProviderB running BGP using the same AS number. The same is at the core 7206, but ProviderA has a "weight" assigned as 55555. When I assign the same weight (or even different, higher weight number than the default 32678 - neighbor 10.xxx.xxx.xxx weight 55555) to the MPLS circuit from the ProviderA at the remote site, this circuit starts to bounce every 30 seconds or so. Remove the weight parameter from the remote site then the circuit becomes stable again.
My objective is to make ProviderA MPLS circuit to be the primary all the time while ProviderB MPLS will be the backup circuit.
a) The default weight attribute value is 0, not 32678.
32678 is the value assigned to the prefixes inserted to the BGP table by the router itself.
b) I can imagine using a value higher than 32678 could confuse your router under some conditions (your providers using as-override, e.g., and you advertising the prefixes received form one provider to the other provider in your core site) and it could accept its own LAN prefix 192.168.xxx.xxx advertised from the provider.
It would stop advertising it to the provider then and finally the prefix would start flapping from your core router point of view.
c) I'd recommend you to try using some weight value lower than 32768 on the remote site (and also in the core actually).
10000 should be good enough.
In that case, the router will still prefer prefixes received from provider A over the same prefixes received from provider B.
But this will not influence the prefixes advertised by the router itself any way.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...