Design:
2 x vCenter VMs version 5.5 on W2k12. Fresh Installations. Linked and using same SSO key (default installation)
2 x SRM VMs version 5.5 fresh installation
20+ vSphere 5.5 hosts with DR/HA configured and working. Two dvSwitches (one per site) configured with port groups / VLANs working
Issue:
Installation going fine until I needed to activate the SRM Plugin in vCenter. Plugin listed as "Available Plug-ins" and I click on link to "download and install"
I got two separate errors on the two vCenter servers, both with same errors so it is consistent.
Errors:
(attached file viclient-3-000.log)
The request was aborted: Could not create SSL/TLS secure channel.
(attached file viclient-3-000.log)
The remote server returned an error: (503) Server Unavailable
I would assume both are related and likely something with SSO. Post vCenter installation on each vCenter server, at the vCenter level I added the AD "Domain Admins" group with full permissions and then successfully logged in and built the cluster with that credential set.
I need help to debug this further.
Thanks,
************
<< Update>>
Seems some features and functions are NOT present if you do not login as "administrator@vSphere.local" (default SSO account for this 'basic' setup)
But even with this login, I have noted that the option within the webclient, does NOT exist to perform vCenter Plug-in installation. It does appear in the vSphere Client (see attached images).
I also found it odd that the vCenter web client shows SRM roles but the traditional client does not.
Maybe this is a clue to the root issue...
Message was edited by: ArrowSIVAC 2013-10-07 To provide more detail and attachments
Message was edited by: ArrowSIVAC This is related to vmware support case 13384832210 This issue is resolved. Several pieces here. 1) vCenters were installed fresh with local administrator account as own of databases and that is how I typically do things 2) SRM servers were built as seperate VMs, vs VMWare's guides assumes and documents with expectation your installing SRM on the same server as vCenter The documentation / installer does not clarify that you MUST use domain accounts for SRM in multi site linked mode installations and if you do not , the installation completes without error, but resources will not work. Errors noted were for client plugin not working. That was the symptom, the reason for that was the SRM service was not running. The service would not start and only error in Windows Event log is “vmware-dr service stopped” This was because connectivity issue of SRM to vCenter hosted SQL instance of new SRM database. The SRM database was installed on the vCenter server instance as vCenter database. And just like default vCenter installation I choose use of localhost\administrator for owner of database. The database does have tables populated but SRM has connectivity issues. The fix for this was to add "domain\user" (called mine SRMAdmin and added as domain admin member), added that user within SQL in database users list then promoted it as owner of SRM database and set rights to DBO. This fixed first issue. Second issue in relation was that the SRM installation defined the system DSN credentials but does not clarify that these also must be domain based accounts. The installer is not clear here and should only allow domain\username during the installation. After several attempts to root cause and tried different installation methods, the way to get the installation to complete and setup correctly was to login to the system AS the domain account Example: domain\srmadmin => setup system DSN by selecting "How should SQL Server verify the authenticity of login ID?" set to "With Integrated Windows Authentication" and then the SRM installation for the "Enter Database user Credentials" set to "domain\srmadmin" . Then the services will start and communication to vCenter database hosted SRM DB will work properly. <see attached images of points of reference>