SG nodes in different subnets

[Lovro VRES]

Hi,

I have two node SG cluster, where nodes are in different subnets. They can ping each other and all needed trust is established.

When I prepare my first package and check package control file, I got an error:
Node node2 does not have access to subnet 10.10.16.0 for package pkg1
Node node1 does not have access to subnet 10.9.16.0 for package pkg1

Is there any idea?

Thanks and regards.

[Steven E. Protter]

Shalom,

Serviceguard is telling you the answer.

The two nodes need to be on the same subnet.

You at least need a the heartbeat on a private network between the two systems (new NIC required).

Servicegaurd works across the network. This behavior seems perfectly normal to me.

However:
What version of SG? Are you using .rhosts or cmnodelist security?

I think you need to do cmquerycl and rebuild the cluster. That might get you around this issue.

SEP

[Lovro VRES]

Hello,

thank you for your answer. I have SG A.11.17.
I have four network cards in the server, using APA, so I have two different addresses.
First node has 10.10.17.2 (255.255.252.0 subnet) for LAN connection and 10.10.21.11 for heartbeat.
Second node has 10.9.17.2 for LAN and 10.10.21.12 for heartbeat.

Heartbeat is on the same subnet, but LAN interfaces ožare on different subnets.

Is that configuration also unsupported? Should I make some changes in conf file? I asume the problem is SUBNET in conf file. I put both subnets in conf file. Can I have different conf file for different node, so the first node has first subnet and the second node has the second subnet?

Regards

[Duncan Edmonstone · Accepted solution]

Yes that is unsupported.

If a network is going to be part of a Serviceguard configuration then it needs to be in the same subnet on both nodes.

So your HB network needs to be in the same subnet and your data LAN needs to be in the same subnet as well. You can have other subnets on the nodes, but they can't be part of the Serviceguard configuration.

HTH

Duncan