Limitations on Inheritance
All BGP peers that are members of the same peer group must send essentially the
same updates. Accordingly, all members of a peer group must be the same kind of
peer; that is, all must be internal peers, all must be external peers, or all must be
confederation peers.
Outbound policies configured for peer groups are still inherited by peer group
members, but you cannot override this inherited outbound policy by configuring a
different outbound policy on individual members of that peer group with the following
commands:
Table 12: Commands That Do Not Override Inherited Outbound Policy
neighbor route-map outneighbor
next-hop-unchanged
neighbor as-override
neighbor
route-reflector-client
neighbor prefix-list outneighbor
default-originate
neighbor send-communityneighbor prefix-tree outneighbor distribute-list
out
neighbor unsuppress-mapneighbor
remove-private-as
neighbor filter-list out
neighbor next-hop-self
NOTE: This restriction does not apply to inbound policy, which you can still override
per peer.
The update messages can vary for members of a peer group as follows:
â– The next hop can be different for each update sent to peer group members if
the members are all external peers.
â– The AS path can be different for each update sent to peer group members if the
members are all external peers if you have enabled AS override with the neighbor
as-override command.
Setting the BGP Identifier
By default, the router ID of the router is used as the BGP identifier. You can use the
bgp router-id command to configure an IP address as the BGP identifier.
bgp router-id
â– Use to configure an IP address as the BGP identifier.
â– Example
24 â– Basic Configuration
JUNOSe 11.1.x BGP and MPLS Configuration Guide
To Next Page
Loading...
Need help?
General
