[j-nsp] Basic BGP Questions

[David Ball]

  I tend to use groups (under [edit groups]) to create sections of
commonly-applied configurations.  Very nice JUNOS feature.  This might
be where you'd list elements that would apply to multiple BGP
neighbours (though groups can be used for ANY configuration elements
that you might want to reuse...not just BGP stuff).  For example
(using arbitrary values, not necessarily yours):

[edit groups ebgp-peers]
        protocols {
            bgp {
                group <*> {
                    type external;
                    log-updown;
                    import inbound-exchange;
                    export outbound-exchange;
                    family inet {
                        unicast {
                            prefix-limit {
                                maximum 128;
                                teardown idle-timeout 3;
                            }
                        }
                    }
                    remove-private;
                }
            }
        }

The inbound-exchange and outbound-exchange are 'policy-statements',
defined at [edit policy-options policy-statement
your-policy-name-here] (as described here:
http://www.juniper.net/techpubs/en_US/junos9.6/information-products/topic-collections/config-guide-policy/frameset.html
 )
  so far though, nothing has been actually 'applied' to your bgp
neighbor.  To apply the above config, list the above 'group' in the
neighbor configuration, something like:

[edit protocols bgp]
group arbitrary-name-here1 {
  apply-groups ebgp-peers;
  neighbour neighbour.ip.address
  ....
  ...
}
group arbitrary-name-here2 {
  apply-groups ebgp-peers;
  neighbour other.ip.address
  ...
  ...
}

and so on.

HTH,

DB


On 4 May 2010 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".
>
>
>
> ;)
>
>
>
> Cheers,
>
>
>
> Paul
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>