VNXe 3150 OE Upgrade Process

The VNXe 3150 is a tidy little array that packs quite a punch, and I’m happy that I have access to one.

Image

It handles my CIFS and NFS storage as well as running a small vSphere VM load. I’m running my VMs over NFS as that’s what I work with in vLab and want a similar setup as a playground.

I handle all the management over it and try to keep up with the OE Upgrades. I saw an internal post recently looking for info on the OE upgrade steps and remembered I had taken some screen shots during my last upgrade. So for your reading pleasure let’s take a stroll through the process.

  1. Locating the latest release, or older releases for that matter couldn’t be easier. Pull up your favorite inter webs browser and point it at support.emc.com. Login with your credentials, you do have an account right? Select your product, and then click the Download section. You’ll see a list of all the great stuff available for that product, VNXe in our case, and select it to start the download to an appropriate location. I’ve just saved mine to the Download directory on the Server I use for management: Image
  2. Next I’ll point my browser to the Unisphere address of my VNXe and login. Navigate into ‘Settings->More configuration…->Update Software’. This is also where you can connect to download updates using ‘Obtain Candidate Version Online’ option in the lower left. I like browsing through the Support Download area just to see if there is something I missed…LOOK! Squirrel! :Image
  3. You’ll want to run a Health Check to make sure things are in good order, and Unisphere will let you know if not. Click on ‘Perform Health Check’ and then ‘Run’:Image
  4. If you come up a winner now you can upload the update, if not…fix that thing!
    Head back over to Support or ECN Forums and get some help if needed. Once you’re in the winners circle, click on ‘Upload Candidate Version’: Image
  5. It shouldn’t take too long and you’ll have the latest and greatest ready to go: Image
  6. Once uploaded the system checks the file integrity: Image
  7. Then lets you know things are in place: Image
  8. Clicking ‘Install Candidate Version’, and I know you want to, will bring up this handy little reminder, and you should follow the advice given: Image
  9. Now I would normally due this over a weekend, after backups completed, or during some other low usage window, but since I was taking some screen shots I ran this during the day with most of my VM’s suspended.
    **Read the Guides. Make sure you have good backups. Low or no I/O on the array and the Health Check was run without errors reported. And you have enough free space to run the upgrade. Read the Guides**
    Now we are ready to click ‘Install’ and watch the progress: Image
  10. In the Dual SP arrays the Peer SP gets the update applied first, and rebooted. Anything running on the Peer SP gets failed over to the Master SP, this is one reason you don’t want a load running when upgrading as you’ll see degraded performance: Image
  11. Once the Peer SP comes back up, the upgrade gets finalized, and the Master SP load moves to the Peer SP so the Master gets a turn for the upgrade reboot:Image
  12. Once the Master SP is back online and the load is shifted back to your original config the upgrade is complete! Woo Hoo! You’ll have to logout and back in to load the changes in Unisphere: Image
  13. Once logged back in you’ll see any changes in Unisphere, if there are new features that you are licensed for they will be available for use and nows a good time to check them out before you get busy… Image

I hope that was helpful, and maybe took away some of the intimidation of performing the upgrade. I can’t stress enough to read the guides, and check out the ECN Forums to post any questions or read what others have already posted…LOOK! Squirrel!

Advertisements