Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Node interfaces do not match cluster interface settings.


khopkins
96 Posts
July 27, 2018, 2:10 pm

Running a cluster of 3 nodes with similar hardware (Dell R410) using two NICS, running well.  Decided to join another node (dissimilar hardware) (Dell R720) to the cluster with has 4 10/100 with 2 "Two port 10G" NICS (x710) and more hard drives.  For testing just using eth0 and eth1.  All connected to same switch.  When trying to join the cluster I get the "node interfaces do not match...".  Did read the other post on this but need to ask the question that all nodes must have the same amount of NICS even though I only have two active?   Eth_count are the same.  By the file config, it was talking to something.

cluster_info.json  ( NEW NODE-4)
{
{
"backend_1_base_ip": "10.0.4.0",
"backend_1_eth_name": "eth0",
"backend_1_mask": "255.255.255.192",
"backend_2_base_ip": "10.0.5.0",
"backend_2_eth_name": "eth1",
"backend_2_mask": "255.255.255.192",
"bonds": [],
"eth_count": 2,
"iscsi_1_eth_name": "eth0",
"iscsi_2_eth_name": "eth1",
"jumbo_frames": [],
"management_eth_name": "eth0",
"management_nodes": [
{
"backend_1_ip": "10.0.4.30",
"backend_2_ip": "10.0.5.30",
"is_iscsi": true,
"is_management": true,
"is_storage": true,
"management_ip": "172.16.14.30",
"name": "PS-NODE-1"
},
{
"backend_1_ip": "10.0.4.31",
"backend_2_ip": "10.0.5.31",
"is_iscsi": true,
"is_management": true,
"is_storage": true,
"management_ip": "172.16.14.31",
"name": "PS-NODE-2"
},
{
"backend_1_ip": "10.0.4.32",
"backend_2_ip": "10.0.5.32",
"is_iscsi": true,
"is_management": true,
"is_storage": true,
"management_ip": "172.16.14.32",
"name": "PS-NODE-3"
}
],
"name": "XenServer"

 

EXISTING NODE 1

cluster_info.json
{
"backend_1_base_ip": "10.0.4.0",
"backend_1_eth_name": "eth0",
"backend_1_mask": "255.255.255.192",
"backend_2_base_ip": "10.0.5.0",
"backend_2_eth_name": "eth1",
"backend_2_mask": "255.255.255.192",
"bonds": [],
"eth_count": 2,
"iscsi_1_eth_name": "eth0",
"iscsi_2_eth_name": "eth1",
"jumbo_frames": [],
"management_eth_name": "eth0",
"management_nodes": [
{
"backend_1_ip": "10.0.4.30",
"backend_2_ip": "10.0.5.30",
"is_iscsi": true,
"is_management": true,
"is_storage": true,
"management_ip": "172.16.14.30",
"name": "PS-NODE-1"
},
{
"backend_1_ip": "10.0.4.31",
"backend_2_ip": "10.0.5.31",
"is_iscsi": true,
"is_management": true,
"is_storage": true,
"management_ip": "172.16.14.31",
"name": "PS-NODE-2"
},
{
"backend_1_ip": "10.0.4.32",
"backend_2_ip": "10.0.5.32",
"is_iscsi": true,
"is_management": true,
"is_storage": true,
"management_ip": "172.16.14.32",
"name": "PS-NODE-3"
}
],
"name": "XenServer"

 

/petascan.log

 

27/07/2018 10:14:29 ERROR    Config file error. The petaSAN os maybe just insta
lled.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/PetaSAN/backend/cluster/deploy.py", lin
e 56, in get_node_status
node_name = config.get_node_info().name
File "/usr/lib/python2.7/dist-packages/PetaSAN/core/cluster/configuration.py",
line 103, in get_node_info
with open(config.get_node_info_file_path(), 'r') as f:
IOError: [Errno 2] No such file or directory: '/opt/petasan/config/node_info.jso
n'
27/07/2018 10:14:47 INFO     Starting node join
27/07/2018 10:14:47 INFO     Successfully copied public keys.
27/07/2018 10:14:48 INFO     Successfully copied private keys.
27/07/2018 10:14:48 INFO     password set successfully.
27/07/2018 10:14:49 INFO     Start copying  cluster info file.
27/07/2018 10:14:49 INFO     Successfully copied cluster info file.
27/07/2018 10:14:49 INFO     Joined cluster XenServer

Strange thing is that going back to the /opt/petasan/conf there is nothing in the directory and its acting strange and unable to do anything, rebooted and same thing.

root@PS-NODE-4:/opt/petasan# cd config
root@PS-NODE-4:/opt/petasan/config# ls
^C
exit

Had to reconnect, same thing.

 

Last edited on July 27, 2018, 3:25 pm by khopkins · #1

admin
2,930 Posts
July 27, 2018, 3:16 pm

The number of interfaces  must be the same and the management interface defined during the installer must be the same interfaces number...so in your case the joining node needs to have exactly eth0 and eth1  and its management interface is on eth0.

Last edited on July 27, 2018, 3:17 pm by admin · #2