Skip to content
Megaport ONE Documentation
Creating an MVE

Creating a VM-Series MVE

This topic describes how to create and configure a Megaport Virtual Edge (MVE) with VM-Series next-generation firewall (NGFW). You can use VM-Series to secure application traffic that flows through the MVE.

Before you begin, you need user accounts with ordering permissions that provide access to the Megaport ONE Portal and the VM-Series firewall.

For details on setting up a Megaport ONE account, see Creating an Account.

Palo Alto Networks provides documentation for VM-Series at VM-Series Tech Docs.

Basic steps

This section provides an overview of the configuration steps in the Megaport ONE Portal and VM-Series. Detailed procedures follow this basic step summary.

The basic steps are:

  • Obtain a VM-Series license from Palo Alto Networks.
  • Set a temporary admin password for VM-Series.
  • Generate an SSH Public Key for authentication.
  • Create a Palo Alto Networks VM-Series MVE in the Megaport ONE Portal.
    We strongly recommend that you provision a Transit VXC onto the Management Plane virtual interface.
  • View the MVE public IP address assignment in the Megaport ONE Portal.
  • Allow secure console access to the VM-Series.

MVE with VM-Series architecture

Licensing

Before you create an MVE in the Megaport ONE Portal, you need a valid license from Palo Alto Networks. After purchasing a VM-Series firewall, you receive an authorization code via email. You will use this Auth Code to register the MVE with Palo Alto Networks.

To obtain an authorization code from Palo Alto Networks for VM-Series

  1. Log in to the Palo Alto Networks Customer Support Portal with your account credentials.

  2. Choose Assets > VM-Series Auth-Codes > Add VM-Series Auth-Code.

  3. Enter the Auth Code you received by email in the Add VM-Series Auth-Code field.

  4. Select the check box on the far right to save.
    The page displays the list of Auth Codes registered to your Support account.

  5. To view all the assets that are deployed, choose Assets > Devices.

Once the product is registered, it appears in the Palo Alto Networks Registration Completion page.

The next step is to generate an SSH key pair for authentication.

Administrative access to MVE

You establish management and administrative access to the MVE/VM-Series through a public/private SSH key pair for secure connections. The public SSH key allows you to SSH into VM-Series and set the administrative password and enable HTTPS access.

Megaport supports the 2048-bit RSA key type.

To generate an SSH key pair (Linux/Mac OSX)

  • Run the SSH keygen command:
     ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048

The key generator command creates an SSH key pair and adds two files to your ~/.ssh directory:

  • megaport-mve-instance-1-2048 – Contains the private key.
  • megaport-mve-instance-1-2048.pub – Contains the public key that is authorized to log in to the Palo Alto account.

To generate an SSH key pair (Windows, using PuTTYgen)

  1. Open PuTTYGen.
  2. In the Key section, choose RSA 2048 bit and click Generate.
  3. Move your mouse randomly in the small screen to generate the key pairs.
  4. Enter a key comment, which will identify the key.
    This is convenient when you use several SSH keys.
  5. Enter a Key passphrase, and re-enter to confirm.
    The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
  6. Click Save private key, choose a location, then click Save.
  7. Click Save public key, choose a location, then click Save.

You’ll copy and paste the contents of the public key file in the Megaport ONE Portal later to distribute the public key to the Palo Alto VM-Series appliance. Your private key will match the public key to grant access. Only a single private key has access to the VM-Series for SSH access.

Creating an MVE in the Megaport ONE Portal

Before you create an MVE, you need to determine the best location - one that supports MVE and one that is in the most compatible metro area. You can connect multiple locations to an individual MVE. For location details, see Planning Your Deployment.

You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons.

