API

Continuing the credential cleanup in the same 9.1 environment from the expired password sync and VCFOPSPWID03 posts, one credential refused to settle: the service account SDDC Manager uses to talk to the NSX Manager API, svc-sddcmanager-a-nsx-mgmt--8199 in my lab. It showed up as disconnected, every remediation attempt failed, and the environment kept trying to rotate it in a loop. This one took several wrong turns before the actual root cause surfaced, and almost every wrong turn taught me something worth writing down. The short version: ...

While rotating credentials in the same 9.1 environment I covered in the expired password sync post, an Update of the NSX Manager admin password (credential type API) from VCF Operations kept failing after about a minute with error code VCFOPSPWID03 and a spectacularly unhelpful message: “call from NSX received invalid response.” The actual cause turned out to be simple — NSX rejected the new password because it had already been used on that manager. This being a lab, I was deliberately recycling a previous password. That goes against best practices, and NSX enforces it. But the way the error surfaces (and the way the reuse policy behaves in this build) is worth writing down. ...

In VCF 9.1, Fleet Password Management accounts can get stuck in EXPIRED status, and the password workflows changed compared to 9.0. In 9.0, you may have seen UI actions such as Disconnected or Remediate. In the 9.1 environment I was working on, those actions were not available. The UI exposed Update, and the Fleet Password Management API provides the same kind of workflow: query password accounts, then update or rotate the password. ...

If you need to pull log events programmatically from VMware Aria Operations for Logs (formerly vRealize Log Insight), filtering by a specific hostname, this guide walks you through the entire process — from authentication to querying the powerful internal API endpoint. This approach is inspired by Brock Peterson’s excellent series on the Aria Operations for Logs API, expanded here with full session authentication steps and hostname-specific query examples. Prerequisites Before we begin, you’ll need: ...

If you manage a VMware Aria Operations (formerly vROps) environment, you know how quickly alert fatigue can set in. In this guide I will focus specifically on the “Guest OS Experiencing CPU queue” alert. While helpful in identifying CPU-constrained VMs, it can quickly generate thousands of entries if you have a heavily over provisioned environment. Inspired by Brock Peterson’s excellent guide on Alert Hygiene, we are going to look at exactly how to cancel and delete these specific CPU queue alerts, both via the User Interface and programmatically via the API. ...

In the world of modern infrastructure operations, observability is only as good as the actions it drives. Integrating VMware Cloud Foundation (VCF) Operations (formerly Aria Operations) with ITSM platforms like ServiceNow is a critical step for many of my clients. It transforms passive monitoring into active incident management. However, as with any integration involving webhooks and external APIs, things don’t always go according to plan. Recently, while implementing a ServiceNow integration following standard deployment guides (kudos to Brock Peterson for his excellent documentation on ServiceNow Management Packs and Webhooks), I hit a roadblock. My instance was failing to send notifications, and the standard UI errors were vague. ...

If your vCenter logs are flooded with ApiGwServicePrincipal messages about token expirations, you’re not alone. These frequent “info” level logs in the apigw.log file can clutter your system, making it tough to identify real issues. Fortunately, there’s a simple workaround: adjust the logging severity from “info” to “error.” Below, I’ll guide you through the exact steps to reduce this log noise effectively. The Issue: Too Many ApiGwServicePrincipal Logs In vCenter, you might see repeated log entries like: ...

In the rapidly evolving landscape of VMware’s Cloud Foundation, security management is a cornerstone for maintaining the integrity and confidentiality of the software-defined data center (SDDC). The SDDC Manager, a critical component of VMware’s Cloud Foundation, offers a comprehensive suite of APIs for managing various aspects of the SDDC, including credentials management. This blog post delves into the specifics of leveraging the /v1/credentials API in SDDC Manager, offering a detailed guide for VMware professionals to enhance their security posture through efficient credentials management. ...

vSphere Resource Management with vRealize Operations (vROPs) DRS across multiple data centers is a critical requirement for managing large-scale virtualized environments. In this blog, we’ll discuss the requirements for using DRS in vROPs across multiple data centers. Cross vCenter vMotion (CVC-vMotion) Support: CVC-vMotion enables vMotion of virtual machines across multiple vCenter servers. This capability is a pre-requisite for vROPs DRS across multiple data centers. vCenter Server 6.7 Update 1 or later: vROPs DRS across multiple data centers requires vCenter Server 6.7 Update 1 or later. This ensures that the necessary APIs are available to enable vROPs to manage resources across multiple vCenter servers. Network Connectivity: All data centers should have a reliable and high-speed network connectivity, with the necessary firewall ports opened for communication between vCenter servers and vROPs instances. vROPs Replication: vROPs instances in different data centers must be able to communicate with each other. vROPs replication can be used to keep the data in all vROPs instances in sync, ensuring that the vROPs DRS decisions are based on consistent data. Same vROPs version: All vROPs instances must be running the same version of vROPs to ensure compatibility and prevent any issues with data consistency. Same vROPs license: All vROPs instances must be licensed with the same vROPs license, and the license should include the vROPs DRS capability. Cluster Configuration: The virtual machines that need to be managed by vROPs DRS must be in a vSphere cluster that spans across multiple vCenter servers. The vSphere cluster must be configured with the appropriate DRS settings, such as automated DRS, to ensure that vROPs DRS can make effective resource management decisions. In conclusion, vROPs DRS across multiple data centers is a powerful tool for managing virtualized environments at scale. By following these requirements, organizations can ensure that their vROPs DRS implementation is effective, efficient, and reliable.

I recently upgraded my LCM deployed SSC server to 8.8. If you need a guide to go through the upgrade you can find my other post here. After the upgrade was completed I was noticing strange behavior in the SSC UI so I checked the status of the services. Here are the errors I found and how I fixed them The first step was to check the status of the service ...