+

Search Tips   |   Advanced Search

Core group custom properties


Use these custom properties for advanced configurations for core groups.

To configure a custom property, on the indicated Custom properties page, complete one of the following actions:

IBM_CS_DATASTACK_MEG

Use this custom property to eliminate a condition that is reported by a message that is displayed repeatedly in the SystemOut.log file.

Deprecated feature: This custom property is deprecated. Do not use this custom property unless we are running in a mixed cell environment that includes at least one core groups that contains a mixture of V 7.0 and V6.x processes.depfeat

If running in a mixed cell environment, and we have core groups that contain a mixture of V7.0 and V 6.x processes, continue to use the IBM_CS_DATASTACK_MEG core group custom property to change how frequently the Discovery Protocol attempts to open a new network

We might see a message, similar to the following message, repeated multiple times in SystemOut.log: 

[9/24/04 13:28:19:497 CDT] 00000013 VSync         W    DCSV2005W: DCS Stack DefaultAccessPointGroup.P at Member 172.16.1.86:9353:  The amount of memory available for synchronization is low. The configured memory  size is 418816 bytes. Currently used memory size is 420307 bytes.

If the member IP address is in the format of a dotted decimal IP address and port, we can eliminate these messages by increasing the amount of memory that is allocated to the core stack used for core group communication. Increase the value of this property until you no longer see the message in your SystemOut.log file. Because the memory is dynamically allocated, setting a larger stack size than we need does not cause memory problems.

We can also set this custom property:

  • On the core group bridge interface that contains the particular core group member that is in the messages.

  • On the access point group or the core group access point for the particular core group member that is in the messages.

See Core group bridge custom properties for more information about how to set the property at those levels.


Table 1. Units and default

Units megabytes
Default 5

To set a value for this custom property, in the admin console ...

Servers > Core Groups > Core group settings > core_group_name. Then, under Additional Properties, click Custom properties .

IBM_CS_FD_CONSECUTIVE_MISSED

This custom property is used to specify the consecutive number of heartbeats that must be missed before the core group member is considered failed.

Deprecated feature: This custom property is deprecated. Do not use this custom property unless we are running in a mixed cell environment that includes at least one core groups that contains a mixture of V 7.0 and V6.x processes.depfeat

However, we can also use the Discovery and failure detection page in the admin console to change the settings for the Discovery and Failure Detection protocols. Unless we are running in a mixed cell environment, using the admin console is the preferred technique for changing the settings for the Discovery and Failure Detection protocols because the IBM_CS_FD_CONSECUTIVE_MISSED property is deprecated.

If running in a mixed cell environment, and we have core groups that contain a mixture of V7.0 and V 6.x processes, continue to use the IBM_CS_FD_CONSECUTIVE_MISSED core group custom property to change how many consecutive heartbeats a core group member must miss before that core group member is considered failed. mixv


Table 2. Units and default

Units seconds
Default 6

To set a value for this custom property, in the admin console ...

Servers > Core Groups > Core group settings > core_group_name. Then, under Additional Properties, click Custom properties .

IBM_CS_FD_PERIOD_SECS

This custom property is used to change how frequently the Failure Detection Protocol checks the core group network connections that the discovery protocol establishes. The Failure Detection Protocol notifies the Discovery Protocol if a connection failure occurs.

Deprecated feature: This custom property is deprecated. Do not use this custom property unless we are running in a mixed cell environment that includes at least one core groups that contains a mixture of V 7.0 and V6.x processes.depfeat

However, we can also use the Discovery and failure detection page in the admin console to change how frequently the high availability manager Discovery Protocol checks for new core group members. Unless we are running in a mixed cell environment, using the admin console is the preferred technique for updating this setting because the IBM_CS_FD_PERIOD_SECS property is deprecated.

If running in a mixed cell environment, and we have core groups that contain a mixture of V7.0 and V 6.x processes, continue to use the IBM_CS_FD_PERIOD_SECS core group custom property to change how frequently the Failure Detection Protocol checks the core group network connections that the discovery protocol establishes. mixv


Table 3. Units and default

Units seconds
Default 6

To set a value for this custom property, in the admin console ...

Servers > Core Groups > Core group settings > core_group_name. Then, under Additional Properties, click Custom properties .

IBM_CS_HAM_PROTOCOL_VERSION

Use this custom property to configure all of the members of the selected core group to run with a different version of the higher level core group protocol, which is also referred to as the high availability manager protocol. We can change the value of this property while the core group members continue to run. After you save and synchronize the changed value to all of the nodes containing core group processes, the high availability manager automatically detects the configuration change and starts using the new core group protocol version to communicate with the core group members.

