Ordering Direct Link Exchange on Classic
As you prepare to order Direct Link on Classic, review the general process that your organization follows for obtaining the Exchange service, including the locations where each service is available, globally. When you're ready to place your order, follow the step-by-step instructions.
To determine which Direct Link solution is best for your networking environment, see How do I know which type of IBM Cloud Direct Link I need?
Direct Link ordering process overview
Here is the general process to order a Direct Link service:
-
Verify your network provider's capabilities to reach the appropriate IBM Cloud PoP.
-
Use the IBM Cloud console to open a Direct Link Exchange request and complete the requested information. You can request assistance from IBM Cloud Sales engineers. When you are ready to create your order, you are prompted to read and agree to the Direct Link Exchange prerequisites.
If the Direct Link order is for the Equinix Cloud Exchange, the service provisioning is fully automated. This means that you can place an order for a Direct Link connection (Equinix) without opening an IBM Support case. Automation capabilities currently are limited to the Equinix Cloud Exchange.
-
Contact your Exchange provider and negotiate connectivity to your colocation.
-
Order a virtual circuit through the Exchange provider, and reference the case ID of the IBM Cloud Direct Link request as your Request ID or Authorization ID.
IP assignment on the IBM Cloud networking infrastructure is completed within three business days after the virtual circuit request is complete.
Ordering instructions
To provision an IBM Cloud Direct Link Exchange connection, complete the following steps. To order Direct Link Exchange for Equinix, follow Steps to order Direct Link Exchange on Classic for Equinix.
-
Log in to your IBM Cloud console account.
-
Select the Navigation Menu icon on the upper left, then click Classic Infrastructure > Direct Link.
The Direct Link on Classic page opens, listing existing Direct Link connections provisioned for this account.
-
Click Order Direct Link in the upper right of the page. The Choose Direct Link option page is displayed.
-
Select the Direct Link Exchange tile to open the order form.
Optionally, if diverse ports are accessible, and you previously provisioned the first virtual circuit, you see a page similar to the following one, which shows two ports from which you can select your second virtual circuit. For example: /n
-
In the order form, complete following information to configure Direct Link Exchange:
- Enter a Direct Link instance name.
- Choose the location in which you want to establish the IBM Cloud Direct Link connection.
- Select the name of your network provider.
- Select the routing option required for the connection: Local routing (free) or Global routing.
- Enter a BGP ASN number from the range given in the information box for the BGP exchanges.
As you complete these values, you can see an approximate monthly charge in the right Summary pane.
-
Read and agree to the Direct Link Exchange prerequisites. Then, click Create to complete your order.
After you complete your order, an IBM Support case number is generated. Click the case number to view case details.
-
After you provision your direct link, see Configuring Direct Link on Classic to configure your subnet to interact with IBM Cloud.
Ordering instructions for the Equinix Cloud Exchange
If the IBM Cloud® Direct Link on Classic order is for the Equinix Cloud Exchange, the service provisioning is fully automated. This means that you can place an order for an IBM Cloud Direct Link connection (Equinix) without opening an IBM Support case.
PREREQUISITE: To use the automated ordering capability, your private VLANs must be associated with a VRF in the IBM Cloud private network. If this requirement is not met, an IBM Support case is generated when you place the order.
To order Direct Link Exchange on Classic for Equinix, follow these steps:
-
Log in to the Equinix Cloud Exchange (ECX) Fabric portal.
- Navigate to https://ecxfabric.equinix.com.
- Enter your username and password.
- Click Sign In.
-
In the Frequent Connections section, click the IBM Cloud tile.
-
In the IBM Cloud Direct Link Exchange profile, click Create Connection.
-
In the Origin section, click Port.
-
Select a Location, followed by a Destination. Then, click Next.
-
On the Connection Details page, enter the connection information. For Account ID, enter the Classic Softlayer Account ID (for example,
114340xxx
). This is the unique account ID that was initially created to start using IBM Cloud. -
Select a Connection Speed, then click Next.
-
Review and click Submit Your Order.
-
Return to the IBM Cloud Direct Link Exchange page in the IBM Cloud console. Notice that the connection status for your direct link connection states Create Approval Pending.
-
Open the Actions menu and click Accept.
The virtual connection shows as Provisioned in the Equinix Fabric portal.
-
Review your order summary, agree to the Direct Link Exchange prerequisites, and then click Create.
The timeline for approval is within 24 hours. If the 24-hour Service Level Agreement (SLA) is not acceptable, you can create an IBM Support case and request that it be routed to the SNS team.
Ordering Direct Link Exchange on Classic when there is no VRF present
For the accounts with no Virtual Routing and Forwarding (VRF) present, the Select VRF field is not displayed in the order form. In this situation, an IBM Support case is generated after you place your order. The case number and details are shown in the IBM Cloud console after you place the order.
Locations
This table shows which IBM Cloud data centers offer Direct Link Exchange connectivity:
Exchange Provider | IBM Data Center Code |
---|---|
AT Tokyo | Tokyo 2 |
Ascenty | Sao Paulo 5 |
Cologix | Montreal 2, Toronto 2 |
Cyrus One | Dallas 13 |
DE-CIX | Frankfurt 3 |
Equinix | Americas: Chicago 1, Dallas 3, New York City 2*, New York City 3*, Sao Paulo 2, San Jose 2, Toronto 2, Toronto 3, Washington DC APAC: Hong Kong 1, Osaka 1, Singapore 2, Sydney 2, Tokyo 3 EU: Amsterdam 2, Frankfurt 3, London 1, London 3, Paris 2 |
KINX | Seoul 2 |
NextDC | Melbourne 2, Sydney 3 |
- NYC02 and NYC03 connect to the IBM Cloud backbone through NYC1. The primary reason for these PoPs is to extend connectivity to different site providers from our NYC01 site. When planning your diversity strategy, keep in mind that traffic for NYC02 and NYC03 have a single, shared path to the IBM network.