4
0

corosync.conf.example 3.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687
  1. # Please read the corosync.conf.5 manual page
  2. totem {
  3. version: 2
  4. # crypto_cipher and crypto_hash: Used for mutual node authentication.
  5. # If you choose to enable this, then do remember to create a shared
  6. # secret with "corosync-keygen".
  7. crypto_cipher: none
  8. crypto_hash: none
  9. # crypto_compat: 2.0|2.2 (default higher) can be used to change
  10. # on-wire crypto packet format. Unless performing some special
  11. # rolling upgrades from corosync < 2.2 to 2.2, to keep the cluster
  12. # running, do not touch this option. This option cannot be changed
  13. # at runtime.
  14. #crypto_compat: 2.2
  15. # interface: define at least one interface to communicate
  16. # over. If you define more than one interface stanza, you must
  17. # also set rrp_mode.
  18. interface {
  19. # Rings must be consecutively numbered, starting at 0.
  20. ringnumber: 0
  21. # This is normally the *network* address of the
  22. # interface to bind to. This ensures that you can use
  23. # identical instances of this configuration file
  24. # across all your cluster nodes, without having to
  25. # modify this option.
  26. bindnetaddr: 192.168.1.0
  27. # However, if you have multiple physical network
  28. # interfaces configured for the same subnet, then the
  29. # network address alone is not sufficient to identify
  30. # the interface Corosync should bind to. In that case,
  31. # configure the *host* address of the interface
  32. # instead:
  33. # bindnetaddr: 192.168.1.1
  34. # When selecting a multicast address, consider RFC
  35. # 2365 (which, among other things, specifies that
  36. # 239.255.x.x addresses are left to the discretion of
  37. # the network administrator). Do not reuse multicast
  38. # addresses across multiple Corosync clusters sharing
  39. # the same network.
  40. mcastaddr: 239.255.1.1
  41. # Corosync uses the port you specify here for UDP
  42. # messaging, and also the immediately preceding
  43. # port. Thus if you set this to 5405, Corosync sends
  44. # messages over UDP ports 5405 and 5404.
  45. mcastport: 5405
  46. # Time-to-live for cluster communication packets. The
  47. # number of hops (routers) that this ring will allow
  48. # itself to pass. Note that multicast routing must be
  49. # specifically enabled on most network routers.
  50. ttl: 1
  51. }
  52. }
  53. logging {
  54. # Log the source file and line where messages are being
  55. # generated. When in doubt, leave off. Potentially useful for
  56. # debugging.
  57. fileline: off
  58. # Log to standard error. When in doubt, set to no. Useful when
  59. # running in the foreground (when invoking "corosync -f")
  60. to_stderr: no
  61. # Log to a log file. When set to "no", the "logfile" option
  62. # must not be set.
  63. to_logfile: yes
  64. logfile: /var/log/cluster/corosync.log
  65. # Log to the system log daemon. When in doubt, set to yes.
  66. to_syslog: yes
  67. # Log debug messages (very verbose). When in doubt, leave off.
  68. debug: off
  69. # Log messages with time stamps. When in doubt, set to on
  70. # (unless you are only logging to syslog, where double
  71. # timestamps can be annoying).
  72. timestamp: on
  73. logger_subsys {
  74. subsys: QUORUM
  75. debug: off
  76. }
  77. }
  78. quorum {
  79. # Enable and configure quorum subsystem (default: off)
  80. # see also corosync.conf.5 and votequorum.5
  81. #provider: corosync_votequorum
  82. }