1.3. Support in Pacemaker Versions

It is recommended to run Pacemaker 1.1.12 or later when using pacemaker_remote due to important bug fixes. An overview of changes in pacemaker_remote capability by version (aside from bug fixes, which are included in every version):

1.1.18

Support for unfencing remote nodes (useful with "fabric fencing" agents)
Guest nodes are now probed for resource status before starting resources

1.1.16

Support for watchdog-based fencing (sbd) on remote nodes

1.1.15

If pacemaker_remote is stopped on an active node, it will wait for the cluster to migrate all resources off before exiting, rather than exit immediately and get fenced.

1.1.14

Resources that create guest nodes can be included in groups
reconnect_interval option for remote nodes

1.1.13

Support for maintenance mode
Remote nodes can recover without being fenced when the cluster node hosting their connection fails
#kind built-in node attribute for use with rules

1.1.12

Support for permanent node attributes
Support for migration

1.1.11

Support for IPv6
Support for remote nodes
Support for transient node attributes
Support for clusters with mixed endian architectures

1.1.10

remote-connect-timeout for guest nodes

1.1.9

Initial version to include pacemaker_remote
Limited to guest nodes in KVM/LXC environments using only IPv4; all nodes' architectures must have same endianness