Alternatives for your Direct Link on Classic deployment

Here are alternatives that customers sometimes choose as use cases for their Direct Link on Classic deployments.

Diverse deployments for Connect and Exchange on Classic

The default deployments of Direct Link Connect and Direct Link Exchange on Classic do not include redundant configuration, although they can be deployed diversely on discrete routers.

Many customers choose to create redundant deployments by setting up an additional Direct Link connection. This document presents some schematic representations of alternative Direct Link on Classic deployments.

Diverse Exchange — Figure 1. A diverse IBM Cloud Direct Link Exchange deployment

IBM Cloud Direct Link also makes it easy to establish diverse Connect deployments, as shown in the following figure.

Using Connect and Exchange on Classic along with other clouds

Some customers want to use Direct Link Connect on Classic along with other cloud providers, such as AWS, Azure, or Google Cloud. The following schematic shows an overview of how to establish this type of connection with a Telco (NSP).

Other Clouds Connect — Figure 4. Using Direct Link Connect in conjunction with other clouds

Some customers want to use Direct Link Exchange on Classic along with other cloud providers, such as AWS, Azure, or Google Cloud. The following schematic shows an overview of how to establish this type of connection with a Cloud Exchange provider.

Other Clouds Exchange — Figure 3. Using IBM Cloud Direct Link Exchange in conjunction with other clouds