Border Gateway Protocol (BGP) Data Center Enhancements

Supported Platforms

Summit X450-G2, X460-G2, X670-G2, X770, and ExtremeSwitching X620, X440-G2 series switches

Limitations

• Support for maximum AS-Path length is on a BGP instance basis, not per peer.
• Enabling the capability to carry IPv6 Network Layer Reachability Information (NLRI) over IPv4 peering sessions and IPv4 NLRI over IPv6 sessions does not include the ability to have mismatching next-hops. You must use outbound route-policy to specify the BGP next-hop value to be a reachable subnet for the remote router or the remote router must have a means to reach the next-hop. For IPv6 NLRI carried over IPv4 peering sessions, in the absence of route policy to set the next-hop, the next-hop is automatically set to the mapped IPv6 address based on the IPv4 address of the outgoing interface. You should either override this with policy or program the downstream router with a static route to reach the mapped address. In either case, it is assumed the VLAN interface used for peering is configured with both IPv4 and IPv6 addresses.
• The ability to carry mismatching NLRI applies to the Unicast, Multicast, and VPNv4 Sub-Address-Families (SAFIs). The VPNv6 SAFI is not supported.

New CLI Commands

configure bgp maximum-as-path-length max-as-path

Changed CLI Commands

The following command now accepts 64 ECMP paths for max-paths:

configure bgp maximum-paths max-paths

The following commands now allows you to enable the capability to carry NLRI of address family indicator (AFI)/SAFI combinations even if the specified AFI does not match the address family of the peering sessions:

enable bgp neighbor ipv4 capability ipv6-unicast

enable bgp neighbor ipv6 capability ipv4-unicast