[[["わかりやすい","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-08-22 UTC。"],[],[],null,["# Create an NCC Gateway spoke\n\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis page describes how to create an NCC Gateway spoke resource\nin a specified region connected to the Network Connectivity Center hub. \n\n### gcloud\n\nUse the [`gcloud beta network-connectivity spokes gateways create` command](/sdk/gcloud/reference/network-connectivity/spokes/gateways/create): \n\n```\ngcloud beta network-connectivity spokes gateways create SPOKE_NAME \\\n --region=REGION \\\n --hub=HUB \\\n --capacity=CAPACITY \\\n --ip-range-reservations=IP_RANGE \\\n --group=gateways\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eSPOKE_NAME\u003c/var\u003e: the name of the spoke\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: the region that you want the NCC Gateway to be deployed in\n- \u003cvar translate=\"no\"\u003eHUB\u003c/var\u003e: the name of the hub for the spoke\n- \u003cvar translate=\"no\"\u003eCAPACITY\u003c/var\u003e: the capacity of the gateway spoke, in Gbps\n\n Supported capacity values are 1, 10, or 100.\n- \u003cvar translate=\"no\"\u003eIP_RANGE\u003c/var\u003e: a block of IP address ranges used to allocate\n supporting infrastructure for this gateway---for example, 10.1.2.0/23\n\n The IP address block must be a /23 range. This IP address block must not\n overlap with subnets in any spoke or peer network that the gateway can\n communicate with.\n | **Note:** You can't change assigned IP address ranges. Some IP address ranges are reserved for SSE partners.\n\n### API\n\nTo create an NCC Gateway spoke, use the\n[`projects.locations.spokes.create` method](/network-connectivity/docs/reference/networkconnectivity/rest/v1beta/projects.locations.spokes/create). \n\n```\n POST https://networkconnectivity.googleapis.com/v1beta/projects/PROJECT_ID/locations/global/spokes/SPOKE_NAME\n {\n \"hub\":\"HUB_NAME\",\n \"location\" : LOCATION,\n \"gateway\": {\n \"ip_range_reservation\": IP_RANGE,\n \"capacity\": CAPACITY\n \"group\": gateways\n },\n }\n```\n\nReplace the following values:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the project ID of the project that contains the new spoke\n- \u003cvar translate=\"no\"\u003eSPOKE_NAME\u003c/var\u003e: the name of the spoke\n- \u003cvar translate=\"no\"\u003eHUB_NAME\u003c/var\u003e: the name of the hub that you are attaching the spoke to\n- \u003cvar translate=\"no\"\u003eLOCATION\u003c/var\u003e: the region that you want the NCC Gateway to be deployed in\n- \u003cvar translate=\"no\"\u003eIP_RANGE\u003c/var\u003e: a block of IP address ranges used to allocate\n supporting infrastructure for this gateway---for example, 10.1.2.0/23\n\n The IP address block must be a /23 range. This IP address block must not\n overlap with subnets in any spoke or peer network that the gateway can\n communicate with.\n | **Note:** You can't change assigned IP address ranges. Some IP address ranges are reserved for SSE partners\n- \u003cvar translate=\"no\"\u003eCAPACITY\u003c/var\u003e: the capacity of the gateway spoke, in Gbps\n\n Supported capacity values are 1, 10, or 100."]]
