corosync.xml.example 3.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109
  1. <?xml version="1.0"?>
  2. <!--
  3. Please read the corosync.xml.5 and corosync.conf.5 manual page
  4. -->
  5. <corosync>
  6. <!--
  7. totem tag configures behavior of totem and interfaces.
  8. crypto_cipher and crypto_hash:
  9. Used for mutual node authentication. If you choose to
  10. enable this, then do remember to create a shared
  11. secret with "corosync-keygen".
  12. -->
  13. <totem version="2" crypto_cipher="none" crypto_hash="none">
  14. <!--
  15. interface tag to 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. Main parameters:
  19. ringnumber:
  20. Rings must be consecutively numbered, starting at 0.
  21. bindnetaddr:
  22. This is normally the *network* address of the
  23. interface to bind to. This ensures that you can use
  24. identical instances of this configuration file
  25. across all your cluster nodes, without having to
  26. modify this option.
  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: bindnetaddr="192.168.1.1"
  33. mcastaddr:
  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. mcastport:
  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 send
  44. messages over UDP ports 5405 and 5404.
  45. ttl:
  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. -->
  51. <interface ringnumber="0" bindnetaddr="192.168.1.0" mcastaddr="239.255.1.1"
  52. mcastport="5405" ttl="1" />
  53. </totem>
  54. <!--
  55. Logging tag for defining various logging options
  56. Main parameters:
  57. fileline:
  58. Log the source file and line where messages are being
  59. generated. When in doubt, leave off. Potentially useful for
  60. debugging.
  61. to_stderr:
  62. Log to standard error. When in doubt, set to no. Useful when
  63. running in the foreground (when invoking "corosync -f")
  64. to_logfile:
  65. logfile:
  66. Log to a log file. When set to "no", the "logfile" option
  67. must not be set.
  68. to_syslog:
  69. Log to the system log daemon. When in doubt, set to yes.
  70. debug:
  71. Log debug messages (very verbose). When in doubt, leave off.
  72. timestamp:
  73. Log messages with time stamps. When in doubt, set to on
  74. (unless you are only logging to syslog, where double
  75. timestamps can be annoying).
  76. -->
  77. <logging fileline="off" to_stderr="no" to_logfile="yes"
  78. logfile="/var/log/cluster/corosync.log" to_syslog="yes" debug="off"
  79. timestamp="on">
  80. <!--
  81. Logger susys tag is used to overwrite default settings for given
  82. subsys if needed.
  83. -->
  84. <logger_subsys subsys="QUORUM" debug="off" />
  85. </logging>
  86. </corosync>