action.skip
Megaport Documentation
Megaport Internet
PDF

Troubleshooting Megaport Internet Connectivity

A Megaport Internet connection is required for MVE provisioning, and can also be created for Ports and MCRs. If your Megaport Internet connection cannot access the internet, step through these specific and general troubleshooting actions.

For more information, see Megaport Internet Routing Guide.

Troubleshooting actions

Action Steps
BGP-enabled Megaport Internet - Review the advertised routes checklist Confirm the following:
  • BGP ASN (public or private) has been provided.
  • Route objects have been created in the appropriate RIR or RADb for all advertised networks.
  • For private ASNs or statically routed networks, AS49915 is used as the origin.
  • Networks can be checked using tools such as BGP Tools by searching for the IP network and verifying that the Validation tab shows IRR database entries matching the provided ASN.
  • A Letter of Authorization (LOA) has been provided for public IPs, confirming the IP range and ASN match the LOA.
  • Upstream filters have been accounted for, with the understanding that they might take up to 48 hours to propagate after service configuration.
BGP-enabled Megaport Internet - Check maximum prefixes have not been reached If the prefix limit is exceeded, the BGP peer will shut down and not re-enable for 45 minutes.
To check the maximum prefixes are not reached:
  • Review the internet VXC logs to confirm whether the maximum number of prefixes has been reached.
  • Review and update the BGP export filters to reduce the number of prefixes.
Verify MVE/SD-WAN configurations Where the Megaport Internet connection is being used with an MVE, confirm this information:
  • Ensure SD-WAN login credentials are accurate.
  • Ensure the MVE has has the correct license and template/workflow.
  • Verify the instance size and software version.
  • Verify the MVE interface status, including configuration values for IP addresses and subnets, VLAN, bandwidth, and ASNs.
  • For gateway and interconnect connectivity, check 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.
     sessions, bandwidth, BGP status, and BGP neighbor status.
For more information about Megaport SD-WAN providers, see MVE Overview.
Verify MVE Public IP Address, Gateway IP Address in Megaport Internet connection details Each MVE is assigned a public IP address by a Megaport configured DHCP server.
To check the assigned IP address:
  1. In the Megaport Portal, go to the Services page and locate your target MVE.
  2. Click the gear icon next to the Megaport Internet connection and the public IP address assigned to the MVE appears.
Ping tests from MVE Run pingA ping test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices.
 tests from MVE to the following destinations:
  • MVE default gateway IP address
  • SD-WAN management server/controller
  • Public IP (for example, ns1.google.com, 8.8.8.8)
A ping test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. In the case of confirmation, a ping test shows the latency (the response time) of the connection.

If you need to contact Support about this issue, provide the results from the ping tests.
General troubleshooting tips For any service that has a Megaport Internet connection, perform these troubleshooting steps:
  • Try pinging the /31 address from anywhere to see if you receive a response.
  • Check the Transit router and make sure it’s online.

Next steps

If the troubleshooting actions do not resolve your issue, contact support. Before contacting support for assistance, collect the following information.

  • Provide details of all troubleshooting steps.
    For example, if you set up loops, note where they were located and their direction. If you ran ping tests, provide the output.

Note

For more information about when a field service technician is needed onsite at the data center, see Customer Field Services.