Fabric Addressing Policy

CAUTION:

After IPv6 has been enabled in a blueprint, it cannot be disabled. Although, you could use Time Voyager to rollback to a revision before IPv6 was enabled.

Enabling support for IPv6 virtual networks on EVPN L2 deployments or L3 deployments adds resource requirements and device configurations. This includes IPv6 loopback addresses on leaf devices and spine devices, IPv6 addresses for MLAG SVI subnets and IPv6 addresses for leaf L3 peer links. The following caveats apply:

• This feature does not include IPv6 support in the fabric.
• IPv6 support is not available on non-EVPN L2 networks.
• When IPv6 is enabled on EVPN L2 deployments, security policy functionality is not available.

To enable ESI (EVPN) LAG multihoming, an Ethernet segment identifier (ESI) is mandatory. ESIs identify ESI LAGs. Apstra automatically generates ESI MAC addresses using most significant byte (msb) values. Configuration of the ESI value is rendered as 10 octets. The first octet is 0. The second octet is the most significant byte value. To ensure that multicast MACs are not generated, the second octet must be an even number between 0 and 254. The second through sixth octets are used as the LACP system ID. The example below is of a rendered ESI value and its respective LACP system id:

The msb value in each Apstra blueprint defaults to the value 2. If you aren't connecting blueprints (IP fabrics) you can leave the value as is. If you're connecting blueprints via data center interconnect (DCI) and ESI, then each blueprint must have a unique most significant byte. Change the msb values so they are unique across the multiple blueprints.

CAUTION:

Updating the Most Significant Byte (MSB) value regenerates all existing ESI MACs in the blueprint.