NIC Bonding in Serviceguard.

[Arun Vijay V C]

Hi,
I have a two node Service Guard cluster. Each node having 6 NICs and they are uses as,

Lan0 Staionary IP
Lan1 First Heart Beat IP
Lan2 Second Heart Beat IP
Lan3 Standby NIC
Lan4 BackupIP (Data Backup will be done through this)
Lan5 is free.

Now the application needs a NIC card with bonding of two NICs for card redundancy. But currently there is only one free card available.

My Plan is to remove the second Heart beat NIC from the cluster and configure a bonding with the free lan card Lan5. Then use this bonded Lan for both second HB IP and app requirement as,
lan900:0 Second Heart Beat IP
lan900:1 Application IP

1) Is it possible first of all?
My doubt is when the server is restarted the cluster will come up automatically. That time the cluster will be looking for the HB NIC lan900:0. By the time Bonding configuration will be activated and ready for lan900:1 ??

If the bonding is not ready, the cluster will be looking for the lan900:0.

2) If its possible, when I remove the HB NIC from cluster, do I need to halt the clsuetr since the other HB NIC is still there??

Could any one help me on this?
Hight Appreciate your immediate reply...!!

Thanks,
Arun Vijay V C

[Viktor Balogh]

Hi,

>Now the application needs a NIC card with bonding of two NICs for card redundancy.

With ServiceGuard you also have NIC-redundancy, you don't need APA on top of that config. I would configure lan5 as a standby interface. Standby means: if there are any NIC failed, the IP Adress will be given to the standby NIC and it runs almost without any other signal than the one in syslog.

Give your HA-packages a free IP adress from the corporate subnet (subnet of lan0), and config it into the cntl file. These will appear as a virtual IP address configured on top of lan0 as lan0:1 etc...