Month: September 2025

vCenter Server shows unhealthy in VAMI:5480 page.

By Lerpong Intaraworrapath | September 18th, 2025

We found that vCenter Server appliance shows unhealthy status in Overall Health alert and Memory alert.

We expand the Memory status alert show message

“Appliance is running low on memory. Add more memory to the machine“

Step

1.In a Web browser, go to the vCenter Appliance Management Interface.

https://appliance-IP-address-or-FQDN:5480.

2.We get an alert stating that the alert is for Overall Health.

3.We discovered that the Overall Health alert comes from the memory alert.

4.We validated KB: https://knowledge.broadcom.com/external/article/318571/appliance-is-running-low-on-memory-add-m.html and determined that it is not applicable.

5.Use the following command.

# grep -i percpu /proc/meminfo

It is not high (not more than 1GB).

6.It is a low number (0) of VMware Pod service restarts, as validated by the following command on the VCSA SSH session:

# journalctl -b 0 | grep "Started VMware Pod" | wc -l

7.The vCenter Server appliance is assigned 30GB of memory, which is insufficient to support 1300+ VMs.

  • vCenter Server Appliance configuration.
  • CPU: 8
  • Memory: 30GB
  • Disk: 1TB

8.We may look at the memory % history from last year and last month.

Based on memory history, we can determine that the memory percentage is sometimes more than 80% and sometimes lower.

Last month

Last year

Memory usage is around 80% which is triggering the alert in the VAMI Page.

We recommend increasing RAM from 30GB to 34 or 36GB to manage more than 1300+ VMs.

Suggestions:

Increase the memory of the vCenter Server appliance as required by following the procedures below:

1.Log in to the ESXi Host UI and shutdown the vCenter Server appliance .

2.Increase Memory.

3.Turn on the vCenter Server appliance


Check replication agreement and status with vCenter Server using CLI

By Lerpong Intaraworrapath | September 3rd, 2025

This article explains how to use the vdcrepadmin command-line interface (CLI) for assessing the vSphere domain and vCenter Server, as well as check the replication agreements and replication status in an environment.

How does it work?

In this article, we will look at 2 vCenter servers that have been setup with enhanced link mode.

Note that this requires BASH Shell access to the appliance. To change from the appliance shell to the BASH shell, see Toggling the vCenter Server Appliance 6.x default shell.

1.SSH into vCenter Server T01 and use the following command to display all of the vCenter Servers with a vSphere domain.

/usr/lib/vmware-vmdir/bin/vdcrepadmin -f showservers -h localhost -u administrator

2.After you press enter, you will be asked to type the password and enter.

3.You will find the results below.

4.Use the following command to determine the current replication status of any replication partner.

/usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartnerstatus -h localhost -u administrator

5.After you press enter, you will be asked to type the password and enter.

6.You will find the results below from vCenter Server T01 .

7.Then, log into vCenter Server T02 and run the command in step 4. The results are provided below.

Here we can see that both replication partners are 0 changes behind, and their changes are equivalent. Keep in mind that the two replication partners’ change values may differ from one another, and as long as they are 0 changes independently, everything is adequate.

Reference

Determining replication agreements and status with the Platform Services Controller (PSC)
https://knowledge.broadcom.com/external/article?legacyId=2127057

Toggling the vCenter Server Appliance default shell
https://knowledge.broadcom.com/external/article/319670