claster wrong NIC

ooko

Renowned Member
Mar 20, 2015
7
1
68
Hello
I have problem with claster on proxmox 6.
My claster config /etc/pve/corosync.conf
Code:
logging {
  debug: off
  to_syslog: yes
}

nodelist {
  node {
    name: pv1
    nodeid: 2
    quorum_votes: 1
    ring0_addr: 192.168.233.104
  }
  node {
    name: pv2
    nodeid: 1
    quorum_votes: 1
    ring0_addr: 192.168.233.102
  }
}

quorum {
  provider: corosync_votequorum
}

totem {
  cluster_name: cl1
  config_version: 2
  interface {
    linknumber: 0
  }
  ip_version: ipv4-6
  secauth: on
  version: 2
}
In /etc/hosts I have:
192.168.233.104 pv1.mydomain.com pv1
192.168.233.102 pv2.mydomain.com pv2

So replication vm should be made by NIC associateed to ip 192.168.233.104 and 192.168.233.102, but isnot, tpcdump shows that there is traffic beetwen nics connected to ISP on public ip.
How can i force proxmox to use lan nic for replication ?
 
Hi,
you can add the following line:
Code:
migration: <secure|insecure>, network=<CIDR>
to '/etc/pve/datacenter.cfg'. See here for the specifics. Then PVE will use that network for migration and replication. But it is not recommended to use the cluster network for this, since corosync requires low latency.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!