If you want the BGP route to be in the table but not active you will
need that same route in inet.0 from a different protocol with a lower
protocol preference.
I'm trying to get a better idea of the ultimate goal here. I'm
assuming that you are not in the forwarding path for the routes in
question and that the advertised BGP routes will have traffic flowing
across different routers in the network. If these assumptions are
correct (and you know what happens when you assume!!) then you could
add a static route to discard which will be active in inet.0 and make
the bgp routes inactive.
-joe
Joseph Soricelli
JNCIE #14/ CCIE #4803
703-980-3999
[email protected]
On Feb 25, 2009, at 9:56 AM, fighter worker wrote:
i tried that but that route iam no longer able to send it to other bgp
peers,, i need that route to be inactive in my routing table but still
can advertise it to other bgp peers
On Wed, Feb 25, 2009 at 4:20 PM, Stefan Fouant <[email protected]>
wrote:
On Wed, Feb 25, 2009 at 8:53 AM, fighter worker <[email protected]
> wrote:
but if i filter it out it wont be in routing table also so i wont be
able to send it to other bgp peers using advertise-inactive
There are probably multiple ways to accomplish this goal. One way
would be to use an import policy and set the next-hop to something
that is not reachable. If the next-hop is not reachable then the
route will not be made active. There are other ways, but this is
just
one example.
--
Stefan Fouant
Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams.
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
