If you can log into both VCs with integrated windows SSO, you know you've done a good job, oh and when you see this: Home -> Administration -> System Configuration -> Nodes Once the second VC comes up, it should show up in your primary VC server under the following directory: Then we need to fill in our newly deployed PSC's FQDN, SSO user and password then carry on through the install process.ĭeployment can take a while depending on your storage. Now we can go ahead and install our second vCenter server, jump into the VCSA install process again but this time choose to deploy a vCenter Server with external PSC: Once joined to your AD again, reboot the PSC and your permissions will be restored across all VC objects. Home -> Administration -> System Configuration -> Nodes -> -> Manage -> Settings -> Active Directory -> Join. You will need to join the PSC to AD again if your vC was previous AD joined to maintain any windows based SSO you may have had as identity services have obviously moved to the PSC now. Vc01: ~ # /usr/lib/vmware-vmafd/bin/vmafd-cli get-ls-location -server-name localhost I've filled out the below command with the params relevant to my environment: Now the fun part, we need to log into the existing vCenter with SSH and reconfigure SSO to point to the new external PSC. Go ahead and deploy the rest of the PSC through the wizard and confirm it comes up okay in your existing vCenter: Then choose to add to the existing SSO site:
Then you want to join it to the existing SSO domain: The first step is to deploy an external PSC only and link it to the already existing vC with embedded PSC, so download the VCSA install ISO, choose install then deploy to your existing vCenter server (in my case: ) - Choose Install Platform Services Controller: I found a great KB for such a migration from a vCenter with an embedded PSC to one with an external PSC.Īnd the final goal (this will likely expand to multiple PSCs in future):
There is quite some complexity in my lab with regard to vCenter and its integrations, I have running in production vRO, NSX and vCD - it's also plugged into VIO and VR, so naturally I really don't want to reinstall all these components and reconfigure them as a lot of work has gone in, in particular with NSX, dynamic peering etc set up with upstream routers and its integration with vCD. On a bit of a shorter note to my previous article/novella - I have been moving my lab to a bit more of an "enterprise" style architecture - deploying SRM was in the way for that, so I had the need to set up another vCenter, however this gave the opportunity to move to a multi-PSC, multi-VC architecture.
0 kommentar(er)
