Problem standby lan cluster service guard 11.17

[Marco Sedda]

Hi my friends...
Please I need help.
when executed the cmcheckconf cmclconfig.ascii,
Show this
lan0 on node seux0001 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.
lan0 on node seux0002 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
cmcheckconf: Unable to reconcile configuration file cmclconf.ascii
with discovered configuration information.

[Steven E. Protter]

Shalom,

The lan0 card can have a ip address configured in serviceguard. I think thats the way to go.

SEP

[Ignacio Javier]

Hello Marco:

What is happening is that the lan you are choosing for heartbeat or data is not configured in your nodes.

You should choose another lan or configure correctly the ones you chose.
Note that if you want a stand by lan, you don´t have to configure.

For example in my two node cluster configuration file i have for the firs node:

NODE_NAME primario
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.1.1.62
NETWORK_INTERFACE lan4
HEARTBEAT_IP 192.168.2.1
NETWORK_INTERFACE lan5


Lan 0 y lan4 must be configured.

lan 5 should not because when one of then others fails, takes the configuratión of the one that broke.



I hope it helps

Regards

[Marco Sedda]

this e' my configuration of the lan:

NODE_NAME pippo NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.168.1.208
NETWORK_INTERFACE lan3
NETWORK_INTERFACE lan2
HEARTBEAT_IP 10.0.0.8
NETWORK_INTERFACE lan4
STATIONARY_IP 172.16.1.1
NETWORK_INTERFACE lan0

FIRST_CLUSTER_LOCK_PV /dev/dsk/c4t1d0
# List of serial device file names
# For example:
# SERIAL_DEVICE_FILE /dev/tty0p0

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

NODE_NAME pluto
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.168.1.209
NETWORK_INTERFACE lan3
NETWORK_INTERFACE lan2
HEARTBEAT_IP 10.0.0.9
NETWORK_INTERFACE lan4
STATIONARY_IP 172.16.1.2
NETWORK_INTERFACE lan0

[Stephen Doud · Accepted solution]

The message:

"lan0 on node seux0001 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" ... indicates that you have listed lan0 in your cluster configuration file, but it has no IP assigned to it AND it is not attached to the same network as any NIC that has an IP assignment. Thus, lan0 is useless to Serviceguard because it has no purpose.

If a NIC has no IP assignment but you want it to be a standby NIC, it MUST be on the same LAN as a primary (IP-bearing) NIC.

If you intend that lan0 be registered as having an IP, it must be listed in /etc/rc.config.d/netconf, and the IP must be associated with lan0 in the cluster configuration file and show up when running 'ifconfig lan0'.

[Marco Sedda]

I have connected the lan0 of node 1 with cable cross to the lan0 of node 2 like of the rest the lan primaryE' this the error? .

[Ignacio Javier]

Hi:

Is not only a wiring problem.
I guess you did this last conecction to set up a dedicate heartebeat lan.

If this is correct, you have to configure it, like it is said in the previous post.
You may use sam wich is easier.


Regards

[Shardha]

Hi,

A network to be a stand by should not be configured and it should be on the same network as of the primary lan. So you need to rewire the network.

Shardha

[melvyn burnard]

if you have connected your "standby " lans using a crossover cable this will not work.
They have to be physically connected so that the "primary" lans can physically linkloop to them

[Marco Sedda]

ok