To create the VM Series MVE (compute)

  1. In the Megaport ONE Portal, choose Networking > Services.

  2. Click Create Service and select MVE.
    Create MVE button

  3. Select an MVE location geographically close to your target branch and/or on-premises locations.
    You can search for your preferred location using the Country drop-down list, or enter a search term to filter results as you type. Click Clear Filters to reset the filters. Note that the country you choose must be a market in which you have already registered. If you haven’t registered a billing market in the location where you will deploy the MVE, see Enabling Billing Markets.
    Select MVE location

  4. Specify the MVE Configuration details:

    • MVE Name – Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport ONE Portal.
    • Vendor – Select Palo Alto VM-Series and the software version. The MVE will be configured to be compatible with this software version from Palo Alto Networks.
    • Service – Displays the vendor name and software version, and any important information such as upgrade requirements.
    • MVE Size – Select a size from the drop-down list. The list displays all sizes that match the CPU capacity at the selected location. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly. For sizing details, see Planning Your Palo Alto MVE Deployment. MVE configuration details

  5. Specify the Palo Alto VM-Series Configuration details:

    • License Data (optional) – Specify the VM-Series Auth Code (the valid license for the virtual appliance). The Auth Code is used to register the VM-Series MVE instance with Palo Alto Networks. You can find it in the Palo Alto Networks Support portal.

    • Admin Password – Specify a temporary administrator password. The password must be a minimum of 8 characters and include:
      - 1 uppercase character (A-Z)
      - 1 lowercase character (a-z)
      - 1 number (0-9)
      - 1 symbol

      Note

      Megaport does not store customer passwords.

    • SSH Key – Copy and paste the contents of your public SSH key here. You can find the public key in the megaport-mve-instance-1-2048.pub file generated earlier. Megaport ONE Portal: Palo Alto VM-Series Configuration

  6. Specify the Billing Details:

    • Service Level Reference (optional) – Specify a unique identifying number for the MVE 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.

    • Minimum Term – Select No Minimum Term to pay-as-you-go, or select a term of 12, 24, or 36 months. Longer terms result in a lower monthly rate for the MVE size. By default, a 12-month term is selected.

      Note

      Partner and partner-managed accounts select MVE subscriptions instead of MVE contract terms.

      For details on contract terms, see MVE Pricing and Contract Terms.

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

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

      Note

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

      Palo Alto VM-Series billing details

  7. Click Deploy MVE.
    A summary screen appears.
    MVE summary

  8. Review the new configuration and pricing then click Confirm.
    You are prompted to create a Transit Virtual Cross Connect (VXC). A Transit VXC provides connectivity and allows MVE to register and communicate with Palo Alto Networks licensing systems and, optionally, Panorama.
    Create Transit VXC

To create the Transit VXC

  1. Click Create IP Transit VXC to proceed (recommended), or click Not now to provision your own internet access at a later time.
    A destination port in the same diversity zone as the MVE will be assigned automatically.

    Note

    MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Transit VXC or configure a third-party internet connection using a private VXC. We strongly recommend that you order a Megaport Transit VXC for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly.

  2. Specify the VXC Configuration details:

    • Connection Name – Specify a unique name for the Transit VXC.
      As a best practice, we recommend including “Management Plane” in the name for reference later.

    • Rate Limit (Mbps) – Specify the speed for the Transit VXC.
      This speed is adjustable from 20 Mbps to 10 Gbps in increments of 1 Mbps. You can change the speed as needed after you create the Transit VXC. Monthly billing details appear based on location and rate limit.

    • A-End vNIC – Select vNIC-0 Management from the drop-down list.

      Important

      The internet connection on the management virtual interface will be used only for management purposes such as licensing, updates, and communication with Panorama. If you require internet traffic to flow between branches, users, and/or the cloud, you will create a second Transit VXC on the data plane virtual interface. See To create a second Transit VXC on the data plane for details.

    • Preferred A-End VLAN (optional) – Specify an unused VLAN ID for this connection.
      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. Alternatively, you can click Untag VLAN. This selection removes the VLAN tagging for this connection and it will be configured without a VLAN ID.

      Transit VXC connection details

  3. Specify the Billing Details:

    • Service Level Reference (optional) – Specify a unique identifying number for the Transit 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.

      Tip

      Use the same Service Level Reference numbers for the Transit VXC and MVE to help identify the matching pair in your invoice.

    • 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.

  4. Click Create Connection to order the connection.
    A summary screen appears.
    Transit VXC summary

  5. Review the new connection details and pricing then click Confirm.
    The MVE and Transit VXC are created.
    Palo Alto MVE and Transit VXC

Note

A second Transit VXC is required if the firewall will be exchanging internet traffic with branches. Each data plane Transit VXC receives its own unique public IP Address.

