MC ServiceGuard and standby lan

[Sergejs Svitnevs]

We`re using HP-UX 11 and Service Guard A.11.09 on 2 nodes. I want to configure standby LAN card in our cluster configuration file.
--------------------------
old cluster config file:
# Definition of nodes in the cluster.
NODE_NAME XXX
FIRST_CLUSTER_LOCK_PV /dev/dsk/c4t0d2
NETWORK_INTERFACE lan2
HEARTBEAT_IP A.B.C.D

--------------------------
new cluster config file:
# Definition of nodes in the cluster.
NODE_NAME XXX
FIRST_CLUSTER_LOCK_PV /dev/dsk/c4t0d2
NETWORK_INTERFACE lan2
HEARTBEAT_IP A.B.C.D
NETWORK_INTERFACE lan0

--------------------------
/etc/rc.config.d/netconf
INTERFACE_NAME[0]="lan2"
#lan2 configuration

INTERFACE_NAME[1]="lan1"
# lan1 configuration

INTERFACE_NAME[2]="lan0"
# no configuration

--------------------------
When I issue the cmcheckconf command I get an error :
"Error: lan0 on node XXX cannot be configured in the cluster because it does not have an IP address, and it is not a standby lan for any other lan.
Failed to evaluate network"

lan0 is connected to the same subnet as lan2.

When I issue cmquerycl command, I get:

NODE_NAME XXX
NETWORK_INTERFACE lan2
STATIONARY_IP A.B.C.D
NETWORK_INTERFACE lan1
HEARTBEAT_IP A.B.F.G
NETWORK_INTERFACE lan0

What entries are necassary in my cluster configuration file if I want only primary lan2 with standby lan0?
Thanks in advance,
Sergejs

[Frederic Sevestre]

Hi,

I think you should have no entry for your standby lan in the netconf.

Then check that the lan0 is physicaly connected to the network and the switch well configured. The lan0 of server A must reach lan 2 of server B.

Regards,
Fr??d??ric

[Rainer von Bongartz]

What do you mean

INTERFACE_NAME[2]="lan0"
# no configuration


I got the following entry for my stand-by card:

INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=
SUBNET_MASK[0]=
BROADCAST_ADDRESS[0]=""
INTERFACE_STATE[0]=""
LANCONFIG_ARGS[0]="ether"

Try checking this....

Regards
Rainer

[Sergejs Svitnevs]

the node Nr.2 is no longer an active part of our cluster. The cluster has reconfigured with only a single node XXX.
This node has 3 lan interfaces: lan0,lan1,lan2

[melvyn burnard]

post your netstat -in output here.
Also, in the ascii file you create with cmquerycl, what do the comments that follow the node information say?
If they do NOT state that lan0 is a possible standby for lan2, then there is a network issue that MUST be fixed.

[Frederic Sevestre]

You can use cmscancl to check the network configuration of your cluster

# cmscancl -n -o /tmp/cmscancl.txt

[Sergejs Svitnevs]

# netstat -in
Name Mtu Network Address Ipkts Opkts
lan2 1500 A.B.C.0 A.B.C.3 23031140 40835154
lan1 1500 A.B.F.0 A.B.F.34 30161 30785
lo0 4136 127.0.0.0 127.0.0.1 1065250 1065250
lan2:1 1500 A.B.C.0 A.B.C.1 616372 27049
lan2:3 1500 A.B.C.0 A.B.C.6 3404 3164
lan2:2 1500 A.B.C.0 A.B.C.2 500539 390003

Fresh ascii configuration file has next records:

# Possible standby Network Interfaces for lan1: lan0.
# Warning: There are no standby network interfaces for lan2.

[Sergejs Svitnevs]

I get an output from cmscancl :

################# INFORMATION FOR THE NODE XXX ###############


------ Output of lanscan (omcdb) ------

Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/0/0 0x00306E038A61 0 UP lan0 snap0 1 ETHER Yes 119
0/1/1/0 0x001083F76397 2 UP lan2 snap2 2 ETHER Yes 119
0/1/0/0 0x001083F7230C 1 UP lan1 snap1 3 ETHER Yes 119

[melvyn burnard · Accepted solution]

Well here is your answer, as per your ascii file:
# Possible standby Network Interfaces for lan1: lan0.
# Warning: There are no standby network interfaces for lan2.
So lan0 is available to be used by lan1 as a standby, but lan2 has no possible standby lans.
So if you need lan0 to be the standby for lan2, you need to make some physical network changes.

[Sergejs Svitnevs]

You are right, thanks Melvyn.