Core Isolation feature shuts down ESI interface(s) when all the core interfaces between the Leaf and Spine nodes go down. During core-isolation, data traffic will be black-holed in the multi-homing nodes if the single homed edge port interfaces are present and the Ethernet VPN Instance VLANs are shared with these interfaces. These single homed edge port interfaces need to be brought up/down along with the ESI client interfaces for better data convergence. This command enables tracking these single homed edge port interfaces to ensure that they are brought up/down along with ESI client interfaces.
Core Isolation tracking is disabled by default. It has to be explicitly enabled using this command.
Interface Configuration Mode (for Ethernet and Port Channel interfaces only).
This command ensures that that the configured single homed edge port interface is brought down along with the ESI interfaces. When the BGP EVPN sessions come up, these tracked single homed edge port interfaces are brought up along with the ESI interfaces to have better data traffic convergence.
This feature is only available when ESI is configured on (at least) a single interface.
Core Isolation Tracking cannot be applied to an interface that is a port-channel member. That is, the interface must not have channel-group configuration present.
The interface on which Core Isolation Tracking is applied to, must not be a multi-homed client. Post this configuration, the tracked interface cannot be assigned as a PO member or a multi-homing client.
During firmware downgrade, core-isolation track configurations are removed.
The following example shows the configuration of Core Isolation Tracking on a port-channel interface.
SLX (config)# interface port-channel 1
SLX (config-Port-channel-1)# core-isolation-track
The following example shows the configuration of Core Isolation Tracking on an ethernet interface.
SLX (config)# interface ethernet 0/1
SLX (config)# core-isolation-track