The following topology shows a VPC network and two on-premises
sites. Each on-premises site connects to Google Cloud by using a
Router appliance spoke. The two on-premises sites can use Google's network
to exchange data with each other.
[![Router appliance topology](https://docs.cloud.google.com/static/network-connectivity/docs/network-connectivity-center/images/router-appliance-topology.svg)](https://docs.cloud.google.com/static/network-connectivity/docs/network-connectivity-center/images/router-appliance-topology.svg) Router appliance topology (click to enlarge)

1. On-premises `Customer network A` and `Customer network B` are each connected
   through *customer premises equipment (CPE)* to a router appliance instance.
   CPEs typically use a connectivity mechanism, such as an SD-WAN overlay tunnel,
   an IPsec VPN tunnel (including Cloud VPN gateways), or
   Cloud Interconnect, to establish connectivity with the
   router appliance instance.

   Each router appliance instance is located in the
   Google Cloud region closest to its associated customer network. Both
   router appliance instances are in a single VPC network.
   However, the router appliance instances are in different regions. For this
   reason, the VPC network has its
   [dynamic routing mode](https://docs.cloud.google.com/vpc/docs/create-modify-vpc-networks#switch-dynamic-routing)
   set to `global`.
2. Both router appliance instances are attached as spokes to the
   Network Connectivity Center (NCC) hub. Because `Customer network A` and `Customer network B`
   need to send data to each other, both spokes have the site-to-site data
   transfer field enabled.

   *You can use site-to-site data transfer only in supported locations.* For
   more information, see
   [Locations supported for data transfer](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/locations).
3. In each region, a router appliance instance establishes Border Gateway
   Protocol (BGP) peering with the appropriate Cloud Router. Each
   Cloud Router receives and advertises route prefixes from the
   corresponding on-premises location.

4. The Cloud Routers dynamically exchange all received
   routes with each other. This configuration provides end-to-end dynamic route
   exchange and data plane connectivity between `Customer network A` and
   `Customer network B`.

   > [!IMPORTANT]
   > **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](https://docs.cloud.google.com/vpc/docs/vpc#routing_for_hybrid_networks).

## What's next

- To learn about high availability requirements, see [High availability requirements for spoke resources](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/high-availability).
- To learn about requirements for assigning ASNs, see [ASN requirements for site-to-site data transfer](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/asn-requirements).
- To create hubs and spokes, see [Working with hubs and spokes](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes).
- To work through a tutorial, see [Connecting two sites by using Cloud VPN spokes](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/tutorials/connecting-two-offices-with-vpns).
- To view a list of partners whose solutions are integrated with NCC, see [NCC partners](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/partners).