■
Use to add an entry to the BGP neighbor table.
■
Specifying a neighbor with an AS number that matches the AS number specified
in the router bgp command identifies the neighbor as internal to the local AS.
Otherwise, the neighbor is treated as an external neighbor.
■
If you specify a BGP peer group by using the
peerGroupName
argument, all the
members of the peer group inherit the characteristic configured with this
command unless it is overridden for a specific peer.
■
This command takes effect immediately.
■
Use the
no
version to remove an entry from the table.
■
See neighbor remote-as
Configuring BGP Peer Groups
You will often want to apply the same policies to most or all of the peers of a particular
BGP speaker. Update policies are usually defined by route maps, filter lists, and
distribution lists. You can reduce the configuration effort by defining a peer group
made up of these peers.
A peer group is defined relative to a particular BGP speaker. Figure 11 on page 27
shows two peer groups,
eastcoast
and
leftcoast
. Each of these peer groups is defined
for router Chicago, the hub router. Routers Boston, NY, and Miami have no knowledge
of being members of Router Chicago’s
eastcoast
peer group. Similarly, routers
SanFran, LA, and SanDiego have no knowledge of being members of router Chicago’s
leftcoast
peer group.
The following commands configure the
eastcoast
peer group on router Chicago:
host1(config)#
router bgp 23
host1(config)#
route-map wtset permit 10
host1(config-route-map)#
set weight 25
host1(config-route-map)#
exit
host1(config-router)#
neighbor eastcoast peer-group
host1(config-router)#
neighbor eastcoast route-map wtset in
host1(config-router)#
neighbor 10.6.6.2 remote-as 12
host1(config-router)#
neighbor 10.6.6.2 peer-group eastcoast
host1(config-router)#
neighbor 10.7.3.2 remote-as 12
host1(config-router)#
neighbor 10.7.3.2 peer-group eastcoast
host1(config-router)#
neighbor 10.4.4.2 remote-as 12
host1(config-router)#
neighbor 10.4.4.2 peer-group eastcoast
The following commands configure the
leftcoast
peer group on router Chicago:
host1(config-router)#
neighbor leftcoast peer-group
host1(config-router)#
neighbor 10.3.3.2 remote-as 78
host1(config-router)#
neighbor 10.3.3.2 peer-group leftcoast
host1(config-router)#
neighbor 10.3.2.2 remote-as 2143
host1(config-router)#
neighbor 10.3.2.2 peer-group leftcoast
host1(config-router)#
neighbor 10.3.1.2 remote-as 136
host1(config-router)#
neighbor 10.3.1.2 peer-group leftcoast
26
■
Configuring BGP Peer Groups
JUNOSe 11.1.x BGP and MPLS Configuration Guide
Summary of Contents for BGP
Page 6: ...vi ...
Page 8: ...viii JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 37: ...Part 1 Border Gateway Protocol Configuring BGP Routing on page 3 Border Gateway Protocol 1 ...
Page 38: ...2 Border Gateway Protocol JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 234: ...198 Monitoring BGP JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 236: ...200 Multiprotocol Layer Switching JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 542: ...506 Monitoring BGP MPLS VPNs JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 544: ...508 Layer 2 Services Over MPLS JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 610: ...574 Virtual Private LAN Service JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 624: ...588 VPLS References JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 680: ...644 Virtual Private Wire Service JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 724: ...688 Monitoring MPLS Forwarding Table for VPWS JUNOSe 11 1 x BGP and MPLS Configuration Guide ...
Page 725: ...Part 6 Index Index on page 691 Index 689 ...
Page 726: ...690 Index JUNOSe 11 1 x BGP and MPLS Configuration Guide ...