ServiceGuard with only 2 NIC cards?

[Ray Humpage]

My equipment was only shipped with 2 NIC cards in each box. I want to be able to get a 2 node cluster up and running and then add in my other cards when they arrive. I have tried different configurations with no luck.

My first card lan0 in each box is configured as 10.60.105.xxx. Should my second card lan1 be configured? I tried the following without lan1 being configured and it errored out.

Error: lan1 on node cadencem cannot be configured in the cluster because it does not have an IP address, and it is not a standby lan for any other lan.

How do I make is standby lan?

NODE_NAME prod_node
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.60.105.xxx
NETWORK_INTERFACE lan1

If it is configured does is have to be on a subnet other that 10.60.105.xxx? Should it be set up as a crossover?

[Mel Burslan · Accepted solution]

First off, I am not sure what type of hardware and which version of serviceguard you are running but on certain combinations, lan0 is not a supported interface for serviceguard setup and communications. Check with HP to be sure for compatibility in your case or someone her will tell you if you are compatible if you post your h/w type and SG version you are running.

Having said that, in the configuration you gave in the original post, you have confgured a heartbeat lan but there is not stationary ip address configured. You have to configure your lan1 for the actual SG functions other than heartbeat, like this in your cmclconfig.ascii file (or whatever name you choose for your cluster config ascii file):

NODE_NAME server1
NETWORK_INTERFACE lan1
STATIONARY_IP 192.168.1.22
NETWORK_INTERFACE lan4
NETWORK_INTERFACE lan0
HEARTBEAT_IP 200.200.200.52

NODE_NAME server2
NETWORK_INTERFACE lan1
STATIONARY_IP 192.168.1.21
NETWORK_INTERFACE lan4
NETWORK_INTERFACE lan0
HEARTBEAT_IP 200.200.200.51


in this example, as you can see, I am using lan4 as my failover interface but you will not have that luxury as you do not have a 3rd interface available.

Again, remember this is only valid if your lan0 can be supported for serviceguard.

Hope this helps

[Devesh Pant_1]

I would suggest gooing through the serviceguard documentation. Have both the NICs cabled.
run the command
cmscancl -n node1 -n node2 -o /tmp/cmscanout.txt

and then go through this file to identify how linkloop sees the connectivity and then decide the main and heartbeat nics you can have the standby added later on.

thanks
DP

[melvyn burnard]

to be a standby lan, lan1 must be unconfigured, but MUST be cabled in such that lan0 on the same host can talk to it, AND so that lan0 and lan1 on th eother host can talk to it.
Essentially they must all be physically connected to each other.

The usual way to do this is have hubs or switchs in between the hosts, to which you connect these lan cards.

One item of concern is what model systems are you using, as certain systems cannot use the built in lans for Serviceguard.
See the Managing Serviceguard manual available at http://docs.hp.com/en/ha

[Thomas J. Harrold]

You do NOT want to specify a "stationary_IP" with only two NIC cards. Use "heartbeat_IP"
This will allow both data and heartbeat to use the same NIC. (since that's all you have...)

Configure an IP on lan0, and leave lan1 unconfigured, but DO list it in the SG configuration. lan1 will be the standby for lan0.

-tjh

[Ray Humpage]

I always find a solution here as I did in this case. I'm just notoriously slow with assigning points and closing threads.