Example C.3. Corosync 1.x configuration file for a cluster with all nodes on the 192.0.2.0/24
network
totem { version: 2 secauth: off threads: 0 interface { ringnumber: 0 bindnetaddr: 192.0.2.0 mcastaddr: 239.255.1.1 mcastport: 1234 } } logging { fileline: off to_syslog: yes syslog_facility: daemon } amf { mode: disabled }
totem
section contains the protocol version and options as with 2.x. However, nodes are also listed here, in the interface
section. The bindnetaddr
option is usually the network address, thus allowing the same configuration file to be used on all nodes. IPv4 or IPv6 addresses can be used with corosync.
amf
section refers to the Availability Management Framework and is not covered in this document.
Example C.4. Corosync 1._x_configuration fragment to enable Pacemaker plugin
aisexec { user: root group: root } service { name: pacemaker ver: 0 }
lrmd
in particular) have sufficient privileges to perform the actions requested of it. After all, a cluster manager that can’t add an IP address or start apache is of little use.