Unable to see a list of ESX servers to install SDC on in plugin

Hi Keith,

Have a look at:

https://community.emc.com/message/892224

That might be something similar. There was a problem with ScaleIO 1.32 before 1.32.2 but I believe you are running a newer version?

Also, try to ping the ESXi FQDNs from the vCenter Server - sometimes DNS can cause such issues.

Can you attach/paste the Virgo logs here so we can see what's going on?

Best!

Pawel

Thanks Pawel....I did see that message you linked to and did most of all that already (minus the manual install). I have installed it manually and it comes in fine, albeit with a different mgmt IP than the SDC installed as part of the ScaleIO cluster install.

The FQDN's ping OK from vcenter and back - resolution seems to be good which is why i can't figure out why they aren't showing up in the plugin...odd.

The virgo logs are like 20MB, so I ran it just to capture the "Install ESX SDC" query in the SIO plugin and all came back fine - it queried the servers I am expecting to see (server1 and server2 - names changed for posting) and I don't see any issues:

[2016-07-11T15:22:42.199-04:00] [INFO ] http-bio-9443-exec-10         c.e.e.v.remoteServices.mdm.service.ScaleIOProxyMngrImpl           Start creating ScaleIOAccessProxy to IP tcp://10.1.1.161:6611, username admin

[2016-07-11T15:22:42.366-04:00] [INFO ] http-bio-9443-exec-10         com.emc.ecs.model.StructuralDataModel                             ELAPSED TIME: initialization response :: internal                               :: 0.008752 sec

[2016-07-11T15:22:42.368-04:00] [INFO ] http-bio-9443-exec-10         com.emc.ecs.model.StructuralDataModel                             ELAPSED TIME: initialization response :: external                               :: 0.001274 sec

[2016-07-11T15:22:42.368-04:00] [INFO ] http-bio-9443-exec-10         com.emc.ecs.model.StructuralDataModel                             ELAPSED TIME: initialization response                                           :: 0.010468 sec

[2016-07-11T15:22:42.369-04:00] [INFO ] http-bio-9443-exec-10         c.e.e.v.remoteServices.mdm.service.ScaleIOProxyMngrImpl           Successfully created a new ScaleIOAccessProxy to IP tcp://10.1.1.161:6611

[2016-07-11T15:22:42.369-04:00] [INFO ] http-bio-9443-exec-10         c.e.e.v.remoteServices.mdm.service.ScaleIOProxyMngrImpl           Successfully created ScaleIOAccessProxy to tcp://10.1.1.161:6611, received id: 2adc7c4819f28894

[2016-07-11T15:22:42.663-04:00] [INFO ] pool-24-thread-12             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     Start getting esx info for server1.fqdn.com

[2016-07-11T15:22:42.680-04:00] [INFO ] pool-24-thread-12             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     fields=[Adapters, Datacenter, Disks, IpAddresses, Cluster, VirtualNics, Firewall, AvailableDisks]

[2016-07-11T15:22:42.747-04:00] [INFO ] pool-24-thread-13             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     Start getting esx info for server2.fqdn.com

[2016-07-11T15:22:42.764-04:00] [INFO ] pool-24-thread-13             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     fields=[Adapters, Datacenter, Disks, IpAddresses, Cluster, VirtualNics, Firewall, AvailableDisks]

[2016-07-11T15:22:42.800-04:00] [INFO ] pool-24-thread-11             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     Start getting esx info for server3.fqdn.com

[2016-07-11T15:22:42.820-04:00] [INFO ] pool-24-thread-11             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     fields=[Adapters, Datacenter, Disks, IpAddresses, Cluster, VirtualNics, Firewall, AvailableDisks]

[2016-07-11T15:22:44.194-04:00] [INFO ] pool-24-thread-13             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     Finished getting esx info for server1.fqdn.com

[2016-07-11T15:22:45.065-04:00] [INFO ] pool-24-thread-12             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     Finished getting esx info for server2.fqdn.com