The following table lists the supported core group protocol version IDs.

Version ID Required Minimum Product Level Description
6.0.2.31 6.0.2.31 for V6.0, 6.1.0.19 for V 6.1, 7.0.0.1 for V 7.0 This protocol version is the original or base version of the HAM protocol. This version was included in the 6.0.2.31, 6.1.0.19, and 7.0.0.1 service packs to facilitate core group bridge scalability. This version is recommended for topologies that contain multiple core groups and core group bridges as part of their configuration.

IBM_CS_IP_REFRESH_MINUTES

Use this custom property to adjust how frequently the core group IP cache is cleared.

The caching of name-to-IP address information at the core group level eliminates some of the system overhead required to assign IP addresses to core group members.


Table 4. Units, default, and acceptable values

Units seconds
Default 60
Acceptable values Any positive integer. 1 is the minimum value that can be specified

To set a value for this custom property, in the admin console ...

Servers > Core Groups > Core group settings > core_group_name. Then, under Additional Properties, click Custom properties .

IBM_CS_SOCKET_BUFFER_SIZE

Use this custom property to change the size of the socket buffer that the core group transport obtains.
Set core group socket buffers includes a table that shows the relationship between the values that can be specified for this property and the underlying memory allocation size per socket buffer type.


Table 5. Units and default

Units One of the following:

  • No over rides

  • small

  • medium

  • large

Default 2 megabytes for all buffer types.

To set a value for this custom property, in the admin console ...

Servers > Core Groups > Core group settings > core_group_name. Then, under Additional Properties, click Custom properties .

IBM_CS_UNICAST_DISCOVERY_INTERVAL_SECS

This custom property is used to change how frequently the high availability manager Discovery Protocol checks for new core group members. A new core group member is not able to communicate with other core group members until the Discovery Protocol establishes communication between the new member and the existing members.

Deprecated feature: This custom property is deprecated. Do not use this custom property unless we are running in a mixed cell environment that includes at least one core groups that contains a mixture of V 7.0 and V6.x processes.depfeat

However, we can also use the Discovery and failure detection page in the admin console to change how frequently the high availability manager Discovery Protocol checks for new core group members. Unless we are running in a mixed cell environment, using the admin console is the preferred technique for updating this setting because the IBM_CS_UNICAST_DISCOVERY_INTERVAL_SECS property is deprecated.

If running in a mixed cell environment, and we have core groups that contain a mixture of V7.0 and V 6.x processes, continue to use the IBM_CS_UNICAST_DISCOVERY_INTERVAL_SECS core group custom property to change how frequently the Discovery Protocol attempts to open a new network


Table 6. Units and default

Units seconds
Default 30

To set a value for this custom property, in the admin console ...

Servers > Core Groups > Core group settings > core_group_name. Then, under Additional Properties, click Custom properties .

IBM_CS_WIRE_FORMAT_VERSION

Use this custom property to configure all of the members of the selected core group to run with a different version of the core group protocol. We can change the value of this property while the core group members continue to run. After you save and synchronize the changed value to all of the nodes containing core group processes, the high availability manager automatically detects the configuration change and starts using the new core group protocol version to communicate with the core group members.

Deprecated feature: Protocol versions 6.0.0 and 6.0.2.9 are deprecated. Whenever possible you should use a newer protocol version.depfeat

The following table lists the supported core group protocol version IDs. 6.0.0 is the default value.

Version ID Required Minimum Product Level Description
6.0.0 6.0.0.0 for V6.0, 6.1.0.0 for V 6.1, 7.0.0.0 for V7.0 This protocol version is the original or base version.

All versions of the high availability manager can use this protocol version. If we do not specify a particular protocol version the high availability manager uses this version.

6.0.2.9 6.0.2.9 for V6.0.2, 6.1.0.0 for V 6.1, 7.0.0.0 for V 7.0. This protocol version was included in the 6.0.2.9 service pack, and in Vs 6.1, and 7.0 of WAS 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 V6.1, 7.0.0.0 for V 7.0 This protocol version was included in Vs 6.1, and 7.0 of WAS to add core group scalability improvements, and more support for large topologies.

To set a value for this custom property, in the admin console ...

Servers > Core Groups > Core group settings > core_group_name. Then, under Additional Properties, click Custom properties .




 

Related tasks


Change the number of core group coordinators

 

Related information


Core group discovery and failure detection protocols