사이트 간 데이터 전송이 Cloud VPN 리소스에서 제대로 작동하려면 99.99% SLO를 보장하도록 여러 HA VPN 게이트웨이 인터페이스와 터널을 구성해야 합니다. 자세한 내용은 Cloud VPN 개요를 참조하세요.
라우터 어플라이언스의 고가용성
사이트 간 데이터 전송이 스포크에 연결된 라우터 어플라이언스 인스턴스에서 제대로 작동하려면 다음을 수행해야 합니다.
모든 라우터 어플라이언스 인스턴스를 단일 스포크에 배치하는 경우 동일 비용 다중 경로(ECMP)를 사용하여 두 라우터 어플라이언스 인스턴스에서 동일한 프리픽스를 공지합니다. 각 스포크마다 서로 다른 프리픽스를 공지하려면 각 라우터 어플라이언스 인스턴스를 다른 스포크에 추가합니다.
단일 스포크에서는 리전 간 구성을 만들 수 없습니다.
ECMP는 2개 이상의 라우터 어플라이언스 인스턴스에서 동일한 MED와 AS 경로가 있는 동일한 프리픽스를 공지한 결과입니다. VPC 네트워크의 경로 선택에 대한 지침은 다른Google Cloud 리소스와 마찬가지로 라우터 어플라이언스 인스턴스에 적용됩니다.
라우터 어플라이언스 인스턴스를 고가용성으로 구성하는 방법에 대한 자세한 내용은 99.9% 가용성 요구사항을 참조하세요.
[[["이해하기 쉬움","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-08(UTC)"],[],[],null,["# High availability requirements for spoke resources\n\nFor Network Connectivity Center to properly enable site-to-site data transfer, you must\nconfigure spoke resources in high availability configurations. If you don't,\nsites might be unable to pass traffic to one another.\n\nEach resource type has different requirements for high availability, as\ndescribed in the following sections.\n\nHigh availability for Cloud Interconnect\n----------------------------------------\n\nFor site-to-site data transfer to work correctly with\nCloud Interconnect resources, you must configure multiple Interconnect\nconnections, each in a separate edge availability domain.\n\nFor detailed information about how to configure Cloud Interconnect\nresources for high availability, see the following documentation:\n\n- [Redundancy and SLA for\n Dedicated Interconnect](/network-connectivity/docs/interconnect/concepts/dedicated-overview#redundancy)\n- [Establishing 99.99% availability for\n Dedicated Interconnect](/network-connectivity/docs/interconnect/tutorials/dedicated-creating-9999-availability)\n- [Redundancy and SLA for\n Partner Interconnect](/network-connectivity/docs/interconnect/concepts/partner-overview#redundancy)\n- [Establishing 99.99% availability for\n Partner Interconnect](/network-connectivity/docs/interconnect/tutorials/partner-creating-9999-availability)\n- [Creating redundant Interconnect connections with sufficient\n capacity](/network-connectivity/docs/interconnect/concepts/best-practices#capacity)\n\nHigh availability for Cloud VPN\n-------------------------------\n\nFor site-to-site data transfer to work correctly with Cloud VPN\nresources, you must configure multiple HA VPN gateway interfaces\nand tunnels to achieve a 99.99% SLO. For guidance, see the\n[Cloud VPN overview](/network-connectivity/docs/vpn/concepts/overview#ha-vpn).\n\nHigh availability for Router appliance\n--------------------------------------\n\nFor site-to-site data transfer to work correctly with router appliance instances\nattached to a spoke, you must do the following:\n\nIf you place all your router appliance instances in a single spoke,\nuse equal-cost multipath (ECMP) to advertise the same set of prefixes from\ntwo router appliance instances. To advertise different prefixes for each\nspoke, add each router appliance instance to a different spoke.\n\nYou can't create a cross-region configuration in a single spoke.\n\nECMP is the result of advertising the same prefix or prefixes, with\nthe same MEDs and AS path as applicable, from two or more\nrouter appliance instances. The guidance about\n[route selection in VPC networks](/vpc/docs/routes#routeselection)\napplies to router appliance instances as it does to other\nGoogle Cloud resources.\n\nFor detailed information about how to configure router appliance instances\nfor high availability, see\n[requirements for 99.9% availability](/network-connectivity/docs/network-connectivity-center/concepts/ra-overview#ra-availability).\n\nWhat's next\n-----------\n\n- To view a sample topology, see [Sample topology for site-to-site data transfer](/network-connectivity/docs/network-connectivity-center/concepts/data-transfer-topology).\n- To learn more about how Network Connectivity Center enables full mesh connectivity, see [Route exchange with site-to-site data transfer](/network-connectivity/docs/network-connectivity-center/concepts/route-exchange).\n- To work through a tutorial, see [Connecting two sites by using Cloud VPN spokes](/network-connectivity/docs/network-connectivity-center/tutorials/connecting-two-offices-with-vpns).\n- To create hubs and spokes, see [Working 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)."]]
