Hi, all.
The VM was deployed with a different IP than the network profile.
I have assigned the range 10.10.27.200 to 10.10.27.229
In vRA, deployed VM's IP address is 10.10.27.200
However, the IP that you see in the VM has a completely different IP allocation.
What am I supposed to fix?
Thanks for your advice !
create customization spec in vCenter:
When you create your VM provisioning blueprint, specify the customization spec.
If you are using profiles, then define the spec in the profile in the same way.
If these are configured, your network setting should be applied to the VM.
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
Check if the interface connected to the VM is associated with the correct network profile.
Are you using a customization spec in your blueprint or component profile? If not, that's your issue. Use of one is required to set a static IP from a profile or elsewhere.
How should I make a template?
I need your help.
Don't understand what you're asking.
When I created catalog, I selected the Clone option to distribute using Template.
The template was assigned an IP (e.g. 1.1.1.1).
Even if I apply 2.2.2 network profile, VMs deployed with that catalog are deployed with IP of 1.1.1.1.
Did you read my previous reply?
Are you using a customization spec in your blueprint or component profile? If not, that's your issue. Use of one is required to set a static IP from a profile or elsewhere.
Yes, I read it.
I do not use component profile.
I'm just using Custom Property.
("VirtualMachine.Disk0.Storage" AND "Hostname")
You're not understanding. You need to use a vCenter customization spec. Are you using this?
Oh, I understand now.
No, I don't use "customization spec".
I just created a VM, and I converted it to Template..
Then that's your problem.
I don't know what's problem with me.
Because the normal network profile was created.
You're not listening to what I'm saying. This ability has nothing to do with network profiles. Please go back and re-read my posts.
I had this issue as well. You need to define a customization spec in vCenter. Then reference that when you provision your VMs in vRA. Other wise the network settings will not get applied to the VM. This is because the customization spec is what does the actual configuration.
Do I need to template a VM created with a customization specification?
I don't know how to make a template...
create customization spec in vCenter:
When you create your VM provisioning blueprint, specify the customization spec.
If you are using profiles, then define the spec in the profile in the same way.
If these are configured, your network setting should be applied to the VM.
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
You were right !
It works !
Thank you so much !
You are my HERO : )
You're welcome!
I had the same questions when I started with vRA. These communities have helped so much. Just trying to pay it back when I can.
Hi, craigso !
I'm so sorry, but I need your help one more time..!
Windows Catalogs has been resolved by assigning Customization Specs with your help.
However, there is a problem creating Linux Catalog.
Creating a customization specification for Linux and assign it to the Linux catalog, the catalog deployment does not complete at 99%.
VM status shown "Customize Machine" in vRA (infrastructure > Managed Machines)
In addition, VMs deployed using Catalog are created in vCenter, but the network adapter is disconnected and IP addresses are not allocated.
If I don't assign a Customization Spec to a Linux blueprint, it's 100% complete, and the Network Adapter is also connected, but it's the same thing that IP address not allocated.
Please help me once more..
Thanks & Regards.
I am a bit less familiar with Linux provisioning, however we do a bunch of it in our environment. The first thing I would check is to make sure your Linux customization spec is correct. This is what mine looks like:
It has a lot less settings configured that the Windows one.
Second, the behavior you described makes sense if you don't assign a customization spec. It would provision, but would just be a clone of the template. Likely on the wrong network, and configured with the same IP.