Skip to content

Latest commit

 

History

History
34 lines (24 loc) · 2.44 KB

File metadata and controls

34 lines (24 loc) · 2.44 KB
copyright
years
2020, 2026
lastupdated 2026-03-17
keywords direct link, known issues, limitations
subcollection dl

{{site.data.keyword.attribute-definition-list}}

Known issues and limitations

{: #known-limitations}

Known limitations are as follows:

  • Each {{site.data.keyword.dl_full_notm}} connection requires a unique order. If you require multiple connections, open an {{site.data.keyword.dl_full_notm}} order for each connection.
  • {{site.data.keyword.dl_full_notm}} requires BGP to establish the routes to a customer's remote network.
  • Each {{site.data.keyword.dl_full_notm}} service is not redundant. Diversity can be supplied by IBM for multiple direct links. However, customers must build redundancy in their own BGP schemes.
  • If you want to connect to the classic infrastructure, keep in mind that IP subnet overlaps might exist and require exception approval. For more information, see Configuring BGP.
  • The {{site.data.keyword.cloud_notm}} services network isn't accessible directly from your remote networks.
  • {{site.data.keyword.cloud_notm}} doesn't permit customers to back haul traffic between their remote sites across the {{site.data.keyword.cloud_notm}} backbone. Use {{site.data.keyword.dl_full_notm}} to let your remote networks communicate privately with your {{site.data.keyword.cloud_notm}} infrastructure.
  • {{site.data.keyword.dl_full_notm}} requires you to use a VRF (Virtual Routing and Forwarding) instance.
  • VRF isn't fully compatible with the {{site.data.keyword.cloud_notm}} SSL and IPsec VPN services.
  • The {{site.data.keyword.cloud_notm}} fees for {{site.data.keyword.dl_short}} Dedicated cover the cost of port termination on the {{site.data.keyword.cloud_notm}} infrastructure. Customers are responsible for any fees that are associated with reaching the PoP from a remote network and any cross-connects needed within the PoP facility. {{site.data.keyword.cloud_notm}} does not order a cross-connect on any customer's behalf.
  • {{site.data.keyword.cloud_notm}} does not colocate any customer equipment in our network PoPs. Customers must work with their provider to determine whether they need to colocate any equipment in the facility where the {{site.data.keyword.cloud_notm}} network PoP exists.

Related link

{: #macsec-related-link}

Guidelines and restrictions for Direct Link Dedicated with MACsec