FAQs for Direct Link on Classic

How does Direct Link on Classic differ from the new Direct Link offering?

The new IBM Cloud Direct Link offering differs from "Direct Link on Classic" in that the new Direct Link is decoupled from classic IaaS, and exists only in the local cross-connect router (XCR). This design enables native connectivity to VPC and future capabilities without being forced into the classic IaaS network.

The zone-region model allows for multiple data centers to exist in a single zone.

The new Direct Link offering allows connectivity to both Classic IaaS as well as VPCs, whereas the Classic Direct Link always connects to IaaS network and a global VRF first. Classic Direct Link can only reach VPC on a limited basis utilizing a VPC feature called Classic Access and by adding global routing to the direct link. For more information, see Setting up access to your Classic Infrastructure from VPC.

For information about the differences between the new Direct Link offerings and the "on Classic" versions, see How do I know which Direct Link solution to order? and Getting started with IBM Cloud Direct Link Dedicated.

How does IBM Cloud Direct Link work?

For every Direct Link customer, the IBM Cloud® team assigns a small private subnet to build a point-to-point network between the IBM Cloud cross-connect router (XCR) and the customer's edge router (CER). Then, IBM Cloud and the customer configure Border Gateway Protocol (BGP) to exchange routes between the environments. Finally, IBM Cloud places the customer into a VRF to allow for the implementation of non-unique routes to the private address space of the customer's remote network.

Can I request to change a VLAN ID on IBM Cloud for a provisioned Direct Link Connect gateway with a VLAN that is already allocated?

For a direct link that was manually provisioned, you can request a VLAN update by opening an IBM Support case. For a Provider API-provisioned gateway, a VLAN ID update is not supported.

Where do I find cost estimates for Direct Link offerings?

You can estimate the cost of a service using the cost estimator on the provisioning pages for Direct Link on Classic offerings. For example, select a tile from the IBM Cloud catalog to view the service's ordering page. As you complete the ordering form, cost estimates appear in the Summary side panel.

Does IBM Cloud meter bandwidth for Direct Link products?

Yes. Bandwidth usage across the Direct Link service between customers and IBM Cloud is free and unmetered, IBM Cloud does meter outbound bandwidth from IBM Cloud services to the public internet.

When does billing begin with Direct Link?

The fees for Direct Link Connect cover the cost of service termination on the IBM Cloud infrastructure.

Infrastructure services are billed in advance and begin upon acceptance of a client’s order, however, due to the nature of IBM Cloud Direct Link, the Direct Link service billing begins when a Border Gateway Protocol (BGP) session is established with IBM Cloud, or 30 days after the service key is provided to the client.

Billing stops after (1) a customer requests a circuit to be deleted AND (2) the Connect Provider or Network Service Provider has de-provisioned the circuit.

What extra charges will I incur from other parties with Direct Link?

You might have extra charges from your exchange provider or network service provider. Refer to your providers for their fee information.

How can I achieve redundancy with IBM Cloud Direct Link?

Direct Link does not provide an inherently Redundant service. Direct Link can provide Diverse connections that enable customers to create redundancy via BGP. You can achieve diversity with Direct Link by connecting to more than one IBM Cloud Direct Link Dedicated provider or Exchange provider for IBM Cloud. Alternatively, with Exchange and Connect you can use diverse network-to-networks (NNIs) with the IBM Cloud Direct Link providers.

What is the difference between the default "local" routing and the global routing add-on for Direct Link?

The local routing option is the default routing option. If your Direct Link is connected at the local PoP, it provides access to all data centers within that same market. In some markets, local routing is applicable for stand-alone PoP locations and direct links that are terminated at the data center.

With our standard Direct Link offering, you can send traffic between the data centers in your selected region. If you need access to other data centers outside of the specified region, you must order the global routing add-on. For example, you might use global routing to share workloads between dispersed IBM Cloud resources (such as Dallas to Ashburn, or Dallas to Frankfurt).

Why does a global routing add-on package exist for Direct Link?

The global routing add-on prevents our customers from experiencing unexpected data costs when traversing outside of their data center's local market. It keeps costs lower for most of our customers, and it provides the ability for customers with a global presence to reach all regions across the globe easily. However, usually a customer requires only a local bandwidth package.

If I am connected to a Direct Link Dedicated, Direct Link Connect, or Direct Link Exchange in a region such as Dallas, do I have access to other regions in the US through Direct Link?

Yes, you are able to gain access to areas outside of your local market if you choose the global routing add-on. If this option is not selected, your Direct Link traffic is limited to the local market for the PoP or DC location you selected.

Can I connect to any available region from a given Direct Link location?

Yes, as long as you order Direct Link with the global routing add-on.

Can I restrict the regions that my Direct Link can reach?

No. IBM Cloud offers two options: (1) a local market only, or (2) all regions, with the global routing add-on.

What if I used the Direct Link automated ordering process for Equinix Cloud Exchange and I was assigned a subnet that overlaps my internal network?

The recommended best practice is to cancel your automated order and submit a new case to complete the Direct Link questionnaire. You should indicate whether you prefer another subnet in the 10.254.x.x range or the 172.16.x.x range.

What is the difference between Direct Link Exchange and Direct Link Connect?

These two services are similar, relatively low-cost, latency tolerant, and rapid entry points to the benefits of IBM Cloud Direct Link. In a nutshell, Exchange uses data center providers and Connect uses Telco carriers. Here are some additional details:

