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

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