Home > EMC, VMware > Configuring VASA with EMC arrays – CLARiiON, VNX and VMAX

Configuring VASA with EMC arrays – CLARiiON, VNX and VMAX

December 20th, 2011

Since last week I have seen a number of questions in and around VASA and how it is configured for EMC arrays.  I got a couple while doing the Q&A for EMC’s recent VNX best practices with vSphere 5 live WebEx and the day after I was asked by Cormac Hogan over at VMware to take a look at a question asked on the VMware blog site.  So I’ll admit now,  I hadn’t really had a chance to look at VASA in-depth, shame on me!  However I thought that this was as good a chance as any to learn and I thought I would do a post on how to configure it for both EMC’s VNX and VMAX systems. Big thank you to my EMC colleague Garrett Hartney for providing both his time and an environment that we could set this up in.

EMC’s VASA implementation

For those not familiar with VASA I strongly suggest reading this article to familiarise yourself with the what and why around this new VMware API. For those who just want the short version, VASA is essentially an API that allows storage vendors to publish array capabilities up to vCenter.  This allows VMware admins to see characteristic information about the storage underpinning their datastores and also allows them to use VMware storage profiles to enforce VM storage placement policy compliance, e.g. This SQL VM will always sit on performance disks.

The table below shows how EMC currently publishes it’s array capabilities through VASA 1.0 up to vCenter.

Capabilities

An example of how this looks for a datastore when pulled through to vCenter can be seen in the screenshot below.

vCenter_View

Core Components and architecture

Regardless of which array you are connecting to, EMC’s implementation of VASA is done using Solution Enabler and something known as the SMI-S provider.  Together these two components act as a middle tier between vCenter and the different arrays being queried.  It’s worth pointing out that the SE \ SMI-S server supports in-band (SAN attached) and out of band (network) connectivity for VNX and CLARiiON arrays and in-band connectivity only for Symmetrix arrays. The architecture of the setup is demonstrated in the diagram below.

VASA_SMI-S

SE / SMI-S server deployment

To get started with VASA you will need to download SMI-S version 4.3.1 which already comes pre-bundled with Solution Enabler 7.3.1.  This software can be downloaded from the link below and comes with an option for 32 and 64 bit Windows as well as Linux.  For full details on OS support see the release notes for SMI-S 4.3.1 – (PowerLink Account Required for downloads)

Home > Support > Software Downloads and Licensing > Downloads S > SMI-S Provider

As part of my own deployment I am using a Windows 2008 R2 64 bit server to deploy the core components.  The server has been built as standard with no special configuration required.

  • We first of all need to deploy Solution Enabler and SMI-S on your designated server, locate the installation media and run the install package.

install1

  • When presented with the welcome screen click next.

install3

  • Leave the install location as default and click next.

install4

  • When prompted select the array provider only and click next.

install5

  • Review the installation settings and space requirements and click next to install.

install6

  • Once the install is complete, click finish.

install7

  • Configure the environment variables on the server to include the SYMCLI path

install8

  • Locate the following file and open it for editing

install9

  • Locate the line below and change the value from 100 to 1200, save and exit the file.

install11

  • Navigate to the services console and restart the ECOM service

install12

  • navigate to the location shown below and run testsmiprovider.exe

install13

  • the next step is to connect to the SMI-S provider. I used the defaults which are shown in the square brackets, just hit enter on each line to use the default.

install14

  • Once connected you will see the following at the command prompt

install15

  • type the dv command at the prompt to display version information about the SMI-S provider install.  This basically proves that everything is working as expected

install16

  • that concludes the basic installation and configuration of the SMI-S and Solution Enabler server,  now all we need to do is add in the storage arrays we want displayed to vCenter via the VASA api.

CLARiiON and VNX

SUPPORTED – CLARiiON Navisphere Release 28, 29 & 30, VNX Unisphere Release 31
(SMI-S supports many earlier CLARiiON releases but vSphere 5 does not)

