How to upgrade Unity OE code

Method 1 : Using Unisphere GUI

1. Go to the "settings" menu on Unisphere logged as "admin or equivalent user"



2. Navigate to "Software and Licenses > Software Upgrade"

Note:
In here it display the current Unity OE version you are on and also these 3 options

• Perform Health Checks
• Start Upgrade
• Download New Software

3 . When ready to start the Upgrade.

• Download the new software file from https://www.dell.com/support/home/en-us/product-support/product/unity-family/drivers
• Perform Health Checks (optional, as it will also be done in the wizard from "Start Upgrade")
• Click on "Start Upgrade" to launch the Upgrade Wizard.

4. "Perform Health Checks" option before upgrading

Note:
If there are warnings, address them first before performing the upgrade.

5. Upload the Unity OE upgrade file downloaded from https://www.dell.com/support/home/ site.

     
How it should look once the Unity OE file is uploaded:

Note:
After hitting "Next" button, the system will prepare the file for the Upgrade. This can take around 5-10 minutes.

Note: If the upgrade is cancelled after this step, make sure the image is deleted from /var/tmp/upgrade on the primary SP. Leaving the root FS in high usage could lead to SP panic.

6. Next step is deciding on when to reboot the SPs. If left selected, the SPs will reboot, one at a time while doing the upgrade. If unticked, you can reboot the SPs yourself at a later time (via "Resume Upgrade"). Default is to auto selected to allow the Unity to Reboot SPs as needed.


7. Review the summary page and make sure that you see the previous version to the new version

Note:
Please read the recommendation on when to do the upgrade.

8. Click on "Finish" button to start Unity OE upgrade.
If there are any errors during the upgrade, Refer the messages and remedies to "Retry". If any issue, contact your Service Provider. 
During the upgrade, the environment may show errors or alerts due to SP reboots, Space is not enough, etc.

9. After Unity OE upgrade complete, reload Unisphere. The new code should now show in the "Summary Tab" in "System View".

 

Method 2 : Using Command Line (uemcli)
1) Download the image first (We can use any clients that supports uemcli like windows, linux or even unity console itself. If Unity console is used, the image need to be copied to peer SP) Below is an example for a complete upgrade by uemcli.

 

a) SSH Login to the array using service account [Example: SPA is managing SP and SPB is peer SP ]
b) Get the upgrade image file using winSCP or sftp to /cores/service(Example: Unity-4.1.2.9257522.tgz.bin.gpg )
For OE 4.5+:
/cores/service/user/
c) Copy the image to peer SP : scp /cores/service/Unity-4.1.2.9257522.tgz.bin.gpg peer:/cores/service
For OE 4.5+:
scp /cores/service/user/Unity-4.1.2.9257522.tgz.bin.gpg peer:/cores/service/user
d) Delete the image from local SP (SPA in this example) : rm /cores/service/Unity-4.1.2.9257522.tgz.bin.gpg
For OE 4.5+:
rm /cores/service/user/Unity-4.1.2.9257522.tgz.bin.gpg
e) ssh to peer SP : ssh peer

 

 



2) Upload the image :
C:\> uemcli -d <unity_management_ip> -u admin -securePassword -upload -f c:\data\Unity-4.2.0.9392909.tgz.bin.gpg upgrade
Password:
Uploaded 2.01 GB of 2.01 GB [ 100%] -PROCESSING-
Operation Completed successfully

If the file was uploaded to Unity via SCP/SFTP:
uemcli -d <unity_management_ip> -u admin -securePassword -upload -f /cores/service/user/Unity-4.1.2.9257522.tgz.bin.gpg upgrade

Note: If the upgrade is cancelled after this step, make sure the image is deleted from /var/tmp/upgrade on the primary SP. Leaving the root FS in high usage could lead to SP panic.


3) Verify the image candidate ID
C:\> uemcli -d 10.0.0.1 -u admin -securePassword /sys/soft/ver show
Password:
1:    ID           = INST_1
      Type         = installed
      Version      = 4.1.1.9138882
      Release date = 2017-02-09 14:30:02

2:    ID           = CAND_1
      Type         = candidate
      Version      = 4.2.0.9392909
      Release date = 2017-06-28 11:28:31







4) Create (start) the upgrade (optional to specify pause before reboot, if not given full upgrade will start immediately):
C:\> uemcli -d 10.0.0.1 -u admin -securePassword /sys/soft/upgrade create -candId CAND_1 -pauseBeforeReboot

5) Monitor the upgrade :
C:\> uemcli -d 10.0.0.1 -u admin -securePassword /sys/soft/upgrade show -detail

6) Resume the upgrade if pause before reboot is given or any health checks failed (like Replication session not paused earlier) :
C:\> uemcli -d 10.0.0.1 -u admin -securePassword /sys/soft/upgrade resume

7) Verify after it completes

04:48:27 service@(none) spb:~> uemcli /sys/soft/ver show -detail

1:    ID              = INST_1
      Type            = installed
      Version         = 4.2.0.9392909
      Release date    = 2017-06-28 11:28:37
      Image type      =
      Reboot required =
      Pause allowed   =
      Image filename  =

04:48:36 service@(none) spb:~> uemcli /sys/soft/upgrade show -detail

1:    Status              = completed
      Creation time       = 2017-08-03 03:30:10
      Elapsed time        = 55m 36s
      Estimated time left =
      Progress            =
      Percent complete    = 100%

DELL EMC recommend performing Unity OE code upgrade during a low production period. There shouldn't be any DU/DL during the upgrade however may slow things down and have higher CPU utilization during the upgrade.

Prior to upgrade cores/service should have at least 5GB free space. Usually deleting old data collects is the best way to free up that space.

If upgrading to 4.5 or 4.5.1 see KB
Dell EMC Unity: Replication Data Store Not Updating after 4.5.0 or 4.5.1 upgrade (User Correctable) https://support.emc.com/kb/531543

This article has been promoted as HVC on DELL EMC Community Network (DECN): https://community.emc.com/docs/DOC-56665