Cloud Router is a distributed and fully managed offering that provides speaker and responder capabilities. Cloud Router works with Cloud Interconnect, Cloud VPN, and Router appliances to create in VPC networks based on BGP-received and custom learned routes. Cloud Router and the work together. Andromeda handles all packet routing and forwarding capabilities, and Cloud Routers manage corresponding BGP sessions. Cloud Routers don't provide packet routing or forwarding capability.
Key features
Cloud Router offers the following features:
BGP session management, including support for and . : advertise IP ranges to your network when you use a . : Cloud Router uses routes received from BGP peers and custom learned routes to create in VPC networks. (): BGP route policies let you set rules to filter BGP routes or modify BGP route attributes.
Best practices
When working with Cloud Router, use the following best practices.
If your on-premises Border Gateway Protocol (BGP) router supports , enable it on your on-premises BGP device and on the Cloud Router to provide a high-availability network link that can respond faster to link failures. If your peer router supports it, consider enabling on your BGP sessions. By default, BGP sessions are unauthenticated. Enable graceful restart on your on-premises BGP device. With graceful restart, traffic between networks isn't disrupted in the event of a Cloud Router or on-premises BGP device failure as long as the BGP session is re-established within the graceful restart period. If graceful restart is not supported or enabled on your device, configure two on-premises BGP devices with one tunnel each to provide redundancy. If you don't configure two separate on-premises devices, Cloud VPN tunnel traffic can be disrupted in the event of a Cloud Router or an on-premises BGP device failure. To ensure that you don't exceed Cloud Router , use Cloud Monitoring to create . For example, you can use the metrics for learned routes to create alerting policies for the . If appropriate, you can manually configure and apply them to a BGP session. Dynamic routes created from custom learned routes are programmed and withdrawn just like dynamic routes that are BGP received.