각 Cloud Router에는 라우터 ID라고도 하는 BGP 식별자가 있습니다.
BGP 식별자는 RFC 6286에 따라 가상 프라이빗 클라우드(VPC) 네트워크의 각 Cloud Router에서 고유합니다. BGP 식별자는 유효한 IPv4 주소로 표시되는 4옥텟 부호 없는 정수입니다.
Cloud Router에 명시적 BGP 식별자 범위를 할당할 수 있습니다.
이렇게 하면 할당된 범위에서 안정적인 BGP 식별자가 Cloud Router에 할당됩니다.
IPv6 BGP에는 명시적인 BGP 식별자 범위가 필요합니다. 아직 BGP 식별자 범위가 할당되지 않은 Cloud Router에 IPv6 인터페이스를 추가하면 IPv4 링크 로컬 주소 공간의 임의 범위가 할당됩니다.
명시적 BGP 식별자 범위가 없는 Cloud Router에는 IPv4 인터페이스 중 사전순으로 마지막 IPv4 주소에 해당하는 BGP 식별자가 할당됩니다.
BGP 식별자 변경 및 BGP 세션 다시 시작
명시적 BGP 식별자 범위를 구성하지 않은 경우 다음과 같은 상황에서 Cloud Router가 자동 생성된 라우터 ID를 변경할 수 있습니다.
이름: Cloud Router의 이름입니다. 이 이름은 Google Cloud 콘솔에 표시되며 Google Cloud CLI에서 Cloud Router를 참조하는 데 사용됩니다(예: my-router).
설명: 선택사항입니다. Cloud Router에 대한 설명입니다.
네트워크: 연결할 인스턴스가 포함된 VPC 네트워크입니다(예: my-network).
리전: Cloud Router를 찾으려는 리전입니다(예: asia-east1).
Google ASN: 온프레미스 네트워크에서 아직 사용하고 있지 않은 모든 비공개 ASN(64512-65534, 4200000000-4294967294)입니다. Cloud Router를 사용하려면 비공개 ASN을 사용해야 하지만 온프레미스 ASN은 공개 또는 비공개일 수 있습니다.
BGP 피어 연결 유지 간격: 피어 라우터로 전송되는 두 개의 연속 BGP 연결 유지 메시지 사이의 간격입니다. 이 값은 간격의 초 단위 값을 지정하는 20~60 사이의 정수여야 합니다. 기본값은 20초입니다. 자세한 내용은 BGP 타이머 관리를 참조하세요.
BGP 식별자: 선택사항. 네트워크에서 Cloud Router를 고유하게 식별하는 BGP 식별자는 라우터 ID라고도 합니다. 생략할 경우, IPv4 BGP 세션이 있는 Cloud Router는 IPv4 BGP 주소 중 하나를 BGP 식별자로 사용하고 이 Cloud Router에 첫 번째 IPv6 인터페이스를 추가하여 필드를 자동으로 채웁니다.
BGP_IDENTIFIER_RANGE를 서브넷 마스크 프리픽스 길이가 최대 /30인 169.254.0.0/16의 링크-로컬 IPv4 범위로 바꿉니다. 범위는 동일한 리전에 있는 Cloud Router의 기존 IPv4 Cloud Router 인터페이스 또는 BGP 식별자 범위와 겹치지 않아야 합니다.
BGP 식별자 범위 수정
이 섹션에서는 Cloud Router에서 기존 명시적 BGP 식별자 범위를 수정하는 방법을 설명합니다.
[[["이해하기 쉬움","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(UTC)"],[],[],null,["# Configure the BGP identifier range for a Cloud Router\n=====================================================\n\nEach Cloud Router has a BGP identifier, also known as a *router ID* .\nThe BGP identifier is unique to each Cloud Router in your\nVirtual Private Cloud (VPC) network as required by [RFC\n6286](https://datatracker.ietf.org/doc/html/rfc6286). A BGP identifier is\na 4-octet unsigned integer, represented as a valid IPv4 address.\n\nYou can assign an explicit BGP identifier *range* to your Cloud Router.\nIf you do, your Cloud Router is assigned a stable BGP identifier from\nthe assigned range.\n\nAn explicit BGP identifier range is required for IPv6 BGP. If you add an IPv6\ninterface to a Cloud Router that doesn't already have a BGP identifier\nrange assigned, a random range from the IPv4 link-local address space is\nassigned to it.\n\nA Cloud Router without an explicit BGP identifier range is assigned a\nBGP identifier corresponding to the lexicographically-last IPv4 address among\nits IPv4 interfaces.\n\nBGP identifier changes and BGP session restarts\n-----------------------------------------------\n\nUnless you've configured an explicit BGP identifier range, Cloud Router\nmight change the automatically generated router ID in the following\ncircumstances:\n\n- You add a BGP session\n- You remove a BGP session\n- During periodic maintenance\n\nBefore you begin\n----------------\n\n### gcloud\n\nIf you want to use the command-line examples in this guide, do the following:\n\n1. Install or update to the latest version of the [Google Cloud CLI](/compute/docs/gcloud-compute).\n2. Set a [default region and\n zone](/compute/docs/gcloud-compute#set_default_zone_and_region_in_your_local_client).\n\n### API\n\nIf you want to use the API examples in this guide, set up\n[API access](/compute/docs/api/prereqs).\n\nAssign a BGP identifier range to Cloud Router\n---------------------------------------------\n\nThis section describes how to assign an explicit BGP identifier range to a\nCloud Router. \n\n### Console\n\n1. In the Google Cloud console, go to the **Create a Cloud Router**\n page.\n\n [Go to Create a\n Cloud Router](https://console.cloud.google.com/hybrid/routers/add)\n2. Specify the Cloud Router's details:\n\n - **Name** : The name of the Cloud Router. This name is displayed in the Google Cloud console and is used by the Google Cloud CLI to reference the Cloud Router---for example, `my-router`.\n - **Description**: Optional. A description of the Cloud Router.\n - **Network** : The VPC network that contains the instances that you want to reach---for example, `my-network`.\n - **Region** : The region where you want to locate the Cloud Router---for example, `asia-east1`.\n -\n **Google ASN** : Any\n [private ASN](https://tools.ietf.org/html/rfc6996)\n (`64512`-`65534`,\n `4200000000`-`4294967294`) that you aren't already\n using in the on-premises network. Cloud Router requires that\n you use a private ASN, but your on-premises ASN can be public or\n private.\n\n\n | **Note:** If you are using Cloud Router with Partner Interconnect, you must specify the Google-owned public ASN `16550` instead.\n\n \u003cbr /\u003e\n\n - **BGP peer keepalive interval** : The interval between two successive BGP keepalive messages that are sent to the peer router. This value must be an integer between 20 and 60 that specifies the number of seconds for the interval. The default is 20 seconds. For more information, see [Manage BGP\n timers](/network-connectivity/docs/router/how-to/managing-bgp-timers).\n -\n **BGP identifier** : Optional. The BGP identifier, sometimes called a\n *router ID*, that uniquely identifies a Cloud Router in a\n network. If omitted, Cloud Routers with IPv4 BGP sessions use\n one of the IPv4 BGP addresses as the BGP identifier, and adding the\n first IPv6 interface to this Cloud Router populates the field\n automatically.\n\n\n For more\n information, see\n [Configure the BGP\n identifier range for a Cloud Router](/network-connectivity/docs/router/how-to/configure-bgp-identifier).\n3. Optional: To specify custom advertised routes, go to the **Advertised routes** section. For more information, see [Advertised routes](/network-connectivity/docs/router/concepts/advertised-routes).\n 1. To specify custom **Routes** , select **Create custom routes**.\n 2. Choose whether to advertise the subnets visible to the Cloud Router. Enabling this option mimics the Cloud Router's default behavior.\n 3. To add an advertised route, select **Add a custom route**, and then configure it.\n4. To save your settings and create a Cloud Router, click **Create**. Your new Cloud Router appears on the Cloud Router listing page. To view its details and to configure a BGP session, select it.\n\n### gcloud\n\nTo assign an explicit BGP identifier range when you create the\nCloud Router, use the `--bgp-identifier-range` flag. \n\n```\ngcloud compute routers create ROUTER_NAME \\\n --bgp-identifier-range=BGP_IDENTIFIER_RANGE\n```\n\nReplace \u003cvar translate=\"no\"\u003eBGP_IDENTIFIER_RANGE\u003c/var\u003e with a link-local IPv4 range\nfrom `169.254.0.0/16` with a subnet mask prefix length of at most `/30`.\nThe IPv4 address range must not overlap either of the following:\n\n- The IPv4 address range used by another BGP session on this\n Cloud Router.\n\n- Any custom BGP identifier range used by another\n Cloud Router in the same VPC network and region.\n\n### API\n\nUse the\n[`routers.insert` method](/compute/docs/reference/rest/v1/routers/insert): \n\n```\n POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/routers/ROUTER_NAME\n {\n \"bgp\": {\n \"asn\": \"ASN_NUMBER\",\n \"keepaliveInterval\": KEEPALIVE_INTERVAL,\n \"identifierRange\": BGP_IDENTIFIER_RANGE\n },\n \"name\": \"ROUTER_NAME\",\n \"network\": \"NETWORK\"\n }\n```\n\nReplace \u003cvar translate=\"no\"\u003eBGP_IDENTIFIER_RANGE\u003c/var\u003e with a link-local IPv4 range\nfrom `169.254.0.0/16` with a subnet mask prefix length of at most `/30`. The\nrange must not overlap with any existing IPv4 Cloud Router\ninterface or a BGP identifier range of a Cloud Router in the same\nregion.\n\nModify the BGP identifier range\n-------------------------------\n\nThis section describes how to modify an existing explicit BGP identifier\nrange on a Cloud Router.\n**Caution:** Changing the explicit BGP identifier range of Cloud Router causes all existing BGP sessions to restart for all BGP peers on the Cloud Router. \n\n### gcloud\n\nTo change the explicit BGP identifier range, run the following command. \n\n```\ngcloud compute routers update ROUTER_NAME \\\n --bgp-identifier-range=BGP_IDENTIFIER_RANGE\n```\n\nReplace \u003cvar translate=\"no\"\u003eBGP_IDENTIFIER_RANGE\u003c/var\u003e with a link-local IPv4 range\nfrom `169.254.0.0/16` with a subnet mask prefix length of at most `/30`.\n\nThe IPv4 address range must not overlap either of the following:\n\n- The IPv4 address range used by another BGP session on this\n Cloud Router.\n\n- Any custom BGP identifier range used by another\n Cloud Router in the same VPC network and region.\n\n### API\n\nUse the\n[`routers.patch` method](/compute/docs/reference/rest/v1/routers/patch)\nto update the `bgp.identifierRange` field: \n\n```\n PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/routers/ROUTER_NAME\n {\n \"bgp\": {\n \"identifierRange\": BGP_IDENTIFIER_RANGE\n }\n }\n```\n\nReplace \u003cvar translate=\"no\"\u003eBGP_IDENTIFIER_RANGE\u003c/var\u003e with a link-local IPv4 range\nfrom `169.254.0.0/16` with a subnet mask prefix length of at most `/30`.\nThe IPv4 address range must not overlap either of the following:\n\n- The IPv4 address range used by another BGP session on this\n Cloud Router.\n\n- Any custom BGP identifier range used by another\n Cloud Router in the same VPC network and region.\n\nWhat's next\n-----------\n\n- [View Cloud Router details](/network-connectivity/docs/router/how-to/viewing-router-details)"]]
