Proxmox primary cluster NIC interface and experimenting with thunderbolt networking

[Giovanni]

Looking for some guidance, on a fresh install when adding the new node to the cluster there is a "Link" selection box, in which configuration file is this setting stored and how do I change it?

For context:
- I would like to setup my cluster node using the native RJ45 NIC initially. Then experiment with peer-to-peer between 2 nodes using thunderbolt network for storage traffic

If I wanted proxmox to always use thunderbolt 25Gbps network for all cluster to cluster communication with this one specific node (point-to-point) so that all "migrate" transfers occur over thunderbolt (25gbps) how would I do it?

Also is it possible to have RJ45 as "failover only" uplink between these 2 thunderbolt nodes?

Note I do wish to keep RJ45 to always be the "management" vlan for web UI - 192.168.10.0/24 range. The Thunderbolt network for peer-to-peer zfs replication and such will likely be setup in a different IPv4 address range like 10.10.0.x or something.

 

[KevinS]

Hi Giovanni,

the Corosync Configuration file can be found int /etc/pve/corosync conf as you can see in the documentation[0]

Using a different network for guest migration is a good idea and also recommended as you can see in the documentation[1]

The corosync network should be kept as clean as possible since any introduced latency and jitter will lead to problems [2], accessing the Web UI should be ok but I assume this is all happening on either a router or switch with all different kind of traffic, so this could still lead to issues.

Ideally you would get another RJ45 NIC and use one for WAN/web GUI access/migration backup and the other one exclusively for corosync traffic

[0] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_corosync_configuration
[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_guest_migration
[2] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_cluster_network_requirements