On Thursday, February 23, 2012 02:55:44 PM Chris Kawchuk
wrote:
> Naturally a prefix-limit would have helped; or a
> route-filter prefix-list... alas apparently neither of
> these were in effect.
I can't say I'm surprised that even these days, such basic
features across customer/peer-provider e
On Wednesday, February 22, 2012 10:25:59 PM Patrick Okui
wrote:
> Put those two together and there's good reason to set the
> AD for both iBGP and eBGP to say 200 (the default AD for
> iBGP and higher than any IGP). IMHO Juniper's default
> preference settings make more sense.
Exactly!
Of cours
On Wednesday, February 22, 2012 09:18:18 PM Phil Mayers
wrote:
> Interesting. I'd not heard that one before. What's the
> rationale?
Two reasons:
a) Make BGP distance the same.
b) Make BGP distance greater than any IGP (bad
things could happen if your traffic is taki
On 2012-02-23, at 1:25 AM, Patrick Okui wrote:
> Well, apart from l3vpns you'll typically want to have your
> infrastructure addresses in your IGP and "internet/customer" addresses
> in BGP. Default AD of 20 for eBGP in IOS means you'll believe an
> advertisement from an external AS before say
On Wed Feb 22 16:18:18 2012, Phil Mayers wrote:
>> Recommendations in the industry have been to equalize these
>> values to avoid issues.
>
> Interesting. I'd not heard that one before. What's the rationale?
Well, apart from l3vpns you'll typically want to have your
infrastructure addresses in yo
On 21/02/12 06:24, Mark Tinka wrote:
IOS (and IOS XR) runs BGP in two ways:
o iBGP routes have an administrative distance (Cisco
speak for Juniper's "preference") of 200.
o eBGP routes have an administrative distance of 20.
Recommendations in the industry have been
On Monday, February 20, 2012 10:30:39 PM Julien Goodwin
wrote:
> 2. IGP (OSPF, IS-IS) routes are preferred over BGP in
> JunOS, unlike IOS
IOS (and IOS XR) runs BGP in two ways:
o iBGP routes have an administrative distance (Cisco
speak for Juniper's "preference") of 200.
On 21/02/12 01:10, Jonas Björklund wrote:
> policy-statement my-export-routes {
> term t10 {
> from {
> protocol bgp;
> route-filter 1.2.3.0/21 prefix-length-range /21-/24;
> route-filter 4.5.6.0/20 prefix-length-range /20-/24;
> }
> t
On Mon, 20 Feb 2012, Jonas Björklund wrote:
I want all networks learned from BGP (even those from OSPF) pass the policy.
advertise-inactive on bgp group seem to be the magic. :-)
/Jonas___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https
Hello,
Im used to Cisco and Cisco doesnt annonce other networks then learned from BGP
default.
I only want to announce networks that my Juniper learns from other iBGP routers.
I tried a policy.
policy-statement my-export-routes {
term t10 {
from {
protocol bgp;
10 matches
Mail list logo
