Ordering IBM Cloud Direct Link Dedicated

To order Direct Link Dedicated, you must determine the location that connects to IBM Cloud, complete the required Direct Link configuration information, then click Create to submit your order.

Planning considerations

Make sure that you review the following information before you order Direct Link Dedicated:

Before you begin, contact your service provider to determine the location to IBM Cloud by verifying your colocation or service provider's capabilities to reach the Meet Me Room and cross-connect into IBM Cloud.
All subnets of the VPC or classic network are connected to the direct link. When you create VPCs, make sure to create the VPCs with nonoverlapping prefixes and unique subnets.
- To avoid IP address conflicts for classic connections to a direct link, don't use IP address ranges in the 10.0.0.0/14, 10.200.0.0/14, 10.198.0.0/15, and 10.254.0.0/16 blocks for on-prem networks. On-prem routes that overlap are dropped.
- For VPC connections to a direct link, you "can" use restricted Classic IP ranges in the 10.0.0.0/14, 10.200.0.0/14, 10.198.0.0/15, and 10.254.0.0/16 blocks.
- For direct links connected to transit gateways, these IP ranges are always filtered to protect classic networks that could potentially be connected to transit gateways.
A Generic Routing Encapsulation (GRE)/IPsec tunneling requirement between your Edge router and a virtual router in IBM Cloud requires a nonconflicting subnet when ordering. Default addresses for Direct Link are nonroutable and do not support tunneling.
IBM Cloud VPC permits the use of RFC-1918 and IANA-registered IPv4 address space, privately within your VPC, with some exceptions in the IANA Special-Purpose ranges, and select ranges that are assigned to IBM Cloud services. When you use IANA-registered ranges within your enterprise, and within VPCs with IBM Cloud Direct Link, custom routes must be installed in each zone. For more information, see Routing considerations for IANA-registered IP assignments.
If you plan to connect your direct link to a transit gateway, keep in mind that a single direct link instance accepts a maximum of 120 on-premises address prefixes when connected to a transit gateway. Consider aggregating prefixes to keep within this limit. (A direct link can accept a maximum of 200 prefixes when not connected to a transit gateway.)
For known limitations and restrictions, see Known limitations.

Ordering instructions

To order IBM Cloud® Direct Link Dedicated, follow these steps.

Log in to your IBM Cloud account.
Click Menu on the upper left, then click Interconnectivity.
Scroll to locate the Dedicated tile, then click Order Direct Link Dedicated to order.

Alternatively, you can click Direct Link in the left navigation pane to view the Direct Link page, which lists existing Direct Link instances. Then click Order Direct Link > Direct Link Dedicated tile.
In the Before you begin section, click Open checklist to review the ordering process (also described in Completing the connection).
In the Resource section, complete the following information:
- Type a name for your Direct Link Dedicated connection.
- Choose a resource group to create the Direct Link connection. Resource groups help manage and contain resources that are associated with an account. Select Default if you don't have other groups that are defined in the menu list. For more information about resource groups, see Best practices for organizing resources in a resource group.
- Type your customer and carrier names.
In the Gateway section, complete the following information:
- Select a geography, followed by a market, type, site, and routing option.
  
  Local and global routing options are supported. When you select a routing option, the location details with reachable sites are displayed.
- Choose a connection speed. The speeds that are supported for the Direct Link Dedicated offering are 1 Gbps, 2 Gbps, 5 Gbps, and 10 Gbps.
  
  Speeds greater than 1 Gbps require 10 Gbps service from the client's carrier and equipment. If you intend to upgrade the speed for this gateway, select 2 Gbps to start with; otherwise, you cannot upgrade to a higher speed on this gateway.
