How to configure two standby interfaces for hosts with two ip

[Marta Gomez]

Hi all,
I've got two servers with two ip adresses of different subnets. Every package in MC/SG has two ip too, one for each subnet.
When I configure MC/SG I put two HEARTBEAT_IP (one of each subnet) and two standby interfaces, one connected fisically to subnet1 and the other to subnet2. How can I tell to MC/SG which standby interface to use with every lan card? so I have two subnets!!

Thanks.

[melvyn burnard · Accepted solution]

provided there is no physical connection between the subnets, there qill be one standby for each primary lan card.
ServiceGuard will work this out when you do things like cmquerycl etc, and apply the binary.
If there is a physical connection, then you have no control over which standby card will be used by which subnet.

[Mark van Hassel]

Hi,

When you want to configure for example lan6 as standby for lan2, make sure both interfaces are physically connected to the same subnet.


When peforming a cmquerycl with the -C option it will create a template config file and will suggest the possible standby interfaces:
# Possible standby Network Interfaces for lan6: lan8.
# Possible standby Network Interfaces for lan7: lan5.


Thyen you configure the IP addresses as follows:

NODE_NAME HOSTNAME
NETWORK_INTERFACE lan6
HEARTBEAT_IP 10.10.10.10
NETWORK_INTERFACE lan8
NETWORK_INTERFACE lan7
HEARTBEAT_IP 20.20.20.20
NETWORK_INTERFACE lan5


This means that lan8 is standby for lan6 and lan5 for lan7.

HtH,

Mark

[Marta Gomez]

My problem is isolated. I have access at level 2 between the two lans.
My question is now if MC/ServiceGuard checks the connectivity of the standby lan cards when I do the cmcheckconf and cmapplyconf only, or once it's configured, every time a primary lan card fails.

Thanks

[melvyn burnard]

SG will check for the connectivity when you do cmquerycl/cmcheckconf/cmapplyconf.
Once this is written into the binary, as long as the cluster is running there will be polling of the networks to regularly check connectivity.