How to Manage Networks via GUI in Hyperion

Written By Sebastian Sime (Super Administrator)

Updated at October 7th, 2026

Table of Contents

Viewing the Network Topology Managing vSwitches Managing Port Groups Managing Physical NICs Alternative Configuration Management

→ Applies to: SynetoOS 6.1.0 and above

Step 1. Login to SynetoOS GUI

https://<your_ip_address_or_hostname>

Viewing the Network Topology

Step 1. From the Network menu, click on Topology

Step 2. Review the topology

List format

Diagram format

Managing vSwitches

Step 1. From the Network menu, click on vSwitches

Step 2. Click + Add vSwitch to create a new vSwitch

Several configuration options are available depending on your needs.

Step 3. Enter the vSwitch name, then click Next

MTU (Maximum Transmission Unit) defines the largest packet size, in bytes, that the virtual switch can forward without fragmenting it.

Step 4. Configure the uplink, then click Next

Uplink type — defines how the virtual switch connects to your physical network hardware:

Isolated (no uplink): no physical network connection. VMs on this switch can talk to each other but not to anything outside the physical server.

Single NIC: routes traffic through exactly one physical network card.

Bond (NIC team): combines multiple physical network cards into a single logical channel for redundancy and increased bandwidth.

Bond mode (only if Bond is selected) — sets the strategy for managing traffic across the teamed network cards:

Active-backup: only one NIC is active at a time. If it fails, a backup NIC takes over automatically.

802.3ad (LACP): dynamically aggregates ports to increase bandwidth and balance traffic. Requires matching configuration on the physical network switch.

balance-xor: balances outbound traffic across the bonded NICs based on hashed MAC or IP addresses.

Members — lists the physical network cards installed on the server. Select the checkboxes for the cards you want to group into the bond:

Primary NIC: (only with Active-backup) the card that handles traffic by default before any failover occurs.

Step 5. Enter the Port group name, then click Next

Choose to Create a default VM port group now or later.

Managing Port Groups

Step 1. From the Network menu, click on Port groups

Step 2. Click + Add port group to create a new one

Multiple configuration options are available depending on your needs.

Step 3 (Optional). If you selected VM, complete with the required information, then click Next

Virtual switch: the vSwitch this port group will be created on.

Port group name: a name to identify this port group.

Type: VM (standard virtual machine traffic) or VMkernel (host-level services: ESXi management, vMotion, iSCSI/NFS storage, fault tolerance).

VLAN mode: Native (the vSwitch automatically strips/adds VLAN tags) or Access (locks the port group to a single VLAN; only devices on that VLAN can communicate with these VMs).

Step 4 (Optional). If you selected VMKernel, Create a VMkernel, complete with the required information, then click Next

Service tags — select which host-level services are permitted on this VMkernel interface:

Management: enables administrative access to the host.

Storage: dedicates the interface to network storage traffic (iSCSI, NFS, NVMe-oF).

Migration: enables vMotion traffic for live VM migration to another host.

Fault tolerance: used for logging and state synchronization between primary and secondary VMs.

VMkernel (IP method) — sets the IP configuration of the VMkernel interface:

Static: manually specify a fixed IP address, gateway, DNS, and search domains. Recommended for host-level stability.

DHCP: the host automatically requests network settings from a local DHCP server.

None: no IP routing stack is bound to the interface.