Operating System - HP-UX
1849239 Members
2950 Online
104042 Solutions
New Discussion

Cluster Configuration - on Same Subnet

 
SOLVED
Go to solution
Faizer Jameel
Frequent Advisor

Cluster Configuration - on Same Subnet

Dear Gurus.
I have a 2 node production cluster and on this same subnet I want to configure another 2 rp servers as a test cluster.
This test cluster would have a different host names, different ip address and a seperate switch for the heartbeat with a different ip address.
Will there be any conflicts or problems with my production cluster.
12 REPLIES 12
S.Arunkumar
Trusted Contributor

Re: Cluster Configuration - on Same Subnet

Hi jameel

As for as there is no ip conflict between the nodes and the package Ip there will not be any probelm for your existing Cluster.So You can go ahead for creating the new test cluster

Regards
S.Arunkumar
Simon Hargrave
Honored Contributor
Solution

Re: Cluster Configuration - on Same Subnet

There's no problem having many clusters on the same IP subnet, provided there are no conflict in IP address. As you say there are none, there is no problem here.
melvyn burnard
Honored Contributor

Re: Cluster Configuration - on Same Subnet

provided you use a differwent cluster name, then there is nothing wrong with this.
I know of sites with >10 clusters on the same subnet
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
Stephen Doud
Honored Contributor

Re: Cluster Configuration - on Same Subnet

Two or more clusters will not interfere with each other's operation even when using the same subnet. Recommend that you keep the heartbeat networks private to each cluster.
Faizer Jameel
Frequent Advisor

Re: Cluster Configuration - on Same Subnet

Thankyou all, But my production cluster config is as follows.
NODE_NAME server 1 NETWORK_INTERFACE lan1
HEARTBEAT_IP 10.10.10.1
NETWORK_INTERFACE lan0
HEARTBEAT_IP 192.168.1.10
NETWORK_INTERFACE lan3 FIRST_CLUSTER_LOCK_PV /dev/dsk/c5t0d3
# List of serial device file names

NODE_NAME server2
NETWORK_INTERFACE lan1
HEARTBEAT_IP 10.10.10.2
NETWORK_INTERFACE lan0
HEARTBEAT_IP 192.168.1.20
NETWORK_INTERFACE lan3
FIRST_CLUSTER_LOCK_PV /dev/dsk/c5t0d3
The production package ip = 192.168.1.15.
The production package name= prod
The production cluster name is oraprod
--------------------------------------------
For my test cluster I propose to configure as follows.
NODE_NAME testserver1 NETWORK_INTERFACE lan0
HEARTBEAT_IP 50.50.50.1
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.1.120
NETWORK_INTERFACE lan1 FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t1d3

NODE_NAME testserver2
NETWORK_INTERFACE lan0
HEARTBEAT_IP 50.50.50.2
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.1.130
NETWORK_INTERFACE lan1
FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t1d3
The production package ip = 192.168.1.115.

The network information is as follows.
testserver1:Lan2 = 192.168.1.120
testserver2:lan2 = 192.168.1.130
The package name = testprod
The cluster name = testora.

So based on the information provided I need your valuable advise.

melvyn burnard
Honored Contributor

Re: Cluster Configuration - on Same Subnet

What more do you need?
Everything is fine as per your configuration details
My house is the bank's, my money the wife's, But my opinions belong to me, not HP!
S.Arunkumar
Trusted Contributor

Re: Cluster Configuration - on Same Subnet

For my test cluster I propose to configure as follows.
NODE_NAME testserver1 NETWORK_INTERFACE lan0
HEARTBEAT_IP 50.50.50.1
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.1.120
NETWORK_INTERFACE lan1 FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t1d3

NODE_NAME testserver2
NETWORK_INTERFACE lan0
HEARTBEAT_IP 50.50.50.2
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.1.130
NETWORK_INTERFACE lan1
FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t1d3
The production package ip = 192.168.1.115.

Check for this IP Is the Existing Production IP what you are talking about are you planned to configure a package with the same IP.
You cannot give same package IP for both the servers.Check it out.Rest of the things sound OK

Regards
S.Arunkumar


Faizer Jameel
Frequent Advisor

Re: Cluster Configuration - on Same Subnet

Its a typing error: the testpackage ip is what I mentioned as 192.168.1.115.


I do not know whether I'm missing a point. The confusion is on the Heartbeat:
where the production cluster is using a dedicated heartbeat and also configured on lan0 for the Heartbeat, which is the same subnet that the testcluster's secondary Heartbeat would also be configured.

Faizer Jameel
Frequent Advisor

Re: Cluster Configuration - on Same Subnet

What would be the position if I have the following.
For my test cluster I propose to configure as follows.
NODE_NAME testserver1
NETWORK_INTERFACE lan0
HEARTBEAT_IP 50.50.50.1
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan1 FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t1d3

NODE_NAME testserver2
NETWORK_INTERFACE lan0
HEARTBEAT_IP 50.50.50.2
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan1
FIRST_CLUSTER_LOCK_PV /dev/dsk/c7t1d3
The test package ip = 192.168.1.115.

my primary lan is lan2 and lan1 is the failover

best regards
Stephen Doud
Honored Contributor

Re: Cluster Configuration - on Same Subnet

Here is a sample section of a cluster configuration file for a node with multiple LANs where one is a dedicated HB net, and the data lan is also used for HB:

NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.126.0.17
NETWORK_INTERFACE lan1
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.0.1

In this cae, lan0 and lan2 are designated to carry HB traffic on top of their other duties.
Note that lan1 has no IP assigned to it, so it appears to be a standby LAN. The comments that follow each node section clarify the nature of that lan.
Faizer Jameel
Frequent Advisor

Re: Cluster Configuration - on Same Subnet

Hi Gurus
Thanks a lot for all of you. I did create the cluster based on your advises. It does work.
Now I am in the process of creating my package.
Thanks alot...
Faizer Jameel
Frequent Advisor

Re: Cluster Configuration - on Same Subnet

The cluster works on the same subnet as per the advises of the Gurus.
best regards