기존 Dedicated Interconnect 연결의 설명, 기술 담당자 이메일 주소, 회선 수(용량)를 수정할 수 있습니다.
설명이나 이메일 주소를 변경할 경우에는 변경사항이 즉시 적용됩니다.
회선 번들에는 LACP(Link Aggregation Control Protocol)가 사용되므로 회선 수를 변경해도 기존 Dedicated Interconnect 연결과 해당 VLAN 연결은 계속 정상적으로 작동합니다. 즉, 트래픽은 중단되지 않습니다.
회선 수를 늘리는 경우 연결 생성 시와 유사한 과정을 거칩니다.
Google에서는 요청된 변경사항이 포함된 LOA-CFA를 보냅니다. 공급업체에 이 문서를 보내 작업을 완료할 수 있는 권한을 부여합니다. 프로비저닝 및 테스트를 거쳐야 새로운 회선을 사용할 수 있습니다.
회선 수를 줄이는 경우 Google에서는 요청된 수만큼의 포트를 번들에서 제거하며, 제거할 회선을 조직에 알려줍니다. 그런 다음 공급업체에 문의하여 이러한 Dedicated Interconnect 연결을 삭제해야 합니다.
다음 항목은 기존 Dedicated Interconnect 연결에서 수정할 수 없습니다.
Dedicated Interconnect 연결의 링크 유형입니다. 예를 들어 회선을 10Gbps에서 100Gbps로 변경합니다. 100Gbps로 마이그레이션하려면 우선 기존 10Gbps 연결과 함께 새 100Gbps Dedicated Interconnect 연결을 프로비저닝한 다음 트래픽을 100Gbps 연결로 마이그레이션해야 합니다.
예를 들어 20Gbps의 Dedicated Interconnect 연결이 있는데 이를 40Gbps로 설정하려는 경우에는 --requested-link-count=4를 사용합니다.
새 회선에 대한 요금은 사용할 수 있게 된 후(모든 테스트 통과 후) 또는 주문 접수일로부터 30일 후에 청구됩니다. 그 전에는 요금이 부과되지 않습니다. 원래 회선 수로 되돌려 주문을 취소할 수 있습니다. LACP 번들의 크기를 조절하면 삭제한 회선에 대한 요금 청구가 중지됩니다.
[[["이해하기 쉬움","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-08(UTC)"],[],[],null,["# Modify connections\n\nFor an existing Dedicated Interconnect connection, you can modify its\ndescription, technical contact email address, and the number of circuits\n(the capacity).\n| **Note:** For definitions of terms used on this page, see [Cloud Interconnect key terms](/network-connectivity/docs/interconnect/concepts/terminology).\n\nIf you modify the description or email address, these changes are immediate.\nIf you change the number of circuits, the existing Dedicated Interconnect connection and\nits VLAN attachments continue to operate as normal because the circuit bundle\nuses Link Aggregation Control Protocol (LACP). Traffic isn't disrupted.\n\n- If you increase the number of circuits, you follow a process similar to\n [creating a connection](/network-connectivity/docs/interconnect/how-to/dedicated/provisioning-overview).\n Google sends you an LOA-CFA with your requested changes. You send this\n document to your vendor to grant them authorization to complete the work. New\n circuits aren't usable until they are provisioned and\n [tested](/network-connectivity/docs/interconnect/how-to/dedicated/testing-connections).\n\n- If you decrease the number of circuits, Google removes the requested number of\n ports from the bundle and notifies you which circuits to remove. You then\n need to contact your vendor to remove those Dedicated Interconnect connections.\n\nThe following items can't be modified for existing Dedicated Interconnect connections:\n\n- The link type on a Dedicated Interconnect connection. For example, changing the\n circuit from 10 Gpbs to 100 Gbps. If you want to migrate to\n 100 Gbps, you must first provision a new 100‑Gbps Dedicated Interconnect\n connection alongside your existing 10‑Gbps connection, and then\n migrate the traffic onto the 100‑Gbps connection.\n\n- Requested features, such as MACsec. For more information, see [MACsec\n support on existing Cloud Interconnect\n connections](/network-connectivity/docs/interconnect/concepts/macsec-overview#macsec-support-existing-connections).\n\n#### Permissions required for this task\n\nTo perform this task, you must have been granted the following permissions\n*or* the following Identity and Access Management (IAM) roles.\n\n**Permissions**\n\n- `compute.interconnects.get`\n- `compute.interconnects.update`\n\n**Roles**\n\n- `roles/owner`\n- `roles/editor`\n- `roles/compute.networkAdmin` \n\n### Console\n\n1. In the Google Cloud console, go to the Cloud Interconnect **Physical\n connections** tab.\n\n [Go to Physical connections](https://console.cloud.google.com/hybrid/interconnects/list?tab=interconnects)\n2. For the Dedicated Interconnect connection that you want to modify, select it.\n\n3. On the connection's detail page, click **Edit**.\n\n4. Modify your Dedicated Interconnect connection:\n\n - **Description**: Information about the connection.\n - **Capacity**: The total capacity of your connection, which is\n determined by the number and size of the circuits that you order.\n\n | **Note:** You can view the estimated cost of your choice in the upper-right corner of the Google Cloud console page.\n\n Select *one* of the following options:\n - 1 x 10‑Gbps circuit in 10‑Gbps increments up to 8 x 10‑Gbps (80 Gbps) circuits\n - 1 x 100‑Gbps (100 Gbps) circuit\n - 2 x 100‑Gbps (200 Gbps) circuits\n - **Technical contact**: An email address where notifications\n about this connection are sent. You don't need to enter your own\n address; you are included in all notifications. You can\n specify only one address.\n\n5. Click **Save**.\n\n6. To confirm your changes, click **Done**.\n\n### gcloud\n\nModify an existing Dedicated Interconnect connection by running the following command: \n\n```\ngcloud compute interconnects update INTERCONNECT_NAME \\\n --description=UPDATED_DESCRIPTION \\\n --noc-contact-email=UPDATED_EMAIL_CONTACT \\\n --requested-link-count=UPDATED_COUNT\n```\n\nReplace \u003cvar translate=\"no\"\u003eUPDATED_COUNT\u003c/var\u003e with the total number of circuits\nof type `link-type`.\n\nFor example, if you have a 20‑Gbps Dedicated Interconnect connection and want\nto make it 40 Gbps, use `--requested-link-count=4`.\n\nBilling for new circuits starts after they're ready to use (all\n[tests](/network-connectivity/docs/interconnect/how-to/dedicated/testing-connections)\nhave passed) or 30 days after your order is received. You aren't charged\nbefore then. You can cancel your order by reverting to the original number of\ncircuits. Billing for removed circuits stops when the LACP bundle is resized.\n\nWhat's next\n-----------\n\n- To create a Dedicated Interconnect connection, see the\n [Dedicated Interconnect provisioning overview](/network-connectivity/docs/interconnect/how-to/dedicated/provisioning-overview).\n\n- To learn more about Cloud Interconnect options, see the\n [Cloud Interconnect overview](/network-connectivity/docs/interconnect/concepts/overview).\n\n- To help you solve common issues that you might encounter when using\n Cloud Interconnect, see\n [Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting)."]]
