Skip to main content

3 Ways to get VMware Platform Services Controller (PSC) information from vCenter Server 6.5




      From vSphere 6.5, VMware Changes its vCenter architecture by introducing Platform services controller (PSC) by replacing vCenter SSO server. VMware Platform Services Controller (PSC) is a component of the VMware Cloud Infrastructure Suite. PSC deals with identity management for administrators and applications that interact with the vSphere platform.

Below are the Components that are installed with platform Service controller includes:
  • VMware Appliance Management Service (only in Appliance-based PSC)
  • VMware License Service
  • VMware Component Manager
  • VMware Identity Management Service
  • VMware HTTP Reverse Proxy
  • VMware Service Control Agent
  • VMware Security Token Service
  • VMware Common Logging Service
  • VMware Syslog Health Service
  • VMware Authentication Framework
  • VMware Certificate Service
  • VMware Directory Service

vCenter Server Deployment Models:

  • vCenter Server with external Platform Services Controller (Separate appliance or server for PSC & vCenter)
  • vCenter Server with embedded Platform Services Controller (Both PSC & vCenter Server are installed on Single VCSA appliance or VM
In most of the larger enterprises, They will be having hundreds and thousands of  ESXi hosts and also multiple vCenter Servers to manage the ESXi hosts in the virtualized infrastructure. With multiple vCenter Servers in the environment, I even personally feel a bit difficult to identify the servers which are associated with vCenter Servers such as  Platform Services controller, External database servers, and Update Manager.  We need to identify the associated Platform services controller before Upgrading vCenter Server. This is essentially important when performing vCenter upgrade and troubleshooting purposes.

1. Get Platform Service Controller from vSphere Web Client

Log in to vCenter Server using vSphere Web Client -> Click on Home -> select Administration -> System Configuration -> Nodes. Select to nodes to understand the deployment type of the node.

2. Get Platform Services Controller from vCenter Advanced Settings

Log in to vCenter Server using vSphere Web Client -> Click on Home -> Hosts & Clusters -> Select vCenter Server -> Configure -> Advanced Settings  and Search for “sso-admin”.

3. Get Platform Services Controller from vCenter Server appliance CLI

Login to your vCenter Server appliance using SSH with root credentials. Switch to Bash shell using command “Shell”. Execute the below command to get the Platform Services controller (PSC) information.

 
/usr/lib/vmware-vmafd/bin/vmafd-cli get-ls-location --server-name localhost



Labels:

Comments

Post a Comment

Popular posts from this blog

Dell EMC VxRail – VMware Virtual SAN Stretched Cluster

Logical Diagram of VMware vSAN Stretched Cluster Physical Diagram of VMware vSAN Stretched Cluster Last week I deployed a test environment of VMware vSAN Stretched Cluster which is running on Dell EMC VxRail Appliance. In this post we will describe how to setup VMware vSAN Stretched Cluster on Dell EMC VxRail Appliance. Above figure is the high level of physical system diagram. In site A/B there are six VxRail Appliances and two 10GB Network Switch which are interconnected by two 10GB links, and each VxRail Appliance has one 10GB uplink connects to each Network Switch. In site C, there are one vSAN Witness host and one 10GB Network Switch. For the details of configuration of each hardware equipment in this environment, you can reference the followings. Site A (Preferred Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and 3 x SAS HDD, 2 x 10GB SFP+ ports 1 x 10GB Network switch Site B (Secondary Site) 3 x VxRail E460 Appliance Each node includes 1 x SSD and...
1 comment
Read more

UEFI Secure Boot with ESXi 6.5

UEFI Secure Boot: UEFI, or Unified Extensible Firmware Interface, is a replacement for the traditional BIOS firmware. In UEFI, Secure Boot is a “protocol” of the UEFI firmware. UEFI Secure boot ensures that the boot loaders are not compromised by validating their digital signature against a digital certificate in the firmware. UEFI can store whitelisted digital certificates in a signature database (DB). There is also a blacklist of forbidden certificates (DBX), a Key Exchange Keys (KEK) database and a platform key. These digital certificates are used by the UEFI firmware to validate the boot loader.  Boot loaders are typically cryptographically signed and their digital signature chains to the certificate in the firmware.The default digital certificate in almost every implementation of UEFI firmware is a x509 Microsoft UEFI Public CA cert. Most of the UEFI implementations also allows the installation of additional certificate in the UEFI firmware and UE...
Post a Comment
Read more

VxRail 4.0 – Scale Out

The above is the physical diagram of VxRail Cluster (3 nodes). In this post I will show how to add one VxRail Appliance into this VxRail Cluster (From 3 nodes to 4 nodes). NOTE: The model of each VxRail Appliance is E460. Before the node expansion, you need to verify each Appliance is running in health in dashboard of VxRail Manager. The above is the final physical diagram of VxRail Cluster after scale out. Now we start the node expansion. You have just mounted a new VxRail Appliance (E460) and cabled it up to the top of each rack switch. When you power it on you can see a notification appear in the top left corner of VxRail dashboard. Click “ Add Node “. When you initially configured your VxRail Appliance, you specified an IP pool for ESXi, vMotion and vSAN. You can see that there available IP addresses in these pools, so the only additional action is to set an ESXi password. Click the scroll bar, then click the “ ESXi Password “. Enter the  ESXi  and ...
1 comment
Read more