Network Connectivity Center (NCC) is an orchestration framework that simplifies network
connectivity among *spoke* resources that are connected to a central
management resource called a *hub*. NCC supports the following
types of spokes:

- Virtual Private Cloud (VPC) spokes
- Producer VPC spokes
- NCC Gateway spokes
- Hybrid spokes

With the hub and spoke connectivity, you can do the following:

- Connect multiple VPC networks to one another. The VPC networks can be located across different projects in the same Google Cloud organization or different organizations.
- Connect multiple VPC networks to on-premise or other cloud provider networks. These external networks can be reachable through any type of hybrid spoke. This approach is known as *site-to-cloud connectivity.*
- Use Router appliance VMs to manage connectivity between your VPC networks.
- Use a Google Cloud VPC network as an enterprise wide area network (WAN) to connect networks that are outside of Google Cloud. You can establish connectivity between your external sites by using any type of hybrid spoke. This approach is known as *site-to-site connectivity*.

For more information about these scenarios, see
[NCC use cases](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/use-cases).

## How it works

When a hub uses VPC spokes, you can configure connectivity
between these VPC networks connected to the hub by exchanging
subnet routes between all or some of the VPC networks.

When a hub uses both VPC spokes and hybrid spokes, any to any
connectivity is supported across all of these spokes.

When a hub uses hybrid spokes located in a single VPC network,
you can also configure [site-to-site data transfer](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/data-transfer)
so that the dynamic routes whose next hops are a hybrid spoke---for example, a
Cloud Interconnect VLAN attachment---are advertised
to an on-premises network by the BGP sessions of the other hybrid spokes in
that VPC network.

See the following sections for a detailed description of hubs and spokes.

## Hubs

An NCC hub is a global resource to which you attach
spokes. A single hub can contain spokes from multiple regions. However, if
any of the spokes of a hub use the site-to-site data transfer feature, the resources
associated with those spokes must all be in the same VPC network.
Spokes that don't use site-to-site data transfer can be associated with any
VPC network in your project.

## Spokes

A spoke represents one or more Google Cloud network resources that are
connected to a hub.

When you create a spoke, you must associate it with at
least one supported connectivity resource, which is also called a
*backing resource*.

A spoke can use any of the following Google Cloud resources as its backing
resource.

### VPC spokes

