Gokhan, This is possible as follow:
PE1: static a.b.c.d/e next-hop n.m.l.r export static --> MP-BGP PE2: static a.b.c.d/e qualified next-hop Z t.s.u.w preference 250 export static --> MP-BGP When VRF on PE2 recive update from PE1, they foud that BGP route is better because of protocol prefernce, and meke them active. Then static route on PE2 is non-active, so will not be annouced in MP-BGP -- Rafał Szarecki JNCIE +48602418971 2007/5/16, Gökhan Gümüş <[EMAIL PROTECTED]>: > > Hi all, > > We have a MPLS backbone for L3 VPN customers.Our some customers take > redundant links for in case of any failure.We use static routing for PE-CE > connectivity.When one of CE facing link fails,we are configuring a new > static routes for that specific destinations that is pointing redundant > link manually.But customer requests to want this operations > automatically.I know that can be when using dynamic routing protocols > on PE-CE > connectivity.But i dont know how can i implement that request when using > static routing on PE-CE connectivity. > > Thanks, > > Gokhan > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Rafał Szarecki JNCIE +48602418971 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
