Creating an unbound Generic Routing Encapsulation tunnel connection

Creating an unbound GRE tunnel connection on an existing transit gateway

To create your unbound GRE tunnel on an existing transit gateway, follow these steps:

1. From your browser, open the IBM Cloud console and log in to your account.

2. Select the Navigation Menu icon from the upper left, then click Interconnectivity.

3. Click Transit Gateway from the left navigation panel. Click the name of the transit gateway where you want to add a connection.

   If you are in the expanded view, click View details.

4. Click Add connection in the Connections tab.

5. Choose Unbound GRE tunnel as your network connection type.

6. Select the base network type and whether this is a connection to a network in another account.

7. If this connection is to a network in another account, enter the account ID.

8. Choose an availability zone in which to create the tunnel.

9. Configure the remaining parameters for the connection:

   • Enter the remote gateway IP^[1] for the endpoint of the GRE tunnel.

   • Enter a /30 remote tunnel IP^[2] for both ends of the tunnel, for example 192.168.103.2.

   • Enter the local gateway IP address^[3] that the transit gateway uses to host the underlay network for the GRE tunnel. This user-selected IP address is configured on the transit gateway GRE tunnel after the tunnel is created.

   • Enter a /30 local tunnel IP^[4] for both ends of the tunnel, for example 192.168.103.1.

   • Optionally, enter the remote BGP ASN, which is a valid 2 or 4 byte value of your choosing.

     You can leave this blank and a unique ASN is assigned.

   • Enter a connection name for your GRE tunnel.

10. Click the Add button to create the GRE tunnel.

Creating an unbound GRE tunnel connection while creating a new transit gateway

To create your unbound GRE tunnel connection while creating a new transit gateway, follow these steps:

1. From your browser, open the IBM Cloud console and log in to your account.

2. Select the Navigation Menu icon from the upper left, then click Interconnectivity.

3. Click Transit Gateway from the left navigation panel. Click Create transit gateway.

4. Enter the transit gateway name, resource group, and location.

5. Choose Unbound GRE tunnel as your network connection type for the connection to create.

6. Select the base network type and whether this is a connection to a network in another account.

7. If this connection is to a network in another account, enter the account ID.

8. Choose an availability zone in which to create the tunnel.

9. Configure the remaining parameters for the connection:

   • Enter the remote gateway IP^[5] for the endpoint of the GRE tunnel.

   • Enter a /30 remote tunnel IP^[6] for both ends of the tunnel, for example 192.168.103.2.

   • Enter the local gateway IP address^[7] that the transit gateway uses to host the underlay network for the GRE tunnel. This user-selected IP address is configured on the transit gateway GRE tunnel after the tunnel is created.

   • Enter a /30 local tunnel IP^[8] for both ends of the tunnel, for example 192.168.103.1.

   • Optionally, enter the remote BGP ASN, which is a valid 2 or 4 byte value of your choosing.

     You can leave this blank and a unique ASN is assigned.

   • Enter a connection name for your GRE tunnel.

10. Click the Add connection button to add the unbound GRE tunnel to the transit gateway.

11. After all connections have been added, click Create to create the transit gateway with the network connections.

Next steps

To configure the other end of the BGP tunnel, expand the newly created unbound GRE tunnel in the Connections panel to see its details. It will show the Local BGP ASN. If you created an optional remote BGP ASN, it also shows in the Connections panel. You must give this ASN information to the person creating the other end of the BGP tunnel, so that the BGP session can be fully configured.

Example

This example illustrates creating an unbound GRE tunnel connection named unbound-gre-connection to a classic network:

ibmcloud tg connection-create-gre $gateway  --network-type unbound_gre_tunnel --name unbound-gre-connection --base-network-type classic  --zone us-south-2 --local-gateway-ip 192.168.100.1 --local-tunnel-ip 192.168.101.1 --remote-gateway-ip 10.242.63.12 --remote-tunnel-ip 192.168.101.2

Request

To request a creation of an Unbound Generic Routing Encapsulation (GRE) tunnel connection, set the following parameters:

curl -X POST "https://transit.cloud.ibm.com/v1/transit_gateways/test/connections?version=2022-01-27" -H "accept: application/json" -H "Content-Type: application/json" -d "{\"local_gateway_ip\":\"192.168.100.1\",\"local_tunnel_ip\":\"192.168.129.2\",\"name\":\"Transit_Service_BWTN_SJ_DL\",\"network_type\":\"unbound_gre_tunnel\",\"base_network_type\":\"classic\",\"remote_bgp_asn\":65010,\"remote_gateway_ip\":\"10.242.63.12\",\"remote_tunnel_ip\":\"192.168.129.1\",\"zone\":{\"name\":\"us-south-1\"}}"

{
  "local_gateway_ip": "192.168.100.1",
  "local_tunnel_ip": "192.168.129.2",
  "name": "Transit_Service_BWTN_SJ_DL",
  "network_type": "unbound_gre_tunnel",
  "base_network_type": "classic",
  "remote_bgp_asn": 65010,
  "remote_gateway_ip": "10.242.63.12",
  "remote_tunnel_ip": "192.168.129.1",
  "zone": {
    "name": "us-south-1"
  }
}

Response

The following response results show after you initiate the request:

{
  "created_at": "2020-03-31T12:08:05Z",
  "id": "1a15dca5-7e33-45e1-b7c5-bc690e569531",
  "name": "example-connection",
  "network_type": "unbound_gre_tunnel",
  "base_network_type": "classic",
  "status": "pending",
  "updated_at": "2020-03-31T12:08:05Z"
}

Example

This example illustrates requesting an unbound GRE tunnel connection:

resource "ibm_tg_connection" "test_ibm_tg_connection" {
  gateway            = ibm_tg_gateway.test_tg_gateway.id
  network_type       = "unbound_gre_tunnel"
  base_network_type  = "classic"
  name               = "myconnection"
  local_gateway_ip   = 192.168.0.1
  local_tunnel_ip    = 10.0.0.1
  remote_bgp_asn     = 36361
  remote_gateway_ip  = 192.168.1.1
  remote_tunnel_ip   = 10.0.1.1
  zone               = us-east
}