Many ways to skin a cat... personally i would use local pref for outbound and as-prepend on the inbound and your golden
-- Payam Chychi Network Engineer / Security Specialist On Thursday, 18 July, 2013 at 4:45 PM, Tim Vollebregt wrote: > Hi Keith, > > Yes, this sounds good. But to have the inbound/outbound traffic on the new > 10GE link you will have to influence the path selection on both import and > export policies. > > A good way to do this is: > > import policy: > > set policy-options policy-statement upstream-in term 1GE from neighbor 1.1.1.1 > set policy-options policy-statement upstream-in term 1GE then metric 1000 > set policy-options policy-statement upstream-in term 1GE then accept > set policy-options policy-statement upstream-in term 10GE from neighbor > 2.2.2.2 > set policy-options policy-statement upstream-in term 10GE then metric 1 > set policy-options policy-statement upstream-in term 10GE then accept > > Of course this is just an example, you can use either accept or next policy > and all other flavors of routing decision/filtering. > > export policy: > > set policy-options policy-statement upstream-out term 1GE to neighbor 1.1.1.1 > set policy-options policy-statement upstream-out term 1GE then metric 1000 > set policy-options policy-statement upstream-out term 1GE then accept > set policy-options policy-statement upstream-out term 10GE to neighbor 2.2.2.2 > set policy-options policy-statement upstream-out term 10GE then metric 1 > set policy-options policy-statement upstream-out term 10GE then accept > > Hopefully the upstream will honor the metrics you are setting on the outbound > policy. Afterwards you can verify if all traffic moves from the 1GE to the > 10GE port and when all is gone you can safely remove the 1GE neighbor > statement(s). > > Good luck. > > Tim > > > On Jul 19, 2013, at 1:10 AM, Keith 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@puck.nether.net > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
