惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

人人都是产品经理
人人都是产品经理
Apple Machine Learning Research
Apple Machine Learning Research
云风的 BLOG
云风的 BLOG
罗磊的独立博客
博客园 - 三生石上(FineUI控件)
量子位
GbyAI
GbyAI
腾讯CDC
T
Tailwind CSS Blog
博客园 - Franky
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
D
Docker
G
Google Developers Blog
aimingoo的专栏
aimingoo的专栏
The GitHub Blog
The GitHub Blog
Microsoft Security Blog
Microsoft Security Blog
Stack Overflow Blog
Stack Overflow Blog
Hugging Face - Blog
Hugging Face - Blog
小众软件
小众软件
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
N
Netflix TechBlog - Medium
Jina AI
Jina AI
IT之家
IT之家
Y
Y Combinator Blog

Megaport Blog

A Guide to NAT Gateway A Guide to Cloud Storage How the Data Center Is Evolving in 2026 What to Expect When Attending Your First Network Operator Group (NOG) Nine Ways to Connect to Cloud Using Private Connectivity Migrate Your On-premises to the Cloud: A Step-by-Step Guide How to Lower Your Egress Fees in 2026 How to Achieve Data Sovereignty in Europe Cisco and Megaport: Redefining the Edge of Modern Networking How to Reduce Latency in Your Multicloud Environment Introducing Megaport High-Speed Cross-Cloud Encryption Are Businesses Leaving the Cloud? Using Meraki and Megaport Virtual Edge for Multicloud Networking Equinix Metal® is Going Away: Here’s What You Can Do Introducing Megaport On-ramp as a Service Megaport’s Full Solution Portfolio Is Coming to India New Bare-metal GPU Instance Now Available with NVIDIA RTX Pro 6000 A Look Back at 2025: Megaport's Biggest Updates Megaport Expands Into India With Strategic Acquisition of Extreme IX Your 2026 Predictions From AWS re:Invent 2025 What’s Next for NaaS? Top Trends for 2026 What is IPsec? When to Move From Public Internet to Private Connectivity Megaport and Latitude.sh: Bringing Compute and Connectivity Together How to Improve Your Microsoft ExpressRoute Resilience with Megaport Connectivity Comparing Ways to Connect to AWS What is API-First Networking? The Hidden Cost of Running Cloud-Hosted SD-WAN for IaaS How to Overcome NaaS Integration Challenges Introducing SCION with Anapaya and Megaport
Nine Common Scenarios for Multicloud Design
Megaport · 2019-01-08 · via Megaport Blog

How to use Megaport and Megaport Cloud Router for multicloud designs – from simple single-region to complex resilient multi-region architectures.

How to use Megaport and Megaport Cloud Router for multicloud designs – from simple single-region to complex resilient multi-region architectures.

When it comes to architecting cloud infrastructure to host business-critical applications, any enterprise should make sure they have measures in place to protect their organisation from experiencing an outage. A high-performance backup architecture could mean the difference between your mission-critical workloads running smoothly and major disruptions causing potential loss of data, customers, and revenue.

Some of the headaches you might experience when designing networks for hybrid and multicloud architectures include:

  • Moving data between CSPs
  • Knowing where to add resiliency
  • Knowing how much resiliency to add to meet budget

In order to solve for these potential issues, we’ll look at nine different design scenarios using Megaport and Megaport Cloud Router (MCR) that you can build. These range from a simple partially protected network to an end-to-end highly available resilient network for multicloud and hybrid cloud with an affordable price tag and with no lock-in contract.

Scenarios

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • Legends

Scenario 1

Single Megaport connecting to each CSP.

HA design

No

Multicloud

Yes

On-premises DC (Colo) or Office

Yes – 1 DC

On-premises geographically close to CSPs

Yes

Diverse regions

No

Prerequisites

  • Customer (on-premises) network equipment supports LX Optical 1Gbps or LR Optical 10Gbps Ports
  • Customer (on-premises) network equipment supports BGP
  • Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) – Specifically for Microsoft Azure

Note: If 802.1ad not supported, use Scenario 3 (MCR).

Megaport Technology Required

How many?

Megaport

Yes

1

Megaport Cloud Router (MCR)

No

VXC (Virtual Cross Connect) – Same Metro

Yes

4 (1 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

No

Single DC non-HA diagram

Scenario 2

Dual Megaports configured as a LAG that connects to each CSP in an HA configuration.

HA design

Yes

Multicloud

Yes

On-premises DC (Colo) or Office

Yes – 1 DC

On-premises geographically close to CSPs

Yes

Diverse regions

No

Prerequisites

  • Customer (on-premises) network equipment supports LX Optical 1Gbps or LR Optical 10Gbps Ports
  • Customer (on-premises) network equipment supports BGP
  • Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) – Specifically for Microsoft Azure

Note: If 802.1ad not supported, use Scenario 3 (MCR).

Megaport Technology Required

How many?

Megaport

Yes

2 (in LAG)

Megaport Cloud Router (MCR)

No

VXC (Virtual Cross Connect) – Same Metro

Yes

