Users Guide

BGP 1337
Resolving Interface Routes
In Dell EMC Networking, the next hop of a route is always a set of next-hop
IP addresses. Dell EMC Networking does not support routes whose next hop
is simply an interface. Thus, the second route resolvability condition in RFC
4271 section 9.1.2.1 does not apply.
Originating BGP Routes
A router running Dell EMC Networking BGP can originate a BGP route
through route redistribution and through configuration (the network
command). Attributes of locally-originated routes may be set through a route
map. Locally-originated BGP routes are sent to both internal and external
peers unless filtered by outbound policy.
Locally-originated routes are added to Accept-RIB-In. Phase 2 of the decision
process considers locally-originated routes along with routes received from
peers when selecting the best BGP route to each destination.
BGP can be configured to originate the same prefix through a network
command and through redistribution. Dell EMC Networking BGP creates a
different path for each if the path attributes differ. BGP only advertises the
prefix with the preferred path.
RFC 4271 section 9.2.1.2 specifies “a minimum amount of time that must
elapse between successive advertisements of UPDATE messages that report
changes within the advertising BGP speaker's own autonomous systems” and
refers to this as minASOriginationInterval. RFC 4271 section 10 suggests a
default of 15 seconds. Dell EMC Networking BGP does not enforce
minASOriginationInterval, but relies on minRouteAdvertisementInterval,
which is applied to all advertisements, to dampen flaps of locally-originated
remove-private-as Remove private ASNs from AS_PATH when sending to
inheriting peers.
route-map Configure a route map for the peer.
route-reflector-client Configure a peer as a route reflector client.
send-community Configure this peer to send BGP communities.
Table 36-3. Session Parameters in BGP Peer Templates—Configurable Per-Address
Family
Parameter Description