[j-nsp] Basic BGP Questions

[Chris Grundemann]

On Tue, May 4, 2010 at 08:16, Paul Stewart <paul at paulstewart.org> wrote:
> Hi folks.
>
>
>
> I'm having a hard time getting a 'stock configuration' done on JunOS for
> eBGP peering.. Been reading Juniper docs and keep circling back with more
> questions than answers ;)
>
>
>
> Could someone get me pointed in the right direction? .
>
>
>
> In Cisco, we do this:
>
>
>
> neighbor xxx.32.235.39 remote-as 12345
>
>  neighbor xxx.32.235.39 peer-group peering-exchangename
>
>  neighbor xxx.32.235.39 description xxxxxxxxxx
>
>  neighbor xxx.32.235.39 activate
>
>  neighbor xxx.32.235.39 maximum-prefix 100 95
>
>
>
> neighbor peering-exchangename peer-group
>
> neighbor peering-exchangename send-community
>
>  neighbor peering-exchangename route-map inbound-exchangename in
>
>  neighbor peering-exchangename route-map outbound-exchangename out
>
>
>
> route-map inbound-exchangename permit 10
>
>  set metric +110
>
>  set local-preference 200
>
>  set community 11666:2000 11666:2002 additive
>
>
>
> route-map outbound-exchangename permit 10
>
>  match community 100
>
>  set metric 110
>
>
>
>
>
> I realize that there's quite a bit going on here - just need some samples of
> folks doing similar and I'll be "off to the races".

My IOS-foo may not be what it once was, but I think this is a mirror
of the above config in Junos:

[edit protocols bgp]
+    group peering-exchangename {
+        description xxxxxxxxxx;
+        import inbound-exchangename;
+        export outbound-exchangename;
+        neighbor 10.32.235.39 {
+            family inet {
+                unicast {
+                    prefix-limit {
+                        maximum 100;
+                        teardown 95;
+                    }
+                }
+            }
+            peer-as 12345;
+        }
+    }
[edit policy-options]
+   policy-statement inbound-exchangename {
+       term term-1 {
+           then {
+               metric 110;
+               local-preference 200;
+               community add inbound-exchangename-1;
+               accept;
+           }
+       }
+   }
+   policy-statement outbound-exchangename {
+       term term-1 {
+           from community outbound-exchangename-1;
+           then {
+               metric 110;
+               accept;
+           }
+       }
+       term ios-implicit {
+           then reject;
+       }
+   }
[edit policy-options]
+   community inbound-exchangename-1 members [ 11666:2000 11666:2002 ];
+   community outbound-exchangename-1 members 100;

It may not be perfect but it should get you pointed in the proper directions...

~Chris

>
> ;)
>
> Cheers,
>
> Paul
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>




-- 
@ChrisGrundemann
weblog.chrisgrundemann.com
www.burningwiththebush.com
www.coisoc.org