Transit Gateway Connect

Question 1

What is the core purpose of TGW Connect?

Answer 1

To integrate SDWAN virtual appliances into TGW by means of GRE tunnels

Question 2

What is MP-BGP, what does it enable, and what is required on AWS to use it?

Answer 2

Multi-Protocol BGP is an extension of BGP to carry routing information for multiple protocols (IPv4, IPv6). Allows you to route multiple address families (types) over a single peering, and retrofit.

Question 3

What is a TGW Connect “Attachment”

Answer 3

What supports up to 4 GRE tunnels between a TGW and a network appliance (either on-prem on inside AWS). The attachment requires an underlay attachment – with VPC or DX.

Question 4

What is a TGW Connect Peer?

Answer 4

A connection to the third-party appliance, with established GRE and BGP sessions, allowing an exchange or routing info

Question 5

One of the reasons to create a TGW Connect overlaying a DX physical connection is to allow the advertisement of a high number of prefixes

Question 6

Three major functions of the TGW Network Manager

Answer 6

A single view of the entire network

Centralized network management

SD-WAN integration

Question 7

How does TGW Network Manager identify SDWAN devices and TGWs?

Answer 7

TGWs have to be registered. Major 3rd party SD-WAN providers (CISCO, etc.) provide for few-click configuration

Question 8

What is Transit Gateway Connect?

Answer 8

An attachment type that uses GRE for higher bandwidth performance compared to a VPN connection

Question 9

Can you create a new Connect attachment on an existing TGW?

Answer 9

Yes

Question 10

What two underlying transport mechanisms can a TGW Connect attachment use?

Answer 10

1. Direct Connect attachment (if the SD-WAN appliance is on-prem)
2. VPC attachment (if the SD-WAN device is in an AWS VPC)

Question 11

What are TGW Connect PEERS?

Answer 11

The (two) GRE tunnels that you establish between TGW and the SD-WAN devices, regardless of whether the WAN device is on-prem or in a VPC