A single IPSec Cloud VPN tunnel is established but the Cloud Router shows the BGP session as not configured. Customer BGP settings: Local BGP address 169.254.11.1/30, Local ASN 64515, Peer BGP address 169.254.11.2, Peer ASN 64517, Base MED 1000, MD5 disabled. You already associated a Cloud Router with the VPN tunnel. Which BGP session settings should you configure on your Cloud Router?

The correct configuration for the Cloud Router's BGP session involves setting its local BGP IP to the peer's BGP IP from the customer's perspective (169.254.11.2) and its peer BGP IP to the customer's local BGP IP (169.254.11.1). The Cloud Router's ASN should be the customer's local ASN (64515) because the Cloud Router is acting as the customer's BGP peer to Google. MD5 authentication should be disabled to match the customer's settings. The Advertised Route Priority (MED) defaults to 100 on Google Cloud unless explicitly changed, and the customer's Base MED of 1000 is for routes advertised from the customer, not to them. The incorrect options either swap the local and peer IPs, use the wrong ASN for the Cloud Router, or incorrectly enable MD5 authentication or set the MED.