Core group protocol versions

Core group members interact with each other through a variety of protocols such as the discovery protocol, the failure detection protocol, and the view synchrony protocol. Each of these protocols define a set of formatted messages that core group members exchange according to a common algorithm.

New protocol versions are added to the product if new messages, or new algorithms are required to support new product features, or to improve core group performance. Because the new messages, or new algorithm might not be compatible with the existing messages or algorithm, a new protocol might not be able to interoperate with the old version of the protocol.

There are two major categories or groups of protocols.

The protocol version settings for each of these two categories are independent of each other.

Whenever a new protocol version is added to the product:

When to select a new core group protocol version

Core group protocol versions are always cumulative. Any functional enhancement that is provided in a previous protocol, is included in any subsequent protocols. It is recommended that you always use the latest protocol version whenever possible. But, before configuring the members of a core group to use a new protocol version, you must make sure that all of the core group members are running at a WebSphere® Application Server code level (VRM) that is equal to or greater than the new protocol version.

Avoid trouble: You do not have to restart the core group members when you move from an older protocol version to a newer protocol version. However, you must restart all of the core group members if you move from a newer protocol version to an older protocol version.gotcha

Determining which protocol version to use

Best practice: It is recommended that you always use the newest protocol version whenever possible. This practice is especially critical for large topologies because most of the recent protocol changes include scalability improvements. However, before configuring the members of a core group to use a new protocol version, you must verify that all of the core group members are running at a product code level (VRM) that is equal to or greater than the VRM in which the desired protocol version was added to the product. For example:bprac

Supported core group protocol version IDs

Deprecated feature: Wire format protocol versions 6.0.0 and 6.0.2.9 are deprecated. Whenever possible you should use a newer protocol version.depfeat
Table 1. Supported wire format protocol version IDs. The protocol version ID indicates the first version, release, and modification level in which that version is included. The following table lists the supported wire format protocol version IDs.
Version ID Required Minimum product Level Description
6.0.0 Any This protocol version is the original or base version. All versions of the high availability manager can use this protocol. If you do not specify a particular wire format protocol version, the high availability manager uses this version.
6.0.2.9 6.0.2.9 for Version 6.0.2, 6.1.0.0 for Version 6.1, 7.0.0.0 for Version 7.0. This protocol version was included in the 6.0.2.9 service pack, and in Versions 6.1, and 7.0 of the product to facilitate core group bridge scalability. This version is recommended for large topologies that contain multiple core groups and core group bridges as part of their configuration.
6.1.0 6.1.0.0 for Version 6.1, 7.0.0.0 for Version 7.0 This protocol version was included in Versions 6.1, and 7.0 of the product. This version adds core group scalability improvements, and more support for large topologies.



Related concepts
Core groups (high availability domains)
Related tasks
Selecting the version of a core group protocol
Concept topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 5:30:17 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=crun_ha_protocol_ver
File name: crun_ha_protocol_ver.html