41
LACP for crossconnects
future consideration
James Malachowski
Support the ability for customers to create LACP bonds for cross connect ports into Metal. Currently cross connects require unique vlans per port which can in many cases require customers to run routing protocols for high availability (eg BGP). Enabling LACP would allow customers to run high-performance physical firewalls and storage in Colo in front of metal instances in HA.
Log In
R
Raj Venkat
future consideration
The common use case for LACP for cross-connects is for port redundancy across a pair of edge devices (aka multi-chassis LACP) for native Layer 2 extensions to cross-connect or Fabric. However, this feature is not expected to be supported at this time. The recommendation is to use Layer 3 redundancy with BGP using Metal's upcoming VRF feature.
R
Raj Venkat
R
Raj Venkat
planned / on deck
Planned. Initial target is for up to 8 members in a single LAG group.
Raj Venkat
Target for Q4'22
Glenn Dekhayser
Large client (Allegis) requested this, not having it may result in them pursuing an alternate solution (colo, etc).
Zain Mujtaba
Yes, additionally if we can get LACP that is multi-chassis and both ports are not terminated on the same switch