Ordering a new Megaport configured in a Link Aggregation Group (LAG)
When ordering a new Megaport (10Gbps or greater) you may request the configuration of this port to be such that it will enabled with Link Aggregation Group (LAG) support. Umbrella terms used to describe the method include port trunking, link bundling, and channel bonding. Note that there exist both proprietary vendor standards as well as the vendor-independent Link Aggregation Control Protocol (LACP) for Ethernet standard as defined in IEEE 802.1AX or previous IEEE 802.3ad standards.
The protocol that Megaport will configure to allow LAG will be Link Aggregation Control Protocol or LACP (only).
A LAG configures one or more physical ports together to make a single aggregated data path, so as to implement traffic load sharing among the member ports in the group to enhance overall connection reliability. Multiple ports in a LAG configuration, with multiple physical cross-connects reduce potential single points of failure such as SFP/optics and structured as well as patch cabling paths.
The simplest LAG is a Single Port LAG which configures the device on the Megaport side to run LACP on this single channel. There is no added resilience provided by this configuration however it is (in most cases) possible to add additional ports in future when port capacity or status of the traffic (eg moving from development to production) dictates that the additional resilience is required.
An existing Megaport can not be converted to a LAG (single port or otherwise) via this process. Should you require this conversion you will need to lodge a support ticket either via email or portal chat functionality. Note that you will need to have an EMPTY (no VXCs or IX services) on the port in order for this conversion to occur.
Note: when adding ports to a live LAG, the new port or ports are automatically assigned the same location, speed and Marketplace visibility as the rest of the LAG.
Up to 8 physical ports can be bonded together into a single LAG. The available total bandwidth of a LAG is the sum of all constituent ports that comprise that LAG. Note however that any single VXC will still be limited to the maximum bandwidth of any single port in the LAG.
NOTE FOR IX connections within same Metro
Note that in the above that VXCs are limited to no greater than the maximum bandwidth of any single port in a LAG, however with local (same metro) IX services these are not bound to the VXC convention and may be configured to utilise the total amount of bandwidth capacity from all members in a LAG. This is the only type of connection that is supported to load-share equally across all LAG members and does not apply when a VXC is used to extend to/from an IX connection outside of the local metro aggregation.