Package Logical IP

[Omar Alvi_1]

Hi,

I've a two node MC/SG cluster with a single package incompletely configured.

Currently, if the package fails over, the users will probably have to use the Lan IP Address of the failover node to login to the system.

Can I create a logical IP address for the package, such that users may login to this IP Address irrespective of where the package resides?

If this is possible, how can it be achieved?

In addition, this logical IP address, is it in fact a physical IP address as well, or can it be any IP address on the same subnet as the physical lans?

Really appreciate any assistance.

Thanks and regards,

-Alvi

[RAC_1 · Accepted solution]

The virtual ip/floating ip has to be on the same sunbet as that of physical ip address. Is is defind in package configuration script.

Anil

[Henk Geurts]

hi Alvi
you can add the package ipadres in the package control file
here is a part of my cntl file:
# IP ADDRESSES
# Specify the IP and Subnet address pairs which are used by this package.
# Uncomment IP[0]="" and SUBNET[0]="" and fill in the name of your first
# IP and subnet address. You must begin with IP[0] and SUBNET[0] and
# increment the list in sequence.
#
# For example, if this package uses an IP of 192.10.25.12 and a subnet of
# 192.10.25.0 enter:
# IP[0]=192.10.25.12
# SUBNET[0]=192.10.25.0 # (netmask=255.255.255.0)
#
# Hint: Run "netstat -i" to see the available subnets in the Network field.
#
# IP/Subnet address pairs for each IP address you want to add to a subnet
# interface card. Must be set in pairs, even for IP addresses on the same
# subnet.
#
IP[0]=10.40.155.16
SUBNET[0]=10.40.155.0

end of output

make sure the userid's and passwords are the same across the clusternodes....

regards.

[melvyn burnard]

This is in fact the way that it should be done.
Read the section on configuring packages in the Managing Serviceguard manual at:
http://docs.hp.com/en/ha
Also read the comments in your package configuration and package control files, as they also have information.

[Omar Alvi_1]

Thanks a lot for the replies

So all I have to do is have a non conflicting IP Address on the same subnet.

Once I configure it any user will be able to telnet into the system with the active package, right?

Can I also configure a hostname for package, like instead of remembering the IP Address for users to telnet using the hostname?

Thanks and Regards,

-Alvi

[Tim D Fulford]

Hi

TThis is EXACTLY what you do in DNS and or hosts file. e.g.

nodea 192.164.193.101
nodeb 192.164.193.102
pkg 192.164.193.103

This is what HP have always reccomend should be done.

Regards

Tim

Regards

[Rita C Workman]

I'm coming in a little late to this one.
But that is what we do here...we resolve to the package name ONLY.
We set everything oracle to resolve to the package name...period...That way no matter what host it resides on, the client will always find it.

Now...here's a twist. As everyone mentions you must be on the same subnet. Welllll....we run a continental cluster. And to fail to our DR site, we still resolve to the same package name !!!!!!!!!!
The trick is to change the IP behind the scenes...i.e. we quickly reconfigure DNS so the package now points to the address at the other site. The package at the DR site has the 'other ip' configured in it. This way we do not require changing any of the client machines. Our boxes at the primary site could all die...and we can be up and running from our DR site in moments, with our clients still sitting back at their same desk at the primary site.


Rgrds,
Rita

[Omar Alvi_1]

Thanks a lot for the excellent support.

Now I'll be digging into services and customer defined run and halt commands for Oracle.

Will definitely be seeking you out if I have issues there.

Thanks and Regards,

-Alvi