Article Number: 000022755
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-22.214.171.12457522.tgz.bin.gpg ) For OE 4.5+: /cores/service/user/ c) Copy the image to peer SP : scp /cores/service/Unity-126.96.36.19957522.tgz.bin.gpg peer:/cores/service For OE 4.5+: scp /cores/service/user/Unity-188.8.131.5257522.tgz.bin.gpg peer:/cores/service/user d) Delete the image from local SP (SPA in this example) : rm /cores/service/Unity-184.108.40.20657522.tgz.bin.gpg For OE 4.5+: rm /cores/service/user/Unity-220.127.116.1157522.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-18.104.22.16892909.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-22.214.171.12457522.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 = 126.96.36.19938882 Release date = 2017-02-09 14:30:02 2: ID = CAND_1 Type = candidate Version = 188.8.131.5292909 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 = 184.108.40.20692909 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
Dell EMC Unity Family
Dell EMC Unity Family
19 Jul 2023