Search results

don't use wal/db disk on separated drive, simply use your enterprise ssd as osd with wal/db disk inside

ah ok ! ^_^ for the restart, I really don't known (maybe it's an option of fortigate side), but you can use "/usr/lib/frr/frr-reload.py /etc/frr/frr.conf --reload" to reload config without restarting the frr process

(just to be sure, your frr.conf is on fortigate ? forgate use frr ? )

you need to announce a default type5 route from your fortigate, and it should already by done with your address-family l2vpn evpn default-originate ipv4 default-originate ipv6 exit-address-family "neighbor VTEP activate" need to be in "address-family l2vpn evpn", like in your config...

this message looks strange. what is the content of /etc/frr/daemons ?

what is your nvme model ? seem unrelated, icmp is network, slow storage can't impact it. but slow network between the osd could impact io. (do you have tried some icmp test between your proxmox nodes directly ?) should be investigated

you can use " qm disk import <vmid> yourexportedfile.qcow2 <targetstorage> --format raw|qcow2", it'll import the disk, do the format converstion and add the disk to vm configuration .

mmm, both ceph-mon && ceph-mgr crashing is really strange. I'm not aware of a ceph bug in 18.2.7. maybe ask to the ceph mailing list, but for me, it's look like an hardware problem (ram or maybe cpu)

A vnet in sdn is a bridge, configured at datacenter level then deployed locally on each host. That's why it's the same permission name.

maybe you have your proxmox host ip on a specific vlan ? (eth.X) , and vm on a non-vlanware bridge with same vlan ?

@tuxis Are you looking for speakers ? Maybe I could make a talk on my current work on SAN snapshot support. (I have already done a conference in French, slides are almost ready, I just need to translate them to English)

services restart occur on logrotate, but they are no impact on the vms. (the "server" in the log, is the service, not the host) /etc/logrotate.d/pve /var/log/pveproxy/access.log { rotate 7 daily missingok compress delaycompress notifempty...

go to the network zone on the left tree, then add permission on the whole zone or on a specific bridge/vlan

you need to add PVESDNUser role to your bridge

you need HA, if you want to auto restart vms of a dead node to another node. you can install corosync qdevice on your truenas as 3rd node. https://pve.proxmox.com/wiki/Cluster_Manager#_corosync_external_vote_support

no, qemu can't emulate missing cpu flags. (vm will not start if you choose a virtual cpu model newer than your physical cpu model)

you need to enable vlan aware on your vnet (in advanced options)

This is the way.

host ip is in the same subnet and same vlan than the vm ?

please test with pve8 && recent qemu, I remember than some iothreads crash has been fixed since. (and pve7 is EOL anyway)