Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
A topologia a seguir mostra uma rede VPC e dois sites
locais. Cada site local se conecta a Google Cloud usando um
spoke do dispositivo roteador. Os dois sites locais podem usar a rede do Google
para trocar dados entre si.
Topologia do dispositivo Router (clique para ampliar)
Cada Customer network A e Customer network B locais são conectados
com equipamentos locais do cliente (CPE, na sigla em inglês) a uma instância de dispositivo de roteador.
Os CPEs normalmente usam um mecanismo de conectividade, como um túnel de sobreposição SD-WAN
ou um túnel de VPN IPsec, para estabelecer conectividade com a
instância do dispositivo de roteador.
Cada instância do dispositivo de roteador está localizada na
regiãoGoogle Cloud mais próxima da rede do cliente associada a ela. As duas
instâncias do dispositivo roteador estão em uma única rede VPC.
No entanto, as instâncias do dispositivo roteador estão em regiões diferentes. Por isso, a rede VPC está com o
modo de roteamento dinâmico
definido como global.
As duas instâncias do dispositivo de roteador são anexadas como spokes ao
Network Connectivity Center de rede. Como Customer network A e Customer network B
precisam enviar dados entre si, os dois spokes estão com o campo de transferência de dados
site a site ativado.
Em cada região, uma instância do dispositivo roteador estabelece o peering do protocolo de
gateway de borda (BGP, na sigla em inglês) com o Cloud Router apropriado. Cada
Cloud Router recebe e divulga prefixos de rota do
local correspondente.
Os Cloud Routers trocam dinamicamente todas as rotas recebidas
entre si. Essa configuração fornece troca de rota dinâmica
completa e conectividade do plano de dados entre Customer network A e
Customer network B.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-12 UTC."],[],[],null,["# Sample topology for data transfer\n\nThe following topology shows a VPC network and two on-premises\nsites. Each on-premises site connects to Google Cloud by using a\nRouter appliance spoke. The two on-premises sites can use Google's network\nto exchange data with each other.\n[](/static/network-connectivity/docs/network-connectivity-center/images/router-appliance-topology.svg) Router appliance topology (click to enlarge)\n\n1. On-premises `Customer network A` and `Customer network B` are each connected\n through *customer premises equipment (CPE)* to a router appliance instance.\n CPEs typically use a connectivity mechanism, such as an SD-WAN overlay tunnel\n or an IPsec VPN tunnel, to establish connectivity with the\n router appliance instance.\n\n Each router appliance instance is located in the\n Google Cloud region closest to its associated customer network. Both\n router appliance instances are in a single VPC network.\n However, the router appliance instances are in different regions. For this\n reason, the VPC network has its\n [dynamic routing mode](/vpc/docs/create-modify-vpc-networks#switch-dynamic-routing)\n set to `global`.\n2. Both router appliance instances are attached as spokes to the\n Network Connectivity Center hub. Because `Customer network A` and `Customer network B`\n need to send data to each other, both spokes have the site-to-site data\n transfer field enabled.\n\n *You can use site-to-site data transfer only in supported locations.* For\n more information, see\n [Locations supported for data transfer](/network-connectivity/docs/network-connectivity-center/concepts/locations).\n3. In each region, a router appliance instance establishes Border Gateway\n Protocol (BGP) peering with the appropriate Cloud Router. Each\n Cloud Router receives and advertises route prefixes from the\n corresponding on-premises location.\n\n4. The Cloud Routers dynamically exchange all received\n routes with each other. This configuration provides end-to-end dynamic route\n exchange and data plane connectivity between `Customer network A` and\n `Customer network B`.\n\n | **Important:** For Cloud Routers in different regions to exchange routes with each other, you must enable global dynamic routing mode in your VPC network. For more information, see [Dynamic routing](/vpc/docs/vpc#routing_for_hybrid_networks).\n\nWhat's next\n-----------\n\n- To learn about high availability requirements, see [High availability requirements for spoke resources](/network-connectivity/docs/network-connectivity-center/concepts/high-availability).\n- To learn about requirements for assigning ASNs, see [ASN requirements for site-to-site data transfer](/network-connectivity/docs/network-connectivity-center/concepts/asn-requirements).\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 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 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)."]]
