> ## Documentation Index > Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL. > Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other. > Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking. > Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify. # Create a Virtual Network > How to create a Local or Switch virtual network on a node using the Virtual Network Creation Wizard in Edge Infrastructure Services. ## Introduction This procedure walks through creating a virtual network on a node using the creation wizard in Edge Infrastructure Services. You can create two types of virtual networks: Local (a routed virtual subnet with DHCP) or Switch (a Layer 2 bridge to a physical network). The wizard sections differ based on the type you select. ### Prerequisites * You have the SysManager or SysAdmin role in your enterprise. See [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md). * At least one node onboarded to Edge Infrastructure Services. * For a Local virtual network: the subnet, gateway, and DNS settings you want to use. * For a Switch virtual network: knowledge of which physical port on the node to bridge. ## Open the Creation Wizard 1. In the sidebar, click **Infrastructure > Workloads > Virtual Networks**. 2. Select the contextual **+** create action. ## Select the Virtual Network Type The first screen asks you to choose how the virtual network should connect your edge applications. * Click **Local** to create an isolated routed subnet. The wizard includes Identity, Details, IP Settings, and Routes sections. * Click **Switch** to create a Layer 2 bridge to a physical port. The wizard includes only Identity and Details sections. There are no IP settings or routes to configure. Clicking a card immediately advances to the wizard with the selected type. ## Configure the Identity 1. In the **Name** field, enter a unique name for the virtual network. This name cannot be changed after creation. 2. In the **Title** field, enter a display title. You can change this value at any time. 3. In the **Description** field, enter an optional description to help other administrators understand the purpose of the virtual network. 4. In the **Tags** field, add optional key-value tags. Tags let you automatically attach this virtual network to application instances in a project that matches the tag. For example, tag this network `role:management` and set a network adapter's Match NI Tag to `role:management` to bind the adapter to this network automatically. 5. Click **Next**. ## Configure the Details 1. In the **Target Type** field, select **Node** to deploy the virtual network to a single node, or **Node Cluster** to deploy it to a cluster. The configuration copies to every node in the cluster when you select Node Cluster. 2. Select the **Node** (or **Node Cluster**) from the dropdown. 3. To enable LLDP (Link Layer Discovery Protocol) traffic on the virtual network, toggle **Enable LLDP Traffic**. 4. In the **Node Port** field, select the physical port, VLAN sub-interface, LAG adapter, or adapter label to use for this virtual network. The options available depend on how the node was configured at onboarding. Adapter labels group multiple physical ports under a single name so that the virtual network can use all of them for multi-path routing with automatic failover instead of being tied to a single port. Adapter labels are assigned to ports in the node's adapter configuration. See [Configure Node Adapters](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/configure-node-adapters.md) for instructions. 5. In the **MTU** field, enter the maximum transmission unit in bytes if you need a value other than the default. The minimum value is 1280. Leave this field empty to use the default (1500 bytes for air-gapped networks, or the lowest MTU among associated ports for networks with external connectivity). The MTU field is only available when no port is selected. 6. To automatically assign this virtual network to all new application instances created on the selected node, select the **Default Node Network Instance** checkbox. This option is not available for cluster deployments. 7. Click **Next**. ## Configure IP Settings (Local Only) This section appears only when the virtual network type is **Local**. Switch virtual networks do not have IP settings. 1. In the **IP Address Config** field, select **DHCP** to let EVE-OS assign IP addresses automatically, or **Static** to specify fixed IP addresses. 2. If you selected **Static**, complete the following fields. * **Subnet**: the subnet in CIDR notation, for example `192.168.10.0/24`. * **Gateway**: the IP address of the default gateway for the virtual network. * **Name Server**: the IP address of the DNS server. * **NTP Server**: the IP address or FQDN of the NTP server. Separate multiple values with commas. * **Domain**: an optional domain name for the virtual network. * **IP Address Range (Start)** and **IP Address Range (End)**: the range of addresses available for assignment to application instances. 3. In the **Hostname** section, add optional hostname-to-IP address mappings for specific devices on the virtual network. 4. Click **Next**. ## Configure Routes (Local Only) This section appears only when the virtual network type is **Local**. Use it to add static routes and configure probing for multi-path failover. ### Add static routes For each static route you want to add, click **Add route**, then fill in the fields: 1. In the **Prefix** field, enter the destination network in CIDR notation, for example `0.0.0.0/0` for a default route or `10.0.0.0/8` for a specific network. 2. In the **Gateway** field, enter the next-hop gateway IP address. Leave this blank to use the default gateway of the selected output port. 3. In the **Output Port** field, select the physical port or adapter label for this route. Selecting an adapter label creates a multi-path route across all ports with that label. When you select an adapter label as the output port, a **Probing Configuration** section appears directly below that route row. Configure probing for each route that uses an adapter label: * Toggle **Prefer Low Adapter Cost** to route traffic through lower-cost ports first (enabled by default). * Toggle **Prefer Stronger Cellular Signal** to prefer cellular ports with better signal strength when multiple cellular modems are available. * Toggle **Gateway Ping** to have EVE-OS check gateway reachability every 15 seconds using ICMP ping (enabled by default). In the **Max Allowed Adapter Cost** field, set the maximum port cost for which gateway ping runs. Ports with higher cost have gateway ping disabled to reduce probe traffic. * Toggle **Custom User Probe** to configure an additional probe that runs every 2.5 minutes. Select a probing method from the dropdown: **ICMP** (enter an IP address or hostname to ping) or **TCP** (enter an IP address or hostname and a TCP port number from 1 to 65535). Repeat for each static route you want to add. ### Enable connected routes Toggle **Connected Routes** to allow EVE-OS to propagate routing information about directly connected subnets to application instances through DHCP. This ensures that application traffic destined for directly reachable networks is routed correctly without requiring additional static route configuration. Click **Next**. ## Create the Virtual Network Click **Create Virtual Network**. A confirmation message appears when the virtual network is created successfully. ## Verify the Configuration After creation, verify that the virtual network was provisioned successfully. 1. In the sidebar, click **Infrastructure > Workloads > Virtual Networks**. 2. Locate the new virtual network in the list. 3. Click the virtual network name to open the detail page. 4. On the **Overview** tab, confirm that the **State** shows **Online** or **Provisioned**. ## Next Steps > [card] [Manage a Virtual Network](https://zededa.mintlify.site/new-ui/infrastructure-services/virtual-networks/manage-a-virtual-network.md) > > View details, update configuration, or delete the virtual network. > [card] [Deploy an Application Instance](https://zededa.mintlify.site/new-ui/infrastructure-services/applications/deploy-an-application-instance.md) > > Attach the virtual network to an application during deployment. > [card] [Virtual Networks Overview](https://zededa.mintlify.site/new-ui/infrastructure-services/virtual-networks.md) > > A reference guide on virtual network types, IP options, VLANs, and routing. > [card] [Tagging](https://zededa.mintlify.site/new-ui/start/tagging.md) > > Tag virtual networks so app network adapters can bind to them by tag instead of by name.