Celerra VSA, VirtualAppliances

UBERTastic : Celerra UBER VSA v3 – Unisphere

Man this has been a busy couple months. I have a whole different blog post about VMworld and the MADNESS. But suffice to say I have been busy. So busy in fact that I didn’t really have time to work on the new Celerra UBER VSA until this week. Which also happens to be a week vacation for me.

Now for a normal 9-5 kind of guy, working a little bit on your vacation is ok. Some people frown, some people smile and approve. But, on the vSpecialists this is a big "no-no". So because of my strong desire to get this awesome piece of virtual goodness in your hands I have risked the smack down from my teammates and managers for working on it during my vacation. I shall likely be banned from a console for a bit so remember me when you are checking out the UBER cool new Unisphere interface.

And so I am excited to announce the release of the Celerra UBER VSA version 3.
I got quite a bit of new features as well as the new code/management interface you have been hearing about. Here is the list of changes and additions:

  • DART is now 6.0.36.4
  • Unisphere management console (rocks!)
  • The Celerra VSA is now 64 bit! This means you can throw RAM at it for bigger setups and it will use it. Over 8GB becomes less beneficial without code changes to simulation services. Future updates will fix this from the Celerra VSA engineering teams.
  • The biggest and most difficult change to construct is that the configuration is now adaptive depending on the virtual machine setup. This version is now intelligent in seeing how many resources you have given it.
  • The new Celerra UBER VSA uses this intelligence to now allow *Thin* mode. If you give the VSA under 2GB of RAM it will automatically size the memory limits, processes, and management interface settings to allow it to run with as low as 1024MB of RAM. You won’t do replication or host a ton of VM’s but you can use this mode to host a few and fully demonstrate/test the new Unisphere interface on even a 2GB laptop.
  • The new VSA also uses this intelligence to automatically allow the configuration of single or dual Data Mover version based on the memory assigned. If you give the VSA more than 4GB of memory you will be given the option to enable an additional Data Mover for use as a standby or load balancing experimentation. This means this single appliance can be a small lightweight NFS unit at 1024MB of RAM or can be a 2 Data Mover powerhouse at 8GB of RAM. All automatically configured on first boot through the wizard.
  • Automatic VMDK/Storage additions have been adjusted for new 64 bit OS. This means this still works. Shutoff the VM, add VMDK(s), turn on and you have more space. Automagic
  • Since automagic is so cool, I have changed the Data Mover Ethernet binding to be automatic also. The VM starts with 1 interface for management and 1 interface for the Data Movers. If you want more for the DM(s), just shutoff the VM, add NIC cards (up to 6 additional), and turn back on. It will automatically bind the Data Mover (yes it works with the 2 DM mode also) to the new interfaces and virtual slots. Just go back into Unisphere and assign away. This allows scale up for the bigger 2 Data Mover 8GB of RAM versions easily.
  • Configuration is now Perl/Bash based instead of just Bash to keep things cleaner and slicker and allow for some coolness later on ;)
  • NTP from the configuration portion of the wizard works correctly. It sets both the Control Station and all Data Movers and enables NTP as a running service. Make sure your NTP server is valid.

So let’s summarize:

  1. New Unisphere
  2. 64 Bit
  3. Automatic sizing
  4. Thin Mode
  5. Optional 2 Data Mover mode
  6. Automatic Data Mover Ethernet adding (along with fixed Storage [VMDK] adding)
  7. NTP works now

Just my opinion but this my favorite version yet. Even without one single piece of my code this version is faster than the last.

Couple things to note:

Adding an extra Data Mover can extend the setup time up to 5-10 minutes depending on your hardware. I will speed this up in the future but for now this is a one-time penalty for being Data Mover greedy. Also remember to give it the extra RAM/vCPU before turning it on the first time.

You cannot change the number of Data Movers without redeploying a new version. Once it is born with two heads it stays that way. Same thing with the Thin mode. Once it is deployed Thin, adding more RAM will not refactor the VSA.

