- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Problem creating the cluster
Operating System - Linux
1748062
Members
5724
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2006 12:35 AM
тАО05-11-2006 12:35 AM
Problem creating the cluster
Hi,
I get this message when I create the cluster :
cmapplyconf -C $SGCONF/elites.config -v
Checking cluster file: /usr/local/cmcluster/conf/elites.config
Checking nodes ... Done
Checking existing configuration ... Done
Warning: Unable to get configuration for cluster elites.
cmapplyconf : Command can not be executed remotely.
Addition of node ELITE-00 to cluster elites is possible only when
command is issued from a node which is configured to be a part of the cluster.
Please login to one of the cluster member nodes of cluster elites
and reissue the command.
This appens on the 2 nodes.
Config file :
CLUSTER_NAME elites
QS_HOST elite-99
QS_POLLING_INTERVAL 120000000
QS_TIMEOUT_EXTENSION 2000000
NODE_NAME elite-00
NETWORK_INTERFACE bond0
HEARTBEAT_IP 10.10.165.83
NETWORK_INTERFACE bond1
HEARTBEAT_IP 192.168.0.1
NODE_NAME elite-01
NETWORK_INTERFACE bond0
HEARTBEAT_IP 10.10.165.84
NETWORK_INTERFACE bond1
HEARTBEAT_IP 192.168.0.2
HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 5000000
AUTO_START_TIMEOUT 600000000
NETWORK_POLLING_INTERVAL 2000000
MAX_CONFIGURED_PACKAGES 5
cmclnodelist:
ELITE-00 root
elite-00 root
10.10.165.83 root
192.168.0.1 root
ELITE-01 root
elite-01 root
10.10.165.84 root
192.168.0.2 root
ELITE-99 root
elite-99 root
10.10.165.86 root
192.168.0.3 root
Thanks.
Ben
I get this message when I create the cluster :
cmapplyconf -C $SGCONF/elites.config -v
Checking cluster file: /usr/local/cmcluster/conf/elites.config
Checking nodes ... Done
Checking existing configuration ... Done
Warning: Unable to get configuration for cluster elites.
cmapplyconf : Command can not be executed remotely.
Addition of node ELITE-00 to cluster elites is possible only when
command is issued from a node which is configured to be a part of the cluster.
Please login to one of the cluster member nodes of cluster elites
and reissue the command.
This appens on the 2 nodes.
Config file :
CLUSTER_NAME elites
QS_HOST elite-99
QS_POLLING_INTERVAL 120000000
QS_TIMEOUT_EXTENSION 2000000
NODE_NAME elite-00
NETWORK_INTERFACE bond0
HEARTBEAT_IP 10.10.165.83
NETWORK_INTERFACE bond1
HEARTBEAT_IP 192.168.0.1
NODE_NAME elite-01
NETWORK_INTERFACE bond0
HEARTBEAT_IP 10.10.165.84
NETWORK_INTERFACE bond1
HEARTBEAT_IP 192.168.0.2
HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 5000000
AUTO_START_TIMEOUT 600000000
NETWORK_POLLING_INTERVAL 2000000
MAX_CONFIGURED_PACKAGES 5
cmclnodelist:
ELITE-00 root
elite-00 root
10.10.165.83 root
192.168.0.1 root
ELITE-01 root
elite-01 root
10.10.165.84 root
192.168.0.2 root
ELITE-99 root
elite-99 root
10.10.165.86 root
192.168.0.3 root
Thanks.
Ben
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2006 04:08 AM
тАО05-11-2006 04:08 AM
Re: Problem creating the cluster
I think the problem is likely to be that you do not have the IP addresses for all interfaces configured as required by SG. You need to ensure that every IP address on every interface on every node in the cluster resolves to the hostname of that node or have this as an alias.
What I suspect is happening is that during the cmapplyconf when we switch from the bootstrap cmclnodelist file to the access control policies we suddenly do not recognise the interface the message is coming from as being within the cluster.
i.e. in your case you need to have something similar to this in /etc/hosts on all nodes:
10.10.165.83 elite-00
192.168.0.1 elite-00
10.10.165.84 elite-01
192.168.0.2 elite-01
You could have this setup as an alias if you do not want the primary lookup to be the same, i.e. you could also have the following instead:
10.10.165.83 elite-00
192.168.0.1 alt-00 elite-00
10.10.165.84 elite-01
192.168.0.2 alt-01 elite-01
if you have any lan cards with IP addresses which you have not configured in elites.config these still need to follow the same rules since these could be used for command access even if they are not configured as heartbeat lans.
I would expect that in the syslog (messages) file you will have messages indicating access is being attempted from unauthorised nodes listing either the IP addresses or the names.
If this does not resolve the problem then please paste any errors reported by cmclconfd processes from the syslog file here. However, I think this should resolve your issue.
What I suspect is happening is that during the cmapplyconf when we switch from the bootstrap cmclnodelist file to the access control policies we suddenly do not recognise the interface the message is coming from as being within the cluster.
i.e. in your case you need to have something similar to this in /etc/hosts on all nodes:
10.10.165.83 elite-00
192.168.0.1 elite-00
10.10.165.84 elite-01
192.168.0.2 elite-01
You could have this setup as an alias if you do not want the primary lookup to be the same, i.e. you could also have the following instead:
10.10.165.83 elite-00
192.168.0.1 alt-00 elite-00
10.10.165.84 elite-01
192.168.0.2 alt-01 elite-01
if you have any lan cards with IP addresses which you have not configured in elites.config these still need to follow the same rules since these could be used for command access even if they are not configured as heartbeat lans.
I would expect that in the syslog (messages) file you will have messages indicating access is being attempted from unauthorised nodes listing either the IP addresses or the names.
If this does not resolve the problem then please paste any errors reported by cmclconfd processes from the syslog file here. However, I think this should resolve your issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2006 06:14 AM
тАО05-11-2006 06:14 AM
Re: Problem creating the cluster
I've found that identd was not running.
After correcting that, no problem.
Thanks for your help.
After correcting that, no problem.
Thanks for your help.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP