Delete Layer 2 Connections
This article details how to delete the following Layer 2 connections:
- Delete a Public ConnectionConnection is a general term that refers to any solution that results in the ability to pass data from one point to another. Connections can be made with Layer 2 or Layer 3 technology, may involve several parts or components and can be created from the portal or with APIs in a variety of ways.
- Delete a Private Connection
- Delete an AWS Connection
- Delete an Azure Connection
Tip: If you want to view any deleted connections, you can use the “Inventory” page filter bar. From the status drop-down, select Deleted.
Delete a connection
To delete connections that have been provisioned, go to the inventory card collection and select the “Connection Card” to expand the connection you want to delete.
When you click Delete, a message box asks you to confirm your deletion request. This message details any additional steps required by the cloud service provider (CSP) before the full service can be terminated.
Note: CSPs and Equinix internal administrators can delete connections if a customer has unpaid bills or has discontinued services. When the deletion occurs, an email notification is sent to both the customer and CSP contacts.
If the CSP requires redundancy to be associated with the same unique authorization keyThe authorization key typically contains alpha-numeric characters and is a unique identifier authorizing Equinix to provision a connection towards the CSPNote: To Equinix, authorization key is a generic term and is NOT encrypted on ECX. CSPs might use a different name to refer to the same key. For example: Azure ExpressRoute calls the authorization key the “service key” while AWS calls it the “account ID”, then both connections must be deleted to completely remove the service. The deletion is performed end-to-end in less than five (5) minutes if the CSP has completed API integration with ECX FabricECX Fabric is an advanced interconnection solution that improves performance by providing a direct, private network connection. Otherwise, the CSP is notified by email that there is a pending deletion request. As the CSP, you must log on to ECX Fabric to manually confirm the deletion. While waiting for the CSP to confirm the deletion, as the customer, you see the remote connection (RC) state as Pending Delete. After the CSP confirms, the provisioning state changes to Deleted in “Connections Details.”
Note: Billing automatically stops for ECX Fabric connections at the timestamp when the Delete Connection request is submitted correctly on ECX Fabric. Billing continues until the CSP confirms the deletion.
Delete a Private Connection
When you delete a private connection, both organizations must approve the deleted status. After the first organization deletes the private connection, the second organization needs to approve the deletion. From the inventory card collection, expand the connection details, then click Approve Deletion.
Note: Once the second organization approves the deletion request, the Layer 2 private connection details move to the Deleted Layer 2 Connections list.
Delete an AWS Connection
For AWS Direct Connect, you must ensure all the virtual interfaces within the hosted connection are deleted before deleting the hosted connection.
ECX Fabric™ does not allow you to delete the hosted connection when there are active virtual interface(s) within the hosted connection.
Delete an Azure Connection
Since Azure requires redundancy, every connection you create has two RCs—whether you have created these redundant connections on a single port or on dual ports. When you create a connection, both redundant connections are created simultaneously. However, this is not the case with deletion, and you must delete both connections manually.
Note: To completely remove Azure service, remember to delete both the primary and secondary remote connections (RCs), then recreate primary and secondary RCs, selecting single or dual ports.