Establishing BGP Sessions

Establishing BGP sessions

Cloud Router uses Border Gateway Protocol (BGP) to exchange routes between your Virtual Private Cloud network and your on-premises network. On Cloud Router, you configure an interface and a BGP peer for your on-premises router. The interface and BGP peer configuration together form a BGP session.

Within GCP, a Cloud Router interface connects to exactly one of the following GCP resources:

  • A Classic VPN tunnel using dynamic routing
  • A HA VPN tunnel (using dynamic routing as required)
  • An interconnect attachment (VLAN) for a Dedicated Interconnect
  • An interconnect attachment (VLAN) for a Partner Interconnect

Cloud Routers support multiple interfaces each. You don't need to create a separate Cloud Router for each VPN tunnel or interconnect attachment (VLAN). However, each Cloud Router uses the same ASN for all of its BGP sessions. Because Partner Interconnect requires a public ASN and all other types of interface require private ASNs, a Cloud Router that manages BGP sessions for an interconnect attachment (VLAN) on a Partner Interconnect cannot manage BGP sessions for any other type of interface.

The following sections provide links describing how to configure BGP sessions for each different type of interface:

Cloud VPN

Cloud Interconnect

What's next

Was this page helpful? Let us know how we did:

Send feedback about...

Cloud Router