Fix SLA eligibility problems

This document describes common problems that you might encounter with the SLA eligibility of your Cloud Interconnect connection groups or VLAN attachment groups, and provides troubleshooting steps to help you resolve those problems.

Topology capability blockers

The following sections describe problems with the topology of your interconnect groups or VLAN attachment groups. For Cloud Interconnect connection groups, the configured.topologyCapability.intendedCapabilityBlockers field returns blockers that map to each of these sections. For VLAN Attachment groups, the same information is returned by the configured.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 any interconnect connections. To resolve this blocker, see Create Cloud Interconnect connections within a connection group or Add existing Cloud Interconnect connections to a group.

No attachments

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

Incompatible metros

If you receive this blocker, then your connections or VLAN attachments need to be configured in additional metropolitan areas (metros). Check the configured.topologyCapability.intendedCapabilityBlockers.metros field (for connection groups) or configured.availabilitySla.intendedSlaBlockers field (for VLAN attachment groups) to identify 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 new metro. 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 in additional regions. Check the configured.availabilitySla.intendedSlaBlockers.regions field to identify 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. To resolve this blocker, see Add 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 to be configured in different edge availability domains. Check the configured.topologyCapability.intendedCapabilityBlockers.zones field to identify the zone in which you are missing an interconnect connection, then see Create Cloud Interconnect connections within a connection group or Add existing Cloud Interconnect connections to a group to resolve this blocker.

No attachments in metro and zone

If you receive this blocker, then your VLAN attachments within the same metro need to be configured in different edge availability domains. Check the configured.availabilitySla.intendedSlaBlockers.zones field to identify the zone in which you are missing a VLAN attachment, then see Add VLAN attachments to a VLAN attachment group to resolve this blocker.

Missing global routing

If you receive this blocker, then your VPC network's dynamic routing mode isn't set to Global. To resolve this blocker, change your VPC network's dynamic routing mode to Global.

Not available

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

Other

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