gcloud

If you want to use the command-line examples in this guide, do the following:

1. Install or update to the latest version of theGoogle Cloud CLI.
2. Set adefault region andzone.

API

If you want to use the API examples in this guide, set upAPI access.

Console

For HA VPN

1. To configure a BGP session for HA VPN,in the Google Cloud console, go to theCloud VPN tunnels page.

   Go to Cloud VPN tunnels

2. Select the Cloud VPN tunnel that contains theBGP session to update.

3. On theVPN tunnel details page, clickEdit BGP session.

4. In theMultiprotocol BGP section, click theEnable IPv6 traffictoggle to the on position.

5. Optional: You can allocate the IPv6 BGP addresses forHA VPN tunnels manually or automatically.

   • To allocate the addresses automatically, selectAutomatically.
   • To allocate the addresses manually:
     1. Enter the IPv6 address for theCloud Router BGP IPv6 next hopfield. This address is an IPv6 address used byCloud Router for this Cloud VPN tunnel. ThisIPv6 address is advertised as the next hop for the IPv6 routesthat Cloud Router advertises to its BGP peer. Theaddress must be in the range2600:2d00:0:2::/63.
     2. Enter the IPv6 address for thePeer BGP IPv6 next hop field.This address is the IPv6 address of the on-premises router orpeer VPN device. This IPv6 address is the next hop for the IPv6routes learned from the BGP peer of Cloud Router. Theaddress must be in the range2600:2d00:0:2::/63.

6. ClickSave and continue.

For Dedicated Interconnect

1. To configure a BGP session for Dedicated Interconnect,go to theVLAN attachments page.

   Go to VLAN attachments

2. Select the VLAN attachment that contains the BGP session to update.

3. On theVLAN attachment details page,clickEdit BGP session.

4. In theMultiprotocol BGP section, click theEnable IPv6 traffictoggle to the on position.

5. ClickSave and continue.

gcloud

Run theupdate-bgp-peer command. Use the--enable-ipv6 flagto allow the BGP session to exchange IPv6 routes, as shown in the followingexample:

gcloud compute routers update-bgp-peerROUTER_NAME \    --peer-name=PEER_NAME \    --enable-ipv6

gcloud compute routers update-bgp-peerROUTER_NAME \    --peer-name=PEER_NAME \    --enable-ipv6 \    --ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS \    --peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS

API

Use therouters.patch methodto update thebgpPeers[] field.

ThebgpPeers[] field accepts an array of BGP peers. When youPATCH thisfield, you overwrite the existing array of BGP peers with the new arrayincluded in your request.

1. Send aGET request to get the current array of BGP peers for the router.For details, seeView BGP session configuration.

2. Send aPATCH request with a new array of BGP peers. For each BGP peer forwhich you want to enable IPv6 in the BGP session,setbgpPeers[].enableIpv6 toTRUE.

   PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/routers/ROUTER_NAME{  "bgpPeers": [BGP_PEERS  ]}

   Replace the following:

   • PROJECT_ID: the project that contains theCloud Router
   • REGION: the region where the Cloud Routeris located
   • ROUTER_NAME: the name of the Cloud Router
   • BGP_PEERS: the contents of the new array of BGPpeers

   The following example enables IPv6 in the session for the first BGP peer:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"169.254.10.1","peerIpAddress":"169.254.10.2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":true},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"169.254.20.1","peerIpAddress":"169.254.20.2","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false"}

   Additionally, if you are enabling IPv6 traffic for a BGP sessionused in an HA VPN tunnel, you can specify IPv6 nexthop addresses:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"169.254.10.1","peerIpAddress":"169.254.10.2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":true,"ipv6NexthopAddress":"2600:2d00:0:2:0:0:1:5","peerIpv6NexthopAddress":"2600:2d00:0:2:0:0:1:6"},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"169.254.20.1","peerIpAddress":"169.254.20.2","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false}

   Use the values ofipv6NexthopAddress andpeerIpv6NexthopAddressto configure your on-premises router or peer VPN device.

   To view example configurations for HA VPN and yourpeer VPN device, seeSet up third-party VPNs for IPv4 and IPv6 traffic.

   To view example configurations for Dedicated Interconnectand your on-premises router,seeSet up on-premises routers for IPv4 and IPv6 traffic.

Console

For HA VPN

1. In the Google Cloud console, go to theCloud VPN tunnels page.

   Go to Cloud VPN tunnels

2. Select the Cloud VPN tunnel that contains the BGP session toupdate.

