![]() ![]() This is the location for installed plugins and saw that I was missing the .h5vsan-6.0 directory and it’s contents… although the mob told me it was available… After this observation, I logged in with winSCP on my working vCenter and copied the .h5vsan-6.0 directory and it’s contents from there to my vCenter where it was missing.Īfter a reboot of my first vCenter the vSAN h5 options all showed up and the plugin was active! Unsure why an out of the box installation was missing this but now it’s fixed. etc/vmware/vsphere-ui/vc-packages/vsphere-client-serenity ![]() No reason why the vSAN plugin should not be working out of the box… as it should…Īnd find it via the string: .h5vsanĪs you see the plugin is available but why are my vSAN config options not showing on when logged in via my first vCenter? Logged in with WinSCP on the first vCenter and went to: Normally it should look like below but the first vCenter was missing it.įirst I checked if the plugin was available at all via the Managed Object Types and that looked all good. So, on both of the vCenters, I checked the enabled plugins and saw that I was missing the plugin for vSAN h5. Just the first vCenter was being a virtual #ass… Checking the plugins: ![]() Logging in via the second vCenter or Flex client all vSAN functionality was available. The whole deployment was one out of the books but somehow on the first vCenter, I was missing the h5 plugin for vSAN and was unable to set it up via h5. This was containing 2 vCenters linked with embedded PSC. Today I was deploying a new vCenter 6.7U1 environment with vSAN. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |