Skip to content
Megaport ONE Documentation
Google MVE Connections

Creating a Google Cloud Services Connection for an MVE with Versa Secure SD-WAN

You can create a network connection from an MVE with Versa Secure SD-WAN to Google Cloud through Partner Interconnect.

When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport ONE, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.

Important

Before you begin, create an MVE in Versa Director. For details, see Creating an MVE Integrated with Versa. The MVE needs to be in the active state.

There are three parts to adding a Google Cloud connection to your MVE and Versa Director.

  1. Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation. For additional details, see the Google documentation on Google Partner Interconnects.

  2. In the Megaport ONE Portal, create a VXC from your MVE to connect to your Google Cloud attachment.

  3. In Versa Director, create a new interface and add the details of the Google Cloud connection.

These instructions step through the second and third parts.

Note

MVE for Versa Secure SD-WAN requires configuration steps in both Versa Director and the Megaport ONE Portal for all cloud connections.

Adding the Google Cloud connection in the Megaport ONE Portal

To set up the Google Cloud Platform connection, you need to create the connection in the Megaport ONE Portal. If you haven’t already created an MVE, see Creating an MVE Integrated with Versa.

To deploy a VXC to GCP from the Megaport ONE Portal

  1. In the Megaport ONE Portal, choose Networking > Services.
  2. Click the gear icon Gear icon next to the MVE you want to use.

  3. Select Add Connection.
    Add Connection

  4. Specify the General connection details:

    • Connection Type – Select Cloud VXC.
    • Cloud Provider – Select Google Cloud. New Connection

  5. Specify the Google Configuration details:

    • Google Partner Pairing Key – Copy and paste the pairing key from the Google Cloud console. The relevant Google targets appear based on the region of your GCI Partner connection.
    • Available Google Ports – Select the target location for your connection.
      Google as the provider

  6. Specify the VXC Configuration details:

    • Connection Name – The name of your VXC to be shown in the Megaport ONE Portal.
    • Rate Limit – The speed of your connection in Mbps. The speed cannot be changed once deployed. Enter the same rate you selected for your Google port speed.
    • A-End VLAN – This is the VLAN for this connection that you will receive through the MVE. This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport ONE will assign one.

  7. Specify the Billing Details:

    • Service Level Reference (optional) – Specify a unique identifying number for the VXC to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.

      Note

      Partner-managed accounts can apply a Partner Deal to a service.

    • Monthly Price – The monthly rate is based on location and size.

    • Promo Code – If you have a promotional code, enter it and click Add Code.

  8. Click Create Connection.

  9. Review the new configuration and pricing then click Confirm.

  10. After you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept it.
    You will be provided your private IP address from Google to configure BGP.
    Ensure that you pre-activate the attachment or mark the attachment as active after configuring the VXC. Otherwise, you cannot set up BGP with your SD-WAN instance.

Note

The Google ASN will always be 16550.

Adding the Google Cloud connection to Versa Director

After you create the connection from your MVE to Google Cloud and set up the connection in the Google console, you need to configure it in Versa Director. This involves configuring BGP settings, ASNs, and VLANs.

