Create a Megaport Internet VXC

Megaport Internet is a scalable, on-demand public-internet upstream delivered as a VXC. Instead of buying transit from an ISP at every site, you connect any Port, MCR, or MVE to a Megaport-operated internet router via a TRANSIT-type VXC. Megaport handles the upstream peering and announces a default route (or a full table on request) to your service.

What you'll provision

How it works

The Megaport network includes dedicated transit routers in each region, exposed as partner ports with connectType=TRANSIT. You buy a VXC from your A-End to one of these routers, and Megaport announces a default route (and optionally accepts your prefixes) over BGP.

• Up to 100 Megaport Internet connections per Port (25 per MCR or MVE).
• Available in every country where Megaport has transit infrastructure.
• Diversity zones are enabled on the transit routers — pick blue or red if you're building a redundant pair.

Step 1 — Get your A-End UID

The A-End is whatever Megaport service you want to attach the internet connection to.

# From a Port
megaport-cli ports list

# From an MCR
megaport-cli mcr list

# From an MVE
megaport-cli mve list

Copy the UID of the service you want as the A-End.

Step 2 — Find a TRANSIT partner port

Megaport Internet uses partner ports filtered by connect type TRANSIT. Find one in the same data centre as your A-End.

# All TRANSIT partner ports
megaport-cli partners list --connect-type "TRANSIT"

# Filter to a specific location
megaport-cli partners list --connect-type "TRANSIT" --location-id 3

# Filter by diversity zone for a redundant pair
megaport-cli partners list --connect-type "TRANSIT" --diversity-zone blue

Example output:

PRODUCT NAME       COMPANY    LOCATION ID  DIVERSITY ZONE  UID
Megaport Internet  Megaport   3            blue            874dbcff-a1f9-4328-9c08-112cd87c20f6
Megaport Internet  Megaport   3            red             a91e83b2-1c58-4f9e-9d3a-742b8cf91021
Megaport Internet  Megaport   10           blue            b4f8a9d2-6e51-4c0a-8f2d-9a3c7e4b1f8d
Megaport Internet  Megaport   67           blue            c19fa3d4-5e72-4c0a-8f2d-1a3c7e4b1f8d

Copy the UID of the transit router you want as the B-End.

# Get your existing service's location ID
megaport-cli ports get <PORT-UID> --output json | jq '.locationId'
# → 3

# Filter transit partners to that exact DC
megaport-cli partners list --connect-type "TRANSIT" --location-id 3

megaport-cli partners list --connect-type "TRANSIT" --output json \
  | jq --slurpfile locs <(megaport-cli locations list --output json) '
      map(. + {dc: ($locs[0][] | select(.id == .location_id)
              | "\(.name), \(.metro), \(.country)")})
      | map({dc, location_id, diversity_zone, uid})'

[
  { "dc": "NextDC S1, Sydney, Australia",  "location_id": 3,  "diversity_zone": "blue" },
  { "dc": "Equinix SY3, Sydney, Australia", "location_id": 10, "diversity_zone": "red" }
]

Step 3 — Create the VXC

Interactive mode

megaport-cli vxc buy --interactive

The CLI prompts for A-End / B-End UIDs, VLAN, rate limit, and term. When asked "Do you want to configure A-End partner?" answer No — your Port, MCR, or MVE doesn't need a partner block. When asked "Do you want to configure B-End partner?" answer Yes and choose TRANSIT as the connect type. See Partner Configurations for why only the B-End needs a config block.

Flag mode

megaport-cli vxc buy \
  --name "Megaport Internet - Sydney" \
  --a-end-uid <A-END-UID> \
  --a-end-vlan 100 \
  --b-end-uid <TRANSIT-PARTNER-PORT-UID> \
  --b-end-vlan 0 \
  --rate-limit 1000 \
  --term 12 \
  --b-end-partner-config '{"connectType":"TRANSIT"}'

JSON file (recommended)

megaport-cli vxc buy --json-file ./megaport-internet.json

Example megaport-internet.json:

{
  "vxcName": "Megaport Internet - Sydney",
  "rateLimit": 1000,
  "term": 12,
  "portUid": "<A-END-UID>",
  "aEndConfiguration": {
    "vlan": 100
  },
  "bEndConfiguration": {
    "productUID": "<TRANSIT-PARTNER-PORT-UID>",
    "partnerConfig": {
      "connectType": "TRANSIT"
    }
  },
  "costCentre": "NET-INTERNET",
  "resourceTags": {
    "environment": "production",
    "purpose": "internet-upstream"
  }
}

From an MVE A-End

When the A-End is an MVE, specify which vNIC index the VXC attaches to:

megaport-cli vxc buy \
  --name "MVE Internet - Sydney" \
  --a-end-uid <MVE-UID> \
  --a-end-vnic-index 0 \
  --a-end-vlan 100 \
  --b-end-uid <TRANSIT-PARTNER-PORT-UID> \
  --b-end-vlan 0 \
  --rate-limit 1000 \
  --term 12 \
  --b-end-partner-config '{"connectType":"TRANSIT"}'

Required fields

MVE-only fields

Step 4 — Verify the VXC is live

# Full details
megaport-cli vxc get <VXC-UID>

# Status only (transitions CONFIGURED → LIVE)
megaport-cli vxc status <VXC-UID>

# Watch until LIVE
megaport-cli vxc status <VXC-UID> --watch

Once LIVE, the transit router begins peering with your A-End. Megaport announces a default route automatically — no BGP configuration is required from your side for basic outbound transit.

Step 5 — Configure routing on the A-End

What happens next depends on the A-End type:

Port A-End

Your customer router (CPE) connected to the Port establishes BGP toward the Megaport Internet router. Megaport advertises a default route; you advertise your prefixes (or none, if you only need outbound NAT).

MCR A-End

Add a BGP peer on the MCR pointing at the Megaport Internet router's peer IP. The CLI surfaces peer details via:

megaport-cli vxc get <VXC-UID> --output json | jq '.bEndConfiguration.partnerConfig'

Configure the BGP session in the MCR — Megaport publishes its peer ASN and IP in the partner config response.

MVE A-End

For SD-WAN appliances, the Megaport Internet VXC is typically the WAN-side underlay. The vendor's WAN interface DHCPs an address from the transit router, after which the appliance can reach its vendor orchestrator (vManage, FortiManager, Panorama). See your vendor's MVE deployment guide on docs.megaport.com/mve/ for interface-specific steps.

Clean up (optional)

# Soft delete — removes at end of billing period
megaport-cli vxc delete <VXC-UID>

# Immediate deletion — irreversible
megaport-cli vxc delete <VXC-UID> --now

What's next?

• Create an MVE — pair Megaport Internet with a virtual SD-WAN appliance
• MCR Routing — use Megaport Internet as a public path alongside private cloud connections
• Multi-Cloud Connectivity — combine private cloud VXCs with Megaport Internet for SaaS access