Skip to content
Megaport Documentation
Creating an MVE

Creating an MVE Integrated with Fortinet

This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Fortinet Secure SD-WAN. Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal and to Fortinet.

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

Tip

Fortinet provides documentation for their SD-WAN product, including FortiManager and cloud connections, at Fortinet SD-WAN Documentation Library.

Basic steps

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

The basic steps are:

  • Obtain a license from Fortinet.
  • Generate an SSH key pair for authentication.
  • Create the Fortinet MVE in the Megaport Portal.
  • View the MVE public IP address assignment in the Megaport Portal.
  • Set an admin password for the FortiGate.
  • Allow secure console access to the FortiGate.
  • Add the FortiGate to FortiManager Cloud (optional).

Licensing

Before you create an MVE in the Megaport Portal, you need a valid license from Fortinet. After purchasing a license from Fortinet, you’ll receive a registration code in a PDF. You’ll use this registration code to generate a license file.

To obtain a license file from Fortinet

  1. Log in to your registration account at Fortinet Support.

  2. Choose Register Product and enter the provided registration code.

  3. Follow the registration process.
    Fortinet generates the serial number and displays it on the Registration Completion page.

  4. Choose Manage > View Products and click the serial number.

  5. Click the download link and save the license file. You’ll upload the license file later in the Megaport Portal.

Once the product is registered, it appears in the FortiCloud Asset Management product list.

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

Administrative access to MVE

MVE and the FortiGate connect through a public/private SSH key pair to establish secure connections. The public SSH key allows you to SSH into the FortiGate and set the administrative password, enable HTTPS access, and optionally register the FortiGate to your FortiManager Cloud.

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 Fortinet 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, and click Save.
  7. Click Save public key, choose a location, and click Save.

You’ll copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the FortiGate. Your private key will match the public key to grant access. Only a single private key has access to the FortiGate for SSH access.

Creating an MVE in the Megaport 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 Fortinet Deployment.

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

To create an MVE

  1. In the Megaport Portal, go to the Services page.

  2. Click Create MVE.
    Create MVE button

  3. Select the MVE location.

    Select a location geographically close to your target branch and/or on-premises locations.

    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, follow the procedure in Enabling Billing Markets.

    To search for your local market in the list, enter a country in the Country Filter or a metro region detail in the Search filter.

    Select MVE location

  4. Click Next.

  5. Select Fortinet and the software version.
    The MVE will be configured to be compatible with this software version from Fortinet.

  6. Specify the MVE details:
    MVE 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 Portal.

      Note

      Partner-managed accounts can associate a Partner Deal to a service with a minimum 12-month subscription. For details, see Associating a Deal With a Service.

    • 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 details, see Planning your Fortinet Deployment.

    • 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. By default, a 12-month term is selected.

      Note

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

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

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

    • Appliance License – (Optional) Click Choose File and select the appliance license generated earlier from Fortinet.

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

    • Virtual Interfaces (vNICs) – Fortinet is configured with one vNIC named Data Plane by default. If required, you can change the name by typing over the Data Plane text.

      You can add a total of five vNICs to the MVE, including the one added by default.

      To add a vNIC:

      • Click + Add.

        Add vNIC

      • Enter a name for the vNIC.

        Add name for vNIC

      Note

      If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You can’t add or delete vNICs from a deployed MVE.

  7. Click Next to view the Summary screen.
    The monthly rate is based on location and size.
    MVE summary

  8. Confirm the configuration and pricing and click Add MVE.
    You are prompted to create a transit Virtual Cross Connect (VXC). A Transit VXC provides connectivity and allows MVE to register and communicate with the Fortinet SD-WAN overlay network.
    Create Transit VXC

  9. Click Create IP Transit VXC to proceed, or click Not now to provision 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. You can either provision a Transit VXC or provide your own Internet access.

  10. Specify the connection details:

    • Connection Name – Specify a unique name for the Transit VXC.

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

    • Rate Limit – The rate limit specifies the speed of the Transit VXC and 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 an A-End vNIC 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. Alternatively, you can click Untag. This selection removes the VLAN tagging for this connection and it will be configured without a VLAN ID. Transit VXC connection details

  11. Click Next to proceed to the connection detail summary, click Add VXC, and order the connection.

  12. Review the Order Services agreement.
  13. Click Save to save the configured MVE before placing the order. Configured services
  14. Click Order.
  15. If you have a promotional code, click Add Promo Code, enter it, then click Add Code.
  16. Click Order Now.
    Order services

