Search results

  1. K

    Beta VXLAN Issue

    One other thing too, is clicking on the "mynet" zone under each host tab freezes the Web UI. I'll be testing the VXLANs today and hopefully EVPN in the future.
  2. K

    Beta VXLAN Issue

    Missed me by 1 minute :p
  3. K

    Beta VXLAN Issue

    Found it! By echoing that line onto my interfaces file: echo "source /etc/network/interfaces.d/*" >> /etc/network/interfaces And reloading network from the main SDN tab, that made them available! Thanks for the help! I'm surprised it doesn't add that line by default though when it applies the...
  4. K

    Guest can ping Host, but not Gateway

    OK, next step: let's dig deeper. Try these commands: ping 192.168.1.1 arping -I vmbr0 192.168.1.1 tracepath 192.168.1.1 arp -a And let's see what those come back with
  5. K

    Beta VXLAN Issue

    root@pxmx01:~# cat /etc/pve/sdn/vnets.cfg vnet: vnet1 tag 500 zone mynet vlanaware 1 root@pxmx01:~# cat /etc/pve/sdn/zones.cfg vxlan: mynet peers 10.0.10.10, 10.0.10.11, 10.0.10.12 mtu 1450 root@pxmx01:~# cat /etc/network/interfaces # network interface...
  6. K

    Guest can ping Host, but not Gateway

    Is the Proxmox firewall enabled?
  7. K

    After Install - host cannot ping gateway or internet

    Also, might sound dumb, but is your router actually using 192.168.0.1?
  8. K

    After Install - host cannot ping gateway or internet

    Can you run a "tcpdump -i vmbr0 arp"? Also, is the firewall disabled?
  9. K

    Beta VXLAN Issue

    Hi Guys, So, I'm attempting to roll out the new GUI SDN at my home Prox lab. Currently, when I create a VXLAN Zone "mynet" and a VNet "vnet1", and attempt to apply the config, I get an error on all nodes, picture attached. I checked in Syslog and all I can really see is an entry of...
  10. K

    VE Guest VM Unable to Discard

    That actually pointed me in the right direction! I stopped the VM, detached the disk from it, and found the disk itself was a VirtIO-Block device. I changed it to SCSI and re-attached it to the VM, so my current config is a VirtIO-SCSI controller with a SCSI disk, and fstrim/discard now seems to...
  11. K

    VE Guest VM Unable to Discard

    Hi everyone, I have a guest VM which seems to be unable to utilize the discard option to free up block space. The guest VM is a Ubuntu 18.04 LTS OS with an ext4 root FS. Underlying storage is Ceph on Bluestore OSDs. VM storage controller is VirtIO-SCSI, with just a standard 1TB disk attached to...
  12. K

    Ceph Placement Groups

    Hi everyone, when creating pools, what size pg_num do you generally shoot for? We have a 16 node cluster set up, with 48 disks stretched across the cluster. I believe we need between 512-1024 PG's, but what does everyone else go with? Just looking for general suggestions and past experience.
  13. K

    [SOLVED] Can't Use NFS Share

    I've self-resolved! In FreeNAS, under the share settings, I experimentally set the mapall users setting to root, which makes anyone using that directory access it with root permissions. The issue then went away, giving me full access to the share. To further lock down the security, I created a...
  14. K

    [SOLVED] Can't Use NFS Share

    So, after getting this error "mkdir /mnt/nfs-backup01/images: Permission denied at /usr/share/perl5/PVE/Storage/Plugin.pm line 954. (500)" when trying to add my NFS share on FreeNAS for backups, I manually added the server via "pvesm add nfs backup01 --server=10.x.x.x --export=/mnt/pool01...
  15. K

    [SOLVED] Adding Node to Cluster Makes Other Nodes Un-pingable

    I ended up reinstalling the cluster, it was a DNS issue. Bleh.
  16. K

    [SOLVED] Adding Node to Cluster Makes Other Nodes Un-pingable

    So, now it poisoned node1 and I had to remove that as well. It was spitting a "could not resolve node1/node12" error. I tried re-installing node12 and totally changing the IP address, incremented the hostname up to node18, and added again, with the same results. So, I removed 1, and here we are...
  17. K

    [SOLVED] Adding Node to Cluster Makes Other Nodes Un-pingable

    So, as far as their hostnames go, the schema is basically nodexx.yyyyyyyyy.com None of them should be the same. All of them have been installed with the latest 5.4 .iso, so their PVE version is all: proxmox-ve: 5.4-1 (running kernel: 4.15.18-12-pve) pve-manager: 5.4-3 (running version...
  18. K

    [SOLVED] Adding Node to Cluster Makes Other Nodes Un-pingable

    Thanks oguz! I'm guessing you mean in the currently active nodes, not node12?
  19. K

    [SOLVED] Adding Node to Cluster Makes Other Nodes Un-pingable

    Hi All. I'm trying to add a 16th node to our cluster, but when I try to add it, I get 1. locked out of the 16th node, and 2. It causes several other members of the cluster to become unpingable, as well as ALL nodes in the cluster showing as beig in Standalone mode, even though you can see them...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!