[j-nsp] BGP Multipath

[Aaron Dewell]

It depends how careful you want to be about it. Multipath and adding the
peer as you've described will get you half traffic on each immediately
which is fine assuming the circuit is good, etc.

If it were me, I'd probably bring up the new one with a different policy
(same group, policy under the neighbor for now) that assigns all prefixes a
lower localpref  than the default (which is 100) or a higher MED (either
will do the same) except a few test prefixes. Make sure bgp comes up, test
those prefixes for a few days, then remove the temporary policy and remove
the peer over GE and multipath at that point.

Either approach is fine. It depends what you are concerned about and what
you want to protect against.
On Jul 18, 2013 5:14 PM, "Keith" <kwoody at citywest.ca> wrote:

> We recently just turned up another connection to one of our upstreams, so
> now we have two. One is a GE the other is a 10GE.
>
> We are getting into new territory here.
>
> The GE connection is in use and working fine.
>
> These two connections home to two different routers on our upstream.
>
> As the BGP policy will remain the same, I was just going to add a new
> neighbour statement to that
> particular BGP group for that upstream.
>
> I was told to also add multipath to that as well if I want to use both
> connections for load balancing.
>
> Don't really want to use both as the GE will be going away sometime, but
> to make sure it works I was
> going to add the new neighbor IP address, make sure BGP comes up and
> traffic is there then remove the old neighbor
> IP address.
>
> Would this be a sensible way to do it?
>
> Thanks.
> ______________________________**_________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/**mailman/listinfo/juniper-nsp<https://puck.nether.net/mailman/listinfo/juniper-nsp>
>