Limitations On Inheritance; Setting The Bgp Identifier; Table 12: Commands That Do Not Override Inherited Outbound Policy - Juniper JUNOSE SOFTWARE FOR E SERIES 11.0.X - BGP AND MPLS CONFIGURATION GUIDE 2009-12-30 Configuration Manual

JUNOSe 11.0.x BGP and MPLS Configuration Guide

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

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:

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
24
Basic Configuration
neighbor as-override neighbor
next-hop-unchanged
neighbor neighbor prefix-list out
default-originate
neighbor distribute-list neighbor prefix-tree out
out
neighbor filter-list out neighbor
remove-private-as
neighbor next-hop-self
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.
Use to configure an IP address as the BGP identifier.
Example
neighbor route-map out
neighbor
route-reflector-client
neighbor send-community
neighbor unsuppress-map