To add the Google Cloud connection in Versa Director

  1. Collect the connection details from the Google console.
    Display the details of the connection you created in Google Cloud for this connection. Note the values for the Peer ASN, Cloud Router BGP IP, and BGP Peer IP.
    Google connection details

  2. Collect the connection details from the Megaport ONE Portal.
    Click the gear icon Gear icon for the Google connection from your MVE and select the Details tab. Note the value for the A-End VLAN.
    Next, you will add a subinterface to your Versa MVE instance.

  3. Log in to Versa Director.

  4. Select the Workflows tab in the top menu bar.
  5. Select Template > Templates in the left menu bar.
    Choose template
  6. Select the template you want to edit, then select the Interfaces tab.
  7. Under WAN Interfaces, click Add icon (Add) to add a subinterface.
    Add subinterface
  8. Provide the following information:
    • VLAN ID – Enter the A-End VLAN value for this Google connection in the Megaport ONE Portal. Click the Details icon for the connection in the Portal to find this value.
    • Network Name – Choose +Create WAN Network from the drop-down to open the Create WAN Network window. Specify a meaningful name for the network, click OK, and then select the WAN network you created. (Or, if appropriate for your environment, select an existing network name.)
    • IPv4 – Choose Static from the dropdown to assign a static IP address to this subinterface.
      Interfaces tab
      We have finished creating the interface. Next we need to create the BGP session.
  9. Select the Routing tab to add the BGP configuration information.
  10. In the BGP section, choose the network created earlier.
  11. Enter the following values for your connection:
    • Local AS – This is the Peer ASN value from the VLAN attachment details in the Google Cloud console.
    • Neighbor IP – This is the local Google Cloud IP address. This value is available in the VLAN attachment details in the Google Cloud console. The IP address appears in the Cloud Router BGP IP field.
    • Peer AS – This is the Google Cloud ASN of 16550. This is a fixed value, and appears in the connection details on the Google console.
    • Optionally, enable BFD (as appropriate for your network).
  12. Click Add icon (Add).
    Director BGP values
  13. Click Recreate.
    A screen appears that shows the differences in the configuration. The auto-merged version is recommended, and selected by default.
  14. Click Deploy.

At this point, we have updated the template assigned to the device group. Next, we will parameterize variables to generate routing information dynamically.

To parameterize the configuration variables

  1. Select the Configuration tab in the top menu bar.
  2. Select Templates > Device Templates in the horizontal menu bar.
    Device Templates
  3. Click the template you want to modify.
    By default, the Interfaces column appears.
  4. In the side navigation, select Virtual Routers, and click the link for the subinterface network to open the Edit window.
    Virtual Routers
  5. In the side navigation, select BGP, then click the Instance ID for your network.
  6. In the Edit BGP Instance window, click Parameterize icon (Parameterize) next to each of the following fields: Router ID, Local AS, Peer AS, and Password.
    Edit BGP Instance window
  7. Click OK two times to update.

Next we need to configure the device and create the BGP session.

To update parameterized variables for a device

  1. Select the Workflows tab in the top menu bar.
  2. Select Devices > Devices in the horizontal menu bar.
    Versa devices list
  3. Click the device to modify.
  4. Select the Bind Data tab.
    All parameterized values are displayed here.
    Bind Data tab
  5. Enter the following values for the variables:
    • Local AS number – The Customer ASN in the Megaport ONE Portal.
    • MD5 password – The BGP Auth Key in the Megaport ONE Portal.
    • BGP Peer AS – 16550, the Google Cloud ASN.
    • BGP Router ID – The Customer IP address (your local IP address) from the MVE details.
    • Next Hop Address – The Cloud Router BGP IP from the VLAN attachment details in the Google Cloud console.
    • Interfaces with Mask – The static IP address of the interface on the Megaport ONE side of the connection, including the mask value.
  6. Click Deploy to create the new configuration for the device.
    When the new configuration for the device has completed successfully, a green checkmark appears at the bottom of the Director window.
  7. In the upper right of the screen under your username, click Commit Template to push the changes to the device.
    Commit Template
  8. Specify the following values:
    • Organization – Select your organization from the drop-down.
    • Select Template – Select your template to display its associated devices in the table.
    • Differences – Click the eye icon in the Differences column to view the configuration to be applied to the device.
      Commit window
  9. If you are satisfied with the configuration, click Commit to Device.
    A green checkmark appears at the bottom right of the screen when the push is successful. The Template State and Appliance State are now IN_SYNC with the device.
  10. Close the window.

Validating your Google Cloud connection

You can review device status, including the connection state, from the Monitor tab in Director.

  1. Select the Monitor tab in the top menu bar.
  2. Select Devices in the horizontal menu bar.
  3. Click the device to view status and activity.
    Select device to monitor
    In the Summary screen you can review your subinterface in the Interface column, and the Operational and Admin Status.
    Monitoring details
  4. Return to Google Cloud Platform and refresh to see the new virtual interface.
Last update: 2023-09-22