Core group and core group bridge custom properties

 

+

Search Tips   |   Advanced Search

 

FW_PASSIVE_MEMBER

Use this property in a core group bridge configuration when there is a firewall between the core groups and the secure side of the firewall is configured to listen only.

Set the FW_PASSIVE_MEMBER custom property to make the bridge interfaces that are in the core group access point passive. Set the value on the core group access point that is on the secure side of the firewall so that the core group bridge interfaces listen for connections from the unsecured side of the firewall but do not initiate any connections. The servers on the secure side of the firewall are passive. The custom property should correspond to your defined firewall rules that allow connections from the unsecured region to the secure region only.

To configure this custom property, click...

Servers | Core groups | Core group bridge settings | Access point groups | access_point_group_name | Core group access points | core_group_access_point_name | Show detail | Custom properties | New

You also must set this custom property in any peer access points that refer to the core group access points that you configure with this custom property.

 

Configure the FW_PASSIVE_MEMBER custom property example

For example, ServerA and ServerB are configured in CoreGroup1. ServerC and ServerD are configured in CoreGroup2. CoreGroup2 is behind a firewall that is configured to listen only through the firewall. CoreGroup1 is on the unsecured side of the firewall. CoreGroup1 and CoreGroup2 can communicate with each other through an access point group. To configure ServerC and ServerD to be passive, perform the following steps:

  1. In the administrative console for the cell that contains CoreGroup2, click...

    Servers | Core groups | Core group bridge settings | Access point groups | access_point_group_name | Core group access points | core_group_access_point_name | Show detail | Custom properties |New

  2. Add the FW_PASSIVE_MEMBER custom property. Enter any value to enable the property.

  3. In the administrative console for the cell that contains CoreGroup1, click...

    Servers | Core groups | Core group bridge settings | Access point groups | access_point_group_name | Peer access points | peer_access_point_name | Show detail | Custom properties | New

    The peer access point you select should correspond to the core group access point for CoreGroup2.

  4. Add the FW_PASSIVE_MEMBER custom property. Enter any value to enable the property.

By configuring the FW_PASSIVE_MEMBER custom property, you configured the servers on the secured side of the firewall, ServerC and ServerD, to be passive. These servers listen for connections from the other side of the firewall but do not initiate any connections to the unsecured side of the firewall.

IBM_CS_LS_DATASTACK_MEG

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

You might see a message similar to the following message in the SystemOut.log file multiple times

[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, one can eliminate these messages by increasing the amount of memory that is allocated to the core stack that is 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.

Set the custom property on the bridge interface that contains the particular member that is in the messages. We can also set the custom property on the access point group or the core group access point. If you set the value on the access point group or core group access point, all the bridge interfaces that are in the particular group are affected. If you set the value on an individual bridge interface and an access point group or core group access point, the value that is set for the bridge interface is used. If the value is set on both an access point group and a core group access point, the value that is set for the core group access point is used.

To configure this custom property, complete the following steps:

  1. Set the custom property in the administrative console.

    • To set the custom property on a bridge interface, click...

      Servers | Core groups | Core group bridge settings | Access point groups | access_point_group_name | Core group access points | core_group_access_point_name | Show detail | Bridge interfaces | bridge_interface_name | Custom properties | New

    • To set the custom property on a core group access point, click...

      Servers | Core groups | Core group bridge settings | Access point groups | access_point_group_name | Core group access points | core_group_access_point_name | Show detail | Custom properties | New

    • To set the custom property on an access point group, click...

      Servers | Core groups | Core group bridge settings | Access point groups | access_point_group_name | Custom properties | New

  2. Add the IBM_CS_LS_DATASTACK_MEG custom property. Enter a value that is greater than the default value of 5 megabytes.

Units megabytes
Default 5