Skip to content
Megaport Documentation
Overview

Internet Exchange Overview

Megaport owns and operates a series of Internet peering exchanges (IXs) in the majority of our global networks. IXs provide greater efficiency between networks and allow traffic to be exchanged directly, reducing latency and bandwidth usage on client Internet connections.

There are two main types of IX peering arrangements:

  • multilateral - Multilateral peering (MLPA) is the default when you connect to MegaIX. With multilateral peering, you use BGP to peer with both route servers (RS1 and RS2) for an IX market, you advertise your routes to the route servers, and all routes available from all other multilaterally peered connections are advertised to your peer from the route servers.
  • bilateral - The second type of peering is bilateral peering (BLPA). This method is required for peers that do not participate in multilateral peering through the route servers and establishes a direct peering relationship with another entity on the exchange. You can participate in both multilateral and bilateral peering across the Megaport IX infrastructure.

If you are connecting to an AMS-IX location, see AMS-IX Connectivity.

Before joining an IX, ensure that you can meet the requirements.

To join an Internet Exchange for Megaport and MegaIX locations

  1. In the Megaport Portal, go to the Services page and select the Port you want to use.
    If you haven’t already created a Port, see Creating a Port.

  2. Add an IX connection for the Port.
    Click +Connection, click Internet Exchange, and click Next.
    Add IX connection

  3. Select the IX location and click Next.
    IX location

  4. Specify these connection details:

    • Connection Name – The name of your VXC to be shown in the Megaport Portal.

    Note

    Partner managed accounts can apply a Partner Deal to a service. For more information, see Applying a Deal to a Service.

    • Service Level Reference (optional) – Specify a unique identifying number for the VXC to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.

    • Rate Limit – This is the speed of your connection in Mbps. The rate limit for an IX cannot exceed the aggregate port speed for metro connections, and 10 Gbps for non-metro connections.
      Connection details

  5. Click Next.

  6. Specify these IX details:

    • Preferred VLAN – Optionally, specify an unused VLAN ID for this connection. The VLAN ID must be unique on this Port and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN ID. Megaport validates the VLAN ID before proceeding with the order. If you don’t specify a value, Megaport will assign one. You can also select the toggle to Untag this connection. This selection removes the VLAN tagging for this connection but limits you to only one IX (or VXC) on this Port.

    • ASN – The autonomous system number (ASN) of your network. The ASN can be either a 16-bit or 32-bit ASN (2 or 4 byte) but must be a public AS. You cannot change the ASN after deployment.

    • MAC Address – The MAC Address of the Layer 3 device that will establish the BGP peering session with the IX. Connections to the IX on this VXC will be locked to this address for security purposes. If you do not have the correct MAC available at the time of ordering, enter a placeholder MAC (such as 00:01:00:01:12:34) as this field remains editable after deployment.

    • BGP Password – Optionally, add a BGP password to the VXC. This field can be left blank. You cannot change the BGP password after deployment.

    • Graph Visibility – Specify how to display your traffic graphs in the MegaIX Looking Glass tool within the Megaport Portal. Public lets other clients see your IX throughput; Private hides this information from other clients.

    • Peer Macro – An optional field that only appears for ECIX connections. The peer macro value defines the AS macro filter for the peer. Megaport uses this value to generate a list of prefixes this AS can originate, and this list filters announcements through the route server.

      Another name for this field is AS-MACRO (or AS-SET) as it contains a list of AS numbers belonging to this peer.

      If you don’t have a Peer Macro, you can enter your ASN in this field (You can only send routes that originate from your own AS). Invalid prefixes won’t be announced by the route server and an incorrect configuration results in the route server rejecting all your prefixes.

      If not specified, your own ASN will be used in the filter and you can only send routes that originate from your own AS and prefixes registered to that AS.

    • Invoice Reference – This is an optional field. It can be any text, such as a PO number or billing reference number.
      IX service details

  7. Click Next.
    A summary page appears that includes the monthly cost. Click Back to make changes or click Add IX to move this configuration to your cart and proceed through the checkout process.

    After deployment, Megaport sends an email to your registered email address with additional information on how to finish the BGP configuration.

Looking Glass

Megaport operates a public, web accessible MegaIX Looking Glass for peers and network operators to investigate the current routing state. You can query both the primary and redundant route servers for live BGP data. The MegaIX Looking Glass is available at https://lg.megaport.com.

IX requirements

Before configuring your IX connection, ensure that you meet these requirements:

  • Permitted traffic types – All frames forwarded to the Internet Exchange must be Ethernet II (DIX), using ARP (0x0806), IPv4 (0x0800), or IPv6 (0x86DD) Ethertypes.

  • First ASN – In a standard BGP configuration the first ASN in the path will match the peer ASN. In multi-lateral peering, the first ASN is the downstream peer that provides the routes. This reduces AS path lengths for correct routing decisions. To permit multi-lateral peering, configure your devices so they do not enforce the first AS requirement. For example, on a Cisco router the command is no bgp enforce-first-as.

