Create Connection to Verizon Software-Defined Interconnect (SDI)

ECX FabricECX Fabric is an advanced interconnection solution that improves performance by providing a direct, private network connection customers can now create a virtual connection to Verizon’s PIP network. This capability is currently available in 18 markets: Denver, Silicon Valley, Hong Kong, Chicago, Tokyo, Sydney, New York, Frankfurt, Amsterdam, Paris, Seattle, Atlanta, Singapore, Los Angeles, London, Miami, Dallas and Ashburn.

Follow the workflow described in the Connecting To Other Layer 2 Cloud Service Providers (CSPs) section to connect to Verizon’s services.   The steps below describe the connection process on the ECX Fabric portal.

Note: VZ offers both Verizon-provided access (orderable through the VZ PIP portal) and Customer-provided access (ordered through the ECX Fabric portal) to the VZ Private IP (PIP) network. This document describes customer-provided access processes.

Please visit the VZ portal for VZ-provided access.

On the Create 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. page, choose Connect to a Service Provider, then search for the Verizon service profile named Software Defined Interconnect and begin the create connection process.

Until VZ accepts the connection, the status will be Not Provisioned.

Once the created a connection to VZ is created via the ECX portal, provide the assigned 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” to your VZ sales representative to complete the connection on the VZ side. The sales representative must log in and enter the Authorization Key and location to signal VZ to accept the connection. Once accepted, the connection will automatically provision within the ECX Fabric portal and the connection status will change to Provisioned.

Multi-VRF Configurations

VZ customers can connect to the PIP network in both Single and Multi-VRF configurations.

VZ SDI doesn’t support Multi-VRF via Port Level Queueing.  However, Multi-VRF is available via customer-ordered SDI (through the ECX Fabric portal) with either single (Dot1q) or double (QinQ) tagging.  However, Multi-VRF via Verizon-ordered SDI is only available for double (QinQ) tagging.

Customers with Dot1q or QinQ ECX ports that who to connect to multiple VZ services (Multi-VRFs), the VZ service utilizes the ECX Fabric authentication key service.  This is explained in detail under Authentication KeyThe Authentication Key is a unique identifier authorizing Equinix to provision a connection towards the CSP. This Key usually contains alphanumeric characters. Note: to Equinix, an Authentication Key is a generic term and is not encrypted on ECX. Cloud Service Providers 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.” Service.

Note: Take note of the auto-generated Authentication Key that’s found on the Success page when the connection is completed.  The Authentication Key is also listed in the Inventory section of the ECX Fabric portal.  This key is required to complete the connection in the Verizon PIP portal.

 

Helpful Hints on How to Enter the Connection Authorization Key and Location in the VZ PIP Portal

See screen shots below:

How are we doing?