Network Connectivity Center에서는 타사 네트워크 가상 어플라이언스를 사용하여 외부 사이트 및 Virtual Private Cloud(VPC) 네트워크 리소스 간 연결을 설정할 수 있습니다. 이 유형의 연결을 설정하려면 라우터 어플라이언스 기능을 사용합니다. 이러한 라우터 어플라이언스 사용 방식은 모든 Google Cloud 리전에서 지원됩니다.
라우터 어플라이언스
라우터 어플라이언스 기능을 사용하면 Google Cloud 내에서 네트워크 가상 어플라이언스를 설치하고 이를 스포크의 지원 리소스로 사용할 수 있습니다.
라우터 애플리케이션 인스턴스를 만들려면 Compute Engine 가상 머신(VM)에 가상 어플라이언스 이미지를 설치하고 추가 설정 단계를 완료합니다.
이 설정에는 VM과 Cloud Router 사이의 Border Gateway Protocol(BGP) 피어링 설정이 포함됩니다. BGP는 Cloud Router와 라우터 어플라이언스 인스턴스 간에 경로를 동적으로 교환합니다. 경로 교환을 통해서는 VPC 네트워크와 다른 네트워크 사이에 연결을 설정할 수 있습니다. 지원되는 Network Connectivity Center 파트너에서 제공하는 이미지를 사용하는 것이 좋습니다.
라우터 어플라이언스에 대한 자세한 내용은 라우터 어플라이언스 개요를 참조하세요.
Network Connectivity Center에서는 네트워크 연결에 대해 허브 및 스포크 아키텍처를 사용할 수 있습니다. Network Connectivity Center에 대한 자세한 내용은 Network Connectivity Center 개요를 참조하세요. 라우터 어플라이언스에 대한 자세한 내용은 라우터 어플라이언스 개요를 참조하세요.
VPC 네트워크에 사이트 연결
다음 토폴로지에서 라우터 어플라이언스 인스턴스는 Network Connectivity Center 스포크의 지원 리소스로 작동합니다. 라우터 어플라이언스 인스턴스는 온프레미스 네트워크의 피어 라우터와 연결됩니다. 또한 라우터 어플라이언스 인스턴스는 Cloud Router와 피어링됩니다. 온프레미스 네트워크의 경로는 VPC 네트워크와 동적으로 교환됩니다.
Router 어플라이언스 스포크를 사용하여 사이트를 VPC 네트워크에 연결(확대하려면 클릭)
2개의 VPC 네트워크에 사이트 연결
다음 토폴로지에서 라우터 어플라이언스 인스턴스에는 2개의 VPC 네트워크에 인터페이스가 있습니다. 각 인터페이스는 라우터 어플라이언스 스포크를 만들기 위해 사용되었습니다. 이 경우 온프레미스 네트워크의 경로가 각 VPC 네트워크에 전파됩니다. 두 VPC 네트워크 사이의 연결은 네트워크 가상 어플라이언스의 기능에 따라 결정됩니다.
라우터 어플라이언스 스포크를 사용하여 2개의 VPC 네트워크에 사이트 연결(확대하려면 클릭)
[[["이해하기 쉬움","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-07-14(UTC)"],[],[],null,["# Site-to-cloud topologies that use a third-party appliance\n\nNetwork Connectivity Center lets you use a third-party network virtual appliance to\nestablish connectivity between an external site and your\nVirtual Private Cloud (VPC) network resources. To establish this type of\nconnectivity, you use the Router appliance feature. Using\nRouter appliance in this way is supported in all Google Cloud regions.\n\n### Router appliance\n\nThe Router appliance feature lets you install a network virtual appliance\nwithin Google Cloud and use it as the backing resource for a spoke.\n\nTo create a router appliance instance, you install a virtual appliance image on\na Compute Engine virtual machine (VM) and complete additional setup steps.\nThis setup includes establishing Border Gateway Protocol (BGP) peering between\nthe VM and a Cloud Router. BGP enables the dynamic exchange of routes between\nthe Cloud Router and the Router appliance instance. Route exchange lets you\nestablish connectivity between your VPC network and other\nnetworks. We recommend using an image provided by a\n[supported Network Connectivity Center partner](/network-connectivity/docs/network-connectivity-center/partners).\nFor more information about Router appliance, see the\n[Router appliance overview](/network-connectivity/docs/network-connectivity-center/concepts/ra-overview).\n\nNetwork Connectivity Center lets you use a hub-and-spoke architecture for network\nconnectivity. For information about Network Connectivity Center, see the\n[Network Connectivity Center overview](/network-connectivity/docs/network-connectivity-center/concepts/overview). For more\ninformation about Router appliance, see the\n[Router appliance overview](/network-connectivity/docs/network-connectivity-center/concepts/ra-overview).\n\nConnect a site to a VPC network\n-------------------------------\n\nIn the following topology, a router appliance instance serves as the backing\nresource for a Network Connectivity Center spoke. The router appliance instance connects\nwith a peer router in an on-premises network. The router appliance instance also\npeers with a Cloud Router. Routes from the on-premises network are\ndynamically exchanged with the VPC network.\n[](/static/network-connectivity/docs/network-connectivity-center/images/site-to-cloud-one-network.svg) Use a Router appliance spoke to connect a site to a VPC network (click to enlarge)\n\nConnect a site to two VPC networks\n----------------------------------\n\nIn the following topology, a router appliance instance has interfaces in\ntwo VPC networks. Each interface has been used to create a\nRouter appliance spoke. In this case, routes from the on-premises network\nare propagated to each VPC network. Connectivity between the\ntwo VPC networks is determined by the features of the\nnetwork virtual appliance.\n[](/static/network-connectivity/docs/network-connectivity-center/images/site-to-cloud-sample-topology.svg) Use Router appliance spokes to connect a site to two VPC networks (click to enlarge)\n\nFor a detailed description of this topology and instructions about how to\nconfigure it, see\n[Establish connectivity by using a third-party appliance](/network-connectivity/docs/network-connectivity-center/how-to/connect-site-to-cloud).\n\nEnable cross-region failover for multicloud deployments\n-------------------------------------------------------\n\nThe following topology shows automatic failover through router appliances\nacross two regions by using [dynamic routing](/vpc/docs/vpc#routing_for_hybrid_networks).\nThe router instance hosts a router\nappliance image. The Router appliance mediates connectivity between\non-premises and multiple VPC networks for hybrid or multicloud scenarios.\n[](/static/network-connectivity/docs/network-connectivity-center/images/cross-region-failover-site-to-cloud-topology.svg) Cross-region failover site-to-cloud topology (click to enlarge)\n\nIn this topology, Router appliances are added to two Network Connectivity Center\nhubs, `hub 1` for route exchange with on-premises, and `hub 2` for route\nexchange with [VPC spokes](/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview).\nThe numerical values in the diagram depict the following connections:\n\n1. On-premises data centers are connected to Google Cloud through the external VPC network by using an Cloud Interconnect or Cloud VPN associated with the Cloud Router in the local region. The hybrid connections are added to the Network Connectivity Center hub, `hub 1` as hybrid spokes.\n2. The VMs that host the router appliance instances are added to the Network Connectivity Center hub, `hub 1`, which is configured to use mesh topology using `nic0` as a [Router appliance spoke](/network-connectivity/docs/network-connectivity-center/concepts/ra-overview). The VMs that host the router appliances are created in pairs across multiple regions for high-availability purposes. Each region is added as a single router appliance spoke to the Network Connectivity Center hub.\n3. In each region, the router appliance instance establishes Border Gateway Protocol (BGP) peering with the local `Cloud Router 1` or `Cloud Router 2`. Each Cloud Router receives and advertises route prefixes from the peered appliance. Because the Router appliance has to exchange data with the on-premises connections, site-to-site data transfer field must be enabled for all spokes in Network Connectivity Center `hub 1`. The dynamic routing mode for the external VPC network must be set to global.\n4. To allow communication with spoke VPC networks, the VMs that host the router appliance instances are connected to Network Connectivity Center `hub 2` through `nic1` as a Router appliance spoke in the center group.\n5. In each region, the router appliance instance establishes BGP peering with the local `Cloud Router 3` or `Cloud Router 4`. Each Cloud Router receives and advertises route prefixes from the peered appliance. To enable cross-region failover for appliances in case of region failures, the dynamic routing mode for the internal VPC network must be set to global.\n6. VPC spokes A, B, and C are all connected to the\n Network Connectivity Center `hub 2` in star topology through VPC spokes\n in an edge group to prevent direct communication between VPCs.\n\n For supported locations, see [Locations supported for data transfer](/network-connectivity/docs/network-connectivity-center/concepts/locations).\n For detailed information about connectivity topologies, see\n [Preset connectivity topologies](/network-connectivity/docs/network-connectivity-center/concepts/connectivity-topologies).\n\nWhat's next\n-----------\n\n- To create hubs and spokes, see [Work with hubs and spokes](/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes).\n- To view a list of partners whose solutions are integrated with Network Connectivity Center, see [Network Connectivity Center partners](/network-connectivity/docs/network-connectivity-center/partners).\n- To find solutions for Router appliance issues, see [Troubleshooting](/network-connectivity/docs/network-connectivity-center/support/troubleshooting#troubleshooting-ra).\n- To get details about API and `gcloud` commands, see [APIs and reference](/network-connectivity/docs/network-connectivity-center/apis)."]]
