> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reviewing MVE Connection Settings in Arista VeloCloud SD-WAN

> This help topic describes how to review your MVE connection settings integrated with Arista VeloCloud SD-WAN through the console and the CLI.

export const Image = ({src, alt = '', caption, width, height, shadow}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Image -';
  if (typeof src !== 'string') {
    src = String(src);
  }
  if (!src || src === 'undefined') {
    console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
    return <></>;
  }
  const img = <img className={['mega-image-style', shadow ? 'shadow' : ''].join(' ')} src={src} alt={alt} width={width} height={height} style={{
    display: 'block'
  }} />;
  return caption ? <figure>
      {img}
      <figcaption style={{
    textAlign: 'center',
    width
  }}>{caption}</figcaption>
    </figure> : img;
};

You can review your MVE connection settings through Orchestrator 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.

<Image src="/images/cloud/mve/vmware/google/orch-bgp-summary-gcp.png" alt="BGP Settings" shadow={true} width={800} />

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@162.43.144.9`

2. Check the interface configuration.

   ```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
   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 169.254.11.18/30 brd 169.254.11.19 scope global eth2.1000
   ```

   <Note>
     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).
   </Note>

3. Ping the remote end.

   ```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
   edge:megaport-demo-1:~# ping 169.254.11.17
   PING 169.254.11.17 (169.254.11.17) 56(84) bytes of data.
   64 bytes from 169.254.11.17: icmp_req=1 ttl=63 time=29.5 ms
   64 bytes from 169.254.11.17: icmp_req=2 ttl=63 time=28.7 ms
   64 bytes from 169.254.11.17: icmp_req=3 ttl=63 time=32.6 ms
   64 bytes from 169.254.11.17: icmp_req=4 ttl=63 time=34.2 ms
   64 bytes from 169.254.11.17: icmp_req=5 ttl=63 time=28.6 ms
   64 bytes from 169.254.11.17: icmp_req=6 ttl=63 time=28.6 ms
   ^C
   --- 169.254.11.17 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.

   ```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
   edge:megaport-demo-1:~# debug.py --bgp_view_summary
   show ip bgp summary
   ===================

   BGP view name 0
   BGP router identifier 192.168.1.1, 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
   169.254.11.17   4      64512    2762    2694        0    0    0 22:25:07            1

   Total number of neighbors 1
   ```