Hello,
The issue was that one node was IBM and another Lenovo version.
We had to get the 2 that matches with a Lenovo machine type 69xx
Have a great day.
Original Message:
Sent: 9/12/2023 8:34:00 AM
From: Slawomir Bielawiec
Subject: RE: Help with V3700 : New node in candidate state but not seen in lsnodecandidate to be re-added.
Hello.
Have You downgraded the code version? What is the result? Do primary node see the second node as candidate?
Any further steps? What was the result because I have similar issue.
Best regards.
------------------------------
Slawomir Bielawiec
------------------------------
Original Message:
Sent: Mon June 05, 2023 09:17 AM
From: Justine Uwase
Subject: Help with V3700 : New node in candidate state but not seen in lsnodecandidate to be re-added.
Hi Evelyne,
First, thank you so much for your response.
We tried the Node rescue and it didn't work as Nodes don't see each other via lsservicenodes: Each node sees itself only ... For the new node, we have to use its service gui or via direct connection to get its information ...
I have obtained the old code version and we'll try to force downgrade the new node controller to 7.7 to see if this will allow the internode communication.
Stay turned !
Thank you again
Original Message:
Sent: 6/5/2023 5:30:00 AM
From: Evelyn Perez
Subject: RE: Help with V3700 : New node in candidate state but not seen in lsnodecandidate to be re-added.
Hi -
to clarify - the nodes DO see each other if they show up in sainfo lsservicenodes. lscandidatenodes will only show nodes that are valid clustering partners, which in this case they are not, as one is installed with an OEM FRU build image and one has the IBM product image. To correct this, you need to upgrade to the same code version as your cluster so they appear to be valid clustering partners.
------------------------------
Evelyn Perez
IBM Senior Technical Staff Member
IBM Storage Virtualize Software Architect for SVC and FlashSystem
Original Message:
Sent: Mon June 05, 2023 02:59 AM
From: Justine Uwase
Subject: Help with V3700 : New node in candidate state but not seen in lsnodecandidate to be re-added.
Hi Christian,
Yes long time, ended ....
I will try the Node rescue ... However, I I have little hope that it will work as the nodes do not see each other somehow ...
Thank you,
------------------------------
Justine Uwase
Original Message:
Sent: Fri June 02, 2023 08:56 AM
From: Christian Schroeder
Subject: Help with V3700 : New node in candidate state but not seen in lsnodecandidate to be re-added.
Hello Justine,
long time no hear ;)
Supposedly the spare part is not considered suitable as candidate due to its code level of 8.2.1.11.
You should attempt to go forward with a node rescue to downgrade the replacement node canister to the system's code level.
Log on to SAGUI > Select the Replacement Node (CANDIDATE!) > Re-install Machine Code > Rescue from another node
------------------------------
Christian Schroeder
IBM SpecV Storage Support with Passion
Original Message:
Sent: Thu June 01, 2023 06:04 AM
From: Justine Uwase
Subject: Help with V3700 : New node in candidate state but not seen in lsnodecandidate to be re-added.
Hello,
A node failed a while ago and then forced removed from the system.
Auditlog Entry 386
Sequence Num : 2886
Timestamp : Tue Jan 11 11:32:11 2022
: Epoch + 1641886331
Cluster User : ram
Challenge :
SSH IP Address :
Result Code : 0
Result Obj ID :
Action Cmd : svctask rmnode -force -gui 2
Source_Panel :
Target_Panel :
We have replaced the node which is now seen in candidate state but it is not seen by the system, thus lsnodecandidate is empty.
The new node is as follow:
node_status Candidate
node_product_mtm_copy 6535-HC4
node_FRU_part 01AC370
product_name IBM Storwize V5000
node_code_version 8.2.1.11
node_code_build 147.20.2007010940000
The current node in the system is as follow:
node_name node1
node_status Active
config_node Yes
product_MTM 6535-HC4
node_FRU_part 01LJ608
product_name Storage V3700 V2
node_code_version 7.7.1.4
node_code_build 130.16.1611221559000
svcinfo lsnodecandidate -delim :
svcinfo lsiogrp -delim :
id:name:node_count:vdisk_count:host_count:site_id:site_name
0:io_grp0:1:2:2:
sainfo lsservicenodes
panel_name cluster_id cluster_name node_id node_name relation node_status error_data
01-1 000000E020207ES2 V3700 1 node1 local Active
svcinfo lsnode -delim :
id:name:UPS_serial_number:WWNN:status:IO_group_id:IO_group_name:config_node:UPS_unique_id:hardware:iscsi_name:iscsi_alias:panel_name:enclosure_id:canister_id:enclosure_serial_number:site_id:site_name
1:node1::500507680G00xxxx:online:0:io_grp0:yes::T5L:iqn.1986-03.com.ibm:2145.v3700.node1::01-1:1:1:781xxxx::
Any idea why the nodes aren't seen each other ?
Can the difference in the code be the issue ?
or the fact that the new node is seen as V5000 instead of the V3700 ?
Any suggestion on how to get around this ?
Thank you
------------------------------
Justine Uwase
------------------------------