Earlier I mentioned that the CLARiiON and VNX arrays could be added to SMI-S in-band or out of band.  The most common method and the one I intend to use here is to connect out of band, i.e. across the network.  If you do want to connect in-band with direct SAN connection then check out page 39 of the SMI-S v4.3.1 release notes.

One major pre-requisite for connecting CLARiiON and VNX is that the user account used to connect to the arrays must be an administrator login with global scope. At this point you should hopefully still be connected to the testsmiprovider.exe application used earlier,  if you are not then please repeat the command line steps shown above to reconnect.

  • Once connected successfully type the commands addsys to begin adding the array
  • Enter the IP address / DNS name for Storage Processor A and hit enter.
  • Enter the IP address / DNS name for Storage Processor B and hit enter.
  • You can continue to add additional arrays here or hit enter to move to the next step.
  • Accept the default for the address type, i.e. IP/Nodename by hitting enter.
  • Continue answering this question for each storage processor / array added
  • enter the global scope administration user account for connecting to the arrays.
  • enter the password for the administration account being used
  • You will then see the message +++++ EMCAddSystem ++++

install17

  • After a while you will see the output from the addsys operation, as you can see below the output is 0 which indicates success.  The details of the system added are then listed.

install18

  • If you now run the dv command the arrays added will be listed as connected.

install19

  • Now that the array is registered we now need to add the VASA provider into vCenter. Log into vCenter and navigate to the home screen, locate and click on the storage providers icon.
    install20
  • Within the storage provider screen click on the add button as shown below.

install21

  • Enter a name for the provider and enter the URL shown below,  the IP address of the server hosting SE / SMI-S should be entered where it has been blanked out below.  The user name is admin and the password is #1Password.

install22

  • When prompted accept the certificate for the SMI-S provider

install23

  • Once successfully added you will see the provider displayed

install24

  • Highlight the provider and you will see the array that was connected to the SMI-S provider server earlier.

install25

  • To check that VASA is working correctly in vCenter click the VM Storage Profiles icon on the home screen within vCenter.

install26

  • When setting up a new Storage Profile you should be able to see the storage capabilities presented to vCenter,  these are shown below and are marked with system.

install27

  • Job done, VASA successfully deployed and storage capabilities showing in vCenter!

DMX4, VMAX and VMAXe

SUPPORTED – Enginuity 5875
(SMI-S supports earlier Enginuity releases but vSphere 5 does not)

Now unfortunately I do not have access to a Symmetrix to complete my testing, however the release notes for SMI-S state the following which makes it sound very easy.

When started, the SMI-S Provider automatically discovers all Symmetrix storage arrays connected to the host on which the Array provider is running. No other action is required, such as running a symcfg discover command.

As mentioned earlier Symmetrix discovery is done in-band through small gatekeeper LUNs presented to the SE / SMI-S server.  If it is a virtual server then ensure that the LUNs are presented to the VM as physical mode RDMs.  The SMI-S release notes has the following to say about best practice.

When using the SMI-S Provider to manage Symmetrix arrays, it is recommended that you configure six gatekeepers for each Symmetrix array accessed by the provider. Only set up these gatekeepers for the host on which the SMI-S Provider is running.

So in theory it should be as simple as completing the following steps

  • Present the gatekeeper LUNs to the server (physical or virtual)
  • Restart the ECOM windows service to restart the SMI-S provider (auto discover arrays)
  • Use testsmiprovider.exe tool,  run the dv command, verify Symmetrix array is attached.
  • Thanks to my colleague Cody Hosterman (who does have a Symm) for the screenshot.

Symm_Config

One point to note, if you have SMI-S installed on the same host as the EMC Control Center (ECC) Symmetrix Agent or Symmetrix Management Console (SMC) there are a couple of steps you need to take to avoid some spurious errors.  Check out page 37 of the SMI-S v4.3.1 release notes for further information on the changes required to avoid this.

Summary