8 (2 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

No

Single DC LAG HA diagram

Scenario 3

MCR as a hub that connects a single Megaport in a DC with CSPs.

HA design

Yes

Multicloud

Yes

On-premises DC (Colo) or Office

Yes – 1 DC

On-premises geographically close to CSPs

No

Diverse regions

No

Prerequisites

  • Customer (on-premises) network equipment supports LX Optical 1Gbps or LR Optical 10Gbps Ports
  • Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory)

Megaport Technology Required

How many?

Megaport

Yes

1

Megaport Cloud Router (MCR)

Yes

1

VXC (Virtual Cross Connect) – Same Metro

Yes

4 (1 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

Yes

1

Single DC non-HA MCR diagram

Scenario 4

Megaport in each Diversity Zone connecting to each CSP in an HA configuration.

HA design

Yes

Multicloud

Yes

On-premises DC (Colo) or Office

Yes

On-premises geographically close to CSPs

Yes

Diverse regions

No

Prerequisites

  • Customer (on-premises) network equipment supports LX Optical 1Gbps or LR Optical 10Gbps Ports
  • Customer (on-premises) network equipment supports BGP
  • Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) – Specifically for Microsoft Azure

Note: If 802.1ad not supported, use MCR (Scenario 6).

Megaport Technology Required

How many?

Megaport

Yes

2 (4 in a LAG)

Megaport Cloud Router (MCR)

No

VXC (Virtual Cross Connect) – Same Metro

Yes

8 (2 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

No

Single DC full HA diagram

Scenario 5

Dual MCRs as hubs that connect CSPs in an HA configuration without requiring on-premises infrastructure.

HA design

Yes

Multicloud

Yes

On-premises DC (Colo) or Office

No

On-premises geographically close to CSPs

N/A

Diverse regions

No

Prerequisites

  • None required

Megaport Technology Required

How many?

Megaport

No

Megaport Cloud Router (MCR)

Yes

2

VXC (Virtual Cross Connect) – Same Metro

Yes

8 (2 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

No

Dual DC cloud only MCR diagram

Scenario 6

Dual MCRs as hubs that connect a DC with a Megaport in each Diversity Zone to CSPs in an HA configuration.

HA design

Yes

Multicloud

Yes

On-premises DC (Colo) or Office

Yes

On-premises geographically close to CSPs

No

Diverse regions

No

Prerequisites

  • Customer (on-premises) network equipment supports LX Optical 1Gbps or LR Optical 10Gbps Ports
  • Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory)

Megaport Technology Required

How many?

Megaport

Yes

2 (4 in a LAG)

Megaport Cloud Router (MCR)

Yes

2

VXC (Virtual Cross Connect) – Same Metro

Yes

8 (2 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

Yes

2

Single DC full HA MCR diagram

Scenario 7

Single Megaport in each DC connecting to CSPs in HA configuration.

HA design

Yes

Multicloud

Yes

On-premises DC (Colo) or Office

Yes – 2 DCs

On-premises geographically close to CSPs

Yes

Diverse regions

Yes

Prerequisites

  • Customer (on-premises) network equipment supports LX Optical 1Gbps or LR Optical 10Gbps Ports
  • Customer (on-premises) network equipment supports BGP
  • Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) – Specifically for Microsoft Azure

Note: If 802.1ad not supported, use MCR (Scenario 8).

Megaport Technology Required

How many?

Megaport

Yes

2 (4 in a LAG)

Megaport Cloud Router (MCR)

No

VXC (Virtual Cross Connect) – Same Metro

Yes

8 (2 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

No

Dual DC HA diagram

Scenario 8

Dual MCRs as hubs that connect DCs with Megaports to CSPs in an HA configuration.

HA design

Yes

Multicloud

Yes

On-premises DC (Colo) or Office

Yes

On-premises geographically close to CSPs

N/A

Diverse regions

Yes

Prerequisites

  • Customer (on-premises) network equipment supports LX Optical 1Gbps or LR Optical 10Gbps Ports
  • Customer (on-premises) network equipment supports BGP

Megaport Technology Required

How many?

Megaport

Yes

2

Megaport Cloud Router (MCR)

Yes

2

VXC (Virtual Cross Connect) – Same Metro

Yes

8 (2 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

Yes

2 (plus 2 optional)

Dual DC HA MCR diagram

Scenario 9

Dual MCRs as hubs that connect DCs with Megaports in different Diversity Zones to CSPs in an HA configuration.

HA design

Yes

Multicloud

Yes

On-premises DC (Colo) or Office

Yes – 2 DCs

On-premises geographically close to CSPs

No

Diverse regions

Yes

Prerequisites

  • Customer (on-premises) network equipment supports LX Optical 1Gbps or LR Optical 10Gbps Ports
  • Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory)

Megaport Technology Required

How many?

Megaport

Yes

4

Megaport Cloud Router (MCR)

Yes

2

VXC (Virtual Cross Connect) – Same Metro

Yes

8 (2 for each CSP)

VXC (Virtual Cross Connect) – Long Haul

Yes

4

Dual DC full HA MCR diagram

Multicloud legend diagram

Implementing a high availability strategy within your organisation means you reduce the risk that service outages can pose to your business continuity, profits, and reputation. Our connectivity specialists can provide design and support to ensure your organisation never goes dark.

Got questions? Visit our contact page and we’d be happy to help.