Corosync 3 - add second ring

rengiared

Renowned Member
Sep 8, 2010
96
0
71
Austria
Hi,

since i have quite a few problems with corosync3 since the updates from the last weeks i tried to add a second ring but somehow the config i made was broken.
i think the problem is that the config i made would be for corosync2 and therefore i got errors like "no multicast port defined" on one server.

my actual corosync config is:

Code:
logging {
  debug: off
  to_syslog: yes
}

nodelist {
  node {
    name: jupiter
    nodeid: 3
    quorum_votes: 1
    ring0_addr: 10.50.30.3
  }
  node {
    name: odin
    nodeid: 1
    quorum_votes: 1
    ring0_addr: 10.50.30.1
  }
  node {
    name: zeus
    nodeid: 2
    quorum_votes: 1
    ring0_addr: 10.50.30.2
  }
}

quorum {
  provider: corosync_votequorum
}

totem {
  cluster_name: EPIC
  config_version: 3
  interface {
    bindnetaddr: 10.50.30.1
    ringnumber: 0
  }
  ip_version: ipv4
  secauth: on
  version: 2
}

and the config i tried was

Code:
logging {
  debug: off
  to_syslog: yes
}

nodelist {
  node {
    name: jupiter
    nodeid: 3
    quorum_votes: 1
    ring0_addr: 10.50.30.3
    ring1_addr: 172.16.18.3
  }
  node {
    name: odin
    nodeid: 1
    quorum_votes: 1
    ring0_addr: 10.50.30.1
    ring1_addr: 172.16.18.1
  }
  node {
    name: zeus
    nodeid: 2
    quorum_votes: 1
    ring0_addr: 10.50.30.2
    ring1_addr: 172.16.18.2
  }
}

quorum {
  provider: corosync_votequorum
}

totem {
  cluster_name: EPIC
  config_version: 3
  interface {
    bindnetaddr: 10.50.30.1
    ringnumber: 0
  }
  interface {
    bindnetaddr: 172.16.18.1
    ringnumber: 1
  }
  ip_version: ipv4
  secauth: on
  version: 2
}

what would be the correct way to implement a second ring for corosync3?
somehow i'm too blind to find a correct config or the correct way to implement it.

thanks

Code:
proxmox-ve: 6.0-2 (running kernel: 5.0.21-1-pve)
pve-manager: 6.0-7 (running version: 6.0-7/28984024)
pve-kernel-5.0: 6.0-7
pve-kernel-helper: 6.0-7
pve-kernel-4.15: 5.4-6
pve-kernel-5.0.21-1-pve: 5.0.21-2
pve-kernel-5.0.18-1-pve: 5.0.18-3
pve-kernel-5.0.15-1-pve: 5.0.15-1
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-14-pve: 4.15.18-39
ceph: 14.2.2-pve1
ceph-fuse: 14.2.2-pve1
corosync: 3.0.2-pve2
criu: 3.11-3
glusterfs-client: 5.5-3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.11-pve1
libpve-access-control: 6.0-2
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 6.0-4
libpve-guest-common-perl: 3.0-1
libpve-http-server-perl: 3.0-2
libpve-storage-perl: 6.0-8
libqb0: 1.0.5-1
lvm2: 2.03.02-pve3
lxc-pve: 3.1.0-64
lxcfs: 3.0.3-pve60
novnc-pve: 1.0.0-60
openvswitch-switch: 2.10.0+2018.08.28+git.8ca7c82b7d+ds1-12
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.0-7
pve-cluster: 6.0-7
pve-container: 3.0-7
pve-docs: 6.0-4
pve-edk2-firmware: 2.20190614-1
pve-firewall: 4.0-7
pve-firmware: 3.0-2
pve-ha-manager: 3.0-2
pve-i18n: 2.0-3
pve-qemu-kvm: 4.0.0-5
pve-xtermjs: 3.13.2-1
qemu-server: 6.0-7
smartmontools: 7.0-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.1-pve2
 

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!