I think the important thing to remember here is that this is version 1.0 of VASA. It may not be the most elegant solution in the world but it is a start on what I think will become a key feature in years to come. We are fast moving into an age where VMs become objects where we simply check a box to ensure our requirement or service level is delivered.  Imagine a scenario where a VM is created and as part of the creation process you select the storage based on the VASA information passed up to vCenter from the array.  Do I want it on a RAID 5 or RAID 6 protected datastore? Do I want it on a RecoverPoint replicated datastore? Do I want it on a vPlex distributed datastore? Do I want it on a datastore that is SRM protected?  Although it is v1.0 you can see the potential use cases for this feature in the future are going to continue to expand.

Some of you may well have seen Chad Sakac’s blog post back in September entitled Help us make VASA (and EMC’s VASA provider) better! It includes a questionnaire with questions about what you, the end customer wants to see from VASA. This is a great chance to have your say and influence how EMC implement VASA going forward, lets make v2.0 of VASA a feature that delivers on the huge potential V1.0 has shown.

EMC, VMware , , ,

  • Mario

    Thanks for this great article! Isn´t it possible to install the SMI-S directly on the vCenter Server instead of a seperate Server/VM ?

  • http://www.virtualpro.co.uk Virtualpro

    Thanks Mario, indeed you can install the SMI-S directly onto the vCenter,  that is what we did when writing the article so I don't see why not.

  • http://www.facebook.com/profile.php?id=504686384 Joshua Post

    Thanks. I got this setup on my system using your guide.

  • http://www.virtualpro.co.uk Virtualpro

    Great news,  glad it was of some use to you

  • Ricardo Oliveira

    Thanks for the post! A similar post but installing it on Linux would be greatly appreciated. I am a bit stuck after launching ECOM server since I don't know how to test if it is correctly running.

  • http://www.virtualpro.co.uk Virtualpro

    That's a good shout,  I will take a look at that and try get back to you with some answers on what to do.

  • Ricardo Oliveira

    Thank you! Just out of curiosity: I installed the VSI in my vSphere client and it also provides storage information. I was wondering if VASA provides any extra information about the storage or if it just gives the same.

  • http://www.virtualpro.co.uk Virtualpro

    The VSI interrogates the information for specific components from the array directly.  With VASA the ECOM server sits in the middle and interrogates the arrays it is connected to,  based on the information it recieves around disk type and RAID configuration it assigns it a label, i.e. unprotected, capacity, performance, etc.  There is a table at the top of the blog post that shows the V1.0 labels that will be assigned.  Long answer but in short VASA does not provide any extra information over the VSI.

  • http://twitter.com/BasRaayman Bas Raayman

    Craig, just a small note. I set this up in our lab environment in Munich, where we also have the VSI plugin installed. Make sure that you sync your storage arrays there. I had a small problem with the file side of a VNX not syncing in the VSI, and that prevented the storage capabilities from showing up under the storage profiles.

    So, if you use both VASA/SMI-S and the VSI plugin, make sure all relevant arrays in the VSI plugin sync properly, otherwise you might run in to issues.

  • http://www.virtualpro.co.uk Virtualpro

    Nice one Bas, good to know, thanks for posting a comment

  • http://twitter.com/burak_uysal Burak Uysal

    Craig, great article

  • http://twitter.com/burak_uysal Burak Uysal

    Craig, great article! Thanks for sharing with us! I would like to see a follow up post with some use cases. Now we know how to set it up but how do we actually use it? Any gotchas with FASTVP etc? I know Duncan has a post on this so as some others but from a VNX and VMAX perspective it would be useful.

  • http://www.bussink.ch Erik Bussink

    Thanks for this very interesting article.

  • nkrick

    My preferred option is to use the Solutions Enabler Virtual Appliance.  Then you don't even have to install anything or use any command line.  Simply deploy the VA and then use a web browser to configure it.

  • Pingback: VCAP5-DCD Objective 3.3 – Create a vSphere 5 Physical Storage Design from an Existing Logical Design - VirtuallyHyperVirtuallyHyper