6.1(2)

Support for eBGP multipath and addpath within the ACI fabric

With the eBGP multipath addpath functionalities you can now stretch eBGP peering directly to forwarding nodes and all the next-hops for an IP prefix publish all unique next-hops within the ACI fabric.

6.1(2)

Sub-optimal forwarding within anchor or non-anchor nodes

The Ignore IGP Metric knob has been introduced as part of the BGP best path policy for a VRF. You can configure this knob to ensure the sub-optimal forwarding of traffic within anchor or non-anchor nodes

5.2(4)

Support for using the same encapsulation for IPv4 and IPv6 floating SVIs for the same L3Out.

The same encapsulation can be used for IPv4 and IPv6 address families with the same VMM domain. While deploying a VMM domain, if both the address families are available, both are deployed.

5.2(3)

Support for using different external VLAN encapsulations, where all of the different external encapsulation instances are treated as part of a single Layer 2 domain

Support is now available where a single L3Out SVI/Bridge domain can be deployed across different leaf switches, with each leaf switch using a different VLAN encapsulation for the same SVI/Bridge domain.

5.2(1)

Next-hop propagation supported with OSPF and static routes redistributed in BGP

For releases prior to release 5.2(1), next-hop propagation is supported with BGP only. Beginning with release 5.2(1), next-hop propagation is also supported with OSPF and static routes redistributed in BGP.

Support for multiple next-hops to be propagated in the ACI fabric for redistributed routes in BGP

Support is available for multiple next-hops to be propagated in the ACI fabric for redistributed routes in BGP.

5.0(1)

Secondary IP and floating secondary IP

You can use a secondary IP as a common IP for anchor leaf nodes. A floating secondary IP enables additional floating IP subnets on the same floating SVI.

Physical domains

Physical domains enable you to use the floating L3Out feature with virtual routers without VMM domain integration or to use a physical router without L3Out logical interface path configurations.

Avoiding suboptimal traffic from ACI internal endpoints to floating L3Out

Prior to Cisco ACI Release 5.0(1), even if an external router is connected under a non-anchor leaf node, traffic from an ACI internal endpoint to a floating L3Out goes to an anchor leaf node and then goes to the external router through the non-anchor leaf node, which is not an optimal traffic path. Beginning in Cisco ACI Release 5.0(1), you can avoid this suboptimal traffic path by using next-hop propagation and direct-attached host route advertising.

4.2(1)

Floating Layer 3 outside network connection (L3Out) for VMware VDS Virtual Machine Manager (VMM) domains

This new feature enables you to configure an L3Out without the need to define a logical interface. Doing so allows a virtual device that requires routing (for instance, a virtual router) to move from one server to a different one. As a result, the virtual device also moves from one leaf switch to another.