Search results

You can either set it up in each interfaces file on each node or you can use Proxmox VE SDN. PVE's SDN is pretty sweet. That would be my recommended approach as it managed from the web GUI at the datacenter level.

Thanks for the additional information. Ceph is remarkably resilient. I have not seen it get corrupted. I am not saying it cannot; I have not seen it. If you can, get redundant switches for your high-speed links. There are two approaches you can take. #1 Best Two switches that support MLAG...

Are any of you still experiencing this issue? We recently investigated something that sounds very similar—a segmentation fault in the OSDs. It happens when: fast_shutdown is enabled (it is enabled by default) BlueStore is using non-rotational drives (i.e. flash storage) OSD is being...

You have posted in the wrong forum. This forum is the Proxmox Datacenter Manager (PDM). You want to post in the Proxmox VE (PVE) forum. You can do that here: https://forum.proxmox.com/forums/proxmox-ve-installation-and-configuration.16/ Also, your issue looks like SMB permissions on your...

You have not provided enough information to assist you. Please post your PVE host network configuration and your VM's configuration. Please also include the network ranges you are using. To get your PVE network configuration: cat /etc/network/interfaces To get your VM configuration from the...

What kind of failover are you looking for? PVE node management? Corosync? Guest traffic? There are several different scenarios for failover. More information about your current network configuration and the failure you are trying to mitigate would be helpful.

Not sure it meets your criteria but the Turnkey Linux file server has WebDAV built in. Super easy to set the LXC up.

Thank you for sharing the contents of those files. At first glance, it seems like it should be working. Please try changing: net1: virtio=BC:24:11:94:E2:F2,bridge=VLAN110,mtu=1 To the following. Bridge to vmbr1 and add the tag for VLAN 110: net1...

Please post the contents of the following files: /etc/pve/qemu-server/<VMID_of_VM_needing_second_NIC>.conf /etc/network/interfaces /etc/network/interfaces.d/sdn

It looks good -- the best way to know is to implement it. :) Your VLAN102 would need to arrive at your PVE host tagged. Out of curiosity, why OVS? Unless you need very specific features, you are making your life more complicated. We always used to deploy Open vSwitch but have reverted since...

No. Yes. You create the ZFS pool and add it as a storage location in PVE. Then, you provision one or more disks to the guest (VM or LXC). The guest will use the provisioned disks very much like a physical disk on a physical server. The guest will not see ZFS; instead, it will see block...

You have not missed it. You will need to do that from the CLI.

No. Only IP addresses for your PVE host should be on those interfaces. Any IP addresses on those interfaces will be used by the PVE host.

@andrew-transparent good stuff! @crankshaft We use pfSense, not OPNsense. It's similar but not exactly the same. OVH has published new (updated?) instructions which may be helpful to you...

Hello I am going to assume the following: You are using OVHcloud (it looks like it is based on the information you provided). The IP address for your server is 1XX.235.225.170/32 The IP address for your OPNsense instance in PVE is 1XX.99.84.229/32 Your OPNsense IP address is an OVH "Additional...

They might. I am not familiar with these processors' differences but adjusting the VM's CPU type should get you there. When provisioning the CPU, do you set the type to host? If so, try using one of the EPYC-Rome-* types (older models). If those do not work, the x86-64-v2-AES should...

You indicated your PVE server has two NICs, but the interfaces file only shows one. Your vmbr1 shows an interface that is not in your interfaces file. I would expect to see a stanza that looks like this: iface enp42s0 inet manual You have an IP address specified twice for your PVE server. You...

Your virtual router will be your gateway on 10.60.3.0/24. The traffic from your PVE subnet will go to the IP address on your virtual router to be routed to your corporate network. ens18 is not working in your configuration as you expect. You indicated that you want your traffic from the...

Okay. Thanks. That helps to provide a clearer picture. My understanding from what you have provided: NICs ens1f0 - 1G - unassigned ens1f1 - 1G - connected to the corporate network enp3s0f0 - 10G - unassigned enp3s0f1 - 10G - unassigned Networks 192.168.28.0/24 - Corporate network...

Thank you for sharing this. You indicated you have four physical network interfaces on your server. I assume these are the ports: ens1f1 enp3s0f0 enp3s0f1 ens1f0 It also appears that you have these subnets: 100.60.3.0/24 - Enterprise network? PVE management network? 100.10.10.0/24 - not sure...