Re: OT: routing dilemma

Hi Tony,

You can complicate the design by adding a track 1 to check the availability
of the /16 from Site A and use a second boolean track 2 to call the first
object negated.

something like ..

track 1 <IP SLA definition>
!
track 2 list boolean and
 object 1 not
!
ip route 10.0.0.0 255.255.0.0 Null0 track 2
!

Better would be to use BGP attributes like MED or AS Prepend from your BGP
router which talks with the ISP PER. You can also do RFC 1998 using BGP
communities provided your ISP supports the same. (have seen most of them
supporting). Routes from both Site A and Site B would exist in the MPLS
cloud, but will use only use one of the /16s which is is your preferred
site.

-ta

Best Regards,
Tharak Abraham Luke

On Fri, Jun 27, 2014 at 11:25 PM, Tony Singh <mothafungla_at_gmail.com> wrote:

> 10.0.0.0/16 SITE A
>
> is required to be withdrawn when site is down & SITE B advertisement of
> the same subnet becomes active
>
> This is an MPLS VPN where the route originates as an IGP where the edge
> routers redistribute into BGP
>
> I cannot use PBR any methods you guys would approach this with
>
> Conditional, higher AD etc be good to know any views on this, something
> simple that wouldn't cause loops is desired
>
> --
> BR
>
> Tony
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Sat Jun 28 2014 - 09:03:40 ART