This document describes common problems that you might encounter with the SLAeligibility of your Cloud Interconnect connection groups or VLANattachment groups, and provides troubleshooting steps to help you resolve thoseproblems.

Topology capability blockers

The following sections describe problems with the topology of your interconnectgroups or VLAN attachment groups. For Cloud Interconnect connection groups, theconfigured.topologyCapability.intendedCapabilityBlockers field returnsblockers that map to each of these sections. For VLAN Attachment groups, the sameinformation is returned by theconfigured.availabilitySla.intendedSlaBlockers field.The solutions generally involve modifying your interconnect connection group resource.

No interconnects

If you receive this blocker, then your connection group doesn't contain anyinterconnect connections. To resolve this blocker, seeCreate Cloud Interconnect connections within a connection grouporAdd existing Cloud Interconnect connections to a group.

No attachments

If you receive this blocker, then your VLAN attachment group doesn't contain anyVLAN attachments. To resolve this blocker, seeAdd VLAN attachments to a VLAN attachment group.

Incompatible metros

If you receive this blocker, then your connections or VLAN attachments need tobe configured in additional metropolitan areas (metros). Check theconfigured.topologyCapability.intendedCapabilityBlockers.metros field (for connection groups)orconfigured.availabilitySla.intendedSlaBlockers field (for VLAN attachment groups) toidentify the metro or metros in which you have already deployed resources,then create or add a connection or VLAN attachment to the group within a newmetro. To resolve this blocker, see the following pages:

• Connection groups:
  • Create Cloud Interconnect connections within a connection group
  • Add existing Cloud Interconnect connections to a group.
• VLAN attachment groups:
  • Add VLAN attachments to a VLAN attachment group.

Incompatible regions

If you receive this blocker, then your VLAN attachments need to be configured inadditional regions. Check theconfigured.availabilitySla.intendedSlaBlockers.regions field toidentify the region or regions in which you have already deployed resources,then create or add a VLAN attachment to the group within a new region. Toresolve this blocker, seeAdd VLAN attachments to a VLAN attachment group.

No interconnects in metro and zone

If you receive this blocker, then your connections within the same metro need tobe configured in different edge availability domains. Check theconfigured.topologyCapability.intendedCapabilityBlockers.zonesfield to identify the zone in which you are missing an interconnect connection,then seeCreate Cloud Interconnect connections within a connection grouporAdd existing Cloud Interconnect connections to a groupto resolve this blocker.

No attachments in metro and zone

If you receive this blocker, then your VLAN attachments within the same metroneed to be configured in different edge availability domains. Check theconfigured.availabilitySla.intendedSlaBlockers.zonesfield to identify the zone in which you are missing a VLAN attachment,then seeAdd VLAN attachments to a VLAN attachment groupto resolve this blocker.

Missing global routing

If you receive this blocker, then your VPC network's dynamic routing mode isn'tset toGlobal. To resolve this blocker,change your VPC network's dynamic routing modetoGlobal.

Not available

If you receive this blocker, then you have chosen a level of reliability thatisn't generally available with your configured connection group or VLANattachment group. To resolve this blocker,contact support.

Other

If you receive this blocker, then there is an issue with your deployment thatdoesn't fall under the other categories. To resolve this blocker,contact support.