Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini memberikan petunjuk tentang cara membuat atau mengupdate lampiran VLAN di Google Distributed Cloud (GDC) yang terisolasi.
Lampiran VLAN mewakili lampiran Virtual Local Area Network (VLAN) dan konfigurasi sesi BGP terkaitnya ke link interkoneksi. VLAN menentukan bagian jaringan Anda yang memiliki akses melalui koneksi ini.
Konfigurasi sesi BGP dan lampiran VLAN terkait adalah resource yang diperlukan
untuk menyiapkan koneksi air-gapped yang aman dengan bandwidth tinggi dan
latensi rendah.
Untuk membuat atau mengupdate lampiran VLAN, Anda harus memiliki hal berikut:
Tiket yang dikirimkan di portal GDC yang meminta interkoneksi dengan spesifikasi pilihan Anda, seperti konektivitas redundan 10 G.
Informasi dan ID resource yang diperlukan untuk resource interkoneksi yang dikonfigurasi oleh Operator Infrastruktur (IO). Untuk mengetahui informasi selengkapnya, lihat Proses pembuatan interkoneksi.
UNIQUE_INTERCONNECT_NAME: nama unik untuk resource InterconnectAttachment ini.
INTERCONNECT_LINK_NAME: referensi objek universal ke link interkoneksi di namespace gpc-system.
INTERCONNECT_GROUP_NAME: referensi objek universal ke grup interconnect di namespace gpc-system yang berisi INTERCONNECT_LINK_NAME.
LOCAL_IP_SUBNET: alamat IP lokal
peer /31 di sisi GDC.
LOCAL_ASN: Nomor sistem otonom (ASN) lokal Border Gateway Protocol (BGP).
PEER_ASN: nomor sistem otonom (ASN)
peer dari Border Gateway Protocol (BGP).
PEER_IP: alamat IP peer dari peer
/31 di sisi peer.
PEER_EXTERNAL_SUBNET: subnet eksternal peer yang diizinkan oleh interkoneksi ini. Jika ada lebih dari satu subnet,
cantumkan semuanya di kolom peerExternalSubnets.
ROUTE_POLICY_NAME: referensi objek
universal ke kebijakan rute di namespace gpc-system.
ATTACHMENT_GROUP_NAME: referensi objek
universal ke kebijakan rute di namespace gpc-system yang
merupakan bagian dari lampiran ini.
VLAN_ID: ID VLAN yang akan digunakan pada
interkoneksi ini.
Output menampilkan lampiran VLAN dan menunjukkan True di kolom Ready:
NAME AGE TYPE MTU VLAN-ID INTERCONNECT GROUP INTERCONNECT LINK READY
interconnect-attachment-zv-aa-blsw01-directconnect-1 3d2h DirectConnect 3966 interconnect-group-directconnect-1 interconnect-zv-aa-blsw01-directconnect-1 True
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis page outlines the process for creating or updating a VLAN attachment in Google Distributed Cloud (GDC) air-gapped environments, which is necessary to connect your network to an interconnect link.\u003c/p\u003e\n"],["\u003cp\u003eBefore creating a VLAN attachment, you must submit a ticket for an interconnect, have the necessary resource information, and possess the required identity and access roles.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves creating a YAML file (\u003ccode\u003einterconnectattachment.yaml\u003c/code\u003e) with specific configuration details, including interconnect link references, BGP session settings, route policy, attachment group, and VLAN ID.\u003c/p\u003e\n"],["\u003cp\u003eAfter configuring the YAML file, you apply it using \u003ccode\u003ekubectl\u003c/code\u003e to create the VLAN attachment, and then you can verify its successful creation by checking its status, ensuring it displays 'True' in the 'Ready' column.\u003c/p\u003e\n"]]],[],null,["# Create a VLAN attachment\n\nThis page provides instructions on how to create or update a VLAN\nattachment in Google Distributed Cloud (GDC) air-gapped.\n\nA VLAN attachment represents an attachment of a Virtual Local Area\nNetwork (VLAN) and its associated BGP session configuration to an interconnect\nlink. The VLAN specifies which part of your network has access through this\nconnection.\n\nThe VLAN attachment and its associated BGP session configuration are a required\nresource for setting up a secure air-gapped connection with high bandwidth and\nlow latency.\n\nThis page is for developers within the application operator group who are\nlooking to establish connectivity with interconnects. For more information, see\n[Audiences for GDC air-gapped\ndocumentation](/distributed-cloud/hosted/docs/latest/gdch/resources/audiences).\n\nBefore you begin\n----------------\n\nTo create or update a VLAN attachment, you must have the following:\n\n- A submitted ticket in the GDC portal requesting an interconnect with your chosen specifications, such as 10 G of redundant connectivity.\n- The necessary resource information and IDs for the interconnect resources that the Infrastructure Operator (IO) configures. For more information, see [Interconnect creation\n process](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/interconnects/interconnect-overview#interconnect-creation).\n- The necessary identity and access roles. For more information, see [Prepare predefined roles and permissions](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/interconnects/interconnect-overview#prepare-roles).\n\nCreate or update a VLAN attachment\n----------------------------------\n\nTo create or update a VLAN attachment, follow these steps:\n\n1. Create a YAML file named `interconnectattachment.yaml`.\n2. Add the following content to the file:\n\n apiVersion: system.private.gdc.goog/v1alpha1\n kind: InterconnectAttachment\n metadata:\n name: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eUNIQUE_INTERCONNECT_NAME\u003c/span\u003e\u003c/var\u003e\n namespace: gpc-system\n spec:\n interconnectLinkRef:\n name: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eINTERCONNECT_LINK_NAME\u003c/span\u003e\u003c/var\u003e\n namespace: gpc-system\n parentInterconnectRef:\n name: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eINTERCONNECT_GROUP_NAME\u003c/span\u003e\u003c/var\u003e\n namespace: gpc-system\n parentInterconnectType: DirectConnect\n bgpSessionConfig:\n localIP: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eLOCAL_IP_SUBNET\u003c/span\u003e\u003c/var\u003e\n localASN: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eLOCAL_ASN\u003c/span\u003e\u003c/var\u003e\n peerASN: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003ePEER_ASN\u003c/span\u003e\u003c/var\u003e\n peerIP: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003ePEER_IP\u003c/span\u003e\u003c/var\u003e\n peerExternalSubnets:\n - \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003ePEER_EXTERNAL_SUBNET\u003c/span\u003e\u003c/var\u003e\n routePolicyRef:\n name: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eROUTE_POLICY_NAME\u003c/span\u003e\u003c/var\u003e\n namespace: gpc-system\n attachmentGroup:\n name: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eATTACHMENT_GROUP_NAME\u003c/span\u003e\u003c/var\u003e\n namespace: gpc-system\n vlanID: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eVLAN_ID\u003c/span\u003e\u003c/var\u003e\n status: {}\n\n3. Replace the following:\n\n - \u003cvar translate=\"no\"\u003eUNIQUE_INTERCONNECT_NAME\u003c/var\u003e: unique name for this `InterconnectAttachment` resource.\n - \u003cvar translate=\"no\"\u003eINTERCONNECT_LINK_NAME\u003c/var\u003e: the universal object reference to the interconnect link in the `gpc-system` namespace.\n - \u003cvar translate=\"no\"\u003eINTERCONNECT_GROUP_NAME\u003c/var\u003e: the universal object reference to the interconnect group in the `gpc-system` namespace containing \u003cvar translate=\"no\"\u003eINTERCONNECT_LINK_NAME\u003c/var\u003e.\n - \u003cvar translate=\"no\"\u003eLOCAL_IP_SUBNET\u003c/var\u003e: the local IP address of the `/31` peer on the GDC side.\n - \u003cvar translate=\"no\"\u003eLOCAL_ASN\u003c/var\u003e: the local autonomous system number (ASN) of the Border Gateway Protocol (BGP).\n - \u003cvar translate=\"no\"\u003ePEER_ASN\u003c/var\u003e: the peer autonomous system number (ASN) of the Border Gateway Protocol (BGP).\n - \u003cvar translate=\"no\"\u003ePEER_IP\u003c/var\u003e: the peer IP address of the `/31` peer on the side of the peer.\n - \u003cvar translate=\"no\"\u003ePEER_EXTERNAL_SUBNET\u003c/var\u003e: the peer external subnet that this interconnect allows. If there is more than one subnet, list all of them in the `peerExternalSubnets` field.\n - \u003cvar translate=\"no\"\u003eROUTE_POLICY_NAME\u003c/var\u003e: the universal object reference to the route policy in the `gpc-system` namespace.\n - \u003cvar translate=\"no\"\u003eATTACHMENT_GROUP_NAME\u003c/var\u003e: the universal object reference to the route policy in the `gpc-system` namespace that this attachment is a part of.\n - \u003cvar translate=\"no\"\u003eVLAN_ID\u003c/var\u003e: the VLAN ID to use on this interconnect.\n4. Create the VLAN attachment:\n\n kubectl apply -f interconnectattachment.yaml -n gpc-system\n --kubeconfig=\u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e with the path to the\n kubeconfig file for the Management API server.\n5. Check that the creation of the VLAN attachment is successful:\n\n kubectl get interconnectattachment -n gpc-system\n --kubeconfig=\u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e\n\n6. The output returns the VLAN attachment and shows `True` in the `Ready` column:\n\n NAME AGE TYPE MTU VLAN-ID INTERCONNECT GROUP INTERCONNECT LINK READY\n interconnect-attachment-zv-aa-blsw01-directconnect-1 3d2h DirectConnect 3966 interconnect-group-directconnect-1 interconnect-zv-aa-blsw01-directconnect-1 True"]]
