VMware VRA Provisioned IP address.

[vikramkumarpuli]

Hi All, 

I have configured Cloudzone, Network profiles , Network etc. I have added IP address to the Network.(which has start IP x.x.x.1 and end IP x.x.x.254 these IP are of range:type-Network) for which x.x.x.1 is default gateway. I have Infoblox plugin configured in VRA for getting the IP address. 

When the VM is deployed ...it is getting .1 for the VM IP address(vCenter and Infoblox i can see IP getting configured) and later it is failing. Tagging is correct as i can see correct segment ip is getting configured.  We have a test subnet(Range:type-Range) for which has range start IP : x.x.x.4 and end ip : x.x.x.14..where VMs are deploying and configuring correct IP address. All other production ranges are starting from .1, but that is default gateway.. 

I see the in Infoblox .1 is unused for the segments. does that cause issue? or something missing in VRA end? 

VRA 8.11 and Infoblox plugin 1.4

Thanks and Regards,

Vikram 

[RonPSSC]

Hi Vikram;

You need to create an IPv4 Reservation for the Default Gateway (.1) in Infoblox for each Network that you are making available for consumption. Doing so will prevent Infoblox from allocating that Address during provisioning in vRA 8. (See images below)

If you're using vSphere as your hosting/hypervisor solution, you might also want to reserve (.2) as well within the same Router Settings in IPv4 DHCP Options in Infoblox. This might no longer be required with vRA 8 (Aria) but I do this all the same as a matter of practice/principle. This was required for vRA 7.x versions.

Hope this helps.

Ron

[vikramkumarpuli]

Hi Ron, 

Thanks for reply, as suggested creating IPV4 reservation on .1 resolved the issue. Deployed VM is taking.2 as IP address. But, its also getting another APIPA IP adderss, due to which VM is not accessible (RDP not working and domain jjni is not working),

In test subnet(Range:type-Range) for which has range start IP : x.x.x.4 and end ip : x.x.x.14, i am not facing this issue.  VM  not getting APIPA IP in test subnet. What could cause APIPA IP in dev network(which has start IP x.x.x.1 and end IP x.x.x.254 these IP having range:type-Network) 

Regards,

Vikram Kumar

[RonPSSC]

Hi Vikram;

I had replied a few days ago to your post via direct email. I'm guessing you weren't notified? No worries however. I've simply reiterated below what I had sent. 

The fact you're getting 2 IP Addresses might have something to do with your Image Template. Make sure your image is prepared correctly using the (Windows) CloudBase-Init. If it is, maybe you can start up your base image, run the Microsoft "Sysprep" tool, and then shut it down.

The other suggestion I have is to check whether your image has a static IP assigned to it. In certain test cases of mine, I've seen incidents of where the image will not release the original adapter which ultimately ends up getting a self-assigned dynamic IP. You shouldn't be getting 2 Addresses.

Another suggestion is to see whether you have a DHCP Server Scope running on your Dev segment that could be causing conflict on bootup?

 

Finally, and more importantly, since you're not able to join the domain or even RDP to your VM in the Dev segment indicates (to me) that traffic might be blocked somewhere between your "AD or Test" segments and your Dev segment. Check either your network firewall settings or perhaps, even more likely, your Windows Image itself to see if Windows Defender Firewall Settings might be started/connected. 

 

That's all I can offer for now.

 

Good luck. Ron

[vikramkumarpuli]

Hi Ron, 

As you suggested, IPV4 reservation done and VM is getting next free IP address. But, it is also getting APIPA, due to which the other actions/workflow failing. (RDP is also not working, joining to domain is failing).

The issue happening with new ip subnet which has  range:type-Network) from .1 to .254 and not with test subnet which has range type: Range .4 to .14. 

Regards,

Vikram Kumar