you need to work this with service since it also depends on Flare revs.
It might be a two-step process
Most likely you will also want / need upgrade the replication sessions to Replicator V2
i have two celerra boxes..
The source box is having one clariion attached to it with flare code 3.24 and there is a destination DR nas with two clarion boxes attached to it.
One is running on flare 3.24 and another one is having flare 3.26.
The nas code is 5.5.29 on both the boxes.
So how can be the upgrade done...here in this environemnt.
you need to open a service request to get that planned.
5.6.49 does support Flare code 24, 26, 28 and 29, therefore it should be safe to first upgrade both NAS box to 5.6.49. In general, the destination NAS box will be upgraded first, while all replication session are manually paused during the upgrade/maintenance window. Following by the upgrade on the source system. If backend Flare code is needed, it would immeditaely upgrade to the CLARiiON array to Flare 26. (Primus emc186425). When all NAS and Flare code upgrade are done, resume the replication sessions. Replication V1 to V2 upgrade can be schedule to different date.
This is a general idea. When CCA is sumbitted by your local CE. Local team will do health check and review all configuration rules/warning in details before proceeding further.
i don't think primus emc186425 is customer viewable, i can't find it.
That's correct. This KB is not open for customer view, but it basically says you cannot keep release 24 on the backend with NAS code 5.6.
We can upgrade the box to 5.6 while the backend is running rel 24, but an upgrade to rel 26 should be done right after the NAS code upgrade.