3. On theVPN tunnel details page, clickEdit BGP session.

4. To disable IPv6 route exchange, click theEnable IPv6 traffic toggleto the off position.

5. ClickSave and continue.

For Dedicated Interconnect

1. In the Google Cloud console, go to theVLAN attachments page.

   Go to VLAN attachments

2. Select the VLAN attachment that contains the BGP session to update.

3. On theVLAN attachment details page, clickEdit BGP session.

4. To disable IPv6 route exchange, click theEnable IPv6 traffic toggleto the off position.

5. ClickSave and continue.

gcloud

Run the update-bgp-peer command. Use the --no-enable-ipv6 flag toprevent the BGP session from exchanging IPv6 routes, as shownin the following example:

gcloud compute routers update-bgp-peerROUTER_NAME \--peer-name=PEER_NAME \--no-enable-ipv6

API

Use therouters.patch methodto update thebgpPeers[] field.

ThebgpPeers[] field accepts an array of BGP peers. When youPATCH thisfield, you overwrite the existing array of BGP peers with the new arrayincluded in your request.

1. Send aGET request to get the current array of BGP peers for the router.For details, seeView BGP session configuration.

2. Send aPATCH request with a new array of BGP peers. For each BGP peer forwhich you want to disable IPv6 in the BGP session, setbgpPeers[].enableIpv6 toFALSE.

   PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/routers/ROUTER_NAME{  "bgpPeers": [BGP_PEERS  ]}

   Replace the following:

   • PROJECT_ID: the project that contains theCloud Router
   • REGION: the region where the Cloud Routeris located
   • ROUTER_NAME: the name of the Cloud Router
   • BGP_PEERS: the contents of the new array of BGPpeers

   The following example disables IPv6 in the session for the first BGP peer:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"169.254.10.1","peerIpAddress":"169.254.10.2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"169.254.20.1","peerIpAddress":"169.254.20.2","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false}

Console

For HA VPN

1. To configure a BGP session for HA VPN,in the Google Cloud console, go to theCloud VPN tunnels page.

   Go to Cloud VPN tunnels

2. Select the Cloud VPN tunnel that contains the BGP session toupdate.

3. On theVPN tunnel details page, clickEdit BGP sessions.

4. In theMultiprotocol BGP section, click theEnable IPv4 traffictoggle to the on position.

5. Optional: You can allocate the IPv6 BGP addresses forHA VPN tunnels manually or automatically.

   • To allocate the addresses automatically, selectAutomatically.
   • To allocate the addresses manually:
     1. SelectManually.
     2. Enter the IPv6 address for theCloud Router BGP IPv6 addressfield. This address is an IPv6 address used byCloud Router for this Cloud VPN tunnel. ThisIPv6 address is advertised as the next hop for the IPv6 routesthat Cloud Router advertises to its BGP peer. Theaddress must be in the range2600:2d00:0:2::/63.
     3. Enter the IPv6 address for theBGP peer IPv6 address field.This address is the IPv6 address of the on-premises router orpeer VPN device. This IPv6 address is the next hop for the IPv6routes learned from the BGP peer of Cloud Router. Theaddress must be in the range2600:2d00:0:2::/63.

6. Optional: You can allocate the Cloud Router BGP IPv4 next hopaddresses for HA VPN tunnels manually orautomatically.

   • To allocate the addresses automatically, selectAutomatically.
   • To allocate the addresses manually:
     1. SelectManually.
     2. Enter the IPv4 address for theCloud Router BGP IPv4 nexthop field. This address is an IPv4 address used byCloud Router for this Cloud VPN tunnel. ThisIPv4 address is advertised as the next hop for the IPv4 routesthat Cloud Router advertises to its BGP peer. Theaddress must be a link-local address within the same/30 subnetas the BGP peer IPv4 address.
     3. Enter the IPv4 address for thePeer BGP IPv4 next hop field.This address is the IPv4 address of the on-premises router orpeer VPN device. This IPv4 address is the next hop for the IPv6routes learned from the BGP peer of Cloud Router. Theaddress must be a link-local address within the same/30 subnetas the Cloud Router BGP IPv4 address.

7. ClickSave and continue.

For Dedicated Interconnect

1. To configure a BGP session for Dedicated Interconnect,go to theVLAN attachments page.

   Go to VLAN attachments

2. Select the VLAN attachment that contains the BGP session to update.

3. On theVLAN attachment details page, clickEdit BGP session.

