VMware Solutions Discussions

[BETA] Using VVOLs with NetApp & VMware

datacenterdude

UPDATE [Apr 9 2015]: The official versions of both VSC 6.0 and VASA Provider 6.0 are available as of today.

 

VSC 6.0 - CLICK HERE TO DOWNLOAD

VP 6.0 - CLICK HERE TO DOWNLOAD

 

FEEDBACK!

 

We want to hear your feedback!  We would love to consolidate everything centrally here in this thread, but if you have something that you don't want to say in the communities, you can always send VSC feedback to xdl-vsc-feedback@netapp.com.

 

-NetApp VSC/VASA team-

102 REPLIES 102

datacenterdude

I've found a couple of things also, and here are some workarounds to try.

If you're failing to register the VASA Provider within the VSC configuration menu:

1)  Check to insure all networking info is configured in the VP.  I ran into an issue where I didn't enter DNS settings and even though they were on the same local subnet and VSC & VP could ping each other, it was still failing to register.

2)  Try triggering a manual storage discovery in the storage controllers tab of VSC.  Wait a few mins and try again.

3)  On first boot, you have to have VMtools installed on the VP for it to finish installation (this is an obvious one, but sometimes overlooked).  Access the appliance console and it will walk you right through the steps nicely.

4)  Make sure you've rebooted after the VMtools installation finishes.

-Nick

RUSHINS46

HI

i was getting this error while deploying VCENTER appliance ?

An error occurred while invoking external commands: 'ERROR: Return Value: 1, Stdout: , Stderr: Traceback (most recent call last): File "/bin/syshostname", line 72, in <module> raise ValueError("pnid %s specified is not valid" % pnid) ValueError: pnid pal.sap.corp specified is not valid '. my company domain is "pal.sap.corp" and i have specified this in global name ? did anyone got errror like this .

can you tell me what is the fix.

BR,

Rushi.

peterl

I haven't seen that specific error, but it sounds like one of two things:

1.  DNS not correctly set up for the vCSA.  The IP address must match the hostname you give it, and hostname and FQDN must resolve correctly to that IP from the workstation where you manage it all.

2.  Parameters not entered correctly in the customize template screen when deploying the OVA. 

How did you deploy the OVA?  Using the new vSphere Host Client (which can directly deploy OVA/OVF to ESXi servers) or to a running instance of a previous version of vCenter?  Previous versions of vCenter don't understand the newer OVA format.  As a result, the customize template screen will ask for network information in two places, asking for slightly different things each time.  You have to provide the same values for equivalent parameters, with the exception of netmask.  In the upper section, it wants the number of bits (22 and 24 are common).  In the lower section, it wants the actual mask (255.255.252.0 or 255.255.255.0 are common).  And of course this all has to match the actual A record in the DNS server.

Reading the /bin/syshostname script, it looks like it wants FQDN and you passed just the domain name maybe in the Host Network Identity field in the first screenshot.

nsrushi46

Hi

I have right DNS and all networks can reach via DNS .

I was using Vsphere new client (Vmware Host Client ) whcih was inside the pacakge of Beta Vcenter ISO. I have installed this client and connected ESX6.0 beta server, upon logging in what i notice that we have to 2 options deploying OVF . 1) Deploy OVF template 2) Deploy Vcenter Server Appliance.

I was using the 2nd option becuase this is VCENTER and get the error that reported earlier, however if i use Deploy OVF by selecting Vcenter OVA it was completed but when you power on it fails with "installation fails".

Can you provide which option should be used, also i am working on to build a windows 2008 R2 so that i can install the package of vcenter instead of apliacne. Keep you posted , meanwhile please let me know if you have any idea how to overcome the above errors.

BR,

Rushi.

peterl

Use deploy vcenter appliance.

Sent from my phone. Any resemblance to an actual email is purely coincidental. Please keep head and arms inside vehicle at all times.

nsrushi46

ok i found it from appliance log files that said with the following message, so i logged with user" Administrator@navolvc3.pal.sap.corp" and i was able to add all the things that were not working with user: root/.

-------------------

Installation Complete

You can now login to vSphere web client from https://navolvc3.pal.sap.corp/vsphere-client as Administrator@navolvc3.pal.sap.corp".

--------

thanks for the tip about user: Administrator.

BR,

Rushi.

nsrushi46

hi

I got another problem  on VASA(Provider 6.0 for clustered Data ONTAP from netapp ) . i was able to deploy VASA and able to access as well https://host:9083 with user: vpserver, however while registering in vcenter wtih storage provider i get this error due to "https certificate is not valid" ? how do i get a valid certificate and also i see option "use storage provider certicate " ...

can someone shoot me how to get this certificate from netapp or is it part of vmware ? or how to bypass, i tried selecting "yes" though its not valid but i cannot register vasa on VCENTER?

BR.

Rushi.

RUSHINS46

Hi

Ok this VASA issue also fixed, basically VASA provider should be registered in VSC plugin inside VCETER , was failing before because i was trying to register in VCENTER server - storage provider which is wrong and should be used inside VCENTER VSC console and i found this little information inside netapp documentation.

----

Go to VSC and register VASA Provider with it. Do not use the vCenter Manage > Storage Provider page to register VASA Provider.

----------

For now looks good. Keep you posted incase if any issues occurs during my beta test evaluation.

BR,

Rushi.

RUSHINS46

i think i have problem after registering VASA provider with VCENTER vsphere web client , as it errors every phase of logon with the folowing message and it appear to be a adobe flash error or something as i get this .

Any idea about a fix. i have tried several times to reload client, however the problem remains same and i cannot continue anything as VSC doens't show the VASA logon.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------

Error: Unable to load resource module from /vp_ui/locales/VendorProviderUI-en_US.swf

An internal error has occurred - Unable to load resource module from /vp_ui/locales/VendorProviderUI-en_US.swf.

Reloading the client is recommended, so as to clear any problems left by this error.

Click Yes to reload the vSphere Web Client?

--------------------------------

BR,
Rushi.

dhollowa

Try appending port 9443 to the vCenter URL.

In the NetApp readme file under Important Notes:

  • Append port 9443 to the IP address when connecting to the vSphere Web Client
    • https://<IP-Address>:9443/vsphere-client/

datacenterdude

RUSHIN,

Anytime you receive this error message, something has broken in the vSphere client itself, and it needs refreshing.  It's often uncertain as to what it is exactly.  When you get this message, be sure to always reload the vSphere client and try your operation again.

-Nick

RUSHINS46

Hi Nick,

I did this , reloading client for 5 times and i get the same error so i have unregistered VASA from VSC and was able to logon without any issues.

Can you provide some tips how to overcome this issues. As it does prevent me to do further steps and a show stopper to my stuff.

BR,

Rushi.

RUSHINS46

Hi Everyone

I have done pretty much everything to test the beta except that VASA is not loading in vsphere client upon configurtaration. I have now ESX 6.0 , Vcenter and netApp clustered data ontp 8.21 , VSC and VASA appliance deployed and configured , i can even run commands on VASA web interface,  however VASA still throwing errors upon logging to VSPHERE after registered in VSC.

Can someone guide me what is required to fix this issue, it is the last step to test VVOL.

i have loaded vsphere for about 20 times after configuring VASA but this error still show up.

----------------------------------------------------------------------------------------------------------------------------------------------------------------

Error: Unable to load resource module from /vp_ui/locales/VendorProviderUI-en_US.swf

An internal error has occurred - Unable to load resource module from /vp_ui/locales/VendorProviderUI-en_US.swf.

Reloading the client is recommended, so as to clear any problems left by this error.

Click Yes to reload the vSphere Web Client?

--------------------------------

BR,
Rushi.

RUSHINS46

HI

Ok , the VASA issue is fixed after rebooting ESX, VCENTER and and VASA.

BR,

Rushi.

nsrushi46

Hi Nick,

I have to come back on this. Now everything configured, installed. I have registed clustered data ontop 8.21 system with VSC storage provider as well?

I've started creating data store and i was able to see VVOL option, however after selecting the VVOL option i don't see any containers in the list of Backing storage containers ?

Question: Do i have create the containers before selecting VVOL or VVOL will create the containers ?

Can you provide what was missing ?

BR,

Rushi.

dhollowa

Rushi,

How did you create the VVOL datastore?  via the vCenter work flow or through the NetApp VP UI?  If you use the NetApp VP UI then it will create the container, set your export policies, and mount the container as a VVOL Datastore.  To create a VVOL datastore via the vCenter workflow then it will only display the containers being advertised by the Vendor Provider.

nsrushi46

Hi Hollowa,

I was trying to create VVOL through VCENTER integrated screen as attached, however in your screen i see VASA Provider for cluster screen is not visible to me ? where did you get this and how to configure ? was it part of VASA appliance that was already configured ? my VASA appliance installed and configured on VCENTER inside VSC but i dont' see this screen.

BR,

Rushi.

dhollowa

Rushi,

The VASA UI is an extension which is registered with vCenter when you register the VP via VSC. Do you reboot your vCenter after registering the VP?

Is so, then you may need to unregister and re-register the VP via VSC. Please see the VSC 5.0 documentation for the VP registration process.

If registering does do work, please let me know and we can try another work around.

Sent from my iPhone

nsrushi46

Hi

I've install all components(ESX 6., VCENTER 6, VASA plugin, VSC)  and started using how to create a vVol, but after selecting option VVOL i don't see any containers from Storage.

It's failing every step not sure if t's because  ontap cluster 821 simulator and beta  esxi 6.?

And the last problem what i found that  after a restart of vsphere web client services the vasa options are ok however VSC wasn't starting at all.

Let me know if you a have a straight forward document with all steps required with (ESX6, VCENTER 6, VASA, VSC, NetApp simulator cluster data ontap 821), as it will be easy to test, however without having any straight process it is very difficult.

BR,

RUshi.

dhollowa

Rushi,

Using the CLI or System Manager, create one or more volumes on your controller that you would like to use in the container.  You will also need to enable NDMP copy on the each of SVMs that you would like to use for VVOLs.  After the volumes have been created then add the controller to MHC using administrator credentials.  Depending on the size of your cluster this could take several minutes,  While discovery is running, create a Storage Capability Profile that matches the attributes of the volumes you created earlier (ie. Deduplication).  After you have created one or more SCPs, then right click on a 6.0 host and select the Provision VVOL Datastore work flow.

This workflow will create the container then map it as a VVOL datastore on vCenter.

nsrushi46

hi Peter,

Thank you, i did according to your steps of NDMO on my Cluster netApp system 821 system however after doing it in VCENTER i still don't see the option of creating VVOL after the screen VVOL option> . i have also restarted services "vmware-sps" but no luck . I am going to wait for couple of mins (may be an 30 mins) since you said it will take some time to show up.

Keep you posted,

BR,

Rushi.

---------------------------

eadrax::> system services ndmp node-scope-mode off

NDMP node-scope-mode is disabled.

Then, set ndmp as an allowed protocol and enable it on the Vserver

eadrax::> vserver modify -vserver vmw_fcp -allowed-protocols fcp,ndmp

eadrax::> vserver services ndmp on -vserver vmw_fcp

eadrax::> system services ndmp node-scope-mode off

NDMP node-scope-mode is disabled.

Then, set ndmp as an allowed protocol and enable it on the Vserver

eadrax::> vserver modify -vserver vmw_fcp -allowed-protocols fcp,ndmp

eadrax::> vserver services ndmp on -vserver vmw_fcp

-------

BR,

Rushi.

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public