HA VPN gateway

Related topics

• Cloud Router works with HA VPN gateway From the official documentation: “The product used with Cloud Router, such as the HA VPN gateway, is configured to use the IPv4 and IPv6 (dual-stack) or the IPv6-only (single stack) stack types.”
• Compute Engine works with HA VPN gateway From the official documentation: “In this topology, you connect an HA VPN gateway to a Compute Engine virtual machine (VM) instance.”
• HA VPN gateway is part of Cloud VPN From the official documentation: “Google Cloud provides a highly available [HA VPN](/network-connectivity/docs/vpn/concepts/overview#ha-vpn) service to connect your VPC network to environments running outside of Google Cloud, such as on-premises or on AWS through an IPsec VPN connection.”
• HA VPN gateway depends on VLAN attachments From the official documentation: “When you create an HA VPN gateway for an HA VPN over Cloud Interconnect deployment, you associate that HA VPN gateway with your encrypted VLAN attachment.”
• HA VPN gateway works with VLAN attachments From the official documentation: “You can only associate HA VPN gateways with encrypted VLAN attachments by using the Google Cloud CLI or the HA VPN API.”
• HA VPN gateway depends on VPC network From the official documentation: “Before creating an HA VPN gateway and tunnel pair, create a Virtual Private Cloud (VPC) network and at least one subnet in the region where the HA VPN gateway resides:”
• HA VPN gateway works with VPC network From the official documentation: “To connect two Google Cloud VPC networks, you create an HA VPN gateway in each network.”
• VPN tunnel is part of HA VPN gateway From the official documentation: “Use this procedure to check the status of tunnels on both interfaces of an HA VPN gateway.”
• Cloud Interconnect is an alternative to Cloud VPN From the official documentation: “Accessible by using hybrid connectivity (Cloud Interconnect or Cloud VPN).”
• Cloud NAT works with Cloud Router From the official documentation: “This will also delete the two Cloud NAT gateways that are connected to the Cloud Routers.”
• Dedicated Interconnect is an alternative to Partner Interconnect From the official documentation: “You can establish connectivity to on-premises networks using either Dedicated Interconnect or Partner Interconnect.”
• Cloud VPN is an alternative to Dedicated Interconnect From the official documentation: “VPC Peering, [Cloud VPN](/network-connectivity/docs/vpn), or Dedicated Interconnect connections for hybrid workloads”
• BGP session is part of Cloud Router From the official documentation: “The status of the Cloud Router's BGP sessions”
• Cloud Interconnect works with Cloud Router From the official documentation: “6. Delete the encrypted Cloud Router used for Cloud Interconnect.”
• Cloud Interconnect works with Cloud VPN From the official documentation: “You must enable high-availability (HA) VPN functionality when using Cloud Interconnect<br>with Cloud VPN.”
• Cloud VPN is an alternative to VPC Network Peering From the official documentation: “As a variation to the design, you can use Cloud VPN instead of VPC Network Peering.”
• Cloud Router works with Partner Interconnect From the official documentation: “For Partner Interconnect, all Cloud Routers must have a local ASN of `16550`.”
• Cloud VPN is an alternative to Partner Interconnect From the official documentation: “You can use Dedicated Interconnect, Partner Interconnect, or Cloud VPN to provide hybrid connectivity to your landing zone.”
• VLAN attachments is part of Cloud Interconnect From the official documentation: “Learn how to deploy HA VPN on top of the encrypted VLAN attachments of your Cloud Interconnect connection.”
• Cloud NAT depends on Cloud Router From the official documentation: “Cloud Router is a necessary control plane component for Cloud NAT.”
• Cloud Router works with VLAN attachments From the official documentation: “On your Cloud Router, add the interface or interfaces that connect to the VLAN attachment.”
• Dedicated Interconnect is part of Cloud Interconnect From the official documentation: “Cloud Interconnect offers two main options for connecting your on-premises network: Dedicated Interconnect and Partner Interconnect.”
• Partner Interconnect is part of Cloud Interconnect From the official documentation: “Cloud Interconnect offers two main options for connecting your on-premises network: Dedicated Interconnect and Partner Interconnect.”
• VLAN attachments depends on Cloud Router From the official documentation: “When you create a VLAN attachment, you associate it with a Cloud Router.”
• VLAN attachments is part of Dedicated Interconnect From the official documentation: “The HA VPN gateway or the VLAN attachment for Dedicated Interconnect is configured to use the `IPV4_IPV6` stack type.”
• Cloud Interconnect works with VPC network From the official documentation: “Connects to on-premises networks by using Cloud VPN tunnels and VLAN attachments for Cloud Interconnect.”
• Cloud NAT works with Compute Engine From the official documentation: “A Cloud NAT gateway provides outgoing connectivity for Compute Engine virtual machine (VM) instances without external IP addresses.”
• Cloud Router configures Cloud NAT From the official documentation: “Create a new Cloud Router to program a Cloud NAT gateway:”
• Cloud Router works with Cloud VPN From the official documentation: “For Cloud Router used with Cloud VPN, set up a dashboard for `network/received_packets_count` and `network/sent_packets_count` to monitor any loss in connectivity.”
• Dedicated Interconnect depends on Cloud Router From the official documentation: “Because Dedicated Interconnect and<br>Partner Interconnect require Cloud Router, all<br>the Cloud Router quotas and limits apply.”
• VLAN attachments is part of Partner Interconnect From the official documentation: “When using Partner Interconnect, you still create VLAN attachments to the VPC networks that you want to use.”
• BGP session depends on Cloud Router From the official documentation: “To create the required BGP sessions, you must create two interfaces on the Cloud Router used by your VLAN attachments.”
• BGP session depends on VLAN attachments From the official documentation: “If you delete the Cloud VPN tunnel or VLAN attachment associated with a BGP session, the session is automatically shut down.”
• BGP session depends on VPN tunnel From the official documentation: “If you delete the Cloud VPN tunnel or VLAN attachment associated with a BGP session, the session is automatically shut down.”
• Cloud Interconnect depends on VLAN attachments From the official documentation: “Using Cloud Interconnect to connect a VPC network to your on-premises network requires a [VLAN attachment](/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments).”
• Cloud Interconnect is an alternative to VPC Network Peering From the official documentation: “Connectivity between the load balancer's VPC network and the backend VPC network can be configured using either VPC Network Peering, Cloud VPN tunnels, Cloud Interconnect VLAN attachments, or a Network Connectivity Center framework.”
• Cloud Interconnect is an alternative to VPN tunnel From the official documentation: “The on-premises network or the other public cloud networks are privately connected to your Google Cloud network through a VPN tunnel or through Cloud Interconnect.”
• Cloud NAT is an alternative to Cloud VPN From the official documentation: “If you create a Managed Service for Apache Spark cluster with [internal IP addresses only](/managed-spark/docs/concepts/configuring-clusters/network#create_a_cloud_dataproc_cluster_with_internal_ip_address_only), attempts to access `github.com` over the internet in an…”
• Cloud Router works with Dedicated Interconnect From the official documentation: “Cloud Router provides dynamic (BGP) routing for Cloud VPN, Dedicated Interconnect, and Partner Interconnect.”
• Compute Engine works with VPC Network Peering From the official documentation: “VPC Network Peering works with [Compute Engine](/compute/docs), [GKE](/kubernetes-engine/docs), and [App Engine flexible environment](/appengine/docs/flexible).”
• Partner Interconnect depends on Cloud Router From the official documentation: “Because Dedicated Interconnect and<br>Partner Interconnect require Cloud Router, all<br>the Cloud Router quotas and limits apply.”
• Partner Interconnect works with VPC network From the official documentation: “Partner Interconnect provides connectivity between your on-premises network and your Virtual Private Cloud (VPC) network through a supported service provider.”
• VLAN attachments depends on Dedicated Interconnect From the official documentation: “The following requirements apply to each VPC network in which you create VLAN attachments that depend on the Cloud Interconnect connections.”
• VLAN attachments works with VPC Network Peering From the official documentation: “A VLAN attachment that is used with either type of connection can use Shared VPC or VPC Network Peering to share the connectivity between multiple VPC networks.”
• VPN tunnel depends on Cloud Router From the official documentation: “When you create HA VPN tunnels in Google Cloud, each tunnel needs a BGP interface to the Cloud Router and a BGP interface to the active-active virtual network gateway (VPN gateway) in Azure.”
• VPN tunnel depends on VPC network From the official documentation: “Before creating an HA VPN gateway and tunnel pair, create a Virtual Private Cloud (VPC) network and at least one subnet in the region where the HA VPN gateway resides:”