Lumen help
With Dynamic Connections Ethernet, you can provision real-time, layer-2 network connections between one of your locations (an Ethernet endpoint device) and partner interconnects, including cloud providers such as AWS, Google, IBM Cloud, Microsoft Azure/Azure Gov, and Oracle/Oracle Gov. Connections are billed hourly and require no long-term contracts.
New to Dynamic Connections Ethernet? Learn how to get ready for Dynamic Connections Ethernet service
Use Control Center to create and manage connections:
Managing connections
For connecions to Microsoft Azure, your equipment must support 802.1ad (Q-in-Q). Before creating a connection, we recommend configuring your router for Q-in-Q. Q-in-Q can be difficult to set up, but use the example below to help you set up your router correctly.
Here’s an example below with a Cisco router.
You’ll assign the outer tag in Control Center and the inner tag in the Azure portal (peering VLAN).
‘Primary EVC VLAN – 100 - Control Center
‘Secondary EVC VLAN – 200 - Control Center
‘Private Peering – VLAN 300 - Azure portal
‘MSFT Peering – VLAN 400 - Azure portal
interface GigabitEthernet0/1.100300
encapsulation dot1Q 100 second-dot1q 300 ‘Azure Private primary peer
description "Cloud Connect"
ip address xxx.xxx.xxx.xxx 255.255.255.252
interface GigabitEthernet0/1.200300
encapsulation dot1Q 200 second-dot1q 300 ‘Azure Private secondary peer
description "Cloud Connect"
ip address xxx.xxx.xxx.xxx 255.255.255.252
interface GigabitEthernet0/1.100400
encapsulation dot1Q 100 second-dot1q 400 ‘MSFT primary peer
description "Cloud Connect"
ip address xxx.xxx.xxx.xxx 255.255.255.252
interface GigabitEthernet0/1.200400
encapsulation dot1Q 200 second-dot1q 400 ‘MSFT secondary peer
description "Cloud Connect"
ip address xxx.xxx.xxx.xxx 255.255.255.252
Higher classes of service offer higher availability SLAs and allow you to increase traffic prioritization for your EVC: