Lumen help

Creating a connection between two Microsoft Azure Gov locations

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

To create a connection between two Microsoft Azure Gov locations:

Dynamic Connections (showing Ethernet tab)
Dynamic Connections (Create Ethernet Connection)
  1. In the Connection Name field, type a name for the connection you're creating.
  1. In both the From Connection Type and To Connection Type lists, select Azure (Gov).
  1. Fill in the information for the connection:

    1. Fill in the two ExpressRoute Service Key fields with the service keys provided by Microsoft. (Note: You can only use a service key that isn't assigned to an active connection. The ExpressRoute service key is a unique service key and is different from the service key for your cloud service from Azure.)

      Once you fill in the ExpressRoute service key, Control Center retrieves connection information from Microsoft.

    2. In the Billing Method field, select whether you want hourly or monthly billing.

    3. In the Class of Service field, select whether you want BasicEnhanced, or Dedicated. (Higher classes of service offer higher availability SLAs and allow you to increase traffic prioritization for your EVC.)

      • Basic (best effort): The service may be oversubscribed on the Lumen network.

      • Enhanced (mid class): Enhanced EVCs (ethernet virtual circuits) can still be oversubscribed like Basic class of service EVCs; however, traffic is marked with an internal class of service marking which will prioritize your traffic over best-effort traffic during times of congestion. For EVCs with this class of service, bandwidth is not reserved on the Lumen network and traffic will not take priority over real-time traffic in the network.

      • Dedicated (real time): The quality of service offering with highest priority on the Lumen network. In addition, Lumen reserves the bandwidth for this EVC across the network on each ring that the EVC touches. Once it is dedicated to you, that bandwidth (and the corresponding CE-VLANs) sits in reserve regardless of how much bandwidth you use.
         
    4. In the Bandwidth field, select the bandwidth for the connection. By default, Control Center selects the lowest bandwidth associated with the service key you entered. You can adjust the bandwidth up/down based on your needs.

      Control Center shows pricing for the bandwidth you selected.
  1. Review your connection information and then click the I agree with the terms and conditions checkbox. (To enable the checkbox, scroll to the bottom of the terms and conditions.)