After the firewall of the Pve cluster is turned on, some default policies conflict with Oracle Rac communication. Is there any way to adjust some default policies while the firewall is turned on? After the iptables - F operation, the default policy will be regenerated. Do you have any good ideas?
Hello everyone, I have a 6-node PVe7 cluster and have deployed 3-node Oracle Rac services on three of them.
When the PVE firewall function is not enabled, the network between nodes in the Oracle Rac cluster operates normally.
After a few minutes of activation, the network of each node in the...
I have encountered this problem for a long time, and I can’t remember which PVE version it started from. This phenomenon still exists after upgrading to the latest 7.1. I remember that replacing E1000 with VirtIO network card did not solve it. I wonder if the latest stable 208 driver is now It...
After upgrading PVE6 to 7, now you can choose to stop, suspend and snapshot in the backup options. I will observe it for a few days. Thank you for your help.
There is no incremental option when configuring the backup task. I observed the time and log of each task executed by the VM, and found that the daily backup time is basically the same as the first backup. There are writes in the log that are repeatedly used but the transmission time is still...
The speed of the 10G fiber optic network card used to connect to the LINUX VM through the iperf test is basically 10G, and the test of the WIN VM on the same node is 2-4G. How to adjust the configuration of the windows VM to make the network bandwidth normal?
The PCI pass-through FC card in my two nodes is not working properly now, and it will not work properly after restoring to 5.3.13-1. Is there any configuration that needs to be adjusted?
The same problem occurred during the previous upgrade of 5.3.13-2. After reducing the pve of the two pass-through node machines to 5.3.13-1, the database speed in the VM returned to normal.
After upgrading to 5.3.18-1 this time, I have reduced the kernel to 5.3.13-1. The problem remains...
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.