This message was deleted.

I’m only using a single server

@rapid-balloon-54181 you can follow the following docs for such a configuration https://docs.harvesterhci.io/v1.4/networking/index/ https://docs.harvesterhci.io/v1.4/networking/harvester-network/ https://docs.harvesterhci.io/v1.4/vm/index 1.Create a cluster network and network config (separate nic)or use a default mgmt cluster 2.step 1 will create a user defined switch ( -bo, -br) or it will be mgmt-br,mgmt-bo if you are using mgmt cluster 3.create a vlan vm network (different vlans with vlan id on the user defined cluster network or mgmt cluster) 4.create a vm and attach the vlan network created in step 3 to the vm 5.step 4 will create veth interfaces on the harvester host which will all be connected to the switch created. 6.communication between the vms happen via this switch which takes care of isolating the traffic between the vlans

I have reviewed the documentation but the terms were foreign to me and not defined. Perhaps it’s because I don’t have much of any container experience Thank you for the directions. Trying this out now

sure please try out in above order of steps

When creating a network config, it is requiring that I add a NIC to the config. For one of my networks, I don’t want it to have a NIC. How do I do that?

you can use the default mgmt cluster instead of creating a new cluster and network config

Will that be isolated from the host as well as from the physical NICs?

No, you need a physical nic on top of which you build your virtual networks.you could use either mgmt cluster which is already attached to a physical nic during harvester installation or you need to create a user cluster network selecting a separate physical nic of your own and vms in vlan networks.By this was the traffic on the mgmt is isolated from user defined traffic on vms

So just to be clear, you can’t just create an isolated switch with no connection to the physical NIC or host, every switch/network will have to have a NIC?

yes, the virtual switch/bridge will have an underlying physical nic from the node/host