View Azure ExpressRoute Connections
For Azure ExpressRoute, the connection information in the expanded view of ports to the buyer (A-side) shown is as follows:
- Connections: the name of the connection that your company has assigned
- Seller-side Service: the name of the service the connection is connected to (i.e., Azure)
- Service Key: your unique Azure ExpressRoute identifier for the connection you submitted. You need to acquire this from Microsoft Azure
- Buyer-side VLAN ID: the VLAN ID the buyer uses to identify the connection within the selected port. This is the Outer Tag/sTag of the 802.1ad tagging mechanism used on the buy-side. If not, it is the 802.1Q VLAN tag. See earlier section for explanation of Ethernet tag and the options available
- VLAN Speed: speed of the Standard speed tiers include 200Mbps, 500Mbps, 1Gbps or 10Gbps
- State: Azure ExpressRoute provisioning state for the connection. Following are the states the connection goes through:
- Not Provisioned—Just starting Provisioning with Microsoft Azure
- Pending BGP Peering—Waiting for customer to Configure Microsoft Peering for Service Name (Public, Private, Microsoft) on the Microsoft side
- Provisioned—Completed Provisioning with Microsoft Azure
- Status: Azure ExpressRoute connection network status, which is provided by ExpressRoute via API
Check for ARP (MAC-Addresses) on Microsoft Portal
On Microsoft Portal the ARP (MAC-addresses) to Customer and Microsoft can be verified for each ExpressRoute circuit.
1. Select ExpressRoute Circuit
2. Select Microsoft Peering – Azure Private, Azure Public or Microsoft; Click on “…”
3. Click on Get ARP records
Can get ARP for Primary or Secondary
On-PREM refers to customer router
Microsoft refers to Microsoft router
MAC ADDRESS should show Values.
If “INCOMPLETE” for:
Check for correct VLAN ID configured on customer router. The VLAN ID should be the same as defined on the Buyer VLAN ID when the Azure circuit was created on Equinix Cloud Portal.
Check that the Microsoft Peering completed Validation. A Typical issue is that if doing Public or Private Peering the ASN number and Primary and Secondary Prefixes are not registered with this customer.
Verify Routes on Microsoft Portal
On Microsoft Portal the route to and from Customer and Microsoft can be verified for each express-route circuit.
Delete Layer 2 connections Azure ExpressRoute
Azure ExpressRoute requires redundancy so every connection you make will have 2 VCs, whether you have created these VCs on Single port or on Dual port. When you create connection, both VCs get created simultaneously, but this is not the case with deletion. You must delete both manually. For Azure ExpressRoute, remember to delete both the PRIMARY and SECONDARY VCs if you want to completely remove the service, and then recreate PRIMARY and SECONDARY VCs selecting Single or Dual Ports.
View deleted connections
If you want to see that deleted connection, click on “Show Deleted Layer 2 Connections.”
If the CSP requires redundancy to be associated with the same unique authorization key, remember to delete both connections to completely remove the service. The deletion is performed end-to-end in less than 5 minutes if the seller has completed API integration with ECX. Otherwise, the seller will be notified by email that there is a pending delete request. The seller will then come to CXP to manually confirm the deletion. While you are waiting for the seller to confirm the deletion, you will see VC state as “Pending Delete.” The provisioning state in the Connections tab will change to “Deleted” after the seller confirms.
Note: Billing automatically stops for ECX connections at the timestamp when the Delete Connection request is submitted correctly on CXP. The billing stop does not wait until the seller (CSP) confirms the deletion.