MC/Service Guard floating IP address

[Clara Rowe]

I am running HP-UX 10.20 on two 380D machines with a 20 disk array and MC/Service Guard for fail over of an Oracle data base. A third party did the initial install. A second Oracle database was added to the primary system using a completely different volume group. I created a new package and successfully failed both packages over to the alternate system. One of the packages did not stay up, and failed back over to the primary system. This left me with one package on each system. The problem is that I am using a floating IP address so that users can access the system regardless of where the package resides. When the packages were split, the floating IP address got hung up too. Should I create a second floating IP address for the new package? Also, how will two separate pacakges be effected by the lock disk?

[Robert Gamble]

Clara,

Each package requires a separate floating IP.

Do not worry about the lock disk.

Good Luck!

[Byron Myers]

Clara,
You definately need a second IP for the second package; otherwise, as you have found out, you will not be able to run the two packages on separate machines at the same time.

As for the lock disk - this is used when the cluster forms or reforms, so it will not affect package start and halts. When the cluster forms, the lock disk is used to "break" any ties for which system will become the "cluster coordinator". One of the responsibilities of the cluster coordinator is to be a central focal point for all heartbeat messages. The same holds for when the cluster "reforms", say if one node fails. A cluster reformation to one node, still needs this lock disk.

[Jeganathan Venkitasamy]

Hi,

you said that "one of the package did not stay up" in alternate system. But you did not mention which package has this problem.
I think there might be some problem in package configuration.
A floating IP can be bound to one LAN at any time.
Note: when package fails over to alternate system, users connected to the package at that time WILL HANG. They have to disconnect and connect again to the same IP.

Regards,
Jeganathan

[Clara Rowe]

Thanx guys for responding. I got it all set up this past weekend. I had to first issue the following command:
ifalias btlan01 ip_address
Then I had to modify the script of the new package I added to use the new floating IP address. Then when I took down that package, it did not cause the original package to go down as well. When it came back up, it was on the new floating IP address. I had help from HP support on both the Service Guard and network issues of the problem. So thanx to them and thanx to you guys for responding.