- Choose an IBM cross-connect router, if available.
The routing option that you select determines the reachability of the resources in the selected location. If you select the Global routing option along with your location selections, the Region menu list displays all the regions that are globally available in the specific account. After you select a region, you can select any VPC from the Available connections menu. If you select Local routing, then only the region that corresponds to the selected location is available to select. When selected, the VPCs available in the local region for your account are shown.
In the Billing section, select Metered or Unmetered. Metered pricing is paying only for what you use. Unmetered is unlimited access, for a predicable, monthly fee.
In the BGP section, complete the following information:
- Select the IBM cross-connect router for the Direct Link connection. The number of direct links that are associated with your account for each router is shown next to the router name.
- Select a BGP peering subnet for the Direct Link connection. You have two choices for BGP subnets:
  - Select Manual-select IP to specify two of your own IP addresses (in CIDR format) from the ranges 10.254.0.0/16, 172.16.0.0/12, 192.168.0.0/16, 169.254.0.0/16, or Public (a public IP address that you own). Manual-select is useful when you are trying to avoid conflicts with an existing subnet that is in use.
  - Select Auto-select IP for IBM to assign an IP address from IP range 169.254.0.0/16.
  Make sure that any self-provided BGP addresses do not conflict with blocks that are used by IBM, or by resources external to your Direct Link deployment. Also, if you plan to use GRE or IPsec tunneling with your direct link, you must select a BGP IP other than 169.254.0.0/16.
- For BGP ASN, use either the default value of 64999 or select an ASN from the specified allowed ranges. Allowed ASN ranges are:
  - For a 2-byte range, enter a value between 1-64495 or the default 64999.
  - For a 2-byte or 4-byte range, enter a value between 131072-4199999999.
  - For a 4-byte range, enter a value between 4201000000-4294967294.
  Excluded ASNs: 0, 13884, 36351, 64512, 64513, 65100, 65201 – 65234, 65402 – 65433, 65500, 65516, 65519, 65521, 65531, and 4201065000 – 4201065999
In the Additional gateway settings section, you can activate one or more of these optional settings.
- Configure Virtual Local Area Network (VLAN) tagging - Specify the VLAN that is configured on your router to establish connectivity to IBM on the VLAN of your choice. For more information, see Activating, deactivating, and updating VLAN tagging.
  
  Activating, deactivating, or updating a VLAN after the BGP session is established causes BGP session downtime and network disruption until the BGP peer device is configured for the same change.
  
  Complete the following information:
  - VLAN – Enter a VLAN ID. Enter a value in the range from 2 to 3967.
  The VLAN must comply with the IEEE 802.1Q (Dot 1Q) standard.
- Verify data integrity with Message Digest 5 (MD5) - Add an extra layer of security between two BGP peers by verifying each transmitted message sent through the BGP session. When MD5 authentication is activated, BGP authenticates every segment that is sent over the TCP session from its peer and verifies the source of each routing update.
  
  Important:
  - Configure the same BGP MD5 authentication key on both your Edge router and the IBM cross-connect router (XCR). The shared authentication key on the IBM device must be stored in your HPCS or Key Protect instance and shared with the Direct Link service. For more information, see Setting up BGP Message Digest 5 (MD5) authentication keys.
  - You can achieve hitless key refresh if the keys are updated on both your Edge router and on the IBM cross-connect router (XCR) within 90 seconds. As a pre-condition, you must configure the BGP hold time on your router to a minimum of 90 seconds. All Direct Link routers have a 90-second configuration by default. Either side can initiate the key refresh, but both sides must refresh within the configured BGP hold time to avoid traffic disruption.
  - If a BGP peering session was established and you enable BGP MD5 authentication (or change the authentication key to a different value), BGP sessions are reestablished. This action causes BGP session downtime and network disruption until the BGP peer device is configured with the same change.
  Complete the following information:
  - For the keystore, select either Hyper Protect Crypto Services or Key Protect.
  - Select an authentication keystore instance.
  - Select an authentication key.
- Detect network failures with Bidirectional Forwarding Detection (BFD) - Activate BFD to quickly detect faults in a network between two routers or switches that are connected by a link. BFD provides a single, standardized method for detecting link failures at any protocol layer, over any media. For more information, see Setting up bidirectional forwarding detection.
  
  Activating and deactivating BFD after the BGP session is established causes BGP session downtime and network disruption until the BGP peer device is configured for the same change.
  
  Complete the following information:
  - Interval – The interval is the minimum time (in milliseconds) expected to occur between when the local routing device sends BFD hello packets and the reply from its neighbor. This value can range from 300 to 255,000 milliseconds.
  - Multiplier – The multiplier is the number of times that a hello packet is missed before BFD declares the neighbor down. This value can range from 1 to 255. The default multiplier value is 3.
