Skip to main content

 

IP Allocation failure during onboarding


Issue/Introduction

Symptoms:
  • When Onboarding a virtual machine, the IP Address allocation phase is skipped
  • When attempting to deploy a new VM from vRA, an IP conflict occurs with a previous onboarded VM


Environment

VMware vRealize Automation 8.x

Cause

IP conflict occurs because the onboarded VM's IP address was not allocated within vRA.

Resolution

VMware is aware of this issue.

In order to avoid IP conflicts in vRA, follow the steps below before onboarding VMs.

Important: The Prerequisites before onboarding are required even when there are no IP conflicts in the environment.


Workaround:

    Note: To query for allocated IP Addresses, run the following API query

    https://vRAFQDN/provisioning/uerp/resources/ip-addresses?expand=true&$filter=(ipAddress eq 'IPADDRESS') and (ipAddressStatus eq 'ALLOCATED')

    Where IPADDRESS is italicized and is required to be updated with the IP Address you wish to check for.

    New provisioned VMs with IP Conflicts

    In case you have new provisioned VMs with IP conflict before applying the workaround follow the next steps. 
    • Delete the newly provisioned VM
    • Release the IP
    • Ensure IP Address is in ‘Available’ status (To verify in: Infrastructure > Resources > Networks > IP Addresses)
    • Unregister the previously onboarded VM 
    • Delete the deployment whose resources were unregistered. To perform this operation only after ensuring VMs were successfully unregistered and back in ‘Discovered’ state. Discovered state can be verified under Virtual Machines tab.

    If you do not have any IP conflicts proceed with the following steps.

    Prerequisites before onboarding

    1. Ensure an address of the discovered VM is data collected: Cloud Assembly > Resources > Virtual Machines > Address 
    2. Create a valid subnetRange if you have not already done so: Infrastructure > Resources > Networks > IP Ranges        Note: when a vSphere cloud account is associated with an NSX instance then subnets need to be created in vRA for NSX networks for allocation to succeed during onboarding.
    3. In case of external IPAM onboarding, in addition to the above, add the below custom properties to the VM before executing the onboarding plan
      __Infoblox.IPAM.Migration.ExtensibilityKey

__IPAM.Migration.ExtensibilityKey 
whose values are the resourceIds of the VM
    Note: A ResouceId can be found and retrieved from Infoblox under the extensible attributes similar to the screenshot provided.
    Note: This step will ensure the deallocate IP to Infoblox occurs when the VM is deleted in vRA.image.png
    1. Add the discovered VM to the onboarding plan and run it. Network should be onboarded and IP should become allocated.
    2. Verify the IP is now allocated: Infrastructure > Resources > Networks > IP Addresses

    Additional Information

    Impact/Risks:
    This can lead to IP conflicts on your network when provisioning new virtual machines.
    Labels:

    Comments

    Post a Comment

    Popular posts from this blog

    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...
    Post a Comment
    Read more
      Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
    Post a Comment
    Read more
      "Cloud zone insights not available yet, please check after some time" message on Aria Automation https://knowledge.broadcom.com/external/article?articleNumber=314894 Products VMware Aria Suite Issue/Introduction Symptoms: The certificate for Aria operations has been replaced since it was initially added to Aria Automation as an integration. When accessing the Insights pane under  Cloud Assembly  ->  Infrastructure  ->  Cloud Zone  ->  Insights  the following message is displayed:   "Cloud zone insights not available yet, please check after some time." The  /var/log/services-logs/prelude/hcmp-service-app/file-logs/hcmp-service-app.log  file contains ssl errors similar to:   2022-08-25T20:06:43.989Z ERROR hcmp-service [host='hcmp-service-app-xxxxxxx-xxxx' thread='Thread-56' user='' org='<org_id>' trace='<trace_id>' parent='<parent_id>' span='<span_id>'] c.v.a.h.a.common.AlertEnu...
    Post a Comment
    Read more