Using Serviceguard Extension for RAC, 6th Edition, April 2008

1. to monitor the CSS-HB network and
2. if any of the following cluster parameters needs to be changed the default values
of:
Oracle Clusterware parameter CSS misscount
or
Serviceguard cluster configuration parameter NODE_TIMEOUT
or
Serviceguard HEARTBEAT_INTERVAL
Then the CSS misscount parameter should be the greater of either:
195 seconds
or
40 times Serviceguard NODE_TIMEOUT plus 25 times Serviceguard
HEARTBEAT_INTERVAL + 120 seconds
When Cluster Interconnect Subnet Monitoring is not used
The Cluster Interconnect Monitoring is not used:
1. to monitor the CSS HB subnet and
2. if the default values of any of the following parameters has to be changed:
Oracle Clusterware parameter CSS misscount
or
Serviceguard cluster configuration parameter NODE_TIMEOUT
Then the CSS misscount parameter should be the greater of either:
195 seconds
or
25 times Serviceguard NODE_TIMEOUT + 15 seconds.
Limitations of Cluster Communication Network Monitor
The Cluster Interconnect Monitoring feature does not coordinate with any feature
handling subnet failures (including self). The failure handling of multiple subnet failures
may result in a loss of services, for example:
A double switch failure resulting in the simultaneous failure of CSS-HB subnet
and SG-HB subnet on all nodes of a two-node cluster. (Assuming the CSS-HB
subnet is different from SG-HB subnet). Serviceguard may choose to retain one
node while the failure handling of interconnect subnets might choose to retain the
other node to handle CSS-HB network failure. As a result, both nodes will go
down.
54 Serviceguard Configuration for Oracle 10g RAC