Recent content by AndyBar

I do not intend to change the dns names. Is there a procedure about changing the management IPs ? So far I can think of the following e.g. 1. Migrate all VMs off the host on which IP is to be changed 2. stop all proxmox services 3. Edit corosync.conf with new IP 4. Edit Interfaces config...

Is there a procedure about changing the management IPs ? So far I can think of the following e.g. 1. Migrate all VMs off the host on which IP is to be changed 2. stop all proxmox services 3. Edit corosync.conf with new IP 4. Edit Interfaces config file - update new IP for the interface 5...

Thank you for the prompt response Udo. Cluster network and management network are running on the same subnet. I am using ovs + bond nics. Switch ports are in trunk mode where the new VLAN is also specified. What happends with certificates (if any) or the ssh keys between the hosts if the IP...

Hello Proxmox community/Support, I am in the middle of changing the management subnet, due to our network topology limitations. I would need a detailed procedure/best practice document on how to seamlessly, without breaking the cluster change the management IPs of each NODE (3 NODES in the...

Thanks Klaus

Hi All, I know that that Proxmox needs 3 nodes to have a Quorum. Does this mean that I need a minimum of 4-node cluster in order to have a proper maintenance (1 host at at time) ?

Hi Support, Is this a bug or a limitation ? it seems that I can clone 1 VM at a time off the same tempate... Clone failed: can't deactivate LV '/dev/template/vm-115-disk-1': Logical volume template/vm-115-disk-1 in use. Logical volume "vm-1020-disk-1" successfully removed TASK ERROR: clone...

Thank you Wolfgang! I will try to make a change on one of the HOSTs and test your config. However the initial problem is still not resolved.... The fact that I am using the OVS for the backend should not make LVs disappear. Unless my OVS config is wrong... Or Maybe PRoxmox does not like the...

HEllo Wolfgang, Thank you for your reply. Here is the output of the command: root@pve2:/etc/lvm/archive# pveversion -v proxmox-ve: 5.1-41 (running kernel: 4.13.13-6-pve) pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4) pve-kernel-4.13.13-6-pve: 4.13.13-41 pve-kernel-4.10.17-2-pve...

Given Configuration: 4 node cluster Proxmox: PVE0 : pve-manager/5.1-46/ae8241d4 PVE1 : pve-manager/5.1-46/ae8241d4 PVE2 : pve-manager/5.1-46/ae8241d4 PVE3 : pve-manager/5.0-30/5ab26bc Networking: Each HOST has 4 NICs 2 for Backend to SAN Switch (LACP 802.3ad) - one IP per HOST (no need for...