Skip to content
Megaport ONE Documentation
SD-WAN Management Connectivity

Troubleshooting MVE Connectivity to SD-WAN Management

Step through these troubleshooting actions to review, investigate, and confirm the SD-WAN configuration and components.

Troubleshooting actions

Action Steps
Verify MVE/SD-WAN configurations 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.
    The BFD protocol detects any path failures between directly connected BGP neighbors, allowing for a faster BGP routing re-convergence time.     sessions, bandwidth, BGP status, and BGP neighbor status.
For more information about Megaport ONE SD-WAN providers, see Introducing MVE.
Verify MVE public IP address and gateway IP address in Transit VXCAs part of the MVE provisioning, Megaport ONE creates a transit Virtual Cross Connect (VXC) to provide internet connectivity and to allow MVE to register and communicate with the SD-WAN overlay network. details Each MVE is assigned a public IP address by a Megaport ONE configured DHCP server. To check the assigned IP address:
  1. From the Megaport ONE Portal, go to the Services page and locate your target MVE.
  2. Click the Transit VXC to select it (always the first VXC under the MVE), and the public IP address assigned to the MVE appears.
PingA ping test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. tests from MVE Run ping 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.

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 instance, if you set up loops, note where they were located and their direction. If you ran ping tests, provide the output.

Note

When a field service technician is needed onsite at the data center, see Customer Field Services for details.

Last update: 2023-09-26