Skip to main content
ExpressRoute Configuration

ExpressRoute Configuration, from the ordering until configuration

D
Written by DE-CIX Consulting Team
Updated over a week ago

Pre-requisites

When selecting the resiliency options, choose standard.

Note: We are offering, as of today, both Standard and Maximum Resiliency; soon, we will enable the High Resiliency model when it becomes available (in the Azure regions)

Important Notes:

  • Region: Select the region closest to the peering location of the circuit

  • Port type: Select Provider; we are connecting through DE-CIX as a partner

  • Peering Location: Select the physical location where you want to connect, the onramp

  • Provider: Choose DE-CIX

  • Bandwidth: Enter the desired bandwidth that you need

  • SKU: Leave it in Standard

  • Billing Model: Metered

Once you have generated the service key, hand it over to DE-CIX to provision the Express Route circuit.

If you prefer and have access to the portal, you can provision the service key on your own following this tutorial:

If the service key has been provisioned, it should be reflected in the provider status.

Click on Azure Private:

Important notes:

  • Peer ASN: Your ASN // Azure will use the 12076 as ASN

  • IPv4 Primary subnet:

    Enter a /30 subnet, where the first IP of the net is the one that will be configured on your router; the second will be the one of Azure.

    Example: If we select the 192.168.0.0/30 network

    Your router: 192.168.0.1/30

    Azure: 192.168.0.2/30

  • IPv4 Secondary subnet: Same note as the primary subnet

  • VLAN ID: Choose a VLAN ID for connecting with Azure

  • Shared Key: - Optional - MD5 Hash for using as shared key

This is an example of what it could look like. Click on save after finish.

Establish a BGP Connection towards Azure using the configuration that was set here. Align with your network connectivity partner for the Layer 2 configuration.

To verify if there is layer two connectivity on the Express Route circuit, click on View ARP records.

As it can be seen, Azure is reached, and we see our on-premises:

With these steps, we have achieved connectivity to the edge routers of Azure, but we don´t have access to our resources in the Cloud, therefore is needed to:

After performing these steps, we will connect with our Azure resources.

How to verify if the routes are received:

Click on View Route Table:

Did this answer your question?