Node interfaces do not match cluster interface settings
Pages: 1 2
admin
2,930 Posts
August 14, 2019, 5:17 pmQuote from admin on August 14, 2019, 5:17 pmanother thing, the cluster_info shows that number of nics per node should be 13 whereas the node show 12 ? + earlier they were 9 ?
another thing, the cluster_info shows that number of nics per node should be 13 whereas the node show 12 ? + earlier they were 9 ?
Last edited on August 14, 2019, 5:19 pm by admin · #11
khopkins
96 Posts
August 14, 2019, 5:21 pmQuote from khopkins on August 14, 2019, 5:21 pmYes, this error is when loading node 2 through the web interface. Earlier I tried creating the "node_info.json" as it wasn't being created as in the error log, cleared the error in the log but the error for the "node status" was still there, just trying something as you can't break something that is broken 🙂 Right now, both Node1 and Node2 have been reloaded, with nothing done to them. Interfaces are acting normal so don't think its an issue now since changing them out. The error's you see are from a newly loaded system.
Yes, this error is when loading node 2 through the web interface. Earlier I tried creating the "node_info.json" as it wasn't being created as in the error log, cleared the error in the log but the error for the "node status" was still there, just trying something as you can't break something that is broken 🙂 Right now, both Node1 and Node2 have been reloaded, with nothing done to them. Interfaces are acting normal so don't think its an issue now since changing them out. The error's you see are from a newly loaded system.
khopkins
96 Posts
August 14, 2019, 5:30 pmQuote from khopkins on August 14, 2019, 5:30 pmThe number for the cluster changed as the network cards added had more ports. Right now both are reporting 13 as it should. 2 NICS w/4 ports = 8, + 4 ports built in, + the idrac = 13
The number for the cluster changed as the network cards added had more ports. Right now both are reporting 13 as it should. 2 NICS w/4 ports = 8, + 4 ports built in, + the idrac = 13
admin
2,930 Posts
August 14, 2019, 5:50 pmQuote from admin on August 14, 2019, 5:50 pmCan you download and run the following on both nodes ( do chmod +x )
https://drive.google.com/open?id=12_bxLnwfHRqIxqDJdLB64VfC-3HQJSTc
Can you download and run the following on both nodes ( do chmod +x )
https://drive.google.com/open?id=12_bxLnwfHRqIxqDJdLB64VfC-3HQJSTc
khopkins
96 Posts
August 14, 2019, 6:02 pmQuote from khopkins on August 14, 2019, 6:02 pmNode 1
cluster management interface eth4
node management interface eth4
management interface match
cluster eth count 13
node eth count 13
eth count match
detected interfaces
eth0
eth1
eth2
eth3
eth4
eth5
eth6
eth7
eth8
eth9
eth10
eth11
idrac
Node2
cluster management interface eth4
node management interface eth4
management interface match
cluster eth count 13
node eth count 12
Error: eth count mis-match !!
detected interfaces
eth4
eth0
eth1
eth2
eth3
eth5
eth6
eth7
eth8
eth9
eth10
eth11
Looks like the idac is missing!
Node 1
cluster management interface eth4
node management interface eth4
management interface match
cluster eth count 13
node eth count 13
eth count match
detected interfaces
eth0
eth1
eth2
eth3
eth4
eth5
eth6
eth7
eth8
eth9
eth10
eth11
idrac
Node2
cluster management interface eth4
node management interface eth4
management interface match
cluster eth count 13
node eth count 12
Error: eth count mis-match !!
detected interfaces
eth4
eth0
eth1
eth2
eth3
eth5
eth6
eth7
eth8
eth9
eth10
eth11
Looks like the idac is missing!
admin
2,930 Posts
August 14, 2019, 6:28 pmQuote from admin on August 14, 2019, 6:28 pmwe use a python lib which detect idrac as interface, i will post you fix in few minutes
we use a python lib which detect idrac as interface, i will post you fix in few minutes
Last edited on August 14, 2019, 6:29 pm by admin · #16
admin
2,930 Posts
August 14, 2019, 6:46 pmQuote from admin on August 14, 2019, 6:46 pmdownload this patch
https://drive.google.com/open?id=1KwwgV9oE6kJJeDPTbuMTKqmKLdZ_oJtK
apply to node 1, 2 ..:
patch -p1 -d / < interfaces-filter-idrac.patch
systemctl restart petasan-deploy
on node 1, change the cluster_info.json eth_count from 13 to 12 then re-deploy node 2, just refresh browser to first page of deployment wizard on node 2 should re-deploy.
download this patch
https://drive.google.com/open?id=1KwwgV9oE6kJJeDPTbuMTKqmKLdZ_oJtK
apply to node 1, 2 ..:
patch -p1 -d / < interfaces-filter-idrac.patch
systemctl restart petasan-deploy
on node 1, change the cluster_info.json eth_count from 13 to 12 then re-deploy node 2, just refresh browser to first page of deployment wizard on node 2 should re-deploy.
Last edited on August 14, 2019, 6:48 pm by admin · #17
khopkins
96 Posts
August 19, 2019, 2:29 pmQuote from khopkins on August 19, 2019, 2:29 pmWell it looks like we found the issue with the interfaces. Started over by wiping the BIOS and setting things to Default so all setting would be the same, idrac or not. Finally got Node 2 done. Kind of strange that it failed at first, than reload the page and it said it was good and awaiting the third node, but at least it joined. You guys are really great about responding to this forum and appreciate your help and input.
Well it looks like we found the issue with the interfaces. Started over by wiping the BIOS and setting things to Default so all setting would be the same, idrac or not. Finally got Node 2 done. Kind of strange that it failed at first, than reload the page and it said it was good and awaiting the third node, but at least it joined. You guys are really great about responding to this forum and appreciate your help and input.
Pages: 1 2
Node interfaces do not match cluster interface settings
admin
2,930 Posts
Quote from admin on August 14, 2019, 5:17 pmanother thing, the cluster_info shows that number of nics per node should be 13 whereas the node show 12 ? + earlier they were 9 ?
another thing, the cluster_info shows that number of nics per node should be 13 whereas the node show 12 ? + earlier they were 9 ?
khopkins
96 Posts
Quote from khopkins on August 14, 2019, 5:21 pmYes, this error is when loading node 2 through the web interface. Earlier I tried creating the "node_info.json" as it wasn't being created as in the error log, cleared the error in the log but the error for the "node status" was still there, just trying something as you can't break something that is broken 🙂 Right now, both Node1 and Node2 have been reloaded, with nothing done to them. Interfaces are acting normal so don't think its an issue now since changing them out. The error's you see are from a newly loaded system.
Yes, this error is when loading node 2 through the web interface. Earlier I tried creating the "node_info.json" as it wasn't being created as in the error log, cleared the error in the log but the error for the "node status" was still there, just trying something as you can't break something that is broken 🙂 Right now, both Node1 and Node2 have been reloaded, with nothing done to them. Interfaces are acting normal so don't think its an issue now since changing them out. The error's you see are from a newly loaded system.
khopkins
96 Posts
Quote from khopkins on August 14, 2019, 5:30 pmThe number for the cluster changed as the network cards added had more ports. Right now both are reporting 13 as it should. 2 NICS w/4 ports = 8, + 4 ports built in, + the idrac = 13
The number for the cluster changed as the network cards added had more ports. Right now both are reporting 13 as it should. 2 NICS w/4 ports = 8, + 4 ports built in, + the idrac = 13
admin
2,930 Posts
Quote from admin on August 14, 2019, 5:50 pmCan you download and run the following on both nodes ( do chmod +x )
https://drive.google.com/open?id=12_bxLnwfHRqIxqDJdLB64VfC-3HQJSTc
Can you download and run the following on both nodes ( do chmod +x )
https://drive.google.com/open?id=12_bxLnwfHRqIxqDJdLB64VfC-3HQJSTc
khopkins
96 Posts
Quote from khopkins on August 14, 2019, 6:02 pmNode 1
cluster management interface eth4
node management interface eth4
management interface match
cluster eth count 13
node eth count 13
eth count match
detected interfaces
eth0
eth1
eth2
eth3
eth4
eth5
eth6
eth7
eth8
eth9
eth10
eth11
idrac
Node2
cluster management interface eth4
node management interface eth4
management interface match
cluster eth count 13
node eth count 12
Error: eth count mis-match !!
detected interfaces
eth4
eth0
eth1
eth2
eth3
eth5
eth6
eth7
eth8
eth9
eth10
eth11Looks like the idac is missing!
Node 1
cluster management interface eth4
node management interface eth4
management interface match
cluster eth count 13
node eth count 13
eth count match
detected interfaces
eth0
eth1
eth2
eth3
eth4
eth5
eth6
eth7
eth8
eth9
eth10
eth11
idrac
Node2
cluster management interface eth4
node management interface eth4
management interface match
cluster eth count 13
node eth count 12
Error: eth count mis-match !!
detected interfaces
eth4
eth0
eth1
eth2
eth3
eth5
eth6
eth7
eth8
eth9
eth10
eth11
Looks like the idac is missing!
admin
2,930 Posts
Quote from admin on August 14, 2019, 6:28 pmwe use a python lib which detect idrac as interface, i will post you fix in few minutes
we use a python lib which detect idrac as interface, i will post you fix in few minutes
admin
2,930 Posts
Quote from admin on August 14, 2019, 6:46 pmdownload this patch
https://drive.google.com/open?id=1KwwgV9oE6kJJeDPTbuMTKqmKLdZ_oJtK
apply to node 1, 2 ..:
patch -p1 -d / < interfaces-filter-idrac.patch
systemctl restart petasan-deployon node 1, change the cluster_info.json eth_count from 13 to 12 then re-deploy node 2, just refresh browser to first page of deployment wizard on node 2 should re-deploy.
download this patch
https://drive.google.com/open?id=1KwwgV9oE6kJJeDPTbuMTKqmKLdZ_oJtK
apply to node 1, 2 ..:
patch -p1 -d / < interfaces-filter-idrac.patch
systemctl restart petasan-deploy
on node 1, change the cluster_info.json eth_count from 13 to 12 then re-deploy node 2, just refresh browser to first page of deployment wizard on node 2 should re-deploy.
khopkins
96 Posts
Quote from khopkins on August 19, 2019, 2:29 pmWell it looks like we found the issue with the interfaces. Started over by wiping the BIOS and setting things to Default so all setting would be the same, idrac or not. Finally got Node 2 done. Kind of strange that it failed at first, than reload the page and it said it was good and awaiting the third node, but at least it joined. You guys are really great about responding to this forum and appreciate your help and input.
Well it looks like we found the issue with the interfaces. Started over by wiping the BIOS and setting things to Default so all setting would be the same, idrac or not. Finally got Node 2 done. Kind of strange that it failed at first, than reload the page and it said it was good and awaiting the third node, but at least it joined. You guys are really great about responding to this forum and appreciate your help and input.