Common Multicloud Connectivity Scenarios

This topic details nine common design scenarios using Megaport and the Megaport Cloud Router (MCR). The scenarios range from a simple partially-protected network to an end-to-end highly available resilient network for multicloud and hybrid cloud.

 

Scenario 1
Business designing non-HA multicloud network connecting from a single Megaport enabled data center (located in or through dark fiber) that are geographically close to CSPs.
HA design No
Multicloud Yes
On-premises data center (colocation) or office Yes - 1 DC
On-premises geographically close to CSPs Yes
Diverse regions No
Prerequisites
    • Customer (on-premises) network equipment supports LX optical 1 Gbps or LR optical 10 Gbps 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 3 (1 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No  
Scenario: non-HA network with a single Megaport
Scenario 2
Business designing non-HA multicloud network and have no on-premises infrastructure required to be connected
HA design No
Multicloud Yes
On-premises data center (colocation) 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 1
VXC (Virtual Cross Connect) – Same Metro Yes 3 (1 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No  
Scenario: non-HA multicloud network
Scenario 3
Business designing non-HA multicloud network connecting from a single Megaport enabled data centers (located in or via dark fiber) that are not geographically close to CSPs.
HA design No
Multicloud Yes
On-premises data center (colocation) or office Yes - 1 DC
On-premises geographically close to CSPs No
Diverse regions No
Prerequisites
  • Customer (on-premises) network equipment supports LX optical 1 Gbps or LR optical 10 Gbps 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: non-HA multicloud network with a single Megaport
Scenario 4
Business designing HA multicloud network connecting from two of Megaport enabled data centers (located in or via dark fiber) that are geographically close to CSPs.
HA design Yes
Multicloud Yes
On-premises data center (colocation) or office Yes - 2 DCs
On-premises geographically close to CSPs Yes
Diverse regions No
Prerequisites
    • Customer (on-premises) network equipment supports LX optical 1 Gbps or LR optical 10 Gbps ports
    • Customer (on-premises) network equipment supports BGP
    • Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) – Specifically for Azure
Note: 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: HA multicloud network from two Megaport data centers
Scenario 5
Business designing HA multicloud network and have no on-premises infrastructure required to be connected
HA design Yes
Multicloud Yes
On-premises data center (colocation) 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 6 (2 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No  
Scenario: HA multicloud network without on-premise infrastructure
Scenario 6
Business designing HA multicloud network connecting from two of Megaport enabled data centers (located in or via dark fiber) that are not geographically close to CSPs.
HA design Yes
Multicloud Yes
On-premises data center (colocation) or office Yes - 2 DCs
On-premises geographically close to CSPs No
Diverse regions No
Prerequisites
  • Customer (on-premises) network equipment supports LX optical 1 Gbps or LR optical 10 Gbps 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: HA multicloud network from two Megaport data centers far from CSPs
Scenario 7
Business designing geographically separated HA multicloud network connecting from two of Megaport enabled data centers (located in or via dark fiber) with each geographically close to the CSP regions.
HA design Yes
Multicloud Yes
On-premises data center (colocation) or office Yes - 2 DCs
On-premises geographically close to CSPs Yes
Diverse regions Yes
Prerequisites
    • Customer (on-premises) network equipment supports LX optical 1 Gbps or LR optical 10 Gbps ports
    • Customer (on-premises) network equipment supports BGP
    • Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) – Specifically for Azure
Note: 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 (with optional 1)
Scenario: Geographically separated HA multicloud network from two Megaport data centers
Scenario 8
Business designing geographically separated HA multicloud network and have no on-premises infrastructure required to be connected
HA design Yes
Multicloud Yes
On-premises data center (colocation) or office No
On-premises geographically close to CSPs N/A
Diverse regions Yes
Prerequisites
  • None required
Megaport Technology Required How many?
Megaport No  
Megaport Cloud Router (MCR) Yes 4
VXC (Virtual Cross Connect) – Same Metro Yes 12 (4 x per CSP)
VXC (Virtual Cross Connect) – Long Haul No  
Scenario: Geographically separated HA multicloud network without on-premise connections
Scenario 9
Business designing geographically separated HA multicloud network connecting from two of Megaport enabled data centers (located in or via dark fiber) that are not geographically close to CSP regions.
HA design Yes
Multicloud Yes
On-premises data center (colocation) or office Yes - 2 DCs
On-premises geographically close to CSPs No
Diverse regions Yes
Prerequisites
  • Customer (on-premises) network equipment supports LX optical 1 Gbps or LR optical 10 Gbps 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)
Scenario: Geographically separated HA multicloud network from two Megaport data centers that are not geographically close
Legend
Legend

Last update: