Heartbeat restrictions

[Bruno Bossier_1]

I'm installing a Serviceguard cluster for an Oracle RAC using CVM. The install documents say that you can only configure 1 subnet as heartbeat subnet. All nodes have network connections to 2 different subnets (+stanby nic's for local fail-over). It's highly preferable to use those 2 subnets as heartbeat and data networks.

Is this possible ?

Bruno

[melvyn burnard]

No
When using SG with CVM you can only have one heartbeat network.
I consider this to be one of the reasons not to use CVM.

[Stephen Doud]

I agree with Melvyn,

The Managing Serviceguard manual states the following in this section:
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90079/B3936-90079_top.html&con=/hpux/onlinedocs/B3936-90079/00/00/39-con.html&toc=/hpux/onlinedocs/B3936-90079/00/00/39-toc.html&searchterms=CVM&queryid=20040920-055203

Section:
Preparing the Cluster for Use with CVM


"To prepare the cluster for CVM disk group configuration, you need to set MAX_CONFIGURED_PACKAGES to 1 or greater in the cluster ASCII configuration file, and ensure that only one heartbeat subnet is configured. Then use the following command, which creates the special package that communicates cluster information to CVM:"

-sd.

[#4]

The reason for this restriction is that the CVM cluster daemon vxclustd does not support multiple communication paths, so therefore SG cannot have multiple paths when vxclustd is used.

What I would suggest is that you use APA to aggregate lans together rather than simply rely on the SG failover capabilities.