This message was deleted.
# harvester
a
This message was deleted.
h
I have made sure I am going through the correct network. I have the VLAN id set to 1 since I am not tagging. The VMs are running CentOS-9 Stream for now, just trying to get the network going before I move forward. The fact that they can ping each other leads me to my Harvester setup but it seems to be pretty limited as far as network config goes.
b
Are they on the MGT network, or did you add a network config for the boxes?
h
I added a network to the box. Only one hypervisor right now, 10 more waiting for me to get this going.
b
Riiiight, but maybe this is something I don't fully understand then.
So there's this with the Cluster Networks:
Then there are VM Networks.
iirc you have the primary backplane network on your default nic (let's call it eth0 ), then you can have other networks (eth1) in there too.
You have to still create the Cluster Network for that untagged traffic, but you'll need to create VMNetwork for it as well to extend to the VMs.
But if you have more than one network trunked in on that location, I think you still need to specifiy the actual VLAN id.
but I could be wrong
But by default I think the mgmt Cluster network and VM networks are what vms can default to, and maybe it shares an IP range but isn't actually on the same network?
h
I just delete the VMs and redeployed, and the only change I made was the device type, i made it e1000 and everything is working this time around..
*deleted
b
¯\_(ツ)_/¯
h
right..
b
yay technology
I will add that everything I said is a huge caveat and your setup might totally differ.
Congrats on dodging the v-tax though!
h
thanks again for the help though