Launch Aviatrix Spoke Gateways

In this blog, I’ve logged steps to provision AWS VPC or Azure vNet for launching Aviatrix Spoke Gateways (HPE and none-HPE)

AWS – HPE

  • Create VPC with CIDR allocated for application.
  • Create subnets to populate application CIDR range.
  • Create IGW and associate with VPC.
  • Create appropriate route table for application subnet.
  • On VPC, add /25 CIDR for Aviatrix HPE spoke gateways. (Each HPE gateway require /26 for up to 50 secondary IPs)
  • In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Select VPC and enable High Performance Encryption, select the first /26 within added /25 range, and launch spoke gateway
  • In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Enable/Disable HA to an Aviatrix Spoke Gateway -> Select primary gateway, select the second /26 range and AZ, click Enable

AWS – None HPE

  • Create VPC with CIDR allocated for application.
  • Create subnets to populate application CIDR range.
  • Create IGW and associate with VPC.
  • Create appropriate route table for application subnet.
  • On VPC, add /27 CIDR for Aviatrix none HPE spoke gateways.
  • Within /27 range, create two /28 subnets in different AZ, one for primary gateway, one for HA gateway.
  • Create route table for each subnet, and associate 0.0.0.0 with IGW
  • Associate each route table to each subnet
  • In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Select VPC, select the first /28 subnet, and launch spoke gateway
  • In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Enable/Disable HA to an Aviatrix Spoke Gateway -> Select primary gateway, select the second /28 subnet, click Enable

Azure – HPE

  • Create vNet with CIDR allocated for application.
  • Create subnets to populate application CIDR range.
  • Create appropriate route table for application subnet.
  • On vNet address space, add /25 CIDR for Aviatrix HPE spoke gateways. (Each HPE gateway require /26 for up to 50 secondary IPs)
  • In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Select vNet and enable High Performance Encryption, select the first /26 within added /25 range, and launch spoke gateway
  • In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Enable/Disable HA to an Aviatrix Spoke Gateway -> Select primary gateway, select the second /26 range and AZ, click Enable

Azure – None HPE

  • Create vNet with CIDR allocated for application.
  • Create subnets to populate application CIDR range.
  • Create appropriate route table for application subnet.
  • On vNet address space, add /27 CIDR for Aviatrix HPE spoke gateways.
  • Within /27 range, create two /28 subnets in different AZ, one for primary gateway, one for HA gateway.
  • (optional) For each subnet, create route table, and add 0.0.0.0 target Internet
  • In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Select vNet and enable High Performance Encryption, select the first /28 subnet with appropriate AZ, and launch spoke gateway
  • In Aviatrix Controller -> Multi-cloud Transit -> Setup -> Spoke -> Enable/Disable HA to an Aviatrix Spoke Gateway -> Select primary gateway, select the second /28 subnet with appropriate AZ, click Enable

Leave a Reply

Your email address will not be published. Required fields are marked *