Is there a way to use the secondary network in a cluster for command (ssh) communication?
I have two interfaces on all hosts in a cluster: a local 192.168.x.x, and a public with public ips, set as ring0 and ring1, respectively in corosync. Due to a switch failure, some of the interfaces in ring0 are not working on some hosts.

If I try to migrate from such a host, qm tries to ssh using the failed network, even though I set the migration network to be the ring1 one. For example:

qm migrate 520 pve4 --online
ssh: connect to host 192.168.0.23 port 22: No route to host
command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve4' -o 'UserKnownHostsFile=/etc/pve/nodes/pve4/ssh_known_hosts' -o 'GlobalKnownHostsFile=none' root@192.168.0.23 pvecm mtunnel -migration_network xxx.xxx.xxx.xxx/yy -get_migration_ip' failed: exit code 255

I already set knet_link_priority in corosync, but that does not fix this problem.

How can I coax the system to use the ring1 address for the target host? Preferably without editing the primary ip address for any hosts.

that's pretty much correct, regular communication (SSH or API proxying) will happen on the IP that the hostname of the node resolves to. only the actual data streams will use the migration network (and the IP to connect to is discovered using the regular network).

for some parts, you also need to restart pve-cluster, since the IP is resolved at startup there and broadcast to the rest of the cluster