Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
O Network Connectivity Center permite usar a rede do Google como parte de uma rede de longa distância (WAN, na sigla em inglês)
que inclui seus sites externos. Esse recurso é conhecido como
transferência de dados site a site.
Por exemplo, imagine que você tem um escritório em Nova York, um em Sydney e
outro em Tóquio. Depois de concluir a configuração necessária, é possível usar
a rede do Google para mover dados entre os três locais.
Para ativar essa funcionalidade, use um recurso compatível para conectar cada
site ao Google Cloud. Em seguida, crie um spoke do Network Connectivity Center
para representar cada recurso de conectividade. Cada spoke é associado a um
hub central, que fornece conectividade de malha completa entre todos os spokes.
Os recursos de conectividade compatíveis incluem o Cloud VPN
(túneis de VPN de alta disponibilidade), o Cloud Interconnect e o dispositivo roteador. O dispositivo roteador é um recurso do Network Connectivity Center que
permite instalar um dispositivo virtual de rede no Google Cloud
que pode ser usado para trocar rotas com o Cloud Router.
Transferência de dados pela rede do Google (clique para ampliar)
Quando a transferência de dados é ativada para um ou mais spokes, todos os recursos de
conectividade associados a esses spokes precisam fazer parte de uma única
rede VPC.
Se você quiser trocar rotas entre spokes de várias regiões, a
rede VPC em que seus recursos spoke residem precisa ter o
modo de roteamento dinâmico
definido como global.
Em cada spoke, verifique se o
roteador local está divulgando rotas idênticas para o Cloud Router
associado ao spoke.
Em alguns casos, sua rede pode estar com divulgações de rota duplicadas
de vários spokes das mesmas sub-redes com a mesma prioridade.
O Network Connectivity Center lida com essas situações da seguinte maneira:
Quando diferentes tipos de recursos estão sendo usados, os anexos da VLAN
recebem mais tráfego do que as conexões do Cloud VPN,
que recebem mais tráfego do que as VMs que atuam como instâncias do dispositivo roteador.
Quando o Network Connectivity Center divide o tráfego em vários recursos do
mesmo tipo, como dois túneis de VPN, ele usa o roteamento de vários caminhos de custo igual
(ECMP, na sigla em inglês)
para distribuir tráfego.
Problema conhecido. Podem ocorrer problemas quando há divulgações
de rota duplicadas de recursos nos spokes participantes, como
túneis de VPN de alta disponibilidade, e também de recursos semelhantes fora dos
spokes. Quando existirem divulgações de rota duplicadas, o tráfego nos
spokes participantes poderá usar o ECMP para distribuir o tráfego por todos os
próximos saltos disponíveis. Esse comportamento ocorre mesmo se os próximos saltos não
estiverem participando de hubs ou spokes.
As rotas aprendidas personalizadas do Cloud Router não são
honradas. Se você usar rotas aprendidas personalizadas em sessões do BGP associadas a esse
recurso, as rotas não serão propagadas para sites externos.
Consulte também
Considerações
na visão geral principal do Network Connectivity Center.
Requisitos
Ao usar a transferência de dados site a site, faça o seguinte:
Verifique se todos os recursos de conectividade associados aos
spokes usam uma configuração de alta disponibilidade. Saiba mais em
Alta disponibilidade para recursos spoke.
Verifique se os prefixos de roteamento são divulgados exclusivamente dentro ou fora de
um hub. Se você não fizer isso, a seleção do melhor caminho poderá escolher uma rota que
não está associada a um spoke.
[[["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-28 UTC."],[],[],null,["# Site-to-site data transfer overview\n\nNetwork Connectivity Center lets you use Google's network as part of a wide area network (WAN)\nthat includes your external sites. This feature is known as\n*site-to-site data transfer*.\n\nFor example, suppose you have an office in New York, an office in Sydney, and an\noffice in Tokyo. After completing the required configuration, you can use\nGoogle's network to move data between all three locations.\n\nTo enable this functionality, you use a supported resource to connect each\nsite to Google Cloud. Then you create a Network Connectivity Center\n*spoke* to represent each connectivity resource. Each spoke is attached to a\ncentral *hub*, which provides full mesh connectivity between all of the spokes.\n\nSupported connectivity resources include Cloud VPN\n(HA VPN tunnels), Cloud Interconnect, and\nRouter appliance. Router appliance is a Network Connectivity Center feature that\nlets you install a third-party network virtual appliance in Google Cloud\nand use it to exchange routes with Cloud Router.\n[](/static/network-connectivity/docs/network-connectivity-center/images/data-transfer.svg) Data transfer over Google's network (click to enlarge).\n\nFor a comparison of hybrid connectivity\nproducts and features, see\n[Choosing a Network Connectivity product](/network-connectivity/docs/how-to/choose-product).\n\nFor more information about Router appliance, see the\n[Router appliance overview](/network-connectivity/docs/network-connectivity-center/concepts/ra-overview). For\ninformation about Network Connectivity Center, see the\n[Network Connectivity Center overview](/network-connectivity/docs/network-connectivity-center/concepts/overview).\n\nConsiderations\n--------------\n\nBefore using Network Connectivity Center for data transfer, review and consider the\nfollowing points:\n\n- Data transfer traffic between sites is best-effort, and there are no bandwidth\n or latency guarantees.\n\n- Data transfer is available only in\n [supported locations](/network-connectivity/docs/network-connectivity-center/concepts/locations). For an example of\n how to configure route advertisements when one of your redundant\n Interconnect connections is to an unsupported location, see\n [Configure on-premises router for mixed advertisements](/network-connectivity/docs/network-connectivity-center/concepts/optimal-route-advertisement).\n\n- When data transfer is enabled for one or more spokes, all connectivity\n resources associated with these spokes must be part of a single\n VPC network.\n\n- If you want to exchange routes between spokes in multiple regions, the\n VPC network where your spoke resources are located must have\n its [dynamic routing mode](/vpc/docs/create-modify-vpc-networks#switch-dynamic-routing)\n set to `global`.\n\n- For each spoke, ensure that the\n on-premises router advertises identical routes to the Cloud Router\n associated with the spoke.\n\n- In some cases, your network might experience duplicate route advertisements\n from multiple spokes for the same subnets with the same priority.\n Network Connectivity Center handles these situations as follows:\n\n - When different types of resources are being used, VLAN attachments receive more traffic than Cloud VPN connections, which receive more traffic than VMs acting as router appliance instances.\n - When Network Connectivity Center splits traffic across multiple resources of the same type (for example, two VPN tunnels), it uses equal-cost multi-path ([ECMP](https://en.wikipedia.org/wiki/Equal-cost_multi-path_routing)) routing to distribute traffic.\n- **Known issue.** Problems can occur if there are duplicate route\n advertisements from resources in participating spokes, such as\n HA VPN tunnels, and from similar resources outside\n spokes. When duplicate router advertisements exist, then the traffic in\n participating spokes might use ECMP to distribute traffic across all\n available next hops. This behavior occurs even if the next hops aren't\n participating hubs or spokes themselves.\n\n- [Cloud Router custom learned routes](/network-connectivity/docs/router/concepts/learned-routes) aren't\n honored. If you use custom learned routes on BGP sessions associated with this\n feature, the routes aren't propagated to external sites.\n\n- See also\n [Considerations](/network-connectivity/docs/network-connectivity-center/concepts/overview#considerations)\n in the main Network Connectivity Center overview.\n\nRequirements\n------------\n\nWhen using site-to-site data transfer, you must do all of the following:\n\n- Make sure that all connectivity resources associated with your\n spokes use a high availability configuration. For more information, see\n [High availability for spoke resources](/network-connectivity/docs/network-connectivity-center/concepts/high-availability).\n\n- Follow the guidelines described in\n [ASN requirements for site-to-site data transfer](/network-connectivity/docs/network-connectivity-center/concepts/asn-requirements).\n\n- Make sure that routing prefixes are exclusively advertised within a hub or outside of\n a hub. If you fail to do this, best-path selection might choose a route that\n is not associated with a spoke.\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 learn about high availability requirements, see [High availability requirements for spoke resources](/network-connectivity/docs/network-connectivity-center/concepts/high-availability).\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 [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)."]]