4. In theMultiprotocol BGP section, click theEnable IPv4 traffictoggle to the on position.

5. ClickSave and continue.

gcloud

Run theupdate-bgp-peer command. Use the--enable-ipv4 flagto allow the BGP session to exchange IPv4 routes, as shown in the followingexample:

gcloud compute routers update-bgp-peerROUTER_NAME \    --peer-name=PEER_NAME \    --enable-ipv4

gcloud compute routers update-bgp-peerROUTER_NAME \    --peer-name=PEER_NAME \    --enable-ipv4 \    --ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS \    --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS

API

Use therouters.patch methodto update thebgpPeers[] field.

ThebgpPeers[] field accepts an array of BGP peers. When youPATCH thisfield, you overwrite the existing array of BGP peers with the new arrayincluded in your request.

1. Send aGET request to get the current array of BGP peers for the router.For details, seeView BGP session configuration.

2. Send aPATCH request with a new array of BGP peers. For each BGP peer forwhich you want to enable IPv4 in the BGP session,setbgpPeers[].enableIpv4 toTRUE.

   PATCH https://compute.googleapis.com/compute/projects/PROJECT_ID/regions/REGION/routers/ROUTER_NAME{  "bgpPeers": [BGP_PEERS  ]}

   Replace the following:

   • PROJECT_ID: the project that contains theCloud Router
   • REGION: the region where the Cloud Routeris located
   • ROUTER_NAME: the name of the Cloud Router
   • BGP_PEERS: the contents of the new array of BGPpeers

   The following example enables IPv4 in the session for the first BGP peer:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"fdff:1::1","peerIpAddress":"fdff:1::2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv4":true},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"fdff:1::3","peerIpAddress":"fdff:1::4","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv4":false}

   Additionally, if you are enabling IPv4 traffic for a BGP sessionused in an HA VPN tunnel, you can specify IPv4 nexthop addresses:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"fdff:1::1","peerIpAddress":"fdff:1::2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv4":true,"ipv4NexthopAddress":"169.254.0.1","peerIpv4NexthopAddress":"169.254.0.2"},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"fdff:1::3","peerIpAddress":"fdff:1::4","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv4":false}

Console

For HA VPN

1. In the Google Cloud console, go to theCloud VPN tunnels page.

   Go to Cloud VPN tunnels

2. Select the Cloud VPN tunnel that contains the BGP session toupdate.

3. On theVPN tunnel details page, clickEdit BGP session.

4. In theMultiprotocol BGP section, click theEnable IPv4 traffictoggle to the off position.

5. ClickSave and continue.

For Dedicated Interconnect

1. In the Google Cloud console, go to theVLAN attachments page.

   Go to VLAN attachments

2. Select the VLAN attachment that contains the BGP session to update.

3. On theVLAN attachment details page, clickEdit BGP sessions.

4. In theMultiprotocol BGP section, click theEnable IPv4 traffictoggle to the off position.

5. ClickSave and continue.

gcloud

Run theupdate-bgp-peer command. Use the--no-enable-ipv4 flag toprevent the IPv6 BGP session from exchanging IPv4 routes, as shownin the following example:

gcloud compute routers update-bgp-peerROUTER_NAME \    --peer-name=PEER_NAME \    --no-enable-ipv4

API

Use therouters.patch methodto update thebgpPeers[] field.

ThebgpPeers[] field accepts an array of BGP peers. When youPATCH thisfield, you overwrite the existing array of BGP peers with the new arrayincluded in your request.

1. Send aGET request to get the current array of BGP peers for the router.For details, seeView BGP session configuration.

2. Send aPATCH request with a new array of BGP peers. For each BGP peer forwhich you want to disable IPv4 in the BGP session, setbgpPeers[].enableIpv4 toFALSE.

   PATCH https://compute.googleapis.com/compute/projects/PROJECT_ID/regions/REGION/routers/ROUTER_NAME{  "bgpPeers": [BGP_PEERS  ]}

   Replace the following:

   • PROJECT_ID: the project that contains theCloud Router
   • REGION: the region where the Cloud Routeris located
   • ROUTER_NAME: the name of the Cloud Router
   • BGP_PEERS: the contents of the new array of BGPpeers

   The following example disables IPv4 in the session for the first BGP peer:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"fdff:1::1","peerIpAddress":"fdff:1::2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv4":false},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"fdff:1::3","peerIpAddress":"fdff:1::4","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv4":false}

Console

For HA VPN