Ordering MVE provisions the instance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a FortiGate.

Viewing the MVE

After creating the MVE, you can view it in the Megaport Portal on the Services page.

To view an MVE in the Megaport Portal

MVE and Transit VXC in MP Portal
The Transit VXC icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.

For details on the Services page, see Understanding the Services Page.

To view the public IP addresses assigned to the MVE

  1. Click the gear icon Gear icon next to the Transit VXC.
    The Connection Details screen appears. 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.

Allow console access to the FortiGate

Console access to the FortiGate is delivered through a secure HTTPS session. The MVE blocks all access to the public IP addresses assigned to the device until you SSH into it and grant HTTPS access.

To set an admin Web UI password and allow HTTPS access

  1. SSH to the Fortinet MVE instance using the SSH private key generated earlier. The default username is admin, followed by the public IP address assigned to the device by Megaport.

    ssh -i ~/.ssh/megaport-mve-instance-1-2048 admin@162.43.xx.x

    Once in the FortiOS CLI, you can view system status and allow access to the device using CLI commands.

    Note

    The FortiOS CLI differs from the standard NOS CLI or Linux shell.

  2. Configure a password for the user admin account.

      FGVM08TM21001375 # config system admin
  FGVM08TM21001375 (admin) # edit admin
  FGVM08TM21001375 (admin) # set password xxxxxxxx
  FGVM08TM21001375 (admin) # next
  FGVM08TM21001375 (admin) # end

  3. Allow HTTPS access to the public interface GUI on port 1. 

      FGVM08TM21001375 # config system interface
  FGVM08TM21001375 (interface) # edit port1
  FGVM08TM21001375 (port1) # append allowaccess https
  FGVM08TM21001375 (port1) # next
  FGVM08TM21001375 (interface) # end

  FGVM08TM21001375 #

  4. Verify that HTTPS access is allowed. 

      FGVM08TM21001375 # show system interface

With HTTPS access allowed, you can log in to the FortiGate through its Web UI using the user admin credentials.

Add the FortiGate to FortiManager Cloud

The next step is to add the FortiGate to FortiManager Cloud, Fortinet’s SD-WAN centralized management platform.

Note

This step is optional. You can manage a FortiGate as a standalone device without using FortiManager Cloud as its central manager.

To add the FortiGate to FortiManager Cloud

  1. Log in to the FortiGate GUI: https://162.43.xx.x

  2. Select Device Manager.

  3. From the Device Dashboard, Choose Security Fabric > Fabric Connectors.

  4. Select FortiManager and click Edit.

    Add FortiGate to FortiManager

  5. Select the following settings:

    • Status - Enabled
    • Type - FortiManager Cloud
    • Mode - Normal

  6. Click OK.

    The FortiCloud contacts your registered FortiManager Cloud for approval. The registration process does not require an IP address but instead uses backend authentication through prior registration and licensing.

Authorize the FortiGate in FortiManager

Before FortiManager adds the FortiGate to its list of managed devices, you need to manually authorize it.

To authorize the FortiGate

  1. Log in to your FortiManager Cloud instance at Fortinet Support.

  2. Choose Services > FortiManager.

    Authorize device

    You’ll see an unauthorized device awaiting approval.

    FortiGate awaiting authorization

  3. Click Unauthorized Devices, and then select the device to authorize.

  4. Click Authorize.

  5. You can optionally change the device name, apply a preconfigured policy package, or apply a preconfigured provisioning template to the device.

  6. Click OK when you are satisfied with the configuration.
    A green check mark indicates the FortiGate was authorized by FortiManager.

    FortiGate successful authorization

  7. Click Close.

The device is now managed via FortiManager Cloud and you can view it in the list of managed devices.

FortiCloud managed through FortiManager

Note

The IP address for the FortiGate displayed on the dashboard is an internal, private IP that is specifically used for the SD-WAN overlay.

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-09-12