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