Megaport Internet Routing Guide
This topic describes standard Megaport Internet configuration and how you can configure Border Gateway Protocol (BGP)Border Gateway Protocol (BGP) is a standardized routing protocol designed to exchange route and reachability information among autonomous systems (AS) on the internet.
on Megaport Internet VXCs.
Megaport InternetMegaport Internet connections are scalable, on-demand services that allow you to connect to the internet from Ports, MCRs, and MVEs. As part of the MVE provisioning, you create a Megaport Internet connection to provide connectivity and to allow MVE to register and communicate with the SD-WAN overlay network.
is available for PortsA Port is the high-speed Ethernet interface that connects to Megaport’s global software-defined network (SDN). Ports are available in 1 Gbps, 10 Gbps and 100 Gbps speed options.
, MCRsThe MCR is a managed virtual router service that establishes Layer 3 connectivity on the worldwide Megaport software-defined network (SDN). MCR instances are preconfigured in data centers in key global routing zones. An MCR enables data transfer between multicloud or hybrid cloud networks, network service providers, and cloud service providers.
, and MVEsThe MVE is an on-demand, vendor-neutral Network Function Virtualization (NFV) platform that provides virtual infrastructure for network services at the edge of Megaport’s global software-defined network (SDN). Network technologies such as SD-WAN and NGFW are hosted directly on Megaport’s global network via Megaport Virtual Edge.
in selected countries. For the latest information on Megaport Internet availability, see Locations available. You can access the product by ordering a Megaport Internet connection to a Megaport internet router.
Multiple diversity zones are available in all metros where Megaport Internet is available. For maximum resiliency, you should connect to both zones by matching red-to-red and blue-to-blue. Additional resiliency is available by connecting to Megaport Internet in an additional nearby metro. For more information, see Port Diversity and MCR and MVE Diversity.
All Megaport Internet VXCs are assigned IPv4 and IPv6 addresses as standard and configured as follows:
-
/31 Point-to-point IPv4 network
-
/64 Point-to-point IPv6 network
-
DHCPDynamic Host Configuration Protocol (DHCP) is a client/server protocol that automatically provides an Internet Protocol (IP) host with its IP address and other related configuration information such as the subnet mask and default gateway.
is enabled for IPv4 and will permanently offer the same static IPv4 address. -
IPv6 router advertisements are enabled for SLAAC-capable IPv6 clients.
-
It is not required to use the dynamic address assignment methods. The address information is also available in the Megaport Portal and you can configure your equipment with static addresses from the assigned range.
-
Megaport adheres to BCP 38. Packets sent to Megaport must have a valid source address in the assigned IPv4 or IPv6 ranges.
-
To protect against abuse of Megaport IP address space for the sending of spam, Megaport filters outgoing connections to TCP port 25 when the source address is a Megaport-owned IP address. Customer-supplied address space is not filtered. Exceptions for specific IP addresses can be made upon request, with valid justification.
Additional IP addresses
-
Megaport can assign one or more additional IP address blocks to customers who can demonstrate a genuine requirement. There is a fee per IP address.
-
Megaport-assigned IP address space must be advertised only on Megaport Internet VXC services. Advertising these networks to other Megaport services or third party providers is forbidden.
Enabling BGP
You can request BGP on new and existing Megaport Internet VXCs. With BGP enabled:
- Customers might advertise Megaport assigned IP blocks or their own provider independent IP addresses (see BGP filtering).
-
Megaport configures an IPv4 and IPv6 BGP neighbor.
-
Megaport uses the first IP address and configures the BGP neighbor as the second IP address in the point-to-point network.
-
You can optionally provide a BGP password.
-
Source address filtering permits only Megaport assigned IP addresses and prefixes that customers have provided for advertisement over BGP.
-
Megaport sets a minimum BGP hold timer of 20 seconds. A BGP connection will not establish if you configure a value lower than this on your router.
Note
BFDBidirectional Forwarding Detection (BFD) is a network fault detection protocol that detects any path failures between directly connected BGP neighbors. It provides fast failure detection times, which facilitates faster re-convergence time for dynamic BGP routing protocols. It is independent of media, routing protocol, and data.
is not currently supported with Megaport Internet.
To enable BGP on new and existing Megaport Internet VXCs
- Provide a BGP AS Number - Submit a valid BGP Autonomous System (AS) number.
- Validate Route Objects - Ensure that valid route objects are created in the appropriate Regional Internet Registry (RIR) or Routing Assets Database (RADb) for all advertised networks.
- Submit a Letter of Authorization (LOA) - Provide an LOA for your public IPs.
-
Specify Routing Table Requirements - Indicate your routing preferences, such as:
- Full table (DFZ)
- Metro and peering routes
- Default route only
Note
This feature requires manual approval and can be organized by contacting your local Support team. For more information, see Contacting Support.
BGP filtering
You can optionally provide a list of IPv4 and IPv6 prefixes that you want to advertise.
-
Prefixes must be publicly assigned addresses and owned by the customer, or the customer must provide an LOA from the owner authorizing their use.
-
Prefix length must be between /12 and /24 for IPv4 prefixes.
-
Prefix length must be between /24 and /48 for IPv6 prefixes.
Megaport will filter out any advertised prefixes not listed.
Megaport performs RPKIResource Public Key Infrastructure (RPKI) is a public key infrastructure framework that is designed to support improved security for the internet’s Border Gateway Protocol (BGP) routing infrastructure. RPKI provides a way to connect internet number resource information (such as Autonomous System numbers and IP addresses) to a trust anchor.
filtering. Invalid routes are filtered. For more information, see RPKI.
Megaport automatically permits longer prefixes down to /32 for IPv4 and /128 for IPv6 in our filters. This allows you to share a single /24 (IPv4) or /48 (IPv6) route across multiple Megaport Internet services in the same metro area.
Prefixes longer than /24 and /48 are not exported to external neighbors.
The maximum number of BGP prefixes accepted is 4x the number of registered prefixes to allow for limited traffic engineering using more specific routes.
Customer prefixes will not be learned from Megaport peer autonomous systems.
Megaport sets a high local-preference on customer BGP routes.
Route objects must be created with the relevant Regional Internet Registry (RIR) or Routing Assets Database (RADb) for all networks, regardless of whether the network uses private or public ASNs. For statically routed networks or private ASNs, route objects must specify the origin of AS49915.
Note
Upstream filters can take up to 48 hours to update after the service has been configured. During this period, newly created or modified routes might not propagate to the internet completely.
Advertised routes
You can choose from four options, with an increasing number of routes. If you do not specify your preferred option, Megaport will only advertise a default route.
Routing options:
-
Default Route: A locally originated default route (one route).
-
Customer Routers: In addition to the above, this includes the routes of Megaport customers.
-
Customer and Peer Routes: In addition to the above, this includes the routes of Megaport peers.
-
Full Routes: A complete Internet routing table (>900,000 routes).
Megaport internal communities and private communities are removed from outbound route announcements.
Traffic engineering communities
You can set these communities to influence the advertisement of your routes to other neighbors.
TE communities are stripped on egress.
Large Community | Standard Community | Action |
---|---|---|
49915:65000:0 | 65000:0 | Do not export |
49915:65000:ASN | 65000:ASN | Do not export to ASN |
49915:65001:0 | 65001:0 | Prepend once |
49915:65001:ASN | 65001:ASN | Prepend once to ASN |
49915:65002:0 | 65002:0 | Prepend twice |
49915:65002:ASN | 65002:ASN | Prepend twice to ASN |
49915:65003:0 | 65003:0 | Prepend three times |
49915:65003:ASN | 65003:ASN | Prepend three times to ASN |
49915:65010:0 | 65010:0 | Advertise with no-export |
49915:65010:ASN | 65010:ASN | Advertise with no-export to ASN |
Using private AS numbers
Megaport supports BGP for customers that do not have a public AS number, using private AS numbers.
You can choose your ASN from either the 2-byte or 4-byte private ranges.
Important
Megaport does not allow customers, whether using private or public AS numbers, to provide transit for downstream AS. All routes must originate from the directly connected AS.
All routes Megaport advertises upstream will have private AS numbers stripped from the AS path. This might result in Megaport appearing to be the origin of the prefix. If the network owner has published RPKI ROA records, you might need to create additional ROAs permitting Megaport AS49915 to advertise the route.
Helpful references
- Port Diversity
- MCR and MVE Diversity
- Creating a Megaport Internet Connection for a Port
- Creating a Megaport Internet Connection for an MCR
- Creating a Megaport Internet Connection for an MVE
- Monitoring Ports, VXCs, Megaport Internet, and IXs
- Troubleshooting Megaport Internet Connectivity
- Creating a Megaport Internet Connection with the API
- Terminating a Megaport Internet Connection