Link Aggregation (LACP) Support on Dedicated Servers
Our network fully supports IEEE 802.3ad Link Aggregation Control Protocol (LACP). This means that your server can have redundant network uplinks. By default, it operates on a single uplink.
What you get with LACP
- Higher availability: traffic keeps flowing if one physical link goes down.
- Scalability: capacity can be distributed across multiple links.
- Standards-based: uses IEEE 802.3ad, widely supported by OSes and hypervisors.
How our network is configured
- Ready for LACP: switch ports facing your server are LACP-capable.
- Works without LACP: if you prefer a single uplink (no bonding), your connectivity will still work normally.
Requirements on your side
- Your operating system or hypervisor must support 802.3ad (LACP) link aggregation.
- Use two physical NIC ports from your Intel X520 adapter for the team/bond.
- Plan for a single team/bond MAC address exposed to the network (common with LACP).
Security note: To protect the network, public IPs are allowed only for approved MAC addresses. If you enable LACP, create new teams/bonds, add extra NICs, or run VMs/containers with their own MACs, please open a ticket so we can authorize them before use.
What to send us (for fastest setup)
- Server ID/Hostname
- Intended mode: “802.3ad (LACP)”
- Bond/team MAC address (if known)
- Any additional MACs that will need public IP access (e.g., for VMs)
FAQ
Do I have to use LACP?
No. A single-port (non-bonded) setup works fine and is fully supported.
Need help?
Open a support ticket with the details above. We’ll verify switch-side settings and MAC authorization to ensure a smooth turn-up.