If you only have one CE then i would use the BGP weight attribute which is Cisco specific. So you receive routes from both PEs and you simply assign a higher weight to the routes received from your primary PE.
The weight attribute is the first thing considered in the BGP path selection on Cisco routers and it is only significant on the router itself ie. it is not passed to any other BGP routers.
Routes learnt from EBGP peers are 0 by default. The higher the weight the more preferred the route is.
That will take care of outgoing traffic. Are you concerned about incoming as well ?
I have one seemingly interesting point here, when the active's PE interface to core goes down then the CE's weight will be still active pointing to this now faulty PE, until tables are flushed on PE. Is this correct?
And yes returning traffic should be symmetrical, via the same active PE. I guess MED is the way here.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...