DOCSEARCHbyAlgolia
Submit Docs

Megaport Documentation

website·Indexed 39 days ago

https://docs.megaport.com

Guides for configuring and managing the Megaport network, including Virtual Cross Connects (VXC), Megaport Cloud Router (MCR), Megaport Virtual Edge (MVE), and physical Port management. Includes documentation on multicloud connectivity, Global Mesh WAN, API integration for service providers, and the Megaport Portal.

Tokens
368.3K
Snippets
502
Records
2.7K
Agent score
68%

What's inside Megaport

  1. Overview of Megaport Virtual Edge (MVE) Juniper Deployment

    The Megaport Virtual Edge (MVE) allows users to host Juniper virtual appliances to create secure connections between branch locations and the Megaport SDN.

    Responsibilities:

    • Customer provides: Internet connection from branch, SD-WAN vendor enablement at branch, Customer Premises Equipment (CPE), and the SD-WAN software license.
    • Megaport provides: The hosting platform for virtual SD-WAN appliances, connectivity from branch to Megaport network destinations, and the Megaport Internet connection to terminate tunnels between MVE and branch CPE.

  2. Overview of Megaport Cross Connects

    A Cross Connect is a dedicated physical point-to-point connection linking a user's location within a Megaport-enabled data center to a Megaport Port.

    Key Constraints:

    • Cross Connects can only be ordered with a Port on a term.
    • When a Port is ordered with a Cross Connect, the Port will not be live immediately; there is a provisioning delay until the Cross Connect is deployed.

  3. Overview of Versa Secure SD-WAN on Megaport Virtual Edge (MVE)

    Versa Secure SD-WAN on MVE uses the Versa Operating System (VOS) to deliver next-generation firewall (NGFW) and SD-WAN services on a single virtual machine. It supports a 'private gateway' deployment model, allowing Versa SASE gateway functionality to run on the MVE platform. Core SASE services provided include Cloud Access Security Broker (CASB), Next-Generation Firewall (NGFW), Secure Web Gateway (SWG), and Zero Trust Network Access (ZTNA). The Versa Secure Access Client (VSAC) can be used to steer client traffic to these private gateways on MVE based on application-specific policies.

  4. Overview of Megaport Service Keys

    A service key is a 36-character UUID used to connect ports, MCRs, MVEs, and NAT Gateways across separate Megaport accounts, enabling business-to-business Virtual Cross Connects (VXCs). The service key acts as an address containing configuration details, allowing a consumer to create a connection without knowing the specific service type they are connecting to. The consumer of the service key is responsible for paying for the connection and has the right to delete the service.

  5. Overview of Salesforce Express Connect via Megaport MCR

    Salesforce Express Connect provides a private, dedicated Layer 3 routed connection to Salesforce applications. Key technical characteristics include:

    • Routing: Requires BGP to receive Salesforce routes.
    • IP Addressing: Megaport allocates a /31 public IP range for each peering. Users can advertise their own public IPv4 address ranges, but RFC 1918 (private) routes are not accepted.
    • Redundancy: A single Virtual Cross Connect (VXC) provisions two logical connections to redundant Salesforce routers to ensure uptime.
    • Provisioning Time: Salesforce may take up to 2 business days to approve the connection after the VXC is deployed in the Megaport Portal.
    • Failover: If public IP space is used, routing can revert to the public internet if the Megaport connection fails.

  6. Overview of creating an Anapaya MVE

    To deploy a Megaport Virtual Edge (MVE) integrated with Anapaya, you must obtain an Anapaya license, generate an SSH key pair for administrative access, and provision the MVE via the Megaport Portal. Once deployed, the instance uses a single Anapaya VM image; the specific appliance role (EDGE, CORE, or GATE) is configured later through the Anapaya management console based on your license and requirements.

  7. Overview of the Megaport Virtual Edge (MVE) API workflow

    Creating a Megaport Virtual Edge (MVE) via API follows a four-step process: identifying a supported location, selecting a vendor image, validating the configuration and pricing, and submitting the final order. All requests require an Authorization: Bearer <accessToken> header. The vendor appliance and software version are specified using an imageId (retrieved from the images endpoint) rather than a vendor name. Additionally, each vendor requires specific fields within the vendorConfig object.

  8. Overview of MACsec encryption with Megaport

    MACsec encrypts traffic at the Ethernet layer between devices connected by a layer 2 path. Because it is typically implemented in hardware, it can maintain wire-speed performance, making it suitable for high-throughput environments like data centers. Megaport supports MACsec at 10 Gbps and 100 Gbps options. Most Cloud Service Providers (CSPs) support MACsec from 10 Gbps or above.

  9. Overview of Megaport Configuration Assistance

    Megaport Configuration Assistance is a task-based, professional implementation service where Megaport engineers execute approved network designs. It is designed to accelerate deployments and ensure correct configuration by transferring implementation tasks from the customer's internal team to Megaport.

    Availability: This service is available for direct and partner accounts only; it is not available for managed accounts.

    Included Services:

    • Megaport Core Services: Provisioning and configuration of physical Ports, Megaport Cloud Routers (MCRs), Megaport Virtual Edges (MVE), Virtual Cross Connects (VXCs), Megaport NAT Gateways, and Megaport Internet connections.
    • Cloud Connectivity: Layer 2 and Layer 3 routing configuration for AWS Direct Connect, Azure ExpressRoute, and Google Cloud Interconnect.
    • Scheduled Network Events: Technical execution of deployments, upgrades, or configuration tasks during designated maintenance windows.

  10. Overview of Megaport MCP Server

    The Megaport MCP Server is a specialized middleware layer (currently in read-only open beta) that transforms Megaport's public APIs into a standardized, authenticated, and searchable interface using the Model Context Protocol (MCP). It allows AI coding assistants and LLMs (such as Claude Code, Copilot CLI, and Gemini CLI) to query and manage Megaport infrastructure directly within a development environment using natural language.

  11. Overview of 6WIND integration with Megaport Virtual Edge (MVE)

    The integration of 6WIND's Virtual Service Router (VSR) with Megaport Virtual Edge (MVE) provides secure, high-performance multicloud and hybrid cloud connectivity. In this architecture, the Megaport SDN serves as the underlay network, while the 6WIND fabric acts as the overlay network. 6WIND is responsible for managing the overlay network, including network connections, routing, and network policies. Users utilize the Megaport Portal to provision the MVE and manage Virtual Cross Connects (VXCs) to cloud on-ramps and other Megaport SDN services.

  12. Overview of Extreme IX Internet Exchange

    Extreme IX is a carrier-neutral and data-center-neutral internet exchange (IX) in India, operated by Extreme Infocom Pvt. Ltd. (a Megaport company). It is designed for internet service providers (ISPs) and both local and international content providers. To join the exchange, network operators must possess an Autonomous System Number (ASN), assigned IP address space, and maintain an open peering policy.