Users Guide

BGP 1335
peer session (if the network administrator activates IPv6 on the peer session)
and in an IPv6 update group for an IPv6 peer session. Such a configuration is
probably a misconfiguration. BGP will send IPv6 NLRI to the neighbor twice.
BGP assigns peers to update groups automatically. The Dell EMC
Networking UI has no configuration associated with update groups and the
UI does report update group membership.
Removing Private AS Numbers
An organization may use private AS numbers internally. Private ASNs must be
removed from routes to destinations within an AS before the routes are
advertised in order to avoid conflicts with other networks also using
overlapping private ASNs. Dell EMC Networking BGP may be configured to
remove private AS numbers from the AS_PATH attribute of paths advertised
to external peers as an outbound policy.
Two-byte ASNs in the range from 64,512 to 65,535 are removed when this
option is enabled. The administrator may optionally configure BGP to replace
private ASNs with the local AS number. The replace option maintains the
original length of an AS path, which can be important when the AS path
length is used in route selection. The option to remove or replace private
ASNs can be configured independently for each address family (IPv4 or IPv6).
Templates
Dell EMC Networking BGP supports configuration of neighbor parameters in
named peer templates. A template defines a set of peer parameters. Multiple
peers can inherit parameters from a template, eliminating the need to repeat
common configuration for every peer. A neighbor can inherit from a single
template. BGP accepts configuration of up to 32 templates.
Neighbor configuration parameters can be divided into two groups, session
parameters and policy parameters. Session parameters apply to the peering
session. Session parameters include configuration options such as keep-alive
and hold timers. Policy parameters are specific to the routes for an address
family (e.g., IPv4 and IPv6), such as the maximum number of routes accepted
from a peer or prefix lists used to filter routes received from or sent to a peer.
Peer templates allow both session parameters and policies to be configured
within the same template. With a template, policy parameters are configured
for a specific address family.