VPC spokes let you connect two or more VPC
networks to a hub so that the networks exchange
[subnet routes](https://docs.cloud.google.com/vpc/docs/routes#subnet-routes). VPC spokes
attached to a single hub can reference VPC networks
in the same project or a different project (including a project
in a different organization).

VPC spokes export subnet routes to the hub and import subnet
routes and dynamic routes from the hub.

For detailed information about VPC spokes, see
[VPC spokes overview](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview).

VPC spokes provide connectivity among IPv4 and IPv6
subnet ranges from multiple VPC networks. You can configure each
VPC spoke to export subnet ranges as follows:

- Only IPv4 subnet ranges
- Both IPv4 and IPv6 subnet ranges
- Only IPv6 subnet ranges

Consider a spoke whose VPC network has a mix of
[subnet stack types](https://docs.cloud.google.com/vpc/docs/subnets#subnet-types). If you configure the spoke
to export only IPv6 subnet ranges, then IPv6 subnet ranges
from dual-stack and IPv6-only subnets are exchanged, but IPv4 subnet ranges from
IPv4-only and dual-stack and subnets aren't exchanged.

#### Producer VPC spokes

If you have an existing VPC spoke that consumes a service from a
producer network in another project through VPC Network Peering, you can make the
service reachable by the other spokes in your NCC hub
by creating a producer VPC spoke.

For detailed information about producer VPC spokes, see
[Producer VPC spokes](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/producer-vpc-spokes-overview).

### Gateway spokes

NCC Gateway is a regional spoke type attached to the NCC
hub. It enables security for Cross-Cloud Network traffic.
NCC Gateway enables third-party Security Service Edge (SSE)
inspection.

For detailed information about NCC Gateway spokes, see
[NCC Gateway overview](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/ncc-gateway-overview).

### Hybrid spokes

A hybrid spoke represents one or more network connectivity resources that
are connected to a hub. A hybrid spoke type can be any of the following
resources that a spoke is associated with:

- Router appliance VMs
- HA VPN tunnels
- Cloud Interconnect VLAN attachments for:
  - Dedicated Interconnect
  - Partner Interconnect
  - Cross-Cloud Interconnect
  - Partner Cross-Cloud Interconnect for OCI
  - Partner Cross-Cloud Interconnect for AWS

A single hybrid spoke can be associated with more than one resource of
the same type. For example, a hybrid spoke can reference two or more
HA VPN tunnels, but that same hybrid spoke cannot
also reference Router appliance VMs or Cloud Interconnect
VLAN attachments. A hybrid spoke must be in the same project as the
NCC hub.

Site-to-site data transfer using hybrid spokes requires that the spokes
be located in the same VPC network. For more information, see
[Site-to-site data transfer overview](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/data-transfer).

#### Router appliance spokes

A spoke associated with a Router appliance VM instance supports the
following use cases:

- **IPv4 site-to-cloud connectivity**: establish connectivity between an external site and your VPC network resources.
- **IPv4 site-to-site data transfer**: use Google's network as part of a wide area network (WAN) that includes your external sites to move data between all the sites.
- **IPv4 connectivity between VPC networks**: use a third-party network virtual appliance to establish connectivity between your VPC networks.

All of the site-to-site spokes that are connected to the same hub must
have all of their backing resources in the same VPC network.

#### HA VPN tunnel spokes

A spoke associated with Cloud VPN (HA VPN) tunnels
supports the following use cases:

- **IPv4 and IPv6 ([Preview](https://cloud.google.com/products#product-launch-stages)) site-to-cloud connectivity**: Establish connectivity between an external site and your VPC network resources.
- **IPv4 and IPv6 ([Preview](https://cloud.google.com/products#product-launch-stages)) site-to-site data transfer**: Use Google's network as part of a wide area network (WAN) that includes your external sites to move data between all the sites.

All of the appliances linked to from a single spoke, and all of the
Cloud VPN tunnels, VLAN attachments, must be in the same VPC
network.

#### Cloud Interconnect VLAN attachment spokes

A spoke associated with Cloud Interconnect VLAN attachments
supports the following use cases:

- **IPv4 and IPv6 ([Preview](https://cloud.google.com/products#product-launch-stages)) site-to-cloud connectivity**: all of the appliances linked to from a single spoke must be in the same VPC network.
- **IPv4 and IPv6 ([Preview](https://cloud.google.com/products#product-launch-stages)) site-to-site data transfer**: all of the Cloud VPN tunnels, VLAN attachments, or both, must be in the same VPC network.

#### Partner Cross-Cloud Interconnect for managed cloud partners

Partner Cross-Cloud Interconnect
provides an on-demand method for
establishing cross-cloud transport without having to manually set up networking
components. This transport is associated with a customer NCC hub
and creates hybrid spokes.

For detailed information about partner Cross-Cloud Interconnect
connectivity, see the
[partner Cross-Cloud Interconnect overview](https://docs.cloud.google.com/network-connectivity/docs/interconnect/concepts/partner-cci-for-csp-overview).

## Route exchange and spoke filters

You control which routes a spoke sends to the NCC hub by using [export
filters](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/spoke-filters-overview#export-filters):

- VPC spokes support exporting [IPv4 subnet
  ranges](https://docs.cloud.google.com/vpc/docs/subnets#ipv4-ranges) and [IPv6 subnet
  ranges](https://docs.cloud.google.com/vpc/docs/subnets#ipv6-ranges).

- Hybrid spokes support exporting IPv4 and IPv6 ([Preview](https://cloud.google.com/products#product-launch-stages)) dynamic routes, except for
  Router appliance spokes, which support exporting only IPv4 dynamic routes.

VPC spokes import all routes from their spoke group of the
NCC hub. You control which routes a hybrid spoke imports from
its spoke group by using [import
filters](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/spoke-filters-overview#import-filters):

- Hybrid spokes can [re-advertise imported subnet
  routes](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/spoke-filters-overview#hybrid-spokes-ncc-subnets).

- When using site-to-site data transfer, hybrid spokes can [re-advertise imported
  dynamic routes from other hybrid
  spokes](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/spoke-filters-overview#hybrid-spokes-ncc-dynamic).

## NCC considerations

Before setting up NCC, review the following sections.

### Routing

Routes installed by NCC hybrid spokes are treated as dynamic routes.

For information about how dynamic routes are handled in comparison with other
types of routes, see
[Applicability and order](https://docs.cloud.google.com/vpc/docs/routes#instancerouting)
in the VPC documentation.

| Resource | Applicable use cases |
|---|---|
| Prioritization | All hybrid spoke resources use Cloud Routers. For details about how Cloud Routers process learned routes to create dynamic routes in a VPC network or NCC hub, see [Learned routes](https://docs.cloud.google.com/network-connectivity/docs/router/concepts/learned-routes) in the Cloud Router documentation. |
| ASN | All non-Google peering routers that are associated with a single spoke must use the same ASN when advertising prefixes to the Cloud Router. This is important because, if two peers advertise the same prefix with different ASNs or AS paths, only one peer's ASN and AS path is readvertised for that prefix. Different spokes must have different ASNs. That is, if two BGP sessions belong to different spokes, they must have different ASNs. Also, if you are using the data transfer feature, you must assign ASNs as described in [ASN requirements for site-to-site data transfer](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/asn-requirements). |
| BGP sessions | BGP communities aren't supported. |

### Route advertisement changes when using site-to-site data transfer

When you add an Cloud Interconnect VLAN attachment or Cloud VPN tunnel
to a hybrid spoke, NCC updates the corresponding BGP session for the VLAN
attachment or Cloud VPN tunnel so that it re-advertises the prefixes learned by
BGP sessions of the other Cloud Interconnect VLAN attachments or Cloud VPN
tunnels connected to any of the hub's hybrid spokes that have the site-to-site data transfer
option enabled.

## Support for other products

The following sections describe how NCC works with other
networking products and features.

### VPC spokes and VPC Network Peering

NCC VPC spokes can do the following:

- Export local subnet routes to the hub
- Import subnet routes from other VPC spokes
- Import dynamic routes from hybrid spokes

VPC spokes don't support exporting the following:

- [Policy-based routes](https://docs.cloud.google.com/vpc/docs/policy-based-routes)
- [Peering subnet routes](https://docs.cloud.google.com/vpc/docs/routes#types-of-subnet-routes)
- [Static routes](https://docs.cloud.google.com/vpc/docs/static-routes)
- [Dynamic routes](https://docs.cloud.google.com/vpc/docs/routes#dynamic_routes)

For more information about NCC VPC spokes, see
[VPC spokes overview](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview)
and [Spoke filters
overview](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/spoke-filters-overview).

A VPC spoke can connect to another VPC
network that's not a spoke on the hub using VPC Network Peering. For
details about how routes are exchanged using VPC Network Peering, see
[route exchange options](https://docs.cloud.google.com/vpc/docs/vpc-peering#route-exchange-options)
in the VPC Network Peering documentation.

### Shared VPC networks

Shared VPC networks can be added as VPC spokes to a
NCC hub. The hub can be in any project.
These VPC spokes can connect
to the hub from the same project or as [VPC spokes in a
different project from a hub](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/vpc-spokes-overview#vpc-spokes-different-project).

We recommend assigning the `networkconnectivity.googleapis.com/spokeAdmin` role
to administrators of service projects. For details on this role and other
NCC roles, see
[Roles and permissions](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/access-control#networkconnectivity-roles).
If a Shared VPC host or service project containing Private Service Connect global Google API endpoints is attached to a hub as a spoke, these endpoints are propagated ([Preview](https://cloud.google.com/products#product-launch-stages)).

### Legacy networks

Spoke resources can't be part of a [legacy network](https://docs.cloud.google.com/vpc/docs/legacy).

### VPN tunnels

Classic VPN tunnels aren't supported.

### Data transfer

If you're using data transfer, review the
[Considerations](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/concepts/data-transfer#considerations) section
in the site-to-site data transfer overview.

## Service level agreement

For information about the NCC service level agreement, see
[Network Connectivity Center Service Level Agreement (SLA)](https://cloud.google.com/ncc/sla).


## Pricing

For information about pricing, see
[NCC pricing](https://cloud.google.com/network-connectivity/pricing#ncc-pricing).

## What's next

- To learn how to manage hubs and spokes, see [Work with hubs and spokes](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/how-to/working-with-hubs-spokes).
- To learn how to use Cloud VPN spokes, see [Connect 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 obtain 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).
- To view NCC quotas and limits, see [Quotas and limits](https://docs.cloud.google.com/network-connectivity/docs/network-connectivity-center/quotas).