The switch includes a new CLI command to optimize EAPS (Ethernet Automatic Protection Switching) convergence performance in large-scale deployments by providing configurable FDB flush methods.
Issue: In scaled EAPS environments with many shared-port links, protected VLANs, and EAPS domains, convergence events such as link failures or node reboots generate significant numbers of FDB flush operations. By default, the switch performs VLAN-and-port-based FDB flushing, which sends individual flush requests for each protected VLAN on the affected ring ports. As the number of protected VLANs and EAPS domains increases, the volume of FDB flush messages sent to hardware increases, potentially delaying convergence time.
Resolution: The switch supports port-based FDB flushing. This method performs a single port-level flush for all VLANs on the affected ring port, significantly reducing the number of hardware flush messages and improving convergence performance in large-scale EAPS deployments.
Key Capabilities:
Configure the FDB flush method for EAPS convergence events:
configure eaps flush-method [port-based | vlan-and-port-based]
Parameters
port-based — Flushes FDB entries on EAPS ring ports for all VLANs. Use this method for deployments with hundreds of protected VLANs and multiple EAPS shared-port links to reduce the number of flush messages sent to hardware.vlan-and-port-based — Flushes FDB entries only for EAPS-protected VLANs on the affected ring ports. This is the default behavior and works well for deployments with moderate numbers of protected VLANs.Example:
configure eaps flush-method port-based
When you enable port-based flushing, the switch flushes FDB entries for all VLANs on the affected ring ports during convergence events. Temporary flooding occurs for both EAPS-protected and non-protected VLANs traversing those ring ports until the switch relearns forwarding entries. This trade-off is acceptable in large-scale deployments where convergence time is the priority.
VLAN-and-port-based flushing does not cause flooding for non-protected VLANs but generates more flush messages to hardware, making it less suitable for deployments with large numbers of protected VLANs and EAPS domains.
All platforms.