MC/SG B11.13

[THEUNISSEN, J]

Dear support I am using two A6847A cards in my MC/SG cluster configuration, one as the network to use and one as standby lan. I am already using one now, but when I tried to add the second one as standby I got the following message during the cmcheckcl:

Checking cluster file: /etc/cmcluster/cmclconf.ascii
Checking nodes ... Done
Checking existing configuration ... Done
Gathering configuration information ... Done
Gathering configuration information ... Done
Gathering configuration information .............. Done

Error: lan2 on node ELITIL2 cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any oth
er lan.
Failed to evaluate network
cmcheckconf : Unable to reconcile configuration file /etc/cmcluster/cmclconf.as
cii
with discovered configuration information.

I tried a linkloop and that was OK for both cards on both nodes. What can be the problem?

[Jeff Schussele · Accepted solution]

Hi,

Make sure the standby for the primary is listed immediately after the primary in the cmclconf.ascii file and has no STATIONARY_IP listed for it.

Then make sure that the standby has been set to the IP 0.0.0.0 & netmask 0 by using

ifconfig lan2 0.0.0.0 netmask 0

Then try the cmcheckcl again.

HTH,
Jeff

[THEUNISSEN, J]

I did the ifconfig and now I can see lan2 in netstat -i as none none, so I decide to put lan2 in cmclconf.ascii as well and I did an cmcheckconf:
ELITIL2 : / : # cmcheckconf -v -C /etc/cmcluster/cmclconf.ascii

Checking cluster file: /etc/cmcluster/cmclconf.ascii
Checking nodes ... Done
Checking existing configuration ... Done
Gathering configuration information ... Done
Gathering configuration information ... Done
Gathering configuration information ............... Done

Error: lan2 is a slave device which you are not allowed to reference directly fr
om a ServiceGuard configuration.
Error: lan2 is a slave device which you are not allowed to reference directly fr
om a ServiceGuard configuration.
Error: Non-uniform connections detected,
ELITIL1 lan1 successfully received from ELITIL1 lan0
but ELITIL1 lan0 did not receive from ELITIL1 lan1.
This is probably due to heavy network traffic or heavy load on ELITIL1.
Error: Non-uniform connections detected,
ELITIL2 lan1 successfully received from ELITIL1 lan0
but ELITIL1 lan0 did not receive from ELITIL2 lan1.
This is probably due to heavy network traffic or heavy load on ELITIL2.
Error: Non-uniform connections detected,
ELITIL1 lan0 successfully received from ELITIL1 lan1
but ELITIL1 lan1 did not receive from ELITIL1 lan0.
This is probably due to heavy network traffic or heavy load on ELITIL1.
Error: Non-uniform connections detected,
ELITIL2 lan0 successfully received from ELITIL1 lan1
but ELITIL1 lan1 did not receive from ELITIL2 lan0.
This is probably due to heavy network traffic or heavy load on ELITIL2.
Error: Non-uniform connections detected,
ELITIL2 lan1 successfully received from ELITIL2 lan0
but ELITIL2 lan0 did not receive from ELITIL2 lan1.
This is probably due to heavy network traffic or heavy load on ELITIL2.
Error: Non-uniform connections detected,
ELITIL1 lan1 successfully received from ELITIL2 lan0
but ELITIL2 lan0 did not receive from ELITIL1 lan1.
This is probably due to heavy network traffic or heavy load on ELITIL1.
Error: Non-uniform connections detected,
ELITIL2 lan0 successfully received from ELITIL2 lan1
but ELITIL2 lan1 did not receive from ELITIL2 lan0.
This is probably due to heavy network traffic or heavy load on ELITIL2.
Error: Non-uniform connections detected,
ELITIL1 lan0 successfully received from ELITIL2 lan1
but ELITIL2 lan1 did not receive from ELITIL1 lan0.
This is probably due to heavy network traffic or heavy load on ELITIL1.
Warning: Network interface lan2 on node ELITIL1 couldn't talk to itself.
Warning: Network interface lan2 on node ELITIL2 couldn't talk to itself.
Error: lan2 on node ELITIL1 cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any oth
er lan.
Error: lan2 on node ELITIL2 cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any oth
er lan.
Failed to evaluate network
cmcheckconf : Unable to reconcile configuration file /etc/cmcluster/cmclconf.as
cii
with discovered configuration information.

What can be wrong?

The linkloop was okay, so I don't understand the message lan2 couldn't talk to itself.

[Jeff Schussele]

OK, remove the IP from lan2

ifconfig lan2 unplumb

Leave it in the cmclconf.ascii file & try the cmcheckconf again.
Remember that the switch port that lan2 is connected to MUST be set to the proper VLAN that the NIC would dwell in when faled over to.

Is the cluster up & running now?
You may have to stop it, make a safe copy of the cmclconfig binary, run cmdeleteconf to remove the org copy & try to create the new binary. MC/SG reads the current binary when running cmcheck/applyconf commands even though you're trying to create a new one. Kind of like lvmtab & vgscan.

I can't remember for certain whether this is one of the MC/SG tasks that requires the cluster to be down or not.

Rgds,
Jeff

[THEUNISSEN, J]

It turned out to be a VLAN configuration problem, as soon as the lan 2 is also member of the particular VLAN the clusterconfiguration can be changed to have lan2 as standby network and it does work now.

Thanks for all the replies on this issue.