Transit Gateway CLI change log

In this change log, you can learn about the latest changes, improvements, and updates for IBM Cloud® Transit Gateway.

12 June 2024

Support for redundant Generic Routing Encapsulation (GRE) tunnel connections

To build in redundancy and eliminate the need to schedule an outage when a Transit Gateway router must down for maintenance, there is a new redundant GRE type, which is essentially a grouping of at least two GRE tunnels that can connect to classic or VPC networks. This connection type allows GRE tunnels to be placed on different devices in the same zone and not flag overlapping routes that are in the redundant GRE's tunnels. For more information, see Creating a redundant GRE tunnel.

New commands:

tg connection-rgre-create - Create a redundant GRE.
tg redundant-gre-tunnel-add - Add a tunnel to a redundant GRE.
tg redundant-gre-tunnel-remove - Remove a tunnel from a redundant GRE.

24 June 2023

Power Virtual Server connections for transit gateways: Transit gateways now support Power Virtual Server connections. A Power Virtual Server connection allows Power Virtual Server networks to connect to other networks (for instance, VPC and classic infrastructure) that are connected to the same transit gateway. For details, see ibmcloud tg connection-create.

24 April 2023

Direct Link multi-account support: Changed command: You can now create a connection of type directlink to pass into the connection-create command and create a direct link from a different account owner. Previously only connections of type vpc and classic were allowed.

30 November 2022

Unbound GRE tunnels

You can use an unbound Generic Routing Encapsulation (GRE) tunnel connection to connect endpoints, which allows a transit gateway to connect to overlay networks hosted on classic infrastructure resource.

New tg connection-create-gre command options:

base-network-type - Network type of the base connection (classic). For use only with the unbound_gre_tunnel network type.
network-account-id - ID of account to connect to a classic connection. For use only with the classic type when the account of the connection is different than the gateway's account.
network-type - Network type of the GRE connection. Values are gre_tunnel or unbound_gre_tunnel. The default value is gre_tunnel.

26 March 2022

Network prefix filters: Simplify the management of the IP addresses that you reference in your resources to route network traffic. You can create prefix filters to permit or deny specific routes on specific connections. These prefix filters are added to an ordered list that is processed sequentially. A default filter (permit or deny all prefixes) is then applied after the prefix filter list is processed. For more information, see Adding and deleting prefix filters.

15 November 2021

Transit gateway route reports

You can now request a route report, which shows all routes known to a transit gateway and each of its connections. The report shows:

Border Gateway Protocol (BGP) information associated with these routes
Which connections supply which routes
Overlapping routes

For more information, see Generating a transit gateway route report.

30 August 2021

Direct Link connections for transit gateways: Transit gateways now support Direct Link connections. A Direct Link connection allows an on-premises network to connect to other networks (for instance, VPC and classic infrastructure) that are connected to the same transit gateway.

17 June 2021

Allow Generic Routing Encapsulation (GRE) connections for transit gateways: Transit gateways now support connections using GRE tunnels to connect endpoints. A GRE tunnel connection allows a transit gateway to connect to overlay networks hosted on classic infrastructure resources.

01 March 2021

Classic infrastructure connections across IBM Cloud accounts

You can now connect to IBM Cloud® classic infrastructure in another IBM Cloud account by providing the cloud account ID when adding a connection to your transit gateway. The account containing the classic infrastructure is then able to view the gateway and all of its connections, and must choose to opt-in to allow account-to-account interconnectivity.

For more information, see Adding a cross-account connection.

01 January 2021

Connect networks to multiple local gateways

You can now connect networks, VPCs, and classic connections to multiple local transit gateways. Previously, you could connect a network only to a single transit gateway. Now traffic between local networks can use a local gateway. In addition, if you need to connect to a remote network, you can attach to a global gateway. Routing of traffic between networks takes an optimized path (if multiple connections exist), meaning local traffic stays local to the region and is not charged.

The limit for the number of gateways per account has been updated to ten, and the limit of gateways per region to five. You can open an IBM Support case if you need to expand your service limits further.

01 July 2020

VPC connections across IBM Cloud accounts

You can now connect to a VPC in another IBM Cloud account by providing the CRN of the VPC when adding a connection to your transit gateway. The account containing the VPC is then able to view the gateway and all of its connections, and must choose to opt-in to allow account-to-account interconnectivity for that VPC.

For more information, see Adding a cross-account connection.