Direct Link Exchange is recommended for customers who prefer to use an exchange inside a data center. With an Exchange service, customers can enable multi-cloud connectivity to their colocation rapidly because the underlying circuits are provisioned already (these other cloud providers must already have a physical interconnection present within the facility).

Direct Link Exchange can allow for a multi-cloud, shared-use environment through a single cloud exchange port, created by an NNI connection at Layer 2 between IBM Cloud and the Cloud Exchange Service Provider. Port speeds are available up to 5 Gb.

Direct Link Connect is for customers who prefer to use their existing network between their own on-premises deployment and IBM Cloud. With a Direct Link Connect service, customers can use new and existing Telco networks (such as MPLS) to enable IBM Cloud rapidly, by using pre-provisioned underlying circuits.

With Direct Link Connect, customers can connect to IBM Cloud through the Connect provider, over a Network-to-Network Interface (NNI) connection, operated by IBM partners in facilities worldwide. Port speeds are available up to 5 Gb.

How do Direct Link Connect and Direct Link Exchange providers compare?

Connect providers are Telcos who have network reach beyond the data center. Exchange providers are limited to their data centers. Both can enable the multi-cloud experience for customers. Exchange providers usually require colocation in their data centers, while Connect providers can reach a customer's on-premises site and data centers.

Can IBM Support IPv6 over Direct Link?

Not for the BGP Session. We must assign our /30 from IPv4, and we need the same in return from the customer.

Can IBM do IPV6 on the private network?

No. IPv6 is public only.

Does Direct Link support any type of QoS?

We are unable to support any QoS guarantees. QoS requires MPLS mapping between each of our service suppliers and IBM Cloud. Cloud Service providers generally cannot support QoS because it must reach from end-to-end and involve every device in between. No workaround is currently available by "tunneling" or any other method.

Does Direct Link support Jumbo frames?

Jumbo frames (up to 9214 bytes) are supported on Dedicated and Dedicated Hosting. Support on Connect and Exchange is theoretically possible, but it requires your Service Provider to work with IBM and ensure that the end-to-end connection supports Jumbo Frames, including the underlying Network-to Network-Interface (NNI).

Exchange and Connect support up to a 1500-byte Maximum Transmission Unit (MTU).

With Direct Link Connect how does a customer ensure router diversity through the same carrier?

We have diverse cross-connect routers (XCRs) creating diverse NNI links to the carrier. It is up to the carrier to maintain diversity from that point.

For Direct Link Connect does a customer need to order two links for redundancy, or is the Direct Link Connect inherently redundant?

Order two links for diversity. We do not offer redundancy between switches or routers. Customers create redundancy with their BGP configurations on each Direct Link.

How easy is it to upgrade the bandwidth of my Direct Link connection, for example 1 - 5 GB?

Typically, we install speeds of 1G and lower on 1G optics. For speeds of 2 - 10 GB, we install 10 GB optics. Thus, the upgrade 1 - 5 GB would require new optics to be assigned or inserted. It would be a service-affecting event. If you anticipate that type of growth, it's possible to request 10 GB optical fibers to be installed at the beginning of your Direct Link deployment, or to order 2 GB initially so that the 10 GB optics are in place.

Is ECMP the best choice for redundant Direct Link connections? What alternatives exist?

ECMP (Equal-Cost Multi-Path) is primarily designed for load balancing across multiple links, not for providing redundancy. When using ECMP, both connections typically terminate at the same IBM Cloud cross-connect router (XCR), creating a single point of failure. Essentially, ECMP can be set up as two sessions on a single XCR.

It's important to note that you don’t have to use the same XCR for both connections. There may be scenarios involving AS Path issues similar to those mentioned in Routing report considerations. Additionally, with two 10 GB direct links using ECMP, if you exceed 10 GB of throughput and one link fails, the remaining 10 GB link could become overloaded.

IBM Cloud does NOT recommend using ECMP in this context. ECMP load balancing only apples to traffic at the XCRs. Beyond the XCRs, the traffic from ECMP appears as the same IP address to IBM Cloud network, which defaults to the shortest path found. As a result, only one of the direct links in the ECMP configuration is actively used at a given time.

If redundancy is your goal, consider establishing two Direct Link connections——one for each XCR. For those interested in using ECMP alongside redundancy, you would need two Direct Links to each XCR to enable simultaneous ECMP sessions. Alternatively, some customers set up two links to different XCRs in the same data center, such as WDC02, and then manage failover through BGP configurations. While this approach offers some redundancy, it is less safe than having Direct Link connections in separate data centers, like WDC02 and WDC05.

Another consideration with ECMP is that if you have two VPCs advertising the same route, it might attempt to load balance across those as well. This behavior isn't limited to direct links or GREs; it can also apply to IBM Power Virtual Server workspaces.

Where can I get help setting up a Direct Link?

For connecting to Direct Link, see Configuring IBM Cloud Direct Link. If you need more help, you can request engineering support in the case that was opened for the new service. Even if it is an API service with Equinix, opening a case enables an engineer to look at it. Or you can contact your IBM Sales representative.

On Direct Link Exchange, does IBM set a BGP password?

BGP passwords for Direct Link Exchange aren't set up, by default. There is an option to specify BGP ASN and we assign BGP IP addresses. Also, it's possible to set up a BGP password for authentication purposes, we just need to let the engineers know.

How do I convert my account to VRF?

During conversion, your shared tenancy is converted to use a customer VRF, most commonly with a new Direct Link on Classic subscription.

A "customer VRF" refers to multiple isolation network connectivity. For more information, see Enabling VRF and service endpoints.