1. To configure a BGP session for HA VPN,in the Google Cloud console, go to theCloud VPN tunnels page.

   Go to Cloud VPN tunnels

2. Find the Cloud VPN tunnel that contains theBGP session to update.

3. On theVPN tunnel details page, clickEdit BGP sessions.

4. Select a BGP session type. To enable route exchange for IPv4 and IPv6selectBoth.

5. Optional: You can allocate the BGP IPv4 addresses forHA VPN tunnels manually or automatically.

   • To allocate the addresses automatically, selectAutomatically.
   • To allocate the addresses manually:
     1. SelectManually.
     2. Enter the IPv4 address for theCloud Router BGP IPv4 address.This address is an IPv4 address used by Cloud Routerfor this Cloud VPN tunnel. This IPv4 address isadvertised as the next hop for the IPv4 routes thatCloud Router advertises to its BGP peer.The address must be a link-local address within the same/30subnet as the BGP peer IPv4 address.
     3. Enter the IPv4 address for theBGP peer IPv4 address.This address is the IPv4 address of the on-premises router or peerVPN device. This IPv4 address is the next hop for the IPv6 routeslearned from the BGP peer of Cloud Router.The address must be a link-local address within the same/30subnet as the Cloud Router BGP IPv4 address.

6. Optional: You can allocate the BGP IPv6 addresses forHA VPN tunnels manually or automatically.

   • To allocate the addresses automatically, selectAutomatically.
   • To allocate the addresses manually:
     1. SelectManually.
     2. Enter the IPv6 address for theCloud Router BGP IPv6 address.This address is an IPv6 address used by Cloud Routerfor this Cloud VPN tunnel. This IPv6 address isadvertised as the next hop for the IPv6 routes thatCloud Router advertises to its BGP peer.The address must be in the rangefdff:1::/64.
     3. Enter the IPv6 address for theBGP peer IPv6 address. Thisaddress is the IPv6 address of the on-premises router or peer VPNdevice. This IPv6 address is the next hop for the IPv6 routeslearned from the BGP peer of Cloud Router. The addressmust be in the rangefdff:1::/64.

7. ClickSave and continue.

For Dedicated Interconnect

1. To configure a BGP session for Dedicated Interconnect,go to theVLAN attachments page.

   Go to VLAN attachments

2. Select the VLAN attachment that contains the BGP session to update.

3. On theVLAN attachment details page, clickEdit BGP session.

4. Select a BGP session type. To enable route exchange for IPv4 and IPv6selectBoth.

5. In theIPv4 BGP session section, enter the ASN value for theon-premises side of the BGP session inPeer ASN.

6. In theIPv6 BGP session section, enter the ASN value for theon-premises side of the BGP session inPeer ASN.

7. ClickSave and continue.

gcloud

1. To avoid a conflict with the new IPv6 BGP, disable IPv6 route exchange onyour existing IPv4 BGP session.

   Important: Disabling IPv6 route exchange on your existing IPv4 BGP sessioncauses IPv6 traffic to route away from your VLAN attachment and to backuppaths until IPv6 BGP is established.

   Run the following command:

   gcloudcomputeroutersupdate-bgp-peerROUTER_NAME--peer-name=PEER_NAME\--no-enable-ipv6

   Replace the following:

   • ROUTER_NAME: the name of the Cloud Router
   • PEER_NAME: the name of the BGP peer

2. Add the new IPv6 interface:

   gcloudcomputeroutersadd-interfaceROUTER_NAME\--interface-name=INTERFACE_NAME\--interconnect-attachment=ATTACHMENT_NAME\--ip-version=IPV6

   Replace the following:

   • INTERFACE_NAME: the name of the interface
   • ATTACHMENT_NAME: the name of the VLAN attachment

3. Add the new IPv6 BGP peer:

   gcloudcomputeroutersadd-bgp-peerROUTER_NAME\--peer-name=PEER_NAME\--interface=INTERFACE_NAME\--peer-asn=PEER_ASN

   Replace the following:

   • PEER_ASN: the BGP peer's ASN

