Skip to content

Latest commit

 

History

History
91 lines (59 loc) · 4.14 KB

transit_segmentation_workflow.rst

File metadata and controls

91 lines (59 loc) · 4.14 KB

Aviatrix Transit Network Segmentation Workflow

For questions, refer to Aviatrix Transit Segmentation FAQ.

Note

In releases prior to 6.7, the term "security domain" was used. This has been renamed to "network domain".

  1. Enable the Aviatrix Transit Gateway for segmentation.
Setting Value
Aviatrix Transit Gateway Name An Aviatrix Transit Gateway deployed in the Multi-Cloud Transit Network workflow
  1. Create a Multi-Cloud Network domain. You can make changes to your network segmentation at any time, simply come back to this page.
Setting Value
Network Domain Name Specify a unique domain name. For example, Dev_Domain
  1. Add/modify connection policies.

This step specifies the connection relationship of one domain to others. Two connected domains imply that Spokes in each domain can communicate with each other despite the fact that they are in different domains.

Highlight a domain on the left panel and click Add, the domain will appear to the right.


This section is to build the network segmentation by associating a Spoke.

  1. Associate Aviatrix Spoke/Edge to the domain.
Setting Value
Aviatrix Transit Gateway Name The name of the Aviatrix Transit Gateway
Network Domain Name The name of the Network Domain
Attachment Name The name of a Spoke or edge connection to associate to the domain
  1. Disassociate Aviatrix Spoke/Edge to domain.
Setting Value
Aviatrix Transit Gateway Name The name of the Aviatrix Transit Gateway
Network Domain Name The name of the Network Domain
Attachment Name The name of a Spoke or edge connection to disassociate from the domain

This section consists of the delete functions.

  1. Delete Multi-Cloud Network domain.
Setting Value
Network Domain Name The name of the Network Domain
  1. Disable Aviatrix Transit Gateway for segmentation.
Setting Value
Aviatrix Transit Gateway Name An Aviatrix Transit Gateway deployed in the Multi-Cloud Transit Network workflow