Cloud Router is a fully distributed and managed Google Cloud service. It scales with your network traffic; it's not a physical device that might cause a bottleneck.
When you extend your on-premises network to Google Cloud, use Cloud Router to dynamically exchange routes between your Google Cloud networks and your on-premises network. Cloud Router peers with your on-premises VPN gateway or router. The routers exchange topology information through Border Gateway Protocol (BGP). Topology changes automatically propagate between your Virtual Private Cloud (VPC) network and on-premises network. You don't need to configure static routes.
Cloud Router works with both legacy networks and VPC networks.
Static versus dynamic routing
With static routes, you must create or maintain a routing table. A topology change on either network requires you to manually update static routes. Also, static routes can't automatically reroute traffic if a link fails.
Static routing is suitable for small networks with stable topologies. You also have strict control over the routing tables. Routers don't send advertisements between networks.
With Cloud Router, you can use BGP to exchange routing information between networks. Instead of manually configuring static routes, networks automatically and rapidly discover topology changes through BGP. Changes are seamlessly implemented without disrupting traffic. This method of exchanging routes through BGP is dynamic routing.
Dynamic routing is suitable for any size network. It frees you from maintaining static routes. Also, if a link fails, dynamic routing can automatically reroute traffic if possible. To enable dynamic routing, create a Cloud Router. Then, configure a BGP session between the Cloud Router and your on-premises gateway or router.
Static routing for Cloud VPN tunnels
Without Cloud Router, you can configure your Cloud VPN by using only static routes. The disadvantages of using static routes are as follows:
- A network configuration change on either side of a Cloud VPN tunnel requires manually creating and deleting static routes corresponding to these changes. In addition, static route changes are slow to converge.
- When you create a Cloud VPN tunnel to work with static routes, you must specify the list of IP prefixes on either side of the tunnel before the tunnel is created. This means that every time the routes must change, you must delete and recreate the Cloud VPN tunnel and configure new routes, which disrupts existing traffic.
- There is no standard way to configure static routes. Different vendors use different commands.
In the following example, your combined network consists of your Google Cloud
network and 29 subnets (one per rack) on the on-premises network on the other side
of the Cloud VPN tunnel. For this example, assume that your business is
growing such that you need to add a new subnet of machines every week. This
week, you're adding subnet
10.0.30.0/24, as shown in the following diagram.
In this scenario, static route-based Cloud VPN would require the following changes:
- You must add static routes to Google Cloud to reach the new on-premises subnet.
- You must tear down and recreate the Cloud VPN tunnel to include the new on-premises subnet.
You can avoid configuration changes to static routes and Cloud VPN tunnels by deploying a Cloud Router. Cloud Router peers with your Cloud VPN gateway by using BGP to exchange topology information. In effect, network topology changes in your Google Cloud network propagate automatically to your own network and vice versa by using BGP so that you don't have to configure static routes for your Cloud VPN tunnels.
Dynamic routing for Cloud VPN tunnels in VPC networks
Use VPC networks to regionally segment the network IP space into prefixes (subnets) and control which prefix a virtual machine (VM) instance's internal IP address is allocated from. To avoid statically managing these subnets, including the burden of adding and removing related static routes for your Cloud VPN, use Cloud Router to enable dynamic routing for your Cloud VPN tunnel.
A Cloud Router belongs to a specific VPC network and region. Cloud Router advertises subnets from its VPC network to the on-premises gateway by using BGP. It advertises the subnets in its local region or all subnets in the network based on the VPC network's dynamic routing mode. Cloud Router also learns the on-premises routes through BGP and enables the network infrastructure to select the best route to reach the associated prefixes.
The following example shows Cloud Router with custom mode VPC networks. If you use auto mode VPC networks, Cloud Router automatically announces the region's /20 prefix. For more information about auto and custom modes, see the VPC network overview.
The following diagram shows two different regional subnets in a VPC network and 30 subnets in the on-premises network. The two networks are connected through a Cloud VPN tunnel. In this scenario, new subnets are being added in both networks:
- A new
192.168.1.0/24subnet in Region
us-east1of the Google Cloud network.
- A new on-premises
10.0.30.0/24subnet to handle growing traffic in your data center.
To automatically propagate network configuration changes, the Cloud VPN tunnel uses Cloud Router to establish a BGP session between the on- premises VPN gateway, which must support BGP. The new subnets are seamlessly advertised between networks. Instances in the new subnets can start sending and receiving traffic immediately.
To set up BGP, you must assign an additional IP address to each end of the
Cloud VPN tunnel. These two IP addresses must be link-local IP
that belong to the IP address range
169.254.0.0/16. These addresses are not
part of the IP address space of either network. These two addresses are used
exclusively for establishing a BGP session. The addresses are not routable;
therefore, they do not work well with common network testing tools. For example,
Traceroute does not work, and a ping test only works if the request is coming
from the link-local address destined for the peer's link-local address.
Dynamic routing for Cloud VPN tunnels in legacy networks
In legacy networks, network configuration changes are automatically propagated without the need to reconfigure static routes and restart the Cloud VPN tunnel, similar to the previous example.
The BGP session informs each router of local changes. To set up BGP, an
additional IP address has to be assigned to each end of the Cloud VPN
tunnel. These two IP addresses must be link-local IP
that belong to the IP address range
169.254.0.0/16. These addresses are not
part of the IP address space on either side of the tunnel and are used
exclusively for configuring BGP peers to establish a BGP session.
You must configure two link-local IP addresses (both from the same subnet) and a netmask on both sides of the tunnel. After you configure these changes on both sides of the tunnel, a BGP session is established.
Again, if a network has Cloud VPN tunnels in multiple regions, you must create a Cloud Router in each region where you want to use dynamic routing. You can use a single Cloud Router for multiple Cloud VPN gateways and multiple tunnels in the network's region in which the router belongs.
Dynamic routing mode
The dynamic routing mode of a VPC network determines which subnets are visible to Cloud Routers. You can set the dynamic routing mode to be global or regional:
- With global dynamic routing, a Cloud Router advertises all subnets in the VPC network to the on-premises router. Cloud Router propagates learned routes from the on-premises router to all regions.
- With regional dynamic routing, a Cloud Router advertises and propagates routes in its local region.
The dynamic routing mode is configured in the VPC network. When you create or edit a VPC network, you can set the dynamic routing mode to global or regional. All instances of Cloud Router in the VPC network use the network's dynamic routing mode. By default, the mode is regional.
If you change the dynamic routing mode for a VPC network, consider the implications such as interrupting existing connections or enabling unintended routes. For example, if you change to regional dynamic routing, VMs that could connect to Cloud VPN tunnels and Cloud Interconnect connections in another region might lose connection. If you change to global dynamic routing, Cloud Router might advertise VMs from regions that you didn't intend to. To view or configure the dynamic routing mode, see Setting regional or global dynamic routing.
Regional dynamic routing example
With regional dynamic routing, you might have a Cloud VPN tunnel and VMs in a single Google Cloud region. The tunnel extends your on-premises network to a VPC network. VMs in other regions might need to connect to the on-premises network, but they can't reach the tunnel. To get around this constraint, you could create static routes. However, maintaining static routes can be prone to errors and might disrupt traffic.
In the following example, Cloud Router has visibility to resources
only in the
us-west1 region. VMs in other regions, such as
can't reach the Cloud VPN tunnel.
Global dynamic routing examples
With global dynamic routing, Cloud Router has visibility to resources in all regions. For example, if you have VMs in one region, they can reach a Cloud VPN tunnel in another region automatically without maintaining static routes.
The following example shows a VPC network with global dynamic
routing. The Cloud Router in
us-west1 advertises subnets in two
us-central1. VMs in both regions dynamically
learn about on-premises hosts.
For redundant topologies, dynamic routing (BGP) provides enough information to the VPC and on-premises networks so that when a path fails, traffic is rerouted. If a connection in one region has an issue, traffic can fail over to another region.
The following example shows two Cloud VPN tunnels in two different
regions. The VMs (
tunnel-us-west1 in the
region to reach both subnets in the on-premises network. Similarly, the VMs
The routes are configured so that VMs prefer their local tunnels (the tunnels in their region). Cloud Router sets different weights for local and remote routes with the same destination. If one tunnel fails, Cloud Router can reroute traffic appropriately.
In the following example,
tunnel-us-west1 fails. Traffic to and from the VMs
10.128.0.0/20) is rerouted through
tunnel-us-central1 instead of being
Through BGP, Cloud Router advertises the IP addresses that clients in your on-premises network can reach. Your on-premises network sends packets to your VPC network that have a destination IP address matching an advertised IP range. After reaching Google Cloud, your VPC network's firewall rules and routes determine how Google Cloud handles the packets.
You can use Cloud Router's default advertisements or explicitly specify which CIDR ranges to advertise. If you don't specify advertisements, Cloud Router uses the default.
By default, Cloud Router advertises subnets in its region for regional dynamic routing or all subnets in a VPC network for global dynamic routing. New subnets are automatically advertised by Cloud Router. Also, if a subnet has a secondary IP range for configuring alias IP addresses, Cloud Router advertises both the primary and secondary IP addresses.
Each BGP session for a Cloud Router also has a default advertisement. By default, Cloud Router propagates its route advertisements to all of its BGP sessions. If you configure custom route advertisements on a Cloud Router, its BGP sessions inherit those custom advertisements.
You must specify custom route advertisements in the following cases:
- To advertise IP addresses outside of a subnet's primary IP range or one of its secondary IP ranges. For example, advertising external IP addresses.
- To advertise routes from a different VPC network connected to your VPC network by using VPC Network Peering. In this case, subnet routes and imported custom routes in a peer network are not automatically advertised by a Cloud Router in your VPC network. To advertise them, you must create custom route advertisements on the Cloud Router in your VPC network, and also ensure that the VPC Network Peering connections are configured to exchange the custom routes.
When you use custom advertisements, you can selectively advertise subnets or parts of a subnet. That way, you can withhold certain subnets from being advertised. If you don't need these capabilities, use the default advertisements.
When you configure custom route advertisements, you explicitly specify the routes that a Cloud Router advertises. In most cases, custom advertisements are useful for supplementing the default subnet advertisement with custom IP addresses. Custom IP addresses are addresses outside a subnet's IP range, such as reserved external IP addresses. Without custom route advertisements, you would be required to create and maintain static routes for custom IP addresses.
When you configure custom route advertisements, you can choose to advertise all subnets, which emulates the default behavior. You can choose not to advertise all subnets, and instead advertise specific subnets or certain CIDR blocks within a subnet. For example, you might want to prevent Cloud Router from advertising particular subnets. To do that, you advertise just the ones you want to expose. However, when you selectively advertise subnets, new subnets must be manually added to the custom route advertisement. Cloud Router won't automatically advertise new subnets.
You can specify custom route advertisements on a Cloud Router or on a BGP session. Custom route advertisements on the Cloud Router apply to all its BGP sessions. However, if you specify a custom route advertisement on a BGP session, the Cloud Router's route advertisement is ignored and overridden by the session's advertisement.
For each Cloud Router, you can specify a maximum of 200 CIDR ranges. Also, each BGP session has the same limit of 200.
The following examples show the Cloud Router's default behavior and scenarios where custom route advertisements might be useful. The examples assume an existing connection between the VPC and on-premises networks, such as an IPsec VPN tunnel or Dedicated Interconnect.
Default route advertisement
For regional dynamic routing, Cloud Router advertises subnets in its
region. In the following example, Cloud Router advertises subnets in
us-central1 region. It also advertises the secondary IP range of
alias-subnet. If you create new subnets in
Cloud Router automatically advertises them. Cloud Router
doesn't advertise IP addresses that aren't included in a subnet's IP range, such
as external IP addresses.
Advertise an external IP address
You might use an external static IP address for a Google Cloud application that serves clients in your on-premises network. When you perform maintenance on the application, you can remap the static IP address to another VM to minimize downtime. With Cloud Router's default advertisements, you're required to configure and maintain a static route. Instead, you can use custom advertisements to advertise the external IP address through BGP.
In the following example, the Cloud Router advertises the proxy
server's external IP address
220.127.116.11. The external IP address maps to the server's
internal IP address
10.20.0.2. Cloud Router doesn't advertise the
internal IP address of the proxy server or any VMs in the
subnet. On-premises clients are only aware of the proxy server's external IP
For more information, see Advertising custom IP ranges.
Restrict subnet advertisement
You can prevent instances from being advertised so that they're hidden. In the
following example, Cloud Router advertises
Clients in the on-premises network can reach VMs in those subnets but not VMs in
For more information, see Advertising specific VPC subnets.
Route advertisement per BGP session
Assume that you have production and test resources in your VPC
and on-premises networks, and you organized those resources in different
subnets. Accordingly, you set up two BGP sessions that advertise different IP
address ranges. By using two different BGP sessions, traffic bound for one
subnet doesn't inadvertently go to another subnet. The following example shows
two BGP sessions:
prod-bgp that advertises only the
bgp that advertises only the
Best path for egress traffic from Google Cloud to your on-premises network
If Cloud Router receives multiple routes for the same destination, Google Cloud uses route metrics and, in some cases, AS path length to determine the best path. The following list describes the algorithm used for egress traffic with one or more Cloud Routers managing dynamic routes for one VPC network.
- If you have multiple BGP sessions on a single Cloud Router, egress
is determined by the first condition that is met:
- All egress traffic is sent to the route with the shortest AS path length.
- If routes have the same AS path lengths, all egress traffic is sent to the one with the lowest Multi-Exit Discriminator (MED) value (the lowest route metric).
- If routes have the same AS path lengths and MED values (the same route metrics), egress traffic is balanced across all routes by using equal-cost multi-path (ECMP).
- If you use multiple Cloud Routers in the same region, Google Cloud only uses
route metrics to determine the best path. The AS path length is not used.
Egress is determined by the first condition that is met:
- All egress traffic is sent to the route with the lowest Multi-Exit Discriminator (MED) value (the lowest route metric).
- If routes have the same MED values (the same route metrics), egress traffic is balanced across all routes by using ECMP.
- Static routes take priority over Cloud Router dynamic routes in cases of conflict. A static route with the same prefix and route metric as a dynamic route always takes priority, so any conflicting dynamic routes are ignored.
Overlapping IP ranges between a VPC subnet and an on-premises route advertisement
In cases where you have a VPC subnet and an on-premises route advertisement with overlapping IP ranges, Google Cloud directs egress traffic depending on their IP ranges.
If the subnet IP range is broader or the same as the on-premises route
advertisement, Google Cloud ignores the on-premises advertisement. All Google Cloud egress traffic
destined for the subnet's IP range is directed to the VPC subnet. For example,
if you have a subnet with an IP range of
10.2.0.0/16 and an on-premises router
10.2.1.0/24, Google Cloud ignores the on-premises advertisement and directs
10.2.0.0/16 traffic to the VPC subnet.
If the subnet IP range is narrower than the on-premises route advertisement,
Google Cloud egress traffic is directed to the VPC subnet if the destination IP is
within the subnet's IP range. All other egress traffic that matches the
on-premises advertisement is directed to the on-premises network. For example,
if you have a subnet with an IP range of
10.2.0.0/16 and an on-premises router
10.0.0.0/8, Google Cloud directs traffic destined for
10.0.0.0/8 to the
on-premises network unless the destination matches
10.2.0.0/16, which Google Cloud
directs to the subnet.
When Cloud Router advertises or propagates routes, it uses route metrics to specify route priorities. When you have multiple paths between your VPC network and on-premises network, route metrics determine a preferred path. This value is equivalent to the MED value. A lower route metric (MED) indicates higher priority.
A route metric is composed of a base advertised route priority and a regional cost. The base priority is a user-specified value, whereas the regional cost is a Google-generated value that you can't modify. The regional cost represents the cost of communicating between two regions in a VPC network. Cloud Router adds these two values together to generate a route metric.
For regional dynamic routing, because Cloud Router handles only routes in its region, it doesn't add any regional costs to route metrics. Cloud Router uses only the base advertised route priority.
For global dynamic routing, all Cloud Routers advertise and propagate the same routes. However, each Cloud Router might use different route metrics due to regional costs.
- Base advertised route priority
When calculating route metrics, Cloud Router starts with the base advertised route priority value and then adds any regional costs. This base value is the minimum route metric for advertised routes. When you configure a BGP session on a Cloud Router, you can specify a base advertised route priority, which applies to all routes for that session. By default, the base advertised priority value is
The base advertised route priority enables you to set priorities for routes. For example, you might have a Cloud VPN tunnel and a Dedicated Interconnect connection connecting your VPC and on- premises networks. You can set the base advertised route priority so that traffic prefers Dedicated Interconnect. If the Cloud Interconnect connection is unavailable, traffic traverses the tunnel. For more information, see the example topologies.
- Regional cost
When a Cloud Router advertises routes from regions other than its region (routes from remote Google Cloud regions) or propagates routes to remote regions, it adds a regional cost.
The regional cost can range from 201 to 9999, inclusive. The value depends on the distance, latency, and other factors between two regions. Google generates the regional cost value, and you can't modify it. For more information about regional costs, see the example topologies.
Regional costs help prioritize paths based on region proximity. For example, imagine that you have two connections between your VPC and on- premises network, such as two Cloud VPN tunnels with their own Cloud Routers. One connection is in
us-central1and another in
europe-west1. By adding a regional cost to the route metrics, traffic between networks in
us-central1tunnel. Similarly, traffic between networks in
europe-west1tunnel. Without regional costs, traffic is directed equally through both connections, leading to inconsistent network performance.
For learned routes, Cloud Router adds regional costs when it propagates the learned routes to remote Google Cloud regions. This helps maintain symmetry between ingress and egress traffic between VPC and on-premises networks. Cloud Router adds regional costs to the MED value that's advertised by your on-premises router.
Suggested base priority values
To adjust priorities between routes in a single region, use
values less than
201. This guarantees that regional costs won't impact global
route priorities. A route from another region (a remote region) can't have a
priority lower than
201. If you use higher values, regional costs might impact
your route priorities. For example, suppose you have a primary and a backup
connection. If you set the backup connection's base priority too high, you
might unintentionally prefer routes from other regions instead of the backup
To globally deprioritize a route in a VPC network, use values higher than
10,200. This ensures that all other routes lower than
201 have priority
regardless of regional costs.
In cases where all routes in a region are equally preferred, you can use the
default value of
The following examples explain how regional costs influence route metrics when you use global dynamic routing.
Suppose you have a VPC network with two Cloud VPN
tunnels with their own Cloud Routers. One tunnel is in
and the other is in
us-west1. By default, ingress traffic to those regions use
the corresponding tunnels in their respective regions. However, what happens if
you want to reach VMs that aren't in those regions, such as VMs in
europe-west1? The following diagram shows how the regional costs affect route metrics.
Both Cloud Routers advertise routes to
europe-west1 but with different
route metrics. The Cloud Router in
us-central1 advertises routes to
europe-west1 with a lower route metric than to
us-west1 due to distance, latency, and
other factors. The example assumes that the regional cost to
us-west1. Ingress traffic uses the
us-central1 tunnel, which has a lower route metric. It has a route metric of
400 for the
Similarly, Cloud Router adds a regional cost to the MED value of
learned routes (specified by your on-premises router). By default, egress
traffic from the
europe-west1 region also uses the
us-central1 tunnel because it
has a lower route metric. This way ingress and egress traffic maintain symmetry.
Route priorities within a region
For redundancy in
us-west1, suppose you create a backup tunnel. You specify a
higher base priority for the backup tunnel so that ingress traffic to
prefers the primary tunnel, as shown in the following example.
If the primary tunnel fails, ingress traffic to
us-west1 prefers the backup
tunnel with a route metric of
51 over the
us-central1 tunnel, which has a route
Similarly, for egress traffic from the VPC network to your on-
premises network, use MED values lower than
201 to prioritize one path over
another. Otherwise, egress traffic from the VPC network to your
on-premises network might not be symmetric with ingress traffic.
In cases where all tunnels or Cloud Interconnect connections in a
region are equally preferred, you can use the default base route priority of
Globally preferred route
Suppose you have Dedicated Interconnect and a Cloud VPN
tunnel in different regions. You want to prioritize
Dedicated Interconnect because it's more cost effective for your
workloads than the Cloud VPN tunnel. Specify a base priority of
10,051 for the Cloud VPN tunnel routes to deprioritize it. As a
result, all ingress traffic uses Dedicated Interconnect,
independent of regional costs. Route metrics for
Dedicated Interconnect won't exceed
10,051. Traffic uses the
Cloud VPN tunnel only if the connection fails.
You'll also need to make the same adjustments to your on-premises router so that egress traffic from the VPC network to the on-premises network always prefers to use Dedicated Interconnect.
When no route is specified for a particular IP destination, traffic is sent to a
default route, which acts like a last resort when no other options exist. For
example, Google Cloud VPC networks automatically include a
default route (
0.0.0.0/0) that sends traffic to the internet gateway.
In some cases, you might want traffic to be directed to your on-premises network
by default. To do that, you can advertise a default route from your on-premises
router to Cloud Router. With Cloud Router, you don't need to
create and manage static routes. If you advertise a default route from your on-
premises network, check that it's prioritized over other automatically created
default routes (has a lower MED value). Go to the
Routes page and view the Priority for routes
0.0.0.0/0 in Destination IP range, and view
Default internet gateway in
Cloud Router honors graceful restart messages sent by your on-premises router. If you've configured your on-premises router with graceful restart, it can send a notification to Cloud Router whenever your router needs to install software updates or perform periodic maintenance. Cloud Router retains custom dynamic routes learned from your on-premises router for the time period defined by the graceful restart timer setting on your on-premises router.
For more information about graceful restart timers, see BGP timer settings.
Cloud VPN tunnel with graceful restart
In the following example, if Cloud Router requires a maintenance update, it can be updated without causing any disruption to traffic as long as it comes back online within the graceful restart period.
BGP timer settings
Cloud Router and your on-premises router maintain communication by using the following set of timer settings.
- Keepalive timer
- This is the interval between periodic BGP heartbeats exchanged between a Cloud Router and its corresponding on-premises peer router. In conjunction with the hold timer, the keepalive timer indicates each router's availability to the other. We recommend setting the keepalive timer to 20 seconds on your on-premises router.
- Hold timer
- This timer keeps track of the minimum amount of time since the last successful keepalive heartbeat was detected. It indicates how long either the Cloud Router or your on-premises router should wait before removing the routes it learned from the other router. We recommend setting the hold timer to 60 seconds on your on-premises router.
- Graceful restart timer
This is the amount of time that your on-premises router waits, without periodic keepalive heartbeats, after it receives a graceful restart notification message from the corresponding Cloud Router, before expecting new keepalive heartbeats. If new keepalive heartbeats are not received, your on-premises router removes the routes it learned from the Cloud Router.
We recommend setting the graceful restart timer to 1 second on your on-premises router if you want your router to behave in the same way that Cloud Router does.
Cloud Router withdraws the custom dynamic routes it learns from on- premises devices when it determines that a next hop Cloud VPN tunnel is down or that a Cloud Interconnect connection is down. If you set your on-premises router's graceful restart time to a greater value than one second, your on-premises router might send return traffic to a next hop that's no longer active, instead of switching to a configured secondary next hop that is active.
- Stalepath timer
This setting determines how long a router waits before deleting learned routes after it receives an end-of-record (EOR) message from the other router. This timer starts when the BGP session is reinitialized after a graceful restart, but the prefix in question hasn't been addressed by an UPDATE message. We recommend setting the stalepath timer to 300 seconds on your on-premises router to match the setting for Cloud Router.
Redundant Cloud VPN tunnels
If the on-premises gateway doesn't support graceful restart, a failure on either side of the BGP session causes the session to fail and traffic is disrupted. After the BGP timeout is exceeded, which is 60 seconds for Cloud Router, routes are withdrawn from both sides. Dynamically routed Cloud VPN traffic no longer enters the tunnel. Static routes for the tunnel continue to be serviced.
Without graceful restart support, deploying two on-premises gateways with one tunnel each provides redundancy and failover. This configuration enables one tunnel and its devices to go offline for software upgrades or maintenance without disrupting traffic. Also, if one tunnel fails, the other tunnel can keep the routes active and traffic flowing.
The following example shows a single box as the Cloud Router, but with two IP addresses. The two addresses are separate ethernet interfaces inside the same Cloud Router task. Each interface is used for a separate BGP session with a separate on-premises gateway. In this particular use case, because these Cloud VPN tunnels are created for redundancy purposes, both BGP sessions exchange exactly the same set of route prefixes but with different next hops that point to different Cloud VPN tunnels.
Cloud Router gets upgraded periodically, which takes under 60 seconds. Cloud Router is not available during the upgrade. The BGP hold timer determines how long learned routes are preserved when the peered BGP router is unavailable. The BGP hold timer is negotiated to be the lower of the two values from both sides. Cloud Router uses a value of 60 seconds for the BGP hold timer. We recommend that you set your peer BGP hold timer to 60 seconds or greater (the default value is 3 minutes). As a result, both routers preserve their routes during these upgrades and traffic continues to flow.
During Cloud VPN gateway maintenance cycles with a single Cloud VPN gateway, the use of Cloud Router adds about 20 seconds to the tunnel recovery time because the BGP session is reset and routes have to be relearned. Cloud VPN gateway recovery times are usually about a minute. If there are redundant Cloud VPN gateways, traffic is unaffected because only one Cloud VPN gateway is taken down at a time.
For more information about using static and dynamic routing with a supported service, see the following documentation.
|Dedicated Interconnect||Static||Not supported|
|Dedicated Interconnect||Dynamic||Creating VLAN attachments|
|Classic VPN||Policy-based, static||Creating a Classic VPN using static routing|
|Classic VPN or HA VPN||Dynamic||Creating a Classic VPN using dynamic routing
Creating an HA VPN gateway to a Peer VPN gateway
Creating Google Cloud to Google Cloud HA VPN gateways