4. To configure the on-premises BGP session, get the VLAN attachment's IPv6address:

   gcloudcomputeinterconnectsattachmentsdescribeATTACHMENT_NAME

   The output is similar to the following:

   adminEnabled:trueedgeAvailabilityDomain:AVAILABILITY_DOMAIN_1bandwidth:BPS_1GcloudRouterIpAddress:169.254.67.201/29cloudRouterIpv6Address:2600:2d00:0:1::1/125creationTimestamp:'2017-12-01T08:31:11.580-08:00'customerRouterIpAddress:169.254.67.202/29customerRouterIpv6Address:2600:2d00:0:1::2/125description:Interconnect for Customer 1id:'7193021941765913888'interconnect:https://www.googleapis.com/compute/projects/partner-project/global/interconnects/lga-2kind:compute#interconnectAttachmentlabelFingerprint:42WmSpB8rSM=name:partner-attachmentpartnerMetadata:interconnectName:New York (2)partnerName:Partner IncportalUrl:https://partner-portal.comregion:https://www.googleapis.com/compute/projects/partner-project/regions/us-central1selfLink:https://www.googleapis.com/compute/projects/partner-project/regions/us-central1/interconnectAttachments/customer-attachmentstackType:IPV4_IPV6state:ACTIVEtype:PARTNERvlanTag8021q:1000

   The relevant IPv6 addresses are listed undercloudRouterIPv6Address andcustomerRouterIpv6Address.

API

Use therouters.patch methodto update thebgpPeers[] field.

ThebgpPeers[] field accepts an array of BGP peers. When youPATCH thisfield, you overwrite the existing array of BGP peers with the new arrayincluded in your request.

1. Send aGET request to get the current array of BGP peers for the router.For details, seeView BGP session configuration.

2. Send aPATCH request with a new array of BGP peers. For each BGP peer forwhich you want to enable IPv6 in the BGP session,setbgpPeers[].enableIpv6 toTRUE andbgpPeers[].enableIpv4 toFALSE.

   PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/routers/ROUTER_NAME{  "bgpPeers": [BGP_PEERS  ]}

   Replace the following:

   • PROJECT_ID: the project that contains theCloud Router
   • REGION: the region where the Cloud Routeris located
   • ROUTER_NAME: the name of the Cloud Router
   • BGP_PEERS: the contents of the new array of BGPpeers

   The following example enables IPv6 in the session for the first BGP peer:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"169.254.10.1","peerIpAddress":"169.254.10.2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":true,"enableIpv4":false},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"169.254.20.1","peerIpAddress":"169.254.20.2","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false}

   Additionally, if you are enabling IPv6 traffic for a BGP session used inan HA VPN tunnel, you can specify IPv6 next hopaddresses:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"169.254.10.1","peerIpAddress":"169.254.10.2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":true,"enableIpv4":false,"ipv6NexthopAddress":"2600:2d00:0:2:0:0:1:5","peerIpv6NexthopAddress":"2600:2d00:0:2:0:0:1:6"},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"169.254.20.1","peerIpAddress":"169.254.20.2","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false}

   Use the values ofipv6NexthopAddress andpeerIpv6NexthopAddressto configure your on-premises router or peer VPN device.

   To view example configurations for HA VPN and your peerVPN device, seeSet up third-party VPNs for IPv4 and IPv6traffic.

   To view example configurations for Dedicated Interconnectand your on-premises router, seeSet up on-premises routers for IPv4and IPv6traffic.

Console

For HA VPN

1. To configure a BGP session for HA VPN,in the Google Cloud console, go to theCloud VPN tunnels page.

   Go to Cloud VPN tunnels

2. Find the Cloud VPN tunnel that contains theBGP session to update.

3. On theVPN tunnel details page, clickEdit BGP sessions.

4. Select a BGP session type. To enable route exchange for IPv4 selectIPv4 BGP session.

5. To enable MP-BGP, in theMultiprotocol BGP section, click theEnable IPv6 traffic toggle to the on position.

6. Optional: You can allocate the IPv4 BGP addresses forHA VPN tunnels manually or automatically.

   • To allocate the addresses automatically, in theAllocate BGP IPv4address section, selectAutomatically.
   • To allocate the addresses manually:
     1. SelectManually.
     2. Enter the IPv4 address for theCloud Router BGP IPv4 address.This address is an IPv4 address used by Cloud Router forthis Cloud VPN tunnel. This IPv4 address is advertisedas the next hop for the IPv4 routes that Cloud Routeradvertises to its BGP peer. The address must be a link-localaddress within the same/30 subnet as the BGP peer IPv4address.
     3. Enter the IPv4 address for theBGP peer IPv4 address. Thisaddress is the IPv4 address of the on-premises router or peer VPNdevice. This IPv4 address is the next hop for the IPv6 routeslearned from the BGP peer of Cloud Router. The addressmust be a link-local address within the same/30 subnet as theCloud Router BGP IPv4 address.