Thin mode (< 2GB of RAM) will still incur some mild swapping the closer to 1024MB you get. If you have a laptop with an SSD putting the first drive on it will almost completely negate any noticeable slowdown with mild loads.

From now on Eth0 is the management interface. This corresponds to NIC1 in your VM. Every other interface after is for the Data Movers and will start at CGE0 and increment. So NIC2 is Eth1 is CGE0 (per DM) inside Unisphere and NIC3 is Eth3 is CGE1 inside Unisphere. Pretty easy…

Now that this is 64 bit you can no longer run it inside a virtual ESX(i) inside Workstation 7. It has to be run directly on ESX(i) or Workstation 7.

Now get to downloading… (***UPDATE links below are the updated 3.2 version fixing 3.0/3.1 bugs. ****) – LINK

Workstation Version
(MD5: a2136179d4d9544e4f8e3b43b7cc182e)

vSphere Version OVA
(MD5: c3d8abfb536aecca34c83d318c2c3e5f)

Ton of work, ton of lost brain cells so pretty please comment and provide feedback. I am releasing videos on how to configure very soon and maybe a surprise or two. If there is something you would like to see please leave it in the comments below.

.nick

54 thoughts on “UBERTastic : Celerra UBER VSA v3 – Unisphere

  1. Pingback: Tweets that mention UBERTastic : Celerra UBER VSA v3 - Unisphere | Nickapedia -- Topsy.com

  2. Pingback: EMC Unisphere in your pocket! Announcing the UBER VSA 3! (Now with low sodium!) | Christopher Kusek, Technology Evangelist

  3. Pingback: Hyper-V R2 homelab setup and Live Migration Demo | techietom.co.uk

  4. fanbloodytastic. About to deploy a couple of nested vsphere 4.1 environments and configure the nested datastores with Uber V3. Planning on installing SRM and VAAI plugins for unishere.. any issues with this you’re aware of before I crack on ? Will the Vstorage API plugins work with this and the SRM SRA’s for Celerra replicator?

    • Anonymous

      VAAI needs Flare 30 which isn’t a part of this VSA. So no you won’t be able to use VAAI. The SRA will work with one caveat which I am nailing down now. Watch for a post today about it.

  5. Pingback: vFail BrownBag Follow-Up!

  6. Steve

    I cant get to the login screen… just get a blue screen. IE says that the certificate isn’t valid. Any ideas?

  7. John

    When I choose the 2 datamover install after powering on VSA for first time the following message is logged during the startup script: Failed to initialize internal network for server in slot 3 …. network cable or hardware problem. Then via unispehre its hows server_3 at a boot_level=4. I have rebooted server_3 with no luck running version 6.0.36 -4. Thanks!

  8. Pingback: vTARDIS wins Best of Show at VMworld Europe 2010 « Virtualization, Windows, Infrastructure and all that stuff in-between

  9. Paul Aviles

    I am getting horrendous performance on the VSA, tried on vSphere 4 and also on a DL 320 HP server directly (No VM) and in both cases the IO is very restricted. Even for a test lab it is way too slow. Also, it seems that the interface is not complately the same as with the new Unisphere or am I wrong? On the real thing you can open up a browser and connect to one of the DM’s IP addresses, I was not able to get that done on the VSA.

    Regards,

    Paul Aviles

  10. Fred

    I have same issue with performance as Paul, and no matter where I place VSA – on local SAS drive or on fast FC storage the performance is terrible. Maybe I’m doing something wrong but even for a testing it is useless for me. Any advice?

  11. Arash Ghazanfari (EMC)

    Hi Nick,

    The VSA Works like a charm on the iMac. Thanks for all the hard work you’ve put into this.

    Cheers,

    Arash

  12. Pingback: Calivirtualization » Blog Archive » Uber-Celerra… Part II

  13. Pingback: Installing the EMC Celerra UBER VSA in your VMware vSphere Lab – Part 2 | TechHead.co.uk

  14. lcg

    I’m a bit confused…is the Celerra Uber VSA v3.2 supposed to come with pvscsi support? Is it supposed to have a SCSI controller for Hard Drive 1? I just downloaded it twice, and it seems to start with an IDE controller for the boot disk. I was able to switch it to a SCSI disk, but I can’t for the life of me get a paravirtual disk to work. It seems the pvscsi driver isn’t available to recognize the controller. So I started down the road of installing/updating VMware Tools, but without gcc I can’t compile the pvscsi driver. Am I going down a rabbit hole unnecessarily? Any assistance would be greatly appreciated! Thanks for all your hard work!

  15. Pingback: Hardware is Hard, Software is Easy. is 2011 the year of the VSA? « Virtualization, Cloud, Infrastructure and all that stuff in-between

  16. das

    I downloaded the ova (eventually, ftp is far to slow and my isp traffic shape bit torrents, can we not have a traditional download of this, or stick it in the virtual appliances over at vmware.com). all I’m getting when trying to login is a blue screen. will try it on my other 2 lab servers though.

  17. Pingback: vSphere Integration With EMC Unisphere » boche.net – VMware Virtualization Evangelist

  18. Pingback: vSphere Integration With EMC Unisphere | Lee's Notes

  19. ThomasF

    Hi

    Is it possible to use the VTLU funtion in this VM? I have added some scsi tape-devices to the VM, and I can see them from the Linux kernel, but is it possible to use them in the Celerra part?

    Thomas

  20. Pingback: How to create a vSphere lab on a Mac | WEBESTIGATE

  21. Chris

    Hi, I am trying to install the ova package and get the error “failed to deploy ova package. the request was aborted” when the install is at 99%. I tried unpacking the ova to ovf and installing it but get the error “Failed to deploy ovf package. The remote server returnned an error: (500) Internal Server Error”
    This is through VCenter 4.0 and ESXi 4.0.
    How can I deploy this?
    Thanks

  22. Pingback: Hyper-V R2 homelab setup and Live Migration Demo | techietom.co.uk

  23. Pingback: Virtual Storage Appliances | virtualstoragespeak

  24. Captain KnowItNot

    Nick, first of all, thank you so much for putting this up and for maintaining it with the latest and greatest software. This is where I’m doing all of my training basically (so I don’t break the real thing). I was wondering if there was a way to load this VSA on any other hypervisors such as VirtualBox? I use Virtualbox regularly at home and on some machines in the office which are available exclusively to me as lab/demo equipment. I tried to load the vSphere version, but it always fails right in the end saying that its already attached to Device O. Basically what I need is a way to get it to unmount from its base default so I can assign other disks to it (I think)?

  25. Ramlan

    I want to try ova version on vsphere. I tried downloading from the link. The download fails due to corruption. Can anybody share me a working copy of ova here. I would appreciate that.

  26. Eko Purwanto

    I also want to try this, but unfortunately download link are invalid, is there anyway i can get those files, thanks

  27. Pingback: Hacking Site Recovery Manager (SRM) / a Storage Array Adaptor

  28. jimmy

    Hello,
    I downloaed the VSA for vmware workstations 8, but I’m facing a problem that network wizard, interface wizard, route wizard, setup Celera wizard are not working. When I click at any of them, nothing happen. I tried Explorer, Chrom, Firexfox and all are the same. Is this a known issue for any of you guys?  Any help will be highly appreciated.

    Thanks,

    Jimmy

  29. Pingback: My road to a Virtual Lab: Storage « El blog de virtualizacion en Mexico – Jose B Ruelas Blog

  30. Pingback: Installing the EMC Celerra UBER VSA in your VMware vSphere Lab – Part 2 - TechHead

Comments are closed.