Skip to content

Creating a Google Cloud Services Connection for an MVE with Palo Alto VM-Series

You can create a network connection from an MVE (a Palo Alto VM-Series) to Google Cloud through Partner Interconnect.

When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, 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.


Before you begin, create an MVE (VM-Series firewall). For details, see Creating an MVE. The MVE needs to be in the active state.

There are three parts to adding a Google Cloud connection to your MVE and VM-Series.

  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 Portal, create a VXC from your MVE to connect to your Google Cloud attachment.

  3. In VM-Series, create a new interface and add the details of the Google Cloud connection.

These instructions step through the second and third parts.


MVE for Palo Alto VM-Series requires configuration steps in both VM-Series and the Megaport Portal for all cloud connections.

Adding the Google Cloud connection in the Megaport Portal

To set up the GCP connection, you need to create the connection in the Megaport Portal.

To deploy a VXC to Google Cloud Platform from the Megaport Portal

  1. In the Megaport Portal, go to the Services page and select the MVE for the connection.

  2. Click +Connection and click the Cloud tile.

  3. Select Google as the provider.
    Google as the provider

  4. Copy and paste the pairing key from the Google Cloud console into the field in the right-hand pane.
    The relevant Google targets appear based on the region of your GCI Partner connection.

  5. Select the target location for your connection and click Next.
  6. Provide these connection details:

    • Connection Name – The name of your VXC to be shown in the Megaport Portal.


      Partner-managed accounts can apply a Partner Deal to a service. For details, see Associating a Deal With a Service.

    • Rate Limit – Enter the same rate you selected for your Google port speed.

    • Preferred 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 will assign one.

  7. Add the VXC to your order and complete the checkout process.

  8. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept the attachment.
    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.


The Google ASN will always be 16550.

Adding the Google Cloud connection to VM-Series

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 VM-Series. This involves configuring BGP settings, ASNs, and VLANs.

To add the Google Cloud connection in VM-Series

  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 ID.
    Google connection details

  2. Collect the connection details from the Megaport Portal.
    Click the gear icon for the Google connection from your MVE and click the Details view. Note the value for the A-End VLAN.

  3. Log in to the VM-Series.

  4. Choose Network > Interfaces.

  5. Select the A-End MVE (ethernet1/1).

  6. Click Add Subinterface.

  7. Provide these details:

    • Interface Name – Enter a name for the subinterface. In the adjacent field, enter a number to identify the subinterface.

    • Comment – Enter an alternate name.

    • Tag – Specify the A-End VLAN associated with this Google Connection in the Megaport Portal.

    • Virtual Router – Select a virtual router to the interface, as required by your network.

  8. Select the IPv4 tab.

  9. Select Static as the Type.
  10. Click +Add to add a new IP address.
  11. Enter the IPv4 address and netmask.
    These values are available in the VLAN attachment details in the Google Cloud console. The IP address appears in the BGP Peer IP field.
  12. Click OK.
  13. Click Commit in the top right corner.
    Commit button
  14. Review the changes and click Commit. Commit changes

The new VLAN interface appears with your ethernet1/1 physical interface.

Next, you will create a security zone so the interface can route traffic.

To create a security zone

  1. Select the ethernet1/1.1010 subinterface.
  2. Select New Zone from the Security Zone drop-down list.
  3. Specify a name for the security zone.
    Security zone settings
  4. Click +Add under Interfaces and add ethernet1/1.1010 to the security zone.
  5. Specify any additional details as required for your network security.
  6. Select New Zone Protection Profile from the Zone Protection Profile drop-down list.
  7. Specify any details as required for your network security. This example uses all the defaults.
    Zone Protection profile
  8. Click OK.
  9. Click OK in the Layer3 Subinterface screen.
  10. Click Commit in the top right corner.
    Commit button
  11. Review the changes and click Commit. Commit changes

At this point, you have created the interface. Next, you will create the BGP session.

To create the BGP session

  1. In VM-Series, choose Network > Virtual Routers.
  2. Select the virtual router.
    Select virtual router
  3. In the left pane, select BGP.
  4. Provide the following BGP details:

    • Enable – Select this check box to start the BGP session after committing these changes.
    • Router ID – Specify the Cloud Router BGP IP from the VLAN attachment details in the Google Cloud console.
    • AS Number – Provide the ASN for the MVE connection. Specify the Peer ASN that you defined in the BGP configuration for the VLAN attachment in the Google Cloud console. BGP details
  5. Click +Add under Auth Profiles.

  6. Specify a Profile Name.
    Profile name
  7. Enter and confirm the auth password.
  8. Click OK.
  9. Select the Peer Group tab.
    Peer Group tab
  10. Click +Add to add a peer group.
  11. Specify a name for the peer group. For example, AWS-xxxx.
  12. Specify eBGP as the session type.
  13. Specify any additional details as required for your network.
  14. Click +Add to add a new peer.
  15. Specify the details for the peer:
    • Name – Specify a name for the peer.
    • Peer AS – Specify the Google-side Autonomous System Number (ASN) of 16550. This is a fixed value, and appears in the connection details on the Google console.
    • Local Address – Select the proper subinterface and IP address from the drop-down list.
    • Peer Address – Enter the Cloud Router BGP IP from the VLAN attachment details in the Google Cloud console.
      BGP Peer Group screen

Google Cloud requires BGP multihop support. You can configure multihop support from VM-Series, in the Connection Options tab of the BGP peer:


Validating your Google Cloud connection

To check the status of the BGP peer

  1. Choose Network > Virtual Routers.
  2. Locate your virtual router (default).
  3. Click More Runtime Stats in the Runtime Stats column on the right.
    Runtime stats
  4. Select the BGP tab, and then select the Peer tab.
  5. Verify that the peer status is Established.
    Established status

Last update: 2023-05-12