Ordering IBM Cloud Transit Gateway

Creating a transit gateway in the UI

To get started using IBM Cloud Transit Gateway, follow these steps:

1. Review requirements and configuration considerations in Planning for Transit Gateway.

2. From your browser, open the IBM Cloud catalog and log in to your account.

3. Select Networking in the navigation pane, then click the Transit Gateway tile. The Transit Gateway ordering page displays.

   You can also access the ordering page from the IBM Cloud console by selecting the Menu icon on the upper left of the page. Then, select Interconnectivity > Transit Gateway and click the Create transit gateway button.

4. Enter a name for the transit gateway and choose a resource group. You can select a resource group from the list, or keep the default selection.

5. Choose a routing option:

   All of your classic resources and Direct Link connections across MZRs can be accessed regardless of whether local or global routing is enabled.

   • Select Local routing to allow your transit gateway to connect to all VPC and classic resources within the transit gateway's provisioned region.
   • Select Global routing to allow your transit gateway to connect to VPC resources in all IBM Multi-Zone Regions (MZRs).

   You can upgrade routing options at a later point if your needs change. Pricing is changed accordingly.

6. Choose the location where you want to provision your transit gateway.

   If you are using local routing, the specified location limits you to connect VPCs located in that region only. If you are using global routing, the specified location affects network latency, so choose the region closest to the resources that you need connected.

7. Add connections to your transit gateway now, or after it has been provisioned.

   1. Select the network connection to be attached to the transit gateway. To add connections later, see Adding a connection.

      You can add a new connection on the same account as the connection type, or request to connect to a network in another account.

      Select from the following connection types:

      • Classic infrastructure networks allow you to connect to IBM Cloud classic resources. Only one classic infrastructure connection is allowed per account.

      • VPC networks can contain compute resources, allowing you to connect to your account's VPC resources, or, with approval, another account's VPC resources.

      • Unbound GRE tunnel allows a transit gateway to connect to overlay networks hosted on classic infrastructure resources. For more information, see Creating an Unbound Generic Routing Encapsulation tunnel connection.

      • Direct Link creates a network connection to and from Direct Link gateways so that there is a secure connection to on-premises networks and other resources connected to the transit gateway.

        If you select Direct Link, you must also log in to the Direct Link console and specify Transit Gateway as the type of network connection for your direct link.

      • Power Virtual Server - Creates a network connection to a Power Virtual Server workspace to access the resources in a Power Virtual Server colo.

        If you select Power Virtual Server, a Power Virtual Server workspace must be created in a PER-enabled data center. For a list of PER-enabled data centers, see Getting started with the Power Edge Router.

   2. After you select a network connection, choose a connection reach option:

      • Add new connection in this account - Enter an optional connection name and any other required information for your connection.

        For Power Virtual Server, select a location for the Power Virtual Server workspace. Then, select from the list of Power Virtual Server workspaces that are enabled for Transit Gateway. Keep in mind that not all Power Virtual Server workspaces show in this menu.

      • Request connection to a network in another account - Enter either the IBM Cloud ID or Cloud Resource Name (CRN) of the account that manages the network where you want to connect. Then, complete any remaining information. All resources connected to that transit gateway will be accessible from the other network. For more information, including how to obtain the Cloud ID or CRN, see Adding a cross-account connection.

        • IBM Cloud ID - Required by Classic infrastructure and Unbound GRE connections.
        • CRN - Required by VPC, Direct Link, and Power Systems Virtual Server connections.

        To find out if your Power Systems Virtual Server workspace is set up correctly, go to the Power Systems Virtual Server UI and check the navigation for a Cloud connections page. If there isn't a Cloud connections page, the workspace leverages Transit Gateway. Otherwise, you must configure virtual connections with Cloud connections on the Power Systems Virtual Server.

8. Optionally, you can create prefix filters to permit or deny specific routes on specific connections. For prefix filtering considerations and step-by-step instructions, see Adding and deleting prefix filters.

   To begin, expand the drop-down arrow in the upper right of the Prefix filtering section, and complete the following information:

   1. Select the default filter that you want to use. You can either permit (default) or deny all prefixes.

      The default filter is applied only if you don't create prefix filters that bypass this default setting.

   2. Click Create prefix filter to open the side panel and start creating prefix filters. In turn, your prefix filters are added to an ordered list that is processed sequentially.

   3. Click Save to save your changes.

9. View Terms on the right of the page.

10. Click Create to complete your order.

Creating a transit gateway from the CLI

export IBMCLOUD_TG_API_ENDPOINT=private.transit.cloud.ibm.com

ibmcloud tg gateway-create|gwc --name NAME --location LOCATION [--routing ROUTING] [--resource-group-id RES_GROUP_ID] [--output json] [-h, --help]

ibmcloud tg gwc --name myGateway --location us-south

Creating a transit gateway using the API

Follow these instructions to create a transit gateway with the API:

1. Set up your API environment.
2. Store any additional variables to be used in the API commands.

curl -X POST --location --header "Authorization: Bearer
{iam_token}" \
--header "Accept: application/json" \
--header "Content-Type: application/json" \
--data '{ "location": "us-south", "name": "Transit_Service_BWTN_SJ_DL" }' \
"{base_url}/transit_gateways?version={version}"

{
  "created_at": "2020-03-31T12:08:05Z",
  "crn": "crn:[...]",
  "global": true,
  "id": "ef4dcb1a-fee4-41c7-9e11-9cd99e65c1f4",
  "location": "us-south",
  "name": "example-gateway",
  "resource_group": {
    "id": "56969d6043e9465c883cb9f7363e78e8"
  },
  "status": "pending",
  "updated_at": "2020-03-31T12:08:05Z"
}

Creating a transit gateway using Terraform

Review the following argument references that you can specify for your resource when creating a transit gateway using Terraform:

resource "ibm_tg_gateway" "new_tg_gw"{
name="transit-gateway-1"
location="us-south"
global=true
resource_group="30951d2dff914dafb26455a88c0c0092"
}