700 Implementing the IBM Storwize V7000 with IBM Spectrum Virtualize V8.2.1
After uploading the update utility test and Software update package to the cluster by using 
PSCP and running the utility test, complete the following steps:
1. Start by removing node 2, which is the partner node of the configuration node in iogrp 0, 
by using the cluster GUI or CLI.
2. Log in to the service GUI to verify that the removed node is in candidate status.
3. Select the candidate node and click Update Manually from the left pane.
4. Browse and locate the code that you downloaded and saved to your PC.
5. Upload the code and click Update.
When the update is completed, a message caption indicating software update completion 
displays. The node then reboots, and appears again in the service GUI after 
approximately 20 - 25 minutes in candidate status.
6. Select the node and verify that it is updated to the new code.
7. Add the node back by using the cluster GUI or the CLI.
8. Select node 3 from iogrp1.
9. Repeat steps 1 - 7 to remove node 3, update it manually, verify the code, and add it back 
to the cluster.
10.Proceed to node 5 in iogrp 2.
11.Repeat steps 1 - 7 to remove node 5, update it manually, verify the code, and add it back 
to the cluster.
12.Move on to node 7 in iogrp 3.
13.Repeat steps 1 - 7 to remove node 5, update it manually, verify the code, and add it back 
to the cluster.
14.Select node 4 from iogrp 1.
15.Repeat steps 1 - 7 to remove node 4, update it manually, verify the code, and add it back 
to the cluster.
16.Select node 6 from iogrp 2.
17.Repeat steps 1 - 7 to remove node 6, update it manually, verify the code, and add it back 
to the cluster.
18.Select node 8 in iogrp 3.
19.Repeat steps 1 - 7 to remove node 8, update it manually, verify the code, and add it back 
to the cluster.
20.Select and remove node 1, which is the configuration node in iogrp 0.
The removed configuration node becomes candidate, and you do not have to apply the 
code update manually. Add the node back to the cluster. It automatically updates itself and 
then adds itself back to the cluster with the new code.
Note: At this point, the update is 50% completed. You now have one node from each 
iogrp updated with the new code manually. Always leave the configuration node for last 
during a manual software update.
Note: A partner node becomes the configuration node because the original config node 
is removed from the cluster, which keeps the cluster manageable.