HP Serviceguard Extension for RAC (SGeRAC) manual Guidelines for Changing Cluster Parameters

the appropriate subnet if the RAC Instances use a RAC-IC network different from CSS-HB network. No special subnet monitoring is needed for CSS-HB Subnet because Serviceguard monitors the subnet (heartbeat) and will handle failures of the subnet.

The database instances that use 192.168.2.0 must have cluster_interconnects defined in their SPFILE or PFILE as follows:

orcl1.cluster_interconnects=’192.168.2.1’ orcl2.cluster_interconnects=’192.168.2.2’

NOTE: Do not configure CLUSTER_INTERCONNECT_SUBNET in the RAC instance package if the RAC-IC network is the same as CSS-HB network.

The following is an example of the relevant package configuration parameters:

Oracle RAC Instance Package
PACKAGE_NAME	RAC_PACKAGE
PACKAGE_TYPE	MULTI_NODE
LOCAL_LAN_FAILOVER_ALLOWED	YES
NODE_FAIL_FAST_ENABLED	NO
CLUSTER_INTERCONNECT_SUBNET	192.168.2.0

NOTE: For information on guidelines to change certain Oracle Clusterware and Serviceguard cluster configuration parameters, see “Guidelines for Changing Cluster Parameters” (page 39)

Guidelines for Changing Cluster Parameters

This section describes the guidelines for changing the default values of certain Oracle clusterware and Serviceguard cluster configuration parameters.

The guidelines vary depending on whether clustering interconnect subnet monitoring is used to monitor the CSS HB subnet or not.

When Cluster Interconnect Subnet Monitoring is used

The Cluster Interconnect Subnet Monitoring feature is used to monitor the CSS-HB network.

If the Serviceguard cluster configuration parameter MEMBER_TIMEOUT is changed, then it is necessary to also change the Oracle Clusterware parameter CSS miscount.

To change the CSS miscount, use the following guidelines:

The CSS miscount parameter should be greater than the following:

•For SLVM: (number of nodes – 1) times (F + SLVM timeout) + 15 seconds

•For CVM/CFS: (two * number of nodes – 1) times F + 15 seconds

•When both SLVM and CVM/CFS are used, then take the max of the above two calculations.

When Cluster Interconnect Subnet Monitoring is not Used

The Cluster Interconnect Monitoring is not used to monitor the CSS HB subnet.

If the Serviceguard cluster configuration parameter MEMBER_TIMEOUT is changed, then it is necessary to also change the Oracle Clusterware parameter CSS miscount.

To change the CSS miscount, use the following guidelines:

The CSS miscount parameter should be greater than the following:

•For SLVM: F + SLVM timeout + 15 seconds

•For CVM/CFS: 3 times F + 15 seconds

•When both SLVM and CVM/CFS are used, then take the max of the above two calculations.

Cluster Communication Network Monitoring 39