이 페이지에서는 Memorystore for Memcached 네트워킹의 개요를 제공합니다. 일반적인 네트워킹 오류 목록은 네트워킹 오류 시나리오를 참조하세요.
비공개 서비스 액세스
Memorystore for Memcached는 비공개 서비스 액세스를 사용하여 Cloud SQL, Redis용 Memorystore, Memorystore for Memcached 등 일부 Google Cloud 서비스의 내부 네트워크와 프로젝트 간에 네트워크 피어링을 만듭니다.
즉, 해당 네트워크를 사용하여 Memcached 인스턴스를 만들려면 먼저 네트워크의 비공개 서비스 액세스 연결을 설정해야 합니다.
일반적으로 조직의 네트워킹 팀 또는 네트워크 관리자, 또는 둘 다 비공개 서비스 액세스 연결을 설정합니다. 이렇게 하면 네트워킹 팀이 다른 Google Cloud 리소스에 사용된 IP 주소 또는 범위와 겹치지 않도록 하여 연결 문제를 일으킬 수 있습니다.
특히 설정 프로세스에서 오류가 발생하는 경우 조직의 네트워크/보안 팀에 문의하여 비공개 서비스 연결을 설정하는 것이 좋습니다. 네트워킹 팀에 문의할 때 다음 정보를 보냅니다.
The Memorystore for Memcached instance cannot be created due to the following
error:
"Google private services access is not enabled. Enable privates service access
and try again."
Before an instance can be created, a private service access connection needs to
be established for network <project name: network>. Please refer to the
following Memorystore documentation links for more information on how to create
this connection:
* Networking.
* Establishing a private services access connection.
* Verifying a private services access connection.
[[["이해하기 쉬움","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-04(UTC)"],[],[],null,["# Networking\n\nThis page gives an overview of networking for Memorystore for Memcached. For a list of\ncommon networking errors, see [Networking error scenarios](/memorystore/docs/memcached/troubleshoot-issues#networking_error_scenarios).\n\nPrivate services access\n-----------------------\n\nMemorystore for Memcached uses [private services access](/vpc/docs/private-services-access)\nto create a network peering between your project and an internal network for\nsome Google Cloud services like Cloud SQL, Memorystore for Redis,\nand Memorystore for Memcached.\n\n**This means that you must first [establish a private services access connection](/memorystore/docs/memcached/establishing-connection)\nfor a network before you can create a Memcached instance using that network.**\n\nUsing a private services access connection offers you the benefit of\ncentralized, customizable IP address ranges for the aforementioned services. For\ninstructions on selecting a specific IP range allocation, see [Creating a Memcached instance that uses a specific IP address range](/memorystore/docs/memcached/create-manage-instances#creating_a_memcached_instance_that_uses_a_specific_ip_address_range).\n| **Important:** Once a private services connection is established for any of these services on a network, it is established for all other services on that network that use the private services access networking architecture.\n\nOn-premises access with private services access\n-----------------------------------------------\n\nYou can connect from a client in an on-premises network if the on-premises\nnetwork is connected to the VPC network to which your\nMemorystore for Memcached instance is connected. To permit connections from an\non-premises network, do the following:\n\n1. Ensure your Shared VPC network is connected to your on-premises network using a one of the following options\n - [Cloud VPN tunnel](/network-connectivity/docs/vpn/concepts/overview)\n - an interconnect attachment (VLAN) for [Dedicated Interconnect](/network-connectivity/docs/interconnect/how-to/dedicated/provisioning-overview) or [Partner Interconnect](/network-connectivity/docs/interconnect/how-to/partner/provisioning-overview).\n2. [Identify the peering](/vpc/docs/configure-private-services-access#listing-connections) produced by the private services connection. The peering used by Memorystore for Memcached is named `servicenetworking-googleapis-com`.\n3. [Update the peering](/vpc/docs/using-vpc-peering#update-peer-connection) connection to exchange custom routes by setting both `--import-custom-routes` and `--export-custom-routes` flag\n4. [Identify the allocated range](/vpc/docs/configure-private-services-access#listing_allocated_ip_address_ranges) used by the private services connection.\n5. [Create a Cloud Router custom advertised route](/network-connectivity/docs/router/how-to/advertising-custom-ip) for the allocated range on the Cloud Routers managing BGP sessions for your Cloud VPN tunnels or Cloud Interconnect attachments (VLANs).\n\nCommunicating networking requirements\n-------------------------------------\n\nUsually the networking team and/or network admin for your organization is\nresponsible for setting up a private services access connection. This allows the\nnetworking team to ensure that no IP addresses or ranges used for other\nGoogle Cloud resources overlap, which can cause connectivity issues.\n\nWe recommend that you contact the network\\\\security team in your organization to\nset up the private service connection for you, especially if you encounter an\nerror during the setup process. When reaching out to your networking team, send\nthem the following information: \n\n```\nThe Memorystore for Memcached instance cannot be created due to the following\nerror:\n\n\"Google private services access is not enabled. Enable privates service access\nand try again.\"\n\nBefore an instance can be created, a private service access connection needs to\nbe established for network \u003cproject name: network\u003e. Please refer to the\nfollowing Memorystore documentation links for more information on how to create\nthis connection:\n\n* Networking.\n* Establishing a private services access connection.\n* Verifying a private services access connection.\n```\n\nIP addresses\n------------\n\nEach Memorystore for Memcached instance has a [discovery endpoint](/memorystore/docs/memcached/auto-discovery-overview),\nand each node in the instance has its own IP address. You can view these IP\naddresses in the Google Cloud console, or by using [`gcloud memcache instances describe`](/sdk/gcloud/reference/memcache/instances/describe).\n\nIP addresses for nodes and for the discovery endpoint do not change.\n\nSupported networks and client IP ranges\n---------------------------------------\n\n###### The following network or instances with RFC 1918 IP addresses are supported:\n\n- [VPC networks](/vpc/docs/vpc) except [legacy networks](/vpc/docs/legacy)\n- [Shared VPC networks](/vpc/docs/shared-vpc)\n- on-premise systems\n- Compute Engine VM instances except for 172.17.0.0/16 because this IP range is reserved for internal components\n- We recommend using a private services access range with a block size of at least `/24` to support Memorystore for Memcached and other services. However, the minimum block size needed to support Memorystore for Memcached is `/26`.\n\nWhat's next\n-----------\n\n- [Establish a private services access connection](/memorystore/docs/memcached/establishing-connection).\n- [Create a Memcached instance](/memorystore/docs/memcached/creating-managing-instances)."]]
