Dell N3200-ON Networking N-Series Switches User Guide version 6.8.0 - Page 1369

Table 38-3. Session Parameters in BGP Peer Templates-Configurable Per-Address Family Parameter remove-private-as route-map route-reflector-client send-community Description Remove private ASNs from AS_PATH when sending to inheriting peers. Configure a route map for the peer. Configure a peer as a route reflector client. Configure this peer to send BGP communities. The BGP protocol now supports address families IPv4 and also IPv6. You can configure the protocol to run in the default VRF or in configured non-default VRF. You can apply the configuration in distinct modes based on the applicability. All instances of the BGP routers across all the VRFs can use the same AS number. Use the global BGP router mode to configure the AS number, router-id and templates definition. The peers and neighbors can inherit these templates across all the VRFs. When using inherit or when learned using listen-range, activate is derived from a template without an explicit activate command. A peer configuration change is rejected when the neighbor is learned using a listen range. When a new remote-as is configured, or a remote-as is changed, an explicit activate using a command is needed. Resolving Interface Routes In Dell Networking, the next hop of a route is always a set of next-hop IP addresses. Dell 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 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. BGP 1369