This article explains the key differences in network configuration when using Syneto Hyperion or VMware ESXi as the virtualization platform on Syneto HYPER Series devices.

Syneto Hyperion architecture

Overview

In this example, SynetoOS runs Syneto Hyperion, a KVM-based hypervisor. Virtual machines are created and managed directly from SynetoOS.

Network
 

• External Network (green) – 192.168.1.0/24:
  
  
  • The physical interface em0 connects SynetoOS to the external switch;
  • VMs use a bridged network (vSwitch0) to reach the external network.
     
• NAT Network (blue area):
  
  
  • A NAT-based internal network is available for isolated or controlled access;
  • VMs connect via veth0 ↔ veth1.
     
• Internal Management Network (orange) – 172.16.254.0/24:
  
  
  • Same purpose as in ESXi setup: internal services and communication.

Storage
 

• Hyperion uses native SynetoOS storage (no NFS);
• VMs (e.g., VM1, VM2, VM3) directly use disk volumes from the SynetoOS-managed pool.
   

VMware ESXi architecture

Overview

In this example, Syneto HYPER Series runs VMware ESXi as the hypervisor. Virtual machines are managed via VMware ESXi web interface or vCenter.

Network
 

• External Network (green) – 192.168.1.0/24:
  
  
  • Used for external access by SynetoOS, ESXi host and virtual machines;
  • vmnic0 handles Management Network traffic (VMkernel);
  • VM network connects via vSwitch0.
     
• Internal Management Network (orange) – 172.16.254.0/24:
  
  
  • Dedicated to communication between SynetoOS and Syneto HC internal services;
  • vSwitch1 bridges ens192 and ens224 to this network.

Storage
 

• SynetoOS exports NFS shares (vm1 volume, vm2 volume, images volume) to ESXi;
• ESXi mounts these as datastores, where VMs (e.g. VM1, VM2) are stored and run.
   

Summary comparison