Network instances

Network instances enable you to configure network connectivity and routing for your edge applications. This document describes how to manage local and switch network instances using the ZEDEDA GUI.


This document assumes that you are familiar with the following:
  • The content in our Networking overview.
  • Essential networking topics, such as IP addressing, subnetworks, gateways, NTP servers, static and connected routing, etc.

View your network instances

  1. Hover on the Library dropdown menu.
  2. Select Network Instances from the options.
  3. Observe both the list of your instances and the Summary drop down panel.
  4. Click on one of your instances in to see its details.
NOTE: The orange arrow icon (Default_indicator.png) marks a network instance as a default instance.

Create a network instance

  1. Navigate to your Network Instance list view.
  2. Click the Add icon at the top right of your page.
  3. Configure your new instance. Refer to the following subsections for information about your options.
  4. When you finish setting up your new instance, click Add. A toast message will appear.
  5. Refer to the list view to verify that your instance was successfully created.

Identity configuration

You can't change your instance's Name value after you create it.

You can add tags to your network instance, which you can use to attach it to your projects during project creation. If you do so, your network instance will be automatically applied to all edge apps that you add to that project.

Switch instances

When you create a switch network instance, you need to select an edge node before you can select a port. After you select an edge node from the Edge Node dropdown, the Port dropdown options will populate with the ports available on the node that you selected.

Local instances

When you create a local network instance, you need to choose a port and configure IP settings. You also have the option to designate the new instance as default for the edge node that you select.

The Uplink port in EVE-OS groups together all management-type ports. EVE continuously monitors these ports and uses only one at a time for applications using this network instance, based on which port has stable connectivity. If the currently used port loses connection, EVE automatically switches to another management port. However, app-shared ports are not included in this failover functionality.

When you configure the instance's IP addresses, you have the option to let EVE do so automatically, or to provide the required addresses yourself.

Static and connected routes

When you create a local network instance, you can add static routes and enable connected routes. Both types of routes are automatically (zero-touch) propagated by DHCP (option 121) to every app instance connected to the local network instance.

Connected routes route application traffic destined to the network segment that the physical network instance port is part of. Since EVE knows the port’s subnet and the gateway IP (from static IP config or from DHCP), it can automatically generate such a route and propagate it to the application using DHCP. You only need to decide if EVE should propagate connected routes to the network instance’s app instances. Make your selection using the labeled toggle (disabled by default).

Static routes are user-configured routes propagated to applications. These are typically used to route application traffic destined to external networks one or more routing hops away (i.e. not directly connected to the device). Unlike connected routes, which EVE generates automatically when enabled, static routes are edited manually (subnet + gateway).

We recommend using static and connected routes when your application is using more than one network interface for external connectivity. Without static and connected routes, all traffic destined to external endpoints will be routed by a default route, configured by the app’s DHCP client, with a non-deterministically selected output port, which may not be desirable.

Another common case is using one application as a network gateway for other applications running on the same device. The gateway application may provide some network function(s), such as firewall, IDS, network monitoring, etc. Such application will connect on one side with the external network(s) using directly attached network adapter(s) or via switch network instance(s), and the other side will make use of an air-gap local network instance to connect with other applications running on the device. Propagated static IP routes are necessary to make the application traffic flow through the gateway app. In theory, multiple network functions can be chained together in this way using several air-gap network instances with static IP routes.

Update a network instance

  1. Navigate to your Network Instances list view and select an instance.
  2. Click on the Basic Info tab.
  3. Click on the pencil icon.
  4. Make your changes.
  5. Click Submit. A toast notification will appear.

Delete a network instance

  1. Navigate to your Network Instance list view and select an instance.
  2. From the details page of your chosen instance, click the meatballs icon in the top right of the page.
  3. Select Delete form the drop down options.
  4. Confirm the deletion. A toast message will appear.

NOTE: Network Instances cannot be deleted if attached to more than one edge app Instance.

Was this article helpful?
3 out of 3 found this helpful

Articles in this section