7. Optional: You can allocate the IPv6 BGP next hop addresses forHA VPN tunnels manually or automatically.

   • To allocate the addresses automatically, in theAllocate BGP IPv6next hop section, selectAutomatically.
   • To allocate the addresses manually:
     1. SelectManually.
     2. Enter the IPv6 address for theCloud Router BGP IPv6 nexthop. This address is an IPv6 address used byCloud Router for this Cloud VPN tunnel. ThisIPv6 address is advertised as the next hop for the IPv6 routesthat Cloud Router advertises to its BGP peer. Theaddress must be in the range2600:2d00:0:2::/63.
     3. Enter the IPv6 address for thePeer BGP IPv6 next hop. Thisaddress is the IPv6 address of the on-premises router or peer VPNdevice. This IPv6 address is the next hop for the IPv6 routeslearned from the BGP peer of Cloud Router. The addressmust be in the range2600:2d00:0:2::/63.

8. ClickSave and continue.

For Dedicated Interconnect

1. To configure a BGP session for Dedicated Interconnect,go to theVLAN attachments page.

   Go to VLAN attachments

2. Select the VLAN attachment that contains the BGP session to update.

3. On theVLAN attachment details page,clickEdit BGP session.

4. Select a BGP session type. To enable route exchange for IPv4 selectIPv4 BGP session.

5. To enable MP-BGP, in theMultiprotocol BGP section, click theEnable IPv6 traffic toggle to the on position.

6. ClickSave and continue.

gcloud

1. Remove the IPv6 BGP peer:

   gcloudcomputeroutersremove-bgp-peerROUTER_NAME\--peer-name=PEER_NAME

2. Remove the IPv6 BGP interface:

   gcloudcomputeroutersremove-interfaceROUTER_NAME\--interface-name=INTERFACE_NAME

3. Enable IPv4 MP-BGP:

   gcloudcomputeroutersupdate-bgp-peerROUTER_NAME\--peer-name=PEER_NAME\--enable-ipv6

API

Use therouters.patch methodto update thebgpPeers[] field.

ThebgpPeers[] field accepts an array of BGP peers. When youPATCH thisfield, you overwrite the existing array of BGP peers with the new arrayincluded in your request.

1. Send aGET request to get the current array of BGP peers for the router.For details, seeView BGP session configuration.

2. Send aPATCH request with a new array of BGP peers. For each BGP peer forwhich you want to enable IPv6 in the BGP session,setbgpPeers[].enableIpv6 toTRUE andbgpPeers[].enableIpv4 toFALSE.

   PATCH https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/routers/ROUTER_NAME{  "bgpPeers": [BGP_PEERS  ]}

   Replace the following:

   • PROJECT_ID: the project that contains theCloud Router
   • REGION: the region where the Cloud Routeris located
   • ROUTER_NAME: the name of the Cloud Router
   • BGP_PEERS: the contents of the new array of BGPpeers

   The following example enables IPv4 and disable IPv6 in the session for thefirst BGP peer:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"169.254.10.1","peerIpAddress":"169.254.10.2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false,"enableIpv4":true},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"169.254.20.1","peerIpAddress":"169.254.20.2","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false}

   Additionally, if you are enabling IPv6 traffic for a BGP session used inan HA VPN tunnel, you can specify IPv6 next hopaddresses:

   {"name":"peer-1","interfaceName":"if-peer-1","ipAddress":"169.254.10.1","peerIpAddress":"169.254.10.2","peerAsn":64512,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false,"enableIpv4":true,"ipv6NexthopAddress":"2600:2d00:0:2:0:0:1:5","peerIpv6NexthopAddress":"2600:2d00:0:2:0:0:1:6"},{"name":"peer-2","interfaceName":"if-peer-2","ipAddress":"169.254.20.1","peerIpAddress":"169.254.20.2","peerAsn":64513,"advertisedRoutePriority":100,"advertiseMode":"DEFAULT","advertisedGroups":[],"advertisedIpRanges":[],"enable":"TRUE","enableIpv6":false}

   Use the values ofipv6NexthopAddress andpeerIpv6NexthopAddressto configure your on-premises router or peer VPN device.

   To view example configurations for HA VPN and your peerVPN device, seeSet up third-party VPNs for IPv4 and IPv6traffic.

   To view example configurations for Dedicated Interconnectand your on-premises router, seeSet up on-premises routers for IPv4and IPv6traffic.