MICDROP
Enthusiast
Enthusiast

The deployed VM's network settings are incorrect.

Jump to solution

Hi, all.

The VM was deployed with a different IP than the network profile.

network-profile-1.PNGI have assigned the range 10.10.27.200 to 10.10.27.229

network-profile-2.PNGIn vRA, deployed VM's IP address is 10.10.27.200

real-vm.PNG

   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 !

1 Solution

Accepted Solutions
craigso
Enthusiast
Enthusiast

create customization spec in vCenter:

pastedImage_0.png

When you create your VM provisioning blueprint, specify the customization spec.

pastedImage_2.png

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.

View solution in original post

0 Kudos
19 Replies
xian_
Expert
Expert

Check if the interface connected to the VM is associated with the correct network profile.

0 Kudos
daphnissov
Immortal
Immortal

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.

0 Kudos
MICDROP
Enthusiast
Enthusiast
daphnissov
I've got the cause.
The deployed VM was deployed with the IP assigned to the Template.

How should I make a template?

I need your help.

0 Kudos
daphnissov
Immortal
Immortal

Don't understand what you're asking.

0 Kudos
MICDROP
Enthusiast
Enthusiast

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.

0 Kudos
daphnissov
Immortal
Immortal

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.
0 Kudos
MICDROP
Enthusiast
Enthusiast

Yes, I read it.

I do not use component profile.

I'm just using Custom Property.

("VirtualMachine.Disk0.Storage" AND "Hostname")

0 Kudos
daphnissov
Immortal
Immortal

You're not understanding. You need to use a vCenter customization spec. Are you using this?

0 Kudos
MICDROP
Enthusiast
Enthusiast

Oh, I understand now.

No, I don't use "customization spec".

I just created a VM, and I converted it to Template..

0 Kudos
daphnissov
Immortal
Immortal

Then that's your problem.

0 Kudos
MICDROP
Enthusiast
Enthusiast

I don't know what's problem with me.

Because the normal network profile was created.

0 Kudos
daphnissov
Immortal
Immortal

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.

0 Kudos
craigso
Enthusiast
Enthusiast

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.

0 Kudos
MICDROP
Enthusiast
Enthusiast

Do I need to template a VM created with a customization specification?

I don't know how to make a template...

0 Kudos
craigso
Enthusiast
Enthusiast

create customization spec in vCenter:

pastedImage_0.png

When you create your VM provisioning blueprint, specify the customization spec.

pastedImage_2.png

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.

0 Kudos
MICDROP
Enthusiast
Enthusiast

You were right !

It works !

Thank you so much !

You are my HERO : )

craigso
Enthusiast
Enthusiast

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.

0 Kudos
MICDROP
Enthusiast
Enthusiast

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.

0 Kudos
craigso
Enthusiast
Enthusiast

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:

pastedImage_0.png

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.

0 Kudos