- Prioritize direct links with AS prepends - Adjust route preference by lengthening AS paths with multiples of the BGP Autonomous System Number (ASN). When the prefix is matched, the longer AS path becomes a lower priority for the BGP router. For more information, see Prepending an AS path to influence route priority.
- Filter your import routes - Select a default filter to either permit or deny all routes unmatched by active route filters. By default, all import routes are permitted. Next, click Configure filters to start creating import route filters. To prioritize filters, drag and drop the icon next to the Order number in the table. Click Save to save your configuration. For more information, see Filtering routes.
- Filter your export routes - Select a default filter to either permit or deny all routes unmatched by active route filters. By default, all export routes are permitted. Next, click Configure filters to start creating export route filters. To prioritize filters, drag and drop the icon next to the Order number in the table. Click Save to save your configuration. For more information, see Filtering routes.
In the Connections section, select the type of network connection that you want to bind to the Direct Link gateway. You can select a connection type when you create a direct link, or after your direct link is provisioned.

Select from the following connection types:
- Select Direct resources (default) to create a direct, private connection between your on-premises network and IBM Cloud deployment. Optionally, choose a connection and enter a connection name. To add multiple network connections to the Direct Link gateway, click Add connection +. You can create one of the following connections:
  - Classic infrastructure networks allow you to connect to IBM Cloud classic resources. Only one classic infrastructure connection is allowed per Direct Link gateway.
  - VPC networks allow you to connect to your account’s VPC resources.
  You cannot request a connection to a network in another account when you create a gateway. However, you can request a connection to a network in another account after a gateway is provisioned. You also can create classic infrastructure and VPC connections after a gateway is created. To learn more, see Adding virtual connections to a Direct Link gateway.
- Select Transit Gateway to bind your direct link to transit gateways. You can bind your direct link to one or more local gateways, or one global gateway.
  
  If you select Transit Gateway as the type of network connection, you must also initiate a Direct Link connection through the IBM Cloud Transit Gateway console from the same IBM Cloud account. For instructions, see Adding a connection.
An order summary shows pricing estimates for your review. Read and agree to the Direct Link prerequisites and review Cloud Services Terms. Then, click Create to complete your order.

If you want to add GB egress data to your estimate, click Add to estimate to calculate the cost. You can also click the About tab for links to Direct Link pricing tables and other helpful resources.

Complete your connection, using the following instructions.

Completing the connection

After you submit your Direct Link order, the Direct Link table indicates an LOA creation in progress connection status. Click the name of the connection to open its details page. Then, view the Actions section to see if you have any pending actions.

Here's how the process works:

IBM Cloud uploads a Letter of Authorization (LOA) containing a Connecting Facility Assignment (CFA) within 24 hours. In turn, the connection status changes to Waiting LOA review. Currently, you can click the corresponding buttons to preview and accept the LOA.
After you accept the LOA and download it, the connection status changes to Waiting completion notice upload. Now take the LOA document to your carrier and get the completion notice (Example). To do so, you can:
- Supply the LOA/CFA to your colocation provider and have them order a cross-connect and any required inter-campus connectivity.
- Supply the LOA/CFA to your service provider and have them order a third-party cross-connect, as well as the circuit between your on-premises and the appropriate Meet Me Room.
IBM Cloud will not order a cross-connect on a customer's behalf.
After you receive the completion notice from your carrier, upload it. The completion notice must be in PDF format with the name completion_notice.pdf for the automation to process it properly. The specific connection shows an option in the IBM Cloud console to upload the completion notice. Notice that the connection status changes to Completion notice review in progress.
The IBM Cloud team reviews the completion notice and accepts it. The IBM Cloud team then places an order for the fiber to be installed between the patch panel/port mentioned in the LOA and the device port. This process can take 1-4 business days, depending on how quickly the site provider finishes the request. This completes the physical-layer portion of the direct link and the connection status changes to Provisioned.
Configure the BGP parameters on your Edge router for BGP session establishment. After this completes, the BGP status indicates Established and Link status indicates Up. It can take up to 30 minutes for the link status to update.