Monday, November 8, 2010

Upgrading NetApp Virtual Storage Console from 2.0 to 2.0.1 for VMware vSphere

This post isn’t going to particularly interesting as it’s just screenshots of what it looks like to do an inplace upgrade of NetApp’s Virtual Storage Console from 2.0 to 2.0.1. What’s worth mentioning is that the reason why an inplace upgrade had to be done was because of the problems we had when we simply installed 2.0.1 onto a brand new vCenter installation. The following are the details:

  1. Created a new Windows 2008 R2 64-bit virtual machine.
  2. Installed vCenter with a local SQL express instance as the database.
  3. Added ESXi 4.1.0 hosts to vCenter.
  4. Configured SNMP, alarms, etc.
  5. Installed VSC 2.0.1 (VSC-2.0.1-win64).

After number 5, all hell broke loose. It started with a page cannot be displayed when we try to access the registration page at: https://localhost:8143/Register.html then figuring that we should try uninstalling and reinstalling, we found that we could not get the application to uninstall. Every time we uninstall the application in Programs and Features, hit F5, we’d see the VSC application get relisted. Proceeding to going into the registry and removing all the occurrences of the application didn’t help and soon rendered the server unusable. Seeing how we couldn’t get any further, we rebuilt the virtual machine, reinstalled vCenter and proceeded to install 2.0, then 2.0.1 to upgrade it. The upgrade was successful and VSC appears to work properly so I won’t be able to provide a root cause. If you’re interested in seeing what the 2.0 install looks like, see this post: http://terenceluk.blogspot.com/2010/10/installing-netapp-virtual-storage.html

For the inplace upgrade, see the following:

image

image

image

image

image

image

image

image

There you have it.

8 comments:

Dan said...

I have the exact same problem with my VSC 2.0.1 install where it won't fully remove or install correctly, how pleasant.

Terence Luk said...

Hi Dan,

We had no luck cleaning it out via the registry and ended up redeploying the virtual machine (vCenter) to proceed with a 2.0 install then a 2.0.1 upgrade. We never called NetApp support after getting it to work so we still don't know what causes this.

Dan said...

I'm going to call netapp support today so we'll see how it goes. I'll post back with the solution.

Terence Luk said...

Thanks for the reply Dan. I look forward to seeing what NetApp says about this issue.

Dan said...

The Netapp rep said to remove all instances of 'Virtual Storage Console' from the registry and run it again.

What I did:
-run the uninstall
-backed up my entire registry
-go through the registry and remove anything with 'Virtual Storage Console' in it.
-I then logged in as a different local administrative account, ran the installer 'as administrator' and then it installed successfully.

Terence Luk said...

Hi Dan,

Thanks for getting back with the resolution that worked for you. We actually tried that as well but I suspect that since my colleague isn't much of a Windows person, he probably removed some keys he wasn't supposed to thus rendering the whole virtual machine unusable. Great to know it worked for you.

Anonymous said...

Hi Dan

your procedure worked for me to
thanks
DC

Gexton said...

This post isn’t going to particularly interesting as it’s just screenshots of what it looks like to do an inplace upgrade of NetApp’s Virtual Storage Console from 2.0 to 2.0.1. What’s worth mentioning is that the reason why an inplace upgrade had to be done was because of the problems we had when we simply installed 2.0.1 onto a brand new vCenter installation. The following are the details:
Virtual assistant Alberta
Virtual Business Solution Canada