1830749 Members
1970 Online
110015 Solutions
New Discussion

Re: Config MC problem

 
chuanpeng.wang
Frequent Advisor

Config MC problem




NODE_NAME L1000_2
NETWORK_INTERFACE lan0
HEARTBEAT_IP 192.1.1.2
NETWORK_INTERFACE lan1
HEARTBEAT_IP 133.195.232.3
NETWORK_INTERFACE lan2
FIRST_CLUSTER_LOCK_PV /dev/dsk/c9t2d0





HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 2000000



AUTO_START_TIMEOUT 600000000
NETWORK_POLLING_INTERVAL 2000000

MAX_CONFIGURED_PACKAGES 10

------------------------------------------------------------------
cmcheckconf return errors

L1000_1#[/etc/cmcluster]cmcheckconf -C cmclconf.ascii

Begin cluster verification...
Note : a NODE_TIMEOUT value of 2000000 was found in line 91. For a
significant portion of installations, a higher setting is more appropriate.
Refer to the comments in the cluster configuration ascii file or ServiceGuard
manual for more information on this parameter.
Error: Fail to load data from configuration database.
Error: Permission denied accessing node RP4440_2.
Error: Unable to connect to configuration database.
cmcheckconf : Unable to get cluster configuration information: Error on send

------------------------------------------------------------------
The RP4440_2 is not a node of the cluster and not in /etc/hosts. I don't know where it is from.
Is there anybody can help me?

Thanks.
3 REPLIES 3
RAC_1
Honored Contributor

Re: Config MC problem

your config file has reference to the other node. Does it exists and is it accessible? Do you want it in cluster? If yes, you need to check host/ip resolution from both nodes.
There is no substitute to HARDWORK
Geoff Wild
Honored Contributor

Re: Config MC problem

The RP4440_2 is not a node of the cluster - okay - well it is getting that from somewhere - did it used to be a node?

If yes, did you delete the cluster before trying to create this new one?

Does RP4440_2 resolve with DNS?

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
chuanpeng.wang
Frequent Advisor

Re: Config MC problem

There is another MC which has the same name in the subnet