Note

To prevent members from sending all the internet routes to Megaport, we limit the number of prefixes (MaxPFX) that Megaport can receive. The default limit is 1000 IPv4 routes and 100 IPv6 routes. Exceeding this value results in ending the session, however you can contact Megaport support if you require a reset.

Illegal traffic types

The following frames are not permitted on the Internet Exchange:

  • Multiple MAC addresses – ECIX operates on the principle of one router per port, meaning that frames must have the same source MAC address behind each port in each VLAN. Some members connect through intermediate switches or use a Layer 2/Layer 3 hybrid device. If these devices are not configured properly they can cause forwarding loops, STP instabilities, and unwanted traffic on the Exchange.

  • Multicast and broadcast (with the exception of ARP and IPv6 neighbor discovery) – Only exchange unicast routes over your BGP sessions in the Peering LANs. Multicast traffic is not permitted on (unicast) Peering LANs.

  • Frames from Proxy ARP – Peering VLAN traffic is exchanged based on BGP routes, so it is unnecessary to answer ARP queries for any IP addresses other than those configured on your ECIX interface. Some vendors enable Proxy ARP by default, which can lead to unwanted traffic on your network. If you have Proxy ARP enabled at ECIX, it is likely to be enabled at other peering points, which allows parties on both sides to use you as a transit.

  • LLC/SNAP (Subnetwork Access Protocol) frames – LLC/SNAP encapsulation (802.2) is not permitted because the IX infrastructure is based on the Ethernet II standard.

  • STP (Spanning Tree) – Devices connected to the ECIX port are not permitted to be visible as Layer 2 bridges, and should not use STP or any other proprietary L2-specific protocol.

  • Vendor discovery protocols (CDP, EDP, FDP, MNDP) – Some vendors (e.g. Cisco and Extreme Networks) run discovery protocols by default. Running discovery protocols should be avoided as it can cause unwanted broadcast or multicast traffic.

  • Internal routing protocols (OSPF, EIGRP, IGRP, and ISIS) – BGP is the only routing protocol permitted on the Peering VLANs. Interior routing protocols only cause unnecessary multicast and broadcast traffic.

  • Cisco Layer 2 keepalives – By default, Cisco routers and switches periodically test their Ethernet links by sending out loopback frames (Ethertype 0x9000) addressed to themselves. In a switched environment, this tests the functionality of the switch and keeps the router’s MAC address in the switch’s address table. In the ECIX environment, this is not useful because MAC timeouts are longer than the typical BGP or ARP timeouts.

  • Non-unicast IPv6 (IPv6 ND-RA) – IPv6 hosts on the ECIX are not autoconfigured, and can cause IPv6 router advertisements to generate unnecessary traffic.

  • Non-unicast IPv4 (IGMP, DHCP, TFTP) – Do not configure multicast on the ECIX interface. The Peering LAN is for unicast IP traffic only. The only permitted non-unicast traffic is an ARP query.

  • Trunking protocols – On Cisco Layer 2 devices such as the 2900 and 3500 series, disable VTP (VLAN Trunking Protocol), DTP (Dynamic Trunking Protocol), LLDP, and UDLD.

  • Non-IP protocols – Some vendors enable protocols other than IP by default. For example, in some versions of IOS Cisco enables MOP (Maintenance Operation Protocol). Non-IP traffic is not appropriate for the ECIX environment.

Important

Megaport impose a set of restrictions to ensure smooth operation of the MegaIX. Megaport reserves the right to temporarily disable offending services in order to maintain the health and stability of the MegaIX.

Exceptions

Link-local protocols ARP and IPv6 ND (Neighbor Discovery) are exceptions, and are permitted.

Additional considerations

There are some considerations when thinking about configuring an IX peering arrangement:

  • MegaIX route servers do not recognize the BGP community attribute no-export. This community attribute is passed transparently to the other peers connected to the route server.

  • Multiple Exit Discriminator (MED) values are considered in the route selection rules only when the advertising ASN is the same for candidate routes. MED values are not modified by the route servers. Values advertised to the route servers are passed unaltered to other peers.

  • All routes on the IX are given equal local preference by the route servers. The route servers do not compare the BGP router ID for best route selection, instead preferring the oldest route when all other attributes are equal.

  • Do not configure “network 194.146.118.0/24” or any of the other peering LANs in your router’s BGP configuration.

Helpful resources

Last update: 2022-07-25