Reviewing MVE Connection Settings in VMware SD-WAN

You can review your MVE connection settings through the VMware console and the CLI.

In Orchestrator, under Test & Troubleshoot > Remote Diagnostics, select the MVE and click Run for Troubleshoot BGP - Show BGP Summary to verify the BGP session and ensure the remote router is up.

BGP Settings

You can also check connectivity and BGP status from the CLI of the edge device.

  1. SSH to your MVE using the SSH keypair you provided during MVE creation.

    ssh -i megaport-mve-instance-1-2048 root@

  2. Check the interface configuration.

    edge:megaport-demo-1:~# ip addr list | grep eth2.1000
    22: eth2.1000@eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    inet brd scope global eth2.1000


    Interface numbering on the CLI differs from the Orchestrator console. In the CLI, interface numbering begins at 0 so the corresponding CLI interface for GE3 is eth2. The number following eth2 is the subinterface ID (the A-End VLAN ID).

  3. Ping the remote end.

    edge:megaport-demo-1:~# ping
    PING ( 56(84) bytes of data.
    64 bytes from icmp_req=1 ttl=63 time=29.5 ms
    64 bytes from icmp_req=2 ttl=63 time=28.7 ms
    64 bytes from icmp_req=3 ttl=63 time=32.6 ms
    64 bytes from icmp_req=4 ttl=63 time=34.2 ms
    64 bytes from icmp_req=5 ttl=63 time=28.6 ms
    64 bytes from icmp_req=6 ttl=63 time=28.6 ms
    --- ping statistics ---
    7 packets transmitted, 6 received, 14% packet loss, time 6008ms
    rtt min/avg/max/mdev = 28.629/30.413/34.279/2.232 ms
  4. Check the BGP status.

    edge:megaport-demo-1:~# --bgp_view_summary
    show ip bgp summary
    BGP view name 0
    BGP router identifier, local AS number 65135
    RIB entries 1, using 112 bytes of memory
    Peers 1, using 4568 bytes of memory
    Neighbor        V         AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd   4      64512    2762    2694        0    0    0 22:25:07            1
    Total number of neighbors 1

Last update: