[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[],[],null,["# Fix SLA eligibility problems\n\nThis document describes common problems that you might encounter with the SLA\neligibility of your Cloud Interconnect connection groups or VLAN\nattachment groups, and provides troubleshooting steps to help you resolve those\nproblems.\n\nTopology capability blockers\n----------------------------\n\nThe following sections describe problems with the topology of your interconnect\ngroups or VLAN attachment groups. For Cloud Interconnect connection groups, the\n`configured.topologyCapability.intendedCapabilityBlockers` field returns\nblockers that map to each of these sections. For VLAN Attachment groups, the same\ninformation is returned by the `configured.availabilitySla.intendedSlaBlockers` field.\nThe solutions generally involve modifying your interconnect connection group resource.\n\n### No interconnects\n\nIf you receive this blocker, then your connection group doesn't contain any\ninterconnect connections. To resolve this blocker, see\n[Create Cloud Interconnect connections within a connection group](/network-connectivity/docs/interconnect/how-to/dedicated/modifying-connection-groups#create-connections)\nor\n[Add existing Cloud Interconnect connections to a group](/network-connectivity/docs/interconnect/how-to/dedicated/modifying-connection-groups#add-connections).\n\n### No attachments\n\nIf you receive this blocker, then your VLAN attachment group doesn't contain any\nVLAN attachments. To resolve this blocker, see\n[Add VLAN attachments to a VLAN attachment group](/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments#add-to-group).\n\n### Incompatible metros\n\nIf you receive this blocker, then your connections or VLAN attachments need to\nbe configured in additional metropolitan areas (metros). Check the\n`configured.topologyCapability.intendedCapabilityBlockers.metros` field (for connection groups)\nor `configured.availabilitySla.intendedSlaBlockers` field (for VLAN attachment groups) to\nidentify the metro or metros in which you have already deployed resources,\nthen create or add a connection or VLAN attachment to the group within a new\nmetro. To resolve this blocker, see the following pages:\n\n- Connection groups:\n - [Create Cloud Interconnect connections within a connection group](/network-connectivity/docs/interconnect/how-to/dedicated/modifying-connection-groups#create-connections)\n - [Add existing Cloud Interconnect connections to a group](/network-connectivity/docs/interconnect/how-to/dedicated/modifying-connection-groups#add-connections).\n- VLAN attachment groups:\n - [Add VLAN attachments to a VLAN attachment group](/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments#add-to-group).\n\n### Incompatible regions\n\nIf you receive this blocker, then your VLAN attachments need to be configured in\nadditional regions. Check the\n`configured.availabilitySla.intendedSlaBlockers.regions` field to\nidentify the region or regions in which you have already deployed resources,\nthen create or add a VLAN attachment to the group within a new region. To\nresolve this blocker, see\n[Add VLAN attachments to a VLAN attachment group](/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments#add-to-group).\n\n### No interconnects in metro and zone\n\nIf you receive this blocker, then your connections within the same metro need to\nbe configured in different edge availability domains. Check the\n`configured.topologyCapability.intendedCapabilityBlockers.zones`\nfield to identify the zone in which you are missing an interconnect connection,\nthen see\n[Create Cloud Interconnect connections within a connection group](/network-connectivity/docs/interconnect/how-to/dedicated/modifying-connection-groups#create-connections)\nor\n[Add existing Cloud Interconnect connections to a group](/network-connectivity/docs/interconnect/how-to/dedicated/modifying-connection-groups#add-connections)\nto resolve this blocker.\n\n### No attachments in metro and zone\n\nIf you receive this blocker, then your VLAN attachments within the same metro\nneed to be configured in different edge availability domains. Check the\n`configured.availabilitySla.intendedSlaBlockers.zones`\nfield to identify the zone in which you are missing a VLAN attachment,\nthen see\n[Add VLAN attachments to a VLAN attachment group](/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments#add-to-group)\nto resolve this blocker.\n\n### Missing global routing\n\nIf you receive this blocker, then your VPC network's dynamic routing mode isn't\nset to **Global** . To resolve this blocker,\n[change your VPC network's dynamic routing mode](/network-connectivity/docs/router/how-to/create-network-set-modes#change-network-modes)\nto **Global**.\n\n### Not available\n\nIf you receive this blocker, then you have chosen a level of reliability that\nisn't generally available with your configured connection group or VLAN\nattachment group. To resolve this blocker,\n[contact support](/network-connectivity/docs/interconnect/support/getting-support).\n\nOther\n-----\n\nIf you receive this blocker, then there is an issue with your deployment that\ndoesn't fall under the other categories. To resolve this blocker,\n[contact support](/network-connectivity/docs/interconnect/support/getting-support)."]]
