Nine Common Scenarios for Multicloud Design

Filed under:
Tech

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.

Click through to head to Knowledgebase and explore the scenarios.

Scenario 1
Business designing non-HA multi cloud network connecting from a single Megaport enabled DC (Located in or via dark fibre) that are geographically close to CSPs.
HA design No
Multi-cloud 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 Azure
  • If 802.1ad not supported, use MCR (Scenario 3)
Megaport Technology Required How many?
Megaport Yes 1
Megaport Cloud Router (MCR) No
VXC (Virtual Cross Connect) – Same Metro Yes 3 (1 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No
Scenario 2
Business designing non-HA multi cloud network and have no on-premises infrastructure required to be connected
HA design No
Multi-cloud Yes
On-premises DC (Colo) or Office No
On-premises geographically close to CSPs Yes
Diverse regions No
.
Prerequisites
  • None required
Megaport Technology Required How many?
Megaport No
Megaport Cloud Router (MCR) Yes 1
VXC (Virtual Cross Connect) – Same Metro Yes 3 (1 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No
Scenario 3
Business designing non-HA multi cloud network connecting from a single Megaport enabled DCs (Located in or via dark fibre) that are not geographically close to CSPs.
HA design No
Multi-cloud 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 3 (1 x per CSP)
VXC (Virtual Cross Connect) – Long Haul Yes 1
Scenario 4
Business designing HA multi cloud network connecting from two of Megaport enabled DCs (Located in or via dark fibre) that are geographically close to CSPs.
HA design Yes
Multi-cloud Yes
On-premises DC (Colo) or Office Yes – 2 DCs
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 Azure
  • If 802.1ad not supported, use MCR (Scenario 6)
Megaport Technology Required How many?
Megaport Yes 2 or (4 in a Link Aggregation/LAG)
Megaport Cloud Router (MCR) No
VXC (Virtual Cross Connect) – Same Metro Yes 6 (2 x per CSP) (with optional 7)
VXC (Virtual Cross Connect) – Long Haul No
Scenario 5
Business designing HA multi cloud network and have no on-premises infrastructure required to be connected
HA design Yes
Multi-cloud Yes
On-premises DC (Colo) or Office No
On-premises geographically close to CSPs Yes
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 6 (2 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No
Scenario 6
Business designing HA multi cloud network connecting from two of Megaport enabled DCs (Located in or via dark fibre) that are not geographically close to CSPs.
HA design Yes
Multi-cloud Yes
On-premises DC (Colo) or Office Yes – 2 DCs
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 or (4 in a Link Aggregation/LAG)
Megaport Cloud Router (MCR) Yes 2
VXC (Virtual Cross Connect) – Same Metro Yes 6 (2 x per CSP) (with optional 7)
VXC (Virtual Cross Connect) – Long Haul Yes 4
Scenario 7
Business designing geographically separated HA multi cloud network connecting from two of Megaport enabled DCs (Located in or via dark fibre) with each geographically close to the CSP regions.
HA design Yes
Multi-cloud 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 Azure
  • If 802.1ad not supported, use MCR (Scenario 9)
Megaport Technology Required How many?
Megaport Yes 2 or (4 in a Link Aggregation/LAG)
Megaport Cloud Router (MCR) No
VXC (Virtual Cross Connect) – Same Metro Yes 12 (4 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No
Scenario 8
Business designing geographically separated HA multi cloud network and have no on-premises infrastructure required to be connected
HA design Yes
Multi-cloud Yes
On-premises DC (Colo) or Office No
On-premises geographically close to CSPs Yes
Diverse regions Yes
.
Prerequisites
  • None required
Megaport Technology Required How many?
Megaport No
Megaport Cloud Router (MCR) Yes 1
VXC (Virtual Cross Connect) – Same Metro Yes 12 (4 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No
Scenario 9
Business designing geographically separated HA multi cloud network connecting from two of Megaport enabled DCs (Located in or via dark fibre) that are not geographically close to CSP regions.
HA design Yes
Multi-cloud 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 2 or (4 in a Link Aggregation/LAG)
Megaport Cloud Router (MCR) Yes 4
VXC (Virtual Cross Connect) – Same Metro Yes 12 (4 x per CSP)
VXC (Virtual Cross Connect) – Long Haul Yes 8 (with optional 9)
Legends

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? Reach out to us via Twitter or visit our contact page and we’d be happy to help.


interconnection-trends-download

E-GUIDE

2019 in Focus: This Year's Interconnection Trends

See what’s next for enterprise interconnection and how you can get ahead.