This post is more than 5 years old
4 Operator
•
878 Posts
0
2755
About PSC memory size on VxRail 4.0.200 (vSphere6.0u3a~)
Hi Experts,
I upgraded to VxRail 4.0.200, but the upgrading process failed to restart PSC during upgrade.
And I saw an alert of PSC 's memory shortage (High Paging). * PSC memory size is still 2GB.
during the PSC stopped, I could not use the Web Client.
[ VMware vCenter Server 6.0 Update 3 Release Notes ]
[ FAQ: VMware Platform Services Controller in vSphere 6.0 (2113115) | VMware KB ]
vCenter6.0u3 release note known issues and FAQ KB say recommended memory size is 4 GB.
----
Known Issues
- While upgrading vCenter Server Appliance from 6.0.x to 6.0 Update 3, memory of the Platform Services Controller does not change.
While upgrading Platform Services Controller of vCenter Server Appliance from 6.0.x to 6.0 Update 3, memory of the Platform Services Controller does not change and it remains 2 GB.- Workaround: To work around this issue,
- Power off the Platform Services Controller of vCenter Server Appliance VM
- Increase the memory size manually by Edit Settings of the VM
- Power ON the Platform Services Controller of vCenter Server Appliance VM
Note: Platform Services Controller of vCenter Server Appliance is installed with 4 GB of memory by default in case of fresh install and while upgrading from 5.5.x to 6.0 Update 3.
What are the minimum requirements to run PSC 6.0?
Requirements when deploying the Appliance-based Platform Services Controller:
- Processor - Intel or AMD x64 processor with two or more logical cores, each with a speed of 2 GHz
- Memory - 2 GB
Note: In vSphere 6.0 Update 3 and later the PSC is deployed with 4 GB.
----
In addition, I checked the setting of the clear installed appliance of VxRail 4.0.200.
This is correctly set with 4 GB.
PS C:> get-vm | ft -AutoSize
Name PowerState Num CPUs MemoryGB
---- ---------- -------- --------
VMware vCenter Server Appliance PoweredOff 4 16.000
VxRail Manager PoweredOn 2 8.000
VMware vCenter Server Platform Services Controller PoweredOff 2 4.000
VMware vRealize Log Insight PoweredOff 4 8.000
I think that memory size should be changed before or after upgrading according to Vmware's recommendation.
What do you think?
alekseylib
14 Posts
0
May 19th, 2017 18:00
Thanks for bringing this up.
I reviewed the reasoning behind this increase and I view this as future proofing (we have done similar change in vSphere 6.5 releases) as some of our customers with complex configurations (i.e. link mode which we don't support today with VXRAIL's internal VC / PSC) are going be hitting close to 100% of the memory utilization in their environments.
So I would recommend to make this configuration change only whenever you have experienced high memory utilization in your PSC VM during a steady state (and not just during the boot process).
In my test environment I also observed high paging activity after PSC reboot, but it would settle down and work just fine in a steady state.
When VXRAIL 4.0.x releases are going to be upgraded to VXRAIL 4.5+ releases (which will included vSphere 6.5+ bits), we will automatically take care of the PSC memory bump as upgrade process will require deployment of new instances of VC/ PSC appliances.
kwmt
4 Operator
4 Operator
•
878 Posts
0
May 22nd, 2017 07:00
Hi Aleksey,
Thank you for your reply.
I understand your comments and future roadmap.
----
So I would recommend to make this configuration change only whenever you have experienced high memory utilization in your PSC VM during a steady state (and not just during the boot process).
----
Since I want to avoid errors during the upgrade, I would like to add memory as much as possible before upgrading.