Search results

I'm new with VLAN and there is one thing I don't understand in the Proxmox documentation about creating the managment VLAN: Network Configuration - Proxmox VE From what I understand, the purpose of the management VLAN is to separate the subnet used to access the admin interface from the...

Can anyone give me some tips to optimize this setup? TIA

Can always be a good practice to rename all NICs? (using /etc/systemd/network/ as I have to do in this case for one of the three)

The server has 3 network interfaces: 2 onboard and 1 on PCI Express slot. The network interface that is not renamed is one of those on the motherboard. Based on Consistent Network Device Naming a NIC is not renamed if "the firmware information is not valid". But how can this be true only for...

This morning I installed Proxmox 7 on a server that was previously running PVE 6.x. I removed the RAID controller hardware from the motherboard and then used ZFS (RAID 1) by installing everything from scratch. The installation was successful, but two problems emerged after the reboot: 1) After...

I made some tests and it seem to me that this is the minimum configuration to have the cluster working on 192.168.7.0 subnet and administration services (ssh, web interface) working on 192.168.1.0 subnet: (and I don't really understand what is the cluster_network alias mentioned in the...

Thanks again!

Thanks ph0x! Related to cluster subnet: the PVE firewall documentation says: " Standard IP Alias local_network ... The firewall automatically sets up rules to allow everything needed for cluster communication (corosync, API, SSH) using this alias. " But in my case the cluster subnet...

In my test environment I build a small PVE cluster: 2 nodes, both with 4 NICs connected to: NIC1: 192.168.1.0 LAN NIC2: 192.168.5.0 subnet dedicated to VMs backup traffic NIC3: 192.168.6.0 subnet dedicated to PVE VMs NFS storage (a NAS share) NIC4: 192.168.7.0 subnet dedicated to PVE cluster I...

Thanks a lot @t.lamprecht

My PVE server start faster than NAS used as remote storage, so VMs cannot start automaticaly. Is there a way to solve this? P.S.: I read some threads about this issue, one of this, dated 2016, with a smart (IMVHO) solution, but it seems to me that this feature is not available:

Ok ... I forget to run: update-initramfs -u

Everything went fine, but ... One of the two PVE servers has NIC names sets in /etc/udev/rules.d/70-persistent-net.rules. So I add a row for the new NIC: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*"...

Yes, a lot! Now I'm going to do the job with more confidence knowing where problems can arise. Thanks.

I have a 2 sever PVE cluster. Both have 3 NIC: eth0 for corosync, eth1 for VMs storage and for backup traffic and eth2 for LAN connection. I want to add one more NIC to separate storage and backup traffic but one server doesn't has an available PCI slot. So I'm planin to buy a new PCI with 2...