Many thanks for your response flash, unfortunately MED/local pref are nontransitive so won't propagate beyond or direct upstream provider, so that won't have any effect.
Bogus path entries means that I advertise to my backup provider my network with a path of - for example if my as was AS100 - 100 100 100 100 to make it appear further away and thus less preferable than my primary route.
Effect of your AS-PATH prepend (that's what you're doing) might easily be canceled by your (backup) upstream provider if they set higher local-pref on all customers (commonplace). Ask both providers to show you routes towards troubled network as seen from their routers.
As a rule you need to work closely with your providers to figure out which of the attributes you need to tune in order to achieve desired routing policy. Often using communities allows to achieve better results than simple AS-PATH prepend.
The easiest way to see how your prefixes look upstream is to login to a free route servers / looking glasses and see. Go to www.traceroute.org, there is a huge list of these so you can see if your prepending is getting dumped by the provider. Most providers will allow prepending as long as you are prepending your own AS and not someone elses (obviously).
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...