sg : network configuration

[singvey]

1.I have two hosts .
each host has three lan interfaces:lan0,lan1,lan2

my /etc/hosts/
192.168.100.1 hpsrv1
202.102.128.1 ora1


2. I configure my cluster file:
node_name ora1
network_interface lan0
hearbeat_ip 192.168.100.1
network_interface lan1
stationary_ip 202.102.128.1
network_interface lan2

node_name ora2
network_interface lan0
hearbeat_ip 192.168.100.2
network_interface lan1
stationary_ip 202.102.128.2
network_interface lan2
3.I configure my package ip 202.102.128.3
the monitor network number: 202.102.128.0

*********************************************
I ask few question

a.Is my configuration right????
lan0-hb
lan1-staionary(only send data,public lan)
lan2-standby ( if lan0 or lan1 fails)
b.my heartbeat line has a standby lan :lan2???
c.my stationary line has a standby lan:lan2????

d.I configure the package ip 202.102.128.3 witch is at the same network number with lan1, Is it right ????



thank you!!!!!

[Geoff Wild]

You can only have a standby for 1 interface...

Rgds...Geoff

[Kent Ostby]

singvey --

The package IP address should not be configuerd in the netconf file at all.

it is a floating IP and MUST only be configured in the package. If it is configured in the netconf file then the package wont start because it will be trying to assign an IP address that is already in use on the system.

[melvyn burnard]

I would change the lan1 configuration from STATIONARY_IP to HEARTBEAT_IP, this gives you more redundancy for the heartbeats.
As for which lan is lan2 the standby? It depends how you have connected everything.
If you look at your cluster ascii file after running cmquerycl, it should hav eadded comments to tell you which lan has a standby, and what lan is being used as the standby

[Stephen Doud]

lan2 can be a standby lan for both lan0 and lan1 ONLY if they are on a common network.

If lan0 (HB net) is private, then it will not share a network path with lan1, and therefore lan2 cannot act as a standby for lan0 (assuming you intend lan2 to act as a standby for lan1).

As Melvyn said, change STATIONARY_IP to HEARTBEAT_IP for lan1 on both servers, and you will enable Serviceguard to use lan1 to send heartbeat over a second network.
Don't do this if lan0 and lan1 share a common physical network - it will fail cmcheckconf (I tried it)