configure multiple ip address to existing lan card

[srinimar]

below is my o/p of netstat now can i add one more Ip to this and can i use that as heartbeat IP. and how to configure new Ip.

# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
lan0 1500 3.164.120.0 3.164.120.83 171883647 0 303446899 0 0

lo0 4136 127.0.0.0 127.0.0.1 1200846 0 1200846 0 0

[IT_2007]

Not a good idea to use same card for Heartbeat.

Use serial connection for heartbeat.

To configure lan card with multipule ip addresses modify netconf file and add each stanza to make it lan0:1 and la0:2 etc.. at the end of netconf file. Stanza will have name of lancard like lan0:1, ip address, subnet, gateway, broadcast address.

[srinimar]

how to make serial connection any basic idea as i am new to this...or any other procedure..

[Carsten Krege]

You can use a lan as a HB IP if all cluster nodes share the same subnet and can talk to each other on this lan.

You should use cmquerycl -n -n -n .. to determine which are the possible HB lans you can use.

In a SG cluster additional (relocatable) IP addresses can be added to a lan that are associated with packages. The package control script would add the IP addresses during package start (and removes them when the package halts). The relocatable IP addresses must belong to the same subnet like the primary IP of the lan.

In a SG cluster it is not allowed to run multiple subnets on a single lan interface.

It is not recommended to use Serial Heartbeat anymore. Serial Heartbeat will be removed from future versions of SG. Serial Heartbeat is also not a replacement for a heartbeat lan.

Carsten

[srinimar]

i have lan0 lan1 lan2 lan3 interfaces in this lan0 is configured that is for server IP. now i need to configure heartbeat IP for cluster . can i do that for lan1? and my lan0 ip is 3.164.120.X..so i can use any IP like 10.3.3.1 for heartbeat.?

[Stephen Doud]

Thanks for the additional information.
Dedicating a network to heartbeat communication is a good idea.
If the dedicated network will only link the cluster nodes, you can use practically any IP, since the network will not be accessible outside the cluster. A crossover cable is supported in a two-node cluster configuration.

Actually, we recommend enabling all ethernets to pass heartbeat traffic, above and beyond the dedicated heartbeat network. This can be accomplished by editting the cluster configuration file and changing STATIONARY_IP to HEARTBEAT_IP for each ethernet NIC represented in the cluster configuration file - prior to cmapplyconf.

[IT_2007 · Accepted solution]

yes. you can use other unused lan cards for heartbeat. You can use any private IP addresses starts in Class A, B or C networks like 192.168.2.X for Class C.

Make sure you use hub between two nodes for Heartbeat. You can use cross over cable directly from node1 to 2 without hub but it is good method to use it.

[srinimar]

Does it work if they are connected to switch...and i configure them the IP for heartbeats? because i am not sure about this...

[Stephen Doud]

Interconnection via a network switch is okay.
Also, we recommend that all IP-bearing NICs be configured to allow Serviceguard to use them to pass heartbeat traffic. This is done by changing any reference in the cluster configuration ASCII file from STATIONARY_IP to HEARTBEAT_IP, then performing a cmapplyconf on the file.

[srinimar]

Hi,
I have few Q's please help me in this.
Already i have VG's and File systems in hand i,e help me on this.

/dev/vgora/lvol10 ---- /psoft1/fin
/dev/vgora/lvol6 ---- /psoft/fin
/dev/vgora/lvol4 ---- /oraexports/fin

now in which file do i need to add this? do i need to add this before staring the below steps or while in step"6"

1) Go to the MC/ServiceGuard user file area and make a CONF:
# cd /etc/cmcluster
2) Generate the cluster configuration template file
# cmquerycl -C CONF -n -n ...
3) Customize the CONF.
Set CLUSTER_NAME parameter
Set NODE_TIMEOUT = 8000000
Set MAX_CONFIGURED_PACKAGES value.
Add additional parameters such as Access Control Policy (available
A.11.16) and Faster Failover (if installed)
4) Make a directory for each package:
# mkdir pkg1 ...
5) Make a package config file and package control script in each pkg directory:
# cd pkg1; cmmakepkg -p conf ;cmmakepkg -s pkg1.sh
6) Customize the pkg config file and control script in each pkg directory.
7) Verify your configuration:
# cmcheckconf -C CONF -P pkg1/conf
8) Activate clusterlock disk (see CONF file):
# vgchange -a y vgXX
9) Make and distribute a binary configuration file to all the nodes:
# cmapplyconf -C -P
10) Deactivate clusterlock disk now:
# vgchange -a n vgXX
11) Now copy all files to the other node:
# rcp -pr /etc/cmcluster node2:/etc/cmcluster
12) Start cluster:
# cmruncl
# cmviewcl (to see cluster status)
13) Halt the cluster:
# cmhaltcl

[srinimar]

i got the solution. for this.