Using Grafana connected to InfluxDB (nice charts)
for outbound trafic :
SELECT non_negative_derivative(mean("netout"), 10s) FROM "system" WHERE ("nodename" =~ /^proxmox1$/ AND "object" = 'qemu') AND time >= now() - 3h GROUP BY time(10s), "host" fill(null)
Sorry, I've not been clear enough
In the Proxmox Admin Panel, when you click on the left column on the name of your server, then you click System then Network
In the table, is there a line category showind a bridge ?
your gateway must be in the same network
if your conf is 192.168.1.3 / 255.255.255.0 that means that :
- your network begin with 192.168.1.0 and go to 192.168.1.255 (256 IP)
- your network name is 192.168.1.0 (and you can't use that IP for a host)
- the broadcats address of your network is...
First choice : RAM bar
Second : PSU
If IPMI is not accessible when the server freeze, big chance this is a hardware problem as IPMI is OS independant
Have experienced several times that kind of trouble, always RAM ...
With Opensource solutions, you know what is done.
With proprietary software, you don't know what runs inside de box ...
So you are not sure some data dont go away without you authorization
In the past, creating clusters was a little more "complicated"
I always check the name/ip resolution and SSH connection BEFORE starting the cluster creation process.
With that, it never fails for me
I'm only sharing practical experience
Regards
The match between VMware / HyperV / Proxmox is still very active. I recently made a public talk on that.
My purpose was not to tell Proxmox is better because its opensource ... It's better because it can do often more, sometimes equal, rarely less.
Here's my arguments :
- Proxmox born in 2008...
ZFS/iSCSI allows snapshot ... Not simple iSCSI ... Just take care that ZFS use 1 GB of RAM by TB of disk ...
Don't see any diffrence from the VM point of vue as they don't "use" iSCSI but the storage you setup in your VMs.
But for Windows Server, you will have to setup VirtIO virtual hardware...
Hello
Go into your Bios settings (usually hit ESC or SUPPR when computer starts before it starts to load OS) and see what is detected by your Bios as storage and what is your boot order.
Maybe you can put it in a shell script :
nano networkcard.sh
and put into it
ethtool -K eno1 gso off gro off tso off
Save and make it runnable
chmod 777 networkcard.sh
Then add it in the root crontab (crontab -e when you're root) with "@reboot" for frequency
Like :
@reboot root /root/networkcard.sh
create ZFS pool on both the node with the same name
then setup replication
Procedure has been detailed yet in another post :
https://forum.proxmox.com/threads/step-by-step-zfs-storage-replication.52791/
Enjoy Proxmox !
Regards
I was thinking I was clear ... Sorry.
The benefits is that iSCSI is quicker than NFS for the reason I tried to explain.
In the normal life of the cluster, I don't see any difference between iSCSI and NFS.
Maybe your question is about iSCSI versus ZFS/iSCSI and not iSCSI versus NFS ?
Regards
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.