<span style=" font-size:10pt;font-family:sans-serif">Felipe,</span><br><br><span style=" font-size:10pt;font-family:sans-serif">You are correct.
The code is restricted to 4.2.2 or higher. If there is an ESS storage cluster
in the environment then the recommendation I was told is 4.2.3.7 or higher.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">Luke,</span><br><br><span style=" font-size:10pt;font-family:sans-serif">If your clients
are in the same cluster then you need to be careful with the setting to
minReleaseLevel, Exactly as it sounds, it will restrict membership to this
level or higher. </span><br><br><span style=" font-size:10pt;font-family:sans-serif">I have a client
running with filesystem version 3.5.0.7 in several clusters.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">We just recently
upgraded their ESS systems to the current release so I can verify that
the file system format will carry fine. </span><br><br><span style=" font-size:10pt;font-family:sans-serif">If you have ESS
at 5.3.3 or higher, then the GNR recommendation is 4.2.3.7 or higher for
the clients (my client can't go to v5 due to the RHEL version requirement)
and they must be in a remote cluster.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">In my case we
upgraded an ESS storage cluster to 4.1.1 to 5.0.3.3 (ESS v5.3.4.1)  and
for GNR we had to update this cluster to LATEST for minReleaseLevel which
is 5.0.3. </span><br><br><span style=" font-size:10pt;font-family:sans-serif">The client cluster
is running 4.2.3.18 which is as Felipe says is N-1 and minReleaseLevel
is set to 4.2.3.7</span><br><br><span style=" font-size:10pt;font-family:sans-serif">This client cluster
also mounts from another storage cluster  which is constrained to
run at 4.1.1-8. This makes the client cluster at N+1 from its relationship
with this cluster.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">All three clusters
have minReleaseLevel set to LATEST (4.1.0, 4.2.3.7,5.0.3 , respectively).</span><br><br><span style=" font-size:10pt;font-family:sans-serif">These changes
would not work in a single cluster as all nodes would be restricted to
the 4.1.0 or higher and the ESS would not be able to co-exist since it
requires the 5.0 level.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">We have updated
the file systems in the 4.1.1-8 cluster from 3.5.0.7 to 4.1.1 and we updated
the ESS filesystems from 3.5.0.7 to 5.0.3 (compat mode)</span><br><br><span style=" font-size:10pt;font-family:sans-serif">The changes all
went well.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">Hopefully this
helps you understand the nuance that is whether the clients and NSDs are
in a single cluster or different clusters. The rules are slightly but importantly
different.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">Also, when updating
the filesystem versions make sure you use the "compat" flag if
you have any remote clusters. If we would have run this with the "full"
flag on the ESS storage cluster, it would have prevented the 4.2.3.18 client
cluster  from mounting its file systems.</span><br><br><span style=" font-size:10pt;font-family:sans-serif">thanks,</span><br><span style=" font-size:10pt;font-family:sans-serif">Steve</span><br><br><br><span style=" font-size:10pt;font-family:Arial">Steven A. Daniels</span><br><span style=" font-size:10pt;font-family:Arial">Cross-brand Client
Architect</span><br><span style=" font-size:10pt;font-family:Arial">Senior Certified IT
Specialist</span><br><span style=" font-size:10pt;font-family:Arial">National Programs</span><br><span style=" font-size:10pt;font-family:Arial">Fax and Voice: 3038101229</span><br><a href="mailto:sadaniel@us.ibm.com"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>sadaniel@us.ibm.com</u></span></a><br><a href="http://www.ibm.com/"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>http://www.ibm.com</u></span></a><br><img src=cid:_2_10815644108153D8005D7CF1872584BA style="border:0px solid;"><br><br><br><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
       </span><span style=" font-size:9pt;font-family:sans-serif">"Felipe
Knop" <knop@us.ibm.com></span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
       </span><span style=" font-size:9pt;font-family:sans-serif">gpfsug-discuss@spectrumscale.org</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
       </span><span style=" font-size:9pt;font-family:sans-serif">gpfsug-discuss@spectrumscale.org</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
       </span><span style=" font-size:9pt;font-family:sans-serif">11/21/2019
09:49 PM</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
       </span><span style=" font-size:9pt;font-family:sans-serif">[EXTERNAL]
Re: [gpfsug-discuss] Compatibility question</span><br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by:        </span><span style=" font-size:9pt;font-family:sans-serif">gpfsug-discuss-bounces@spectrumscale.org</span><br><hr noshade><br><br><br><span style=" font-size:10pt;font-family:Arial">George,</span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial">Coexistence either
in the same cluster or across remote clusters is only supported with versions
"N" and "N-1". 5.0.3 and 3.5 are "N" and
"N-3", and this is not supported. If I recall, there is even
logic in place that will prevent 5.x nodes from accepting connections from
nodes running below 4.2 .</span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial">  Felipe</span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial">----<br>Felipe Knop knop@us.ibm.com<br>GPFS Development and Security<br>IBM Systems<br>IBM Building 008<br>2455 South Rd, Poughkeepsie, NY 12601<br>(845) 433-9314 T/L 293-9314<br> </span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial">----- Original message
-----<br>From: Luke Raimbach <luke.raimbach@googlemail.com><br>Sent by: gpfsug-discuss-bounces@spectrumscale.org<br>To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br>Cc:<br>Subject: [EXTERNAL] Re: [gpfsug-discuss] Compatibility question<br>Date: Thu, Nov 21, 2019 8:12 PM<br>  </span><br><span style=" font-size:10pt;font-family:Arial">That would make my
eyes water and maybe fall out. Yours might too of you try it. </span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial">Be very careful with
v3 upgrades, especially going up to v5 directly.</span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial">You will certainly
run into RPC incompatibility problems with the v3 and v5 nodes running
concurrently. Staying within the supported envelope of "one major
version" difference will ease the raising of support tickets with
IBM if you run into problems.</span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial">Why can't you upgrade
the clients?</span><br><span style=" font-size:10pt;font-family:Arial">  </span><br><span style=" font-size:10pt;font-family:Arial">On Thu, 21 Nov 2019,
18:24 George Terry, <</span><a href="mailto:gterryc@vmsupport.com" target="_blank"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>gterryc@vmsupport.com</u></span></a><span style=" font-size:10pt;font-family:Arial">>
wrote:</span><br><span style=" font-size:10pt;font-family:Arial">Hello,<br><br>I have a question about compatibility between two different versions. I
have a cluster with 6 gpfs nodes. 2 of them are NSD servers the other 4
are clientes nodes. I will upgrade the NSD servers from 3.5.0 to 5.0.3.
 Due to application's  issues I cannot update the client nodes.
So, my question is, can i have a cluster with client nodes with 3.5.0.7
version and the NSD nodes in 5.0.3 version with de filesystem in 3.5.0.7
(13.23) version?<br><br>Thanks for the support. </span><br><span style=" font-size:10pt;font-family:Arial"> </span><br><span style=" font-size:10pt;font-family:Arial">George</span><p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:10pt;font-family:Arial">_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at </span><a href="http://spectrumscale.org" target="_blank"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>spectrumscale.org</u></span></a><span style=" font-size:10pt;color:blue;font-family:Arial"><u><br></u></span><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank"><span style=" font-size:10pt;color:blue;font-family:Arial"><u>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</u></span></a></p><br><tt><span style=" font-size:10pt">_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org</span></tt><tt><span style=" font-size:10pt;color:blue"><u><br></u></span></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target="_blank"><tt><span style=" font-size:10pt;color:blue"><u>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</u></span></tt></a><tt><span style=" font-size:10pt"></span></tt><br><span style=" font-size:10pt;font-family:Arial"> </span><br><tt><span style=" font-size:10pt">_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></span></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><span style=" font-size:10pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></tt></a><tt><span style=" font-size:10pt"><br></span></tt><br><br><BR>