Skip to main content

 Removing an IPv4 address from a defined static pool in VMware vRealize Automation

https://knowledge.broadcom.com/external/article/343000/removing-an-ipv4-address-from-a-defined.html

Products

VMware Aria Suite

Issue/Introduction

This article provides steps on removing an IPv4 address from a defined static pool in VMware vRealize Automation.

In VMware vRealize Automation, you have defined a static IP address pool and deployed one or more virtual machines using this IP address pool. There are one or more IP addresses that belong to this pool you do not want allocated in the future.

Environment

VMware vRealize Automation 7.1.x
VMware vRealize Automation 7.2.x
VMware vRealize Automation 6.2.x
VMware vRealize Automation 7.0.x

Resolution

To remove an IPv4 address from a defined static pool:
 
Note: Ensure that a backup of the vRealize Automation database is taken prior to performing these steps.
  1. Log in to your SQL server and launch the MS SQL Server Management studio.
  2. Connect to your vRealize Automation database.
  3. Expand the Tables directory tree.
  4. Right-click dbo.StaticIPv4Address and click Select Top 1000 Rows.
  5. In the right-hand pane, you should see a table representing your static IP pool.

    Note: The column StaticIPv4AddressState represents whether vRealize Automation has already provisioned this IP address or not.
    1 = Unallocated, 0 = Allocated

     
  6. To mark an unallocated IP address as allocated and which virtual machine uses is, run this SQL query, changing ‘VM_name’ to the name of the VM that the IP is applied to and changing 'Enter IP Address Here' to the IP address you wish to remove from the pool.

    UPDATE StaticIPv4Address SET StaticIPv4AddressState = 0, VirtualMachineID = (SELECT VirtualMachineID FROM VirtualMachine WHERE VirtualMachineName = 'VM_name') WHERE IPv4Address = ‘Enter_IP_Address_Here

    For example:
    UPDATE StaticIPv4Address SET StaticIPv4AddressState = 0, VirtualMachineID = (SELECT VirtualMachineID FROM VirtualMachine WHERE VirtualMachineName = 'VMtest001') WHERE IPv4Address = '192.168.100.1'

Comments

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...

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...

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...