To create a second Transit VXC on the data plane virtual interface

  1. In the Megaport ONE Portal, choose Networking > Services.

  2. Click the gear icon Gear icon next to the Palo Alto MVE.

  3. Select Add Connection.
    Add Transit VXC Connection

  4. Select Transit VXC.
    Transit VXC
    A destination port in the same diversity zone as the MVE will be assigned automatically.

  5. Specify the VXC Configuration details:

    • Connection Name – Specify a unique name for the data plane Transit VXC. As a best practice, we recommend including “Data Plane” in the name for reference later.

    • Rate Limit (Mbps) – Specify the speed for the Transit VXC.
      This speed is adjustable from 20 Mbps to 10 Gbps in increments of 1 Mbps. You can change the speed as needed after you create the Transit VXC. Monthly billing details appear based on location and rate limit.

    • A-END vNIC – Select vNIC-1 Data Plane from the drop-down list.

    • Preferred A-End VLAN (optional) – Specify an unused VLAN ID for this connection.
      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.

      Transit VXC connection details

  6. Specify the Billing Details:

    • Service Level Reference (optional) – Specify a unique identifying number for the Transit 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.

    • 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.

  7. Click Create Connection to order the connection.
    A summary screen appears.
    Data Plane Transit VXC summary

  8. Review the new connection details and pricing then click Confirm.
    The second Transit VXC on the data plane is created.
    Palo Alto MVE and Data Plane Transit VXC

Ordering MVE provisions the instance and assigns IP addresses from the Megaport SDN. The Palo Alto MVE provisioning time varies between versions and depends on whether you provide a license authorization code. It can take up to 15 minutes for the MVE to provision before you can log in and continue configuration.

After you order the MVE from the Megaport ONE Portal, you can use Palo Alto Panorama to manage the firewall.

Viewing the MVE in the Megaport ONE Portal

After creating the MVE, you can view it in the Megaport ONE Portal on the Services page. You can also view the MVE public IP address assignment.

To view an MVE in the Megaport ONE Portal

  • Go to the Networking > Services page.

MVE and Transit VXC in the Megaport ONE Portal

Under the new MVE, you will see a Transit VXC to “Megaport IP Transit”. The Transit VXC icon differs from a standard VXC icon in the Megaport ONE Portal, as shown in the image.

For details on the Services page, see Viewing Network Services.

To view the public IP addresses assigned to the MVE

  1. Click the gear icon Gear icon next to the Transit VXC and select Edit Service.
    The VXC Configuration details appear. From here, you can modify any of the Transit VXC details.
    Transit VXC Connection details
  2. Click the Details tab.
    Transit VXC details
  3. Locate the public IP address (IPv4 or IPv6). These are the public IP addresses assigned to the MVE. Make a note of these addresses for use later.

Updating the administrator password

Next, you’ll replace the temporary password you set in the Megaport ONE Portal with a new secure password.

To update the administrator password

  1. Log in to the Palo Alto system using the temporary admin password you set in the Megaport ONE Portal.
  2. Choose Device > Administrators.
  3. Select the admin user.
    Admin user
  4. Enter the old temporary password, a new secure password, and confirm the new password.
    Administrators screen
  5. Click OK.
  6. Choose Config > Save Changes.

Configuring the data plane interface

Next, you will configure the data plane interface and assign it an interface type.

To configure the data plane interface

  1. Choose Network > Interfaces.
  2. Select ethernet1/1 from the Interface column.
    Palo Alto Ethernet interfaces
  3. Select Layer3 from the Interface Type drop-down list.
    Palo Alto Ethernet interfaces
  4. Click OK.
  5. Highlight the ‘ethernet1/1’ row and click Add Subinterface at the bottom of the screen. Add subinterface

  6. 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 value associated with the Megaport IP Transit destination Port.

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

  7. Select the IPv4 tab.

  8. Select DHCP Client as the Type.
  9. Click OK.
  10. Click Commit in the top right corner.
    Commit button
  11. Review the changes and click Commit. Commit changes

Next steps

Now that you’ve deployed an MVE, the next step is to connect a VXC to a CSP, a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.

Last update: 2023-11-08