Skip to main content

 Validating VMware Aria Suite Lifecycle 8.x health

https://knowledge.broadcom.com/external/article?articleNumber=326075

Products

VMware Aria Suite

Issue/Introduction

This article provides a list of steps to validate the health of VMware Aria Suite Lifecycle (formerly VMware vRealize Suite Lifecycle Manager) 8.x appliances.

Environment

VMware vRealize Suite Lifecycle Manager 8.x
VMware Aria Suite Lifecycle 8.x

Cause

This article helps to validate the health of VMware Aria Suite Lifecycle (formerly VMware vRealize Suite Lifecycle Manager) 8.x appliances.

Resolution

Prerequisites

  • You have access to root username and password.
  • You have access to PuTTY or a similar utility to connect to SSH on the appliance.

Procedure

Validate Services

  1. SSH into the Aria Suite Lifecycle appliance.
  2. Run the following command to validate health of the main services:
    vrlcm-cli --health-status

If any of the services show any other status then Running, run the following commands to check each service individually:

systemctl status vrlcm-server
systemctl status blackstone-spring
systemctl status vpostgres

List all services:

systemctl list-unit-files --type=service --all
Example Output:

Validating DNS

nslookup $(iface-ip eth0)
nslookup $(uname -n)

Validating Disk Space

df -h

Example Output:

The /data partition can be validated and extended in the product UI by navigating to Lifecycle Operations > Settings > System Details.

As a best practice, always delete binaries that are not in use in Lifecycle Operations > Settings > Binary Mapping.

Additional Articles

VMware Aria Suite Lifecycle Best Practices

  1. Follow snapshots practices as defined in Best practices for using VMware snapshots in the vSphere environment.
  2. Validate you have a backup and restoration plan and are frequently backing up the appliance.
  3. Do not store log bundles or database dumps persistently on the appliance. Remove them once they are copied to VMware or moved to an offline location for review.
  4. VMware Virtual Appliances and customizations to operating system and included packages is not supported.

Product Support Pack Validation

  • When attempting to upgrade a managed product and receiving LCMSOURCEMAPPING10018, review the latest release notes for the required Product Support Pack (PSPAK) for the product you are attempting to upgrade.
    • If you have the correct PSPAK installed, confirm the CHECKSUM of the downloaded file matches the download source.


Comments

Post a Comment

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...
Post a Comment
Read more

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
Post a Comment
Read more
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...
Post a Comment
Read more