Topología de muestra para la transferencia de datos
Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En la siguiente topología, se muestra una red de VPC y dos sitios locales. Cada sitio local se conecta a Google Cloud mediante un radio de dispositivo de router. Los dos sitios locales pueden usar la red de Google para intercambiar datos entre sí.
Topología del dispositivo de router (haz clic para ampliar)
Cada Customer network A y Customer network B local están conectadas a través del equipo local de clientes (CPE) a una instancia de dispositivo de router.
Los CPE suelen usar un mecanismo de conectividad, como un túnel de superposición SD-WAN o un túnel VPN con IPsec, para establecer la conectividad con la instancia del dispositivo de router.
Cada instancia de dispositivo de router se encuentra en la región deGoogle Cloud más cercana a la red de clientes asociada. Ambas instancias del dispositivo de router se ubican en una sola red de VPC.
Sin embargo, las instancias de dispositivo de router están en diferentes regiones. Por este motivo, la red de VPC tiene el modo de enrutamiento dinámico configurado como global.
Ambas instancias del dispositivo de router están conectadas como radios al concentrador de Network Connectivity Center. Debido a que Customer network A y Customer network B necesitan enviarse datos entre sí, ambos radios tienen habilitado el campo de transferencia de datos de sitio a sitio.
En cada región, una instancia de dispositivo de router establece el intercambio de tráfico del protocolo de puerta de enlace fronteriza (BGP) con el Cloud Router adecuado. Cada Cloud Router recibe y anuncia prefijos de ruta desde la ubicación local correspondiente.
Los Cloud Routers intercambian todas las rutas recibidas de forma dinámica entre sí. Esta configuración proporciona un intercambio de rutas de extremo a extremo dinámico y la conectividad del plano de datos entre la Customer network A y la Customer network B.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 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)."]]
