> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aviatrix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Segmentation

> This section provides the purpose, elements, and actions performed on the Network Segmentation pages.

This section provides the purpose, elements, and actions performed on the
**Network Segmentation** pages.

> [tab] Overview
>
> > [tab] Logical View
> >
> > ### Purpose
> >
> > The **Logical view** page shows how network domains are connected or isolated based on configured connection policies, without showing Gateway placement or regional details.
> >
> > ### Elements
> >
> > ![Network Segmentation: Logical View](https://docs.aviatrix.com/images/reference/ui/networking/network-segmentation-logical.png)
> >
> > * **Multi Cloud Network Domain Connectivity canvas**: Visual representation of logical segments and their connections.
> > * **Filter control**: Autocomplete with placeholder **Select a Filter** or **Add Filter**; applies filter chips by **Domain** or **Node** to the canvas.
> > * **Network Domains legend**: Color-coded list of network domain names beside the canvas.
> > * **Canvas helper text**: Describes node reachability and grouping by **network domains**; additional helper text for the arc chart describes domain hover behavior.
> >
> > ### Actions
> >
> > > [accordion] View Logical Segmentation
> > >
> > > To view the logical network domain connectivity:
> > >
> > > 1. Go to **Networking** > **Network Segmentation** > **Overview**.\
> > >    Select the **Logical View** tab.
> > > 2. The Logical View page appears with the Multi Cloud Network Domain Connectivity canvas.
> > > 3. Review the network domains and the connections between them on the canvas. Hover over a domain to highlight reachability.
> > > 4. Optionally, use the **Filter** control to add filter chips by domain or node.
> > >
> > > The canvas shows network domain relationships and connectivity between gateway VPC/VNets based on their network domains. Thick colored lines represent network domains; thin colored lines represent connectivity between gateways.
> > >
> > > ### Parameter Details
> > >
> > > | CoPilot Parameter Name | Description |
> > > | - | - |
> > > | Filter | Domain or node selected to filter the connectivity canvas. |
> > > | Legend (Network Domains) | Name and color of each network domain shown in the side legend. |
>
> > [tab] Physical View
> >
> > ### Purpose
> >
> > The **Physical View** page shows how network domains and their members are placed and connected through Transit Gateways and Spoke Gateways across the Transit network.
> >
> > ### Elements
> >
> > ![Network Segmentation: Physical View](https://docs.aviatrix.com/images/reference/ui/networking/network-segmentation-physical.png)
> >
> > * **Multi Cloud Transit Gateway & Spoke Connectivity canvas**: Visual representation of physical segments and their connections.
> > * **Filter control**: Autocomplete with placeholder **Select a Filter** or **Add Filter**; applies filter chips by **Transit GW**, **Domain**, or **Node** to the canvas.
> > * **Transit Gateways legend**: Color-coded list of transit gateway names beside the canvas.
> > * **Canvas helper text**: Describes node reachability and grouping by **transit gateways**.
> >
> > ### Actions
> >
> > > [accordion] View Physical Segmentation
> > >
> > > To view the physical network domain connectivity:
> > >
> > > 1. Go to **Networking** > **Network Segmentation** > **Overview**.\
> > >    Select the **Physical View** tab.
> > > 2. The Physical View page appears with the Multi Cloud Transit Gateway & Spoke Connectivity canvas.
> > > 3. Review how network domains and their members are placed and connected through Transit Gateways and Spoke Gateways.
> > > 4. Optionally, use the **Filter** control to add filter chips by transit gateway, domain, or node.
> > >
> > > The canvas shows Spoke/Edge VPC/VNets and their connectivity via Transit Gateways across the Transit network.
> > >
> > > ### Parameter Details
> > >
> > > | CoPilot Parameter Name | Description |
> > > | - | - |
> > > | Filter | Transit gateway, domain, or node selected to filter the connectivity canvas. |
> > > | Legend (Transit Gateways) | Name and color of each transit gateway shown in the side legend. |
>
> > [tab] Regional View
> >
> > ### Purpose
> >
> > The **Regional view** page shows where network domain members are deployed across cloud regions to provide geographic visibility of segmentation.
> >
> > ### Elements
> >
> > ![Network Segmentation: Regional View](https://docs.aviatrix.com/images/reference/ui/networking/network-segmentation-regional.png)
> >
> > * **Multi Cloud Region Segmentation canvas**: Visual representation of regions and their domains.
> > * **Filter control**: Autocomplete with placeholder **Select a Filter** or **Add Filter**; applies filter chips by **Region**, **Domain**, or **Node** to the canvas.
> > * **Gateway Regions legend**: Color-coded list of cloud region names beside the canvas.
> > * **Canvas helper text**: Describes node reachability and grouping by **transit gateway regions**.
> >
> > ### Actions
> >
> > > [accordion] View Regional Segmentation
> > >
> > > To view network domain members by cloud region:
> > >
> > > 1. Go to **Networking** > **Network Segmentation** > **Overview**.\
> > >    Select the **Regional View** tab.
> > > 2. The Regional View page appears with the Multi Cloud Region Segmentation canvas.
> > > 3. Review where network domain members are deployed across cloud regions.
> > > 4. Optionally, use the **Filter** control to add filter chips by region, domain, or node.
> > >
> > > The canvas provides geographic visibility of segmentation by showing domain members by cloud region.
> > >
> > > ### Parameter Details
> > >
> > > | CoPilot Parameter Name | Description |
> > > | - | - |
> > > | Filter | Region, domain, or node selected to filter the segmentation canvas. |
> > > | Legend (Gateway Regions) | Name and color of each cloud region shown in the side legend. |

> [tab] Network Domains
>
> ## Purpose
>
> The **Network Domains** page creates and manages network domains that define routing isolation and controlled connectivity between Spoke Gateways through Transit Gateways.
>
> ## Elements
>
> ![Network Segmentation: Network Domains](https://docs.aviatrix.com/images/reference/ui/networking/network-segmentation-domains.png)
>
> * **+ Network Domain** button: Starts the **Create Network Domain** workflow (admin only).
> * **Transit Gateways** button: Opens **Configure Transit Gateways for Network Segmentation** (admin only).
> * **Network Domains table**: Columns **Name**, **Associations**, and **Connected To**; footer **Total N Network Domains** and **Refresh status**.
> * **Filter**, **Download**, and **Search** toolbar controls on the table.
> * **Name** link: Opens a read-only detail dialog with **Associations** and **Connected Domains** tabs.
> * **Edit** row action: Opens **Edit Network Domain** for the selected domain (admin only).
> * **Delete** row action: Opens **Delete Network Domain** after confirmation (disabled when the domain has associations or connections; admin only).
>
> ## Actions
>
> > [accordion] View Network Domains
> >
> > To view network domains:
> >
> > 1. Go to **Networking** > **Network Segmentation** > **Network Domains**.
> > 2. The Network Domains page appears with the table of existing network domains.
> > 3. Review **Name**, **Associations**, and **Connected To** for each domain, or click a **Name** link to open domain details.
> >
> > The table displays all configured network domains and their routing isolation and connectivity settings.
> >
> > ### Parameter Details
> >
> > | CoPilot Parameter Name | Description |
> > | - | - |
> > | Name | Name of the network domain (opens the detail dialog when selected). |
> > | Associations | Spoke/Edge Gateways or TGW Domain associated with the domain. |
> > | Connected To | Other network domains connected to this domain. |
>
> > [accordion] Create Network Domain
> >
> > To create a network domain:
> >
> > 1. Go to **Networking** > **Network Segmentation** > **Network Domains**.
> > 2. Click **+ Network Domain**.
> > 3. Enter the **Name** for the network domain.
> > 4. Configure **Associations** (Spoke/Edge Gateways or TGW Domain).
> > 5. Optionally, configure **Connect to Network Domain** to define connectivity to other domains. Connectivity is bidirectional.
> > 6. Click **Save**.
> >
> > The new network domain is created and appears in the Network Domains table.
> >
> > ### Parameter Details
> >
> > | CoPilot Parameter Name | Description |
> > | - | - |
> > | Name | Name of the network domain. |
> > | Associations | Spoke/Edge Gateways or TGW Domain to associate with the domain. |
> > | Connect to Network Domain | Other network domains this domain can connect to. |
>
> > [accordion] Enable Network Segmentation on Transit Gateways
> >
> > To enable network segmentation on Transit Gateways:
> >
> > 1. Go to **Networking** > **Network Segmentation** > **Network Domains**.
> > 2. Click **Transit Gateways**.
> > 3. In the **Configure Transit Gateways for Network Segmentation** dialog, toggle **Network Segmentation** on for the desired Transit Gateways.
> > 4. Click **Save**.
> >
> > Enable network segmentation on Transit Gateways before creating network domains.
> >
> > ### Parameter Details
> >
> > | CoPilot Parameter Name | Description |
> > | - | - |
> > | Name | Name of the Transit Gateway. |
> > | Cloud | Cloud provider hosting the Transit Gateway. |
> > | Region | Cloud region of the Transit Gateway. |
> > | IP Address Space | IP address space configured for the Transit Gateway. |
> > | Network Segmentation | Toggle to enable or disable network segmentation on the Transit Gateway. |
>
> > [accordion] Edit Network Domain
> >
> > To edit a network domain:
> >
> > 1. Go to **Networking** > **Network Segmentation** > **Network Domains**.
> > 2. Locate the network domain in the table and click **Edit**.
> > 3. Update **Associations** and **Connect to Network Domain** as needed.
> > 4. Save your changes.
> >
> > Changes take effect immediately after saving.
> >
> > ### Parameter Details
> >
> > | CoPilot Parameter Name | Description |
> > | - | - |
> > | Associations | Spoke/Edge Gateways or TGW Domain associated with the domain. |
> > | Connect to Network Domain | Other network domains this domain can connect to. |
>
> > [accordion] Delete Network Domain
> >
> > To delete a network domain:
> >
> > 1. Go to **Networking** > **Network Segmentation** > **Network Domains**.
> > 2. Locate the network domain in the table and click **Delete**.
> > 3. Confirm the deletion.
> >
> > You can only delete a network domain if it has no associations or connections.

> [tab] Settings
>
> ## Purpose
>
> The **Settings** page manages support for Virtual Routing and Forwarding (VRF) on Aviatrix Transit-to-Transit Peering connections.
>
> ## Elements
>
> ![Network Segmentation: Settings](https://docs.aviatrix.com/images/reference/ui/networking/network-segmentation-settings.png)
>
> * **Support for VRF** toggle: Enables or disables VRF support (**Applicable only for Aviatrix Transit-Transit Peering** tooltip).
> * **No peerings found.**: Shown when VRF support is On but no Transit Peerings exist.
> * **All Transit Peerings are up-to-date.** success alert: Shown when every peering has VRF rolled out.
> * **Transit Peering Up-to-date / Stale counts**: When peerings exist, shows how many are up-to-date versus stale.
> * **Rollout Changes to Transit Peerings** button: Opens **Rollout Support for VRF** to select peerings to update (hidden when no peerings exist).
>
> ## Actions
>
> > [accordion] Enable or Disable Support for VRF
> >
> > To turn VRF support on or off:
> >
> > 1. Go to **Networking** > **Network Segmentation** > **Settings**.
> > 2. Turn the **Support for VRF** toggle On or Off.
> > 3. If turning Off, confirm in the **Rollout changes to disable Support for VRF?** dialog. Disabling causes all Transit Peerings to become stale, and changes roll out immediately.
> > 4. If turning On, click **Save**.
> >
> > When enabled, existing Transit Peerings show as stale until VRF is rolled out to them.
>
> > [accordion] Rollout VRF Support to Transit Peerings
> >
> > To roll out or remove VRF support on specific Transit Peerings:
> >
> > 1. Go to **Networking** > **Network Segmentation** > **Settings**, with **Support for VRF** turned On.
> > 2. Click **Rollout Changes to Transit Peerings**.
> > 3. In the **Rollout Support for VRF** dialog, select or deselect the peerings to enable or disable VRF on.
> > 4. Click **Rollout**.
> >
> > The selected peerings are updated, and the Up-to-date and Stale counts refresh accordingly.
> >
> > ### Parameter Details
> >
> > | CoPilot Parameter Name | Description |
> > | - | - |
> > | Transit/Edge Spoke Gateway | The Transit or Edge Spoke Gateway on one side of the peering. |
> > | Peering Type | The type of peering, for example Transit-Transit, Intra-Group, Edge Spoke-Transit, or BGP Spoke-Transit. |
> > | Transit Gateway Instance | The Transit Gateway instance on the other side of the peering. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.