copyright | lastupdated | keywords | subcollection | ||
---|---|---|---|---|---|
|
2024-10-09 |
direct-link |
{{site.data.keyword.attribute-definition-list}}
{: #alternatives-for-your-ibm-cloud-direct-link-deployment}
Here are alternatives that customers sometimes choose as use cases for their Direct Link on Classic deployments. {: shortdesc}
{: #diverse-deployments-for-exchange-and-connect}
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.
{: caption="A diverse IBM Cloud Direct Link Exchange deployment" caption-side="bottom"}
IBM Cloud Direct Link also makes it easy to establish diverse Connect deployments, as shown in the following figure.
{: caption="A redundant and diverse IBM Cloud Direct Link Connect on Classic deployment" caption-side="bottom"}
{: #using-exchange-and-connect-in-conjunction-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).
{: caption="Using Direct Link Connect in conjunction with other clouds" caption-side="bottom"}
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.
{: caption="Using IBM Cloud Direct Link Exchange in conjunction with other clouds" caption-side="bottom"}