05-10-2021 11:22 AM
We have three VPC and Transit Gateway along with Gateway Load Balancer deployed. Two VM series deployed in two AZs and We have test VPC that spans in three AZs Gateway Both FW registered in Target Group of Load Balancer using IP address. When FW are deployed interface swap is not used. Routes are configured as network diagram.
I can ping from test vpc1 to test vpc2 and vice versa when both FW are up and running, BUT when I do failover test by shutting down one of the FW, some test VPC cannot ping to other Test VPC like if I ping from test VPC1 to two VMs on other Test VPC running on two different AZz, one connection drops during when shutting down one FW, i.e. Gateway Load Balancer is not transferring connection other FW which is running, so have following questions:
When deploying FW behind Gateway Load Balancer in AWS, is it mandatory to swap-interface during boot-strap ?
05-10-2021 11:31 AM
Have you enabled Appliance mode on the TGW Attachment and cross-zone load balancing on the GWLB?
Interface swap is not required but recommended when using automation script or autoscaling.
05-10-2021 11:31 AM
Have you enabled Appliance mode on the TGW Attachment and cross-zone load balancing on the GWLB?
Interface swap is not required but recommended when using automation script or autoscaling.
05-14-2021 08:05 AM
After implementing cross-zone load balancing it fix issue.
Thanks
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
