Hello and thank you in advance for any assistance.
I am attempting to set up a 2 node cluster in an offline test environment and seem to be running into an issue with the command to create the cluster in the Separate Cluster Network Wiki page.
I am using two freshly installed nodes, running PVE 4, kernel 4.2.2-1, pve-cluster 4.0-22.
When I run the command:
pvecm create proxcluster -bindnet0_addr 10.10.10.251 -ring0_addr one-corosync
I get the following output:
Unknown option: bindnet0_addr
Unknown option: ring0_addr
400 unable to parse option
I believe I am following the wiki page to a T, have separate NICs connected to a simple dumb switch, hosts and interfaces files seem good.
I understand I have an older version of pve-cluster as the wiki states:
Since version 4.0-23 of the pve-cluster package we have built in support for creating the cluster with separate corosync ring(s) on own networks. If you're running a earlier version please update your system first.
Is this what is causing this?
I assume I should manually update this package and I should be good to go?
I am attempting to set up a 2 node cluster in an offline test environment and seem to be running into an issue with the command to create the cluster in the Separate Cluster Network Wiki page.
I am using two freshly installed nodes, running PVE 4, kernel 4.2.2-1, pve-cluster 4.0-22.
When I run the command:
pvecm create proxcluster -bindnet0_addr 10.10.10.251 -ring0_addr one-corosync
I get the following output:
Unknown option: bindnet0_addr
Unknown option: ring0_addr
400 unable to parse option
I believe I am following the wiki page to a T, have separate NICs connected to a simple dumb switch, hosts and interfaces files seem good.
I understand I have an older version of pve-cluster as the wiki states:
Since version 4.0-23 of the pve-cluster package we have built in support for creating the cluster with separate corosync ring(s) on own networks. If you're running a earlier version please update your system first.
Is this what is causing this?
I assume I should manually update this package and I should be good to go?
Last edited: