vSphere/ESXI 6.0 Support?

Yes, I installed it in a test environment just this week, worked like a charm.

Yes it's working, follow the quick install guide strictly and it'll work nice.

My problem was that i did press enter in the installer powershell script before i logged off from all vsphere-web clients.

I did not see ScaleIO icon on Web Client after installed Plugin 1.32.

Support on VC 6.0 + ESXi 6.0 was tested many times for a long time in the QA.

Which VC exact version are you using?

Please try the following steps:

1. Un-register the plugin (using the PowerCLI ps1 script)

2. Log-out -> log-in in vSphre web client

3. Clear your web browser cookies / history etc.

4. Restart the vSphere web client service (Virgo server) on your VC

5. Register the plugin (using the PowerCLI ps1 script) -> remember NOT to press Enter until you perform the log-in into your vSphere web client (that completes the registration)

6. Once you see the SIO icon in the vSphere web client, you can press Enter in the PowerCLI session (that will stop the embedded tomcat)

You could try and  restart vCenter server after scaleio installation - the icon should appear then.

I'm having the same issue NO ICON

successful deployments no errors using the powercli

tested on Vcenter appliance 5.5

Currently testing on Vcenter appliance 6.0 2776510

Tried multiple reboots, redeploys etc NO ICON

only error I can find is Alarm heath status Datacenters triggered by even 7734 ########cae5_com.emcs3g.scaleio.vsphereplugin status from gray to gray

1. Was this a VC 5.5 and you upgraded it to 6.0? or was it a fresh install / deployment?

2. Did you try the steps I wrote in comment number 5?

3. You verified that there's no connectivity issues / Firewall / wrong VC credentials were used?

4. When using the PowerCLI script, remember NOT to press Enter until you perform the re-login into your vSphere web client (that actually completes the registration). Pressing Enter before that stops the embedded web-server and will fail the registration.

I've had this issue on the two VCs I've tried to install the plugin on (I still have it on the second).

I'm using a fresh install of the latest VC appliance (6), 1.32 plugin, and latest version of PowerCLI. On the first system, after 10 - 20 attempts, it finally registered. On the current system I've lost count of the number of attempts (I've been trying for over 7 hours now).

I've followed the instructions above to the letter, and tried other variants suggested on these forums, but none have succeeded. Very infuriating.

The service shows up under objects, but is listed as stopped / unknown. I'd appreciate any help at all.

Did you perform all steps to clean up your system + cleared the browser's cache/cookies?

Here are the steps again - please clean your system (and the Virgo logs) and repeat the registration procedure and then send us all logs + files (see relevant paths below).

How to clean-up your Env and perform clean install (while using previously defined networks):

VC 5.5

Windows:

Virgo logs: C:\ProgramData\VMware\vSphere Web Client\serviceability\logs

Plugin logs and other files: C:\Windows\System32\config\systemprofile\AppData\Roaming\VMware\scaleio

Linux:

Virgo logs: /var/log/vmware/vsphere-client/

Plugin logs and other files: /opt/.vmware/scaleio

VC 6.0

Windows:

Virgo logs: C:\ProgramData\VMWare\vCenterServer\logs\vsphere-client\logs

Plugin logs and other files: C:\Users\vspherewebclientsvc\AppData\Roaming\VMware\scaleio

C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity – plugin location

Linux:

Virgo logs: /var/log/vmware/vsphere-client/logs

Plugin logs and other files: /etc/vmware/vsphere-client/vc-packages/scaleio

Plugin location: /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity

Thanks for the response. Can I get some clarification? If I am ready your steps correctly, I have to uninstall the entire previous ScaleIO deployment and start from scratch? I'm in a catch 22 situation if that's the case, as I can't delete and of the volumes as they have many VMs on them with no option to move them to other storage temporarily.

Some background info on the situation - the original deployment went fairly smoothly. ScaleIO was up and running for a couple of weeks without issue. The original VC became corrupted and no backups were available. The only option was to build a new VC and re-add the PD. The existing PD is functioning correctly in the background, so it seems like a tall order just to install a plugin in a new VC.

The environment is not live yet, but I'm loathed to dismantle SIO to such an extent that several weeks of work will be undone over what should be a simple plugin!

Thanks for the guidance tomer - it is greatly appreciated. You are correct in your assumption I want to register the plugin and add an existing SIO system - the SVMs and SDCs are all running on the original hosts as you mentioned.

I have tried using several users - admin@vsphere.local, domain\domain.admin, etc all without success.

As a point, the plugin logs and plugin itself don't appear to be on the VC, or not in the locations you mentioned a couple of posts ago (/etc/vmware/vsphere-client/vc-packages). I do see the following errors in the virgo log:

"Unable to get catalogServiceProviderInfo for /etc/vmware/vsphere-client/cmCatalog/ :GB"

I'll run through the process again and upload the logs so you can see them in their entirety.

(The original VC that was used when scaleIO was installed had a corrupted file system and wouldn't boot. No amount of running fsck or other variants got it back online. Mistakenly thought it would be quicker to deploy another!)

I understand you have volumes and  VMs -> no need to delete them.

What do you mean that the VC became corrupted and you re-add the PD (protection domain?)

You installed a new VC and you want to register the plugin and later register the existing SIO system in that plugin - do I understand correctly?

Your SIO system (SVMs + SDC driver) are running on your ESX hosts (same one from the original deployment), which are now added to your new VC?

When you are trying to register the plugin - are you using the correct administrator / root user with administrator privileges? Is there a domain being used and you may be using the "correct" administrator user (e.g. user@[domain])?

Please follow these steps and send us the logs + files (see paths in my previous comment):

1. Close any existing PowerCLI sessions and open a new one
   
2. Unregister plugin using the PowerCLI (ps1 script)
3. Stop vSphere web client service (VC Linux: service vsphere-client stop)
4. Delete the content of the folder (VC 5.5 plugin location): C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity
5. Delete the content of the folder, or folder itself (VC 5.5): "C:\Windows\System32\config\systemprofile\AppData\Roaming\VMware\scaleio"
6. Clean the Virgo logs folder: C:\ProgramData\VMware\vSphere Web Client\serviceability\logs
7. Start the vSphere web client service (VC Linux: service vsphere-client start)
8. Clear your web browser's cache/cookies (or use a different web browser)
9. Register the new plugin using the PowerCLI (ps1 script)
10. Stop -> Start the vsphere web client service (or perform logout -> login to vSphere web client)
    

The last set of instructions finally worked! The only step, which I think I did differently was stopping and starting the web service whilst the script was still waiting for me to press enter. I'm almost certain I'd already tried that, but after countless hours I can't quite remember in all honesty.

Thanks for the perseverance tomer - one heck of a headache behind me!

The steps I used to complete it were as follows:

1. Clear / clean the logs as per tomer's instructions.

2. Run the powershell script (credentials in user.name@domain.com format).

3. When it gets to the part where it waits for you to press enter, SSH to your VC (location doesn't matter).

4. Run the following commands on the VC SSH:

> shell.set --enabled true

> shell

# service-control --stop vsphere-client

# service-control --start vsphere-client

5. Once the web client is back online, log on to your vc (I did this from the same PC the PS script was running on).

6. Fingers-crossed you'll have the ScaleIO icon at this point.

7. Press Enter on the PS window, and log off the client.

This was for the 1.32 plugin on a Linux VC Appliance (v6).

1st of all - Good news!

The correct way to register a plugin is once the embedded tomcat is started as part of the registration (you will see the message about the press Enter) -> you SHOULD NOT press Enter until you perform the logout -> login to vSphere web client (or restart vSphere web client service), that completes the registration. Only after registration completed and you see the SIO plugin icon, you can press Enter (in the PowerCLI) and that stops the tomcat. Pressing enter before the registration completed, will cause the registration to fail. I Assume that was the problem in your previous attempts.

Good luck with registration the SIO system in the plugin.