[2016-07-11T15:22:45.262-04:00] [INFO ] pool-24-thread-11             com.emc.ecs.vSpherePlugin.remoteServices.vmware.VMwareService     Finished getting esx info for server3.fqdn.com

[2016-07-11T15:22:45.330-04:00] [INFO ] http-bio-9443-exec-10         org.springframework.flex.servlet.MessageBrokerHandlerAdapter      Channel endpoint amf received request.

[2016-07-11T15:22:45.331-04:00] [INFO ] http-bio-9443-exec-10         com.emc.ecs.vSpherePlugin.remoteServices.ssh.EsxSshServiceImpl    getPluginZipFolder()

[2016-07-11T15:22:45.368-04:00] [INFO ] http-bio-9443-exec-10         com.emc.ecs.vSpherePlugin.remoteServices.ssh.EsxSshServiceImpl    Check whether needed VIB already exists on vSphere web client server in the following locations: C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity

[2016-07-11T15:22:45.369-04:00] [INFO ] http-bio-9443-exec-10         com.emc.ecs.vSpherePlugin.remoteServices.ssh.EsxSshServiceImpl    Found VIB on vSpehre Web Client Server: sdc-2.0.922.0-esx5.5.zip

[2016-07-11T15:22:45.370-04:00] [INFO ] http-bio-9443-exec-10         com.emc.ecs.vSpherePlugin.remoteServices.ssh.EsxSshServiceImpl    Found VIB on vSpehre Web Client Server: sdc-2.0.922.0-esx6.0.zip

Let me know if you have any more thoughts. thanks!

-Keith

Hi Keith,

Can you confirm the exact versions of the ESXi and ScaleIO you are using?

thanks,

Pawel

Sure - it is ScaleIO 2.0 and ESX 6.0

thanks!

-keith

OK - can you please try the obvious - clear the cache and the cookies, restart the browser/computer and see what happens? And/or try different browser?

Pawel

That might be the best thing to do... can you let me the SR number once you have open it?

Sure thing...I did those a few times over the past days before I posted and they all show blank lists, even though the logs can find and retrieve the settings for them so it seemed to me like a plugin issue of some sort. I haven't created a case for it because I can do it manually, but I might do that just to get a resolution if this is a bug or something weird. I haven't tried to remove the plugin and re-install (not sure if there is an easy way to do this) yet.

Hi Pawel,

I am facing the similar issue. Do you know of any resolution?

Thanks in advance for your help.

Hi Scorsado,

Can you please check for starters whether all DNS names of ESXi hosts are recognized by vC? Also, is there any error in the plugin or the logs or you simply can't see the ESXi's?

Cheers,

Pawel

Hi all,

Also worth noting :

When deploying ScaleIO, the relevant ESXi hosts should have no faulty disks or unknown disk partitions.

If a host has either (faulty disks or unknown disk partitions), the ScaleIO plugin will not see that ESXi host during the deployment.

Rdgs, Gearóid

Interestingly enough, I had destroyed and completely rebuilt the ScaleIO cluster after doing some destructive testing on it when I posted it above.

After the new rebuild, I see the same phenomenon where the web client doesn't see the ESX servers. During the install, I didn't check off the SDC install purposely because I wanted to play around with it manually and even though it installed it on the ESX hosts because it is called out as part of the install process, they don't load automatically and still don't show in the web client....so I think something is up with either the install process or possibly a bug or something....not sure...I need to get back to it to investigate more....but I did find it interesting that the problem repeated on a new fresh install.

-keith

Yes I can ping FQDN of all esxi hosts from vcenter server. I am not seeing any errors in logs.

FYI - all 6 ESXi hosts are booting of SD cards. Vcenter 6.0, ESXi 6.0  and scaleio 1.32.403

Hi Scorsado,

I found a similar problem here:

https://community.emc.com/thread/215686?start=0&tstart=0

It was an older vSphere version, but I remember that the plugin might have issues with getting ESXi host information via vSphere API, as it doesn't always work well without "real" disks apparently. Can you please try to display the list of ESXi hosts again and check in the newest Virgo logs for any errors or failed API calls?

Many thanks,

Pawel