IP address after deploying a virtual machine (Windows)

[dya]

I am deploying a Windows virtual machine after creating a template.

During provisioning, I entered the host name and IP address. After deployment, I confirmed that the host name was as entered, but the IP address remained the same as in the original image.

I don't understand why the host name has changed but the IP address has not. Why is only the host name changed? Is this the correct result?
If so, I don't understand the purpose of entering the IP address during provisioning.

*Please excuse any confusion due to machine translation.

[dya]

When the connection destination is set to “OVS Port Group,” the IP address does not change.

When the connection destination is set to “OVS Bridge,” the IP address changes.

I noticed a change, so I think I've made some progress, but I would like to connect the virtual machine to the “OVS Port Group” that has the VLAN ID set.

Is it designed so that the IP address does not change when connected to the “OVS Port Group”?

[dya]

The IP address has been set.

There are multiple virtual machines, and to configure the tag VLAN, we created a network type called “OVS Port Group” under [Infrastructure] - [Network] - [Network].

By configuring the following settings, the host name and IP address were entered during provisioning, and the NIC connection destination was set to “OVS Port Group” with the entered host name and IP address.

1. Settings for the base network type “OVS Bridge”
・Checked “Allow IP override”
・Left other settings at their default values

2. Settings for the network type “OVS Port Group”
・ Entered VLAN ID, CIDR, gateway, primary DNS, and secondary DNS

Many of these settings are not documented, making it difficult to determine if they are correct, but I have resolved the issue for now.

[dya]

Additional information.

Even with the same settings, there are situations where it may not work properly.
You may need to configure the settings in the following order.

1. Configure the base network type as “OVS Bridge.”
・Check “Allow IP override.”
・Leave the other settings as default without changing them.

2. Create and configure a network type “OVS Port Group”
・Enter the VLAN ID, CIDR, gateway, primary DNS, and secondary DNS

Even with the same settings, the results may vary.
Therefore, it would be reassuring to have a way to confirm that the settings made in the WebUI are correctly reflected.

[Olivia431]

I also have the same issue with, If you find the solution please must let me know as it's a great favour.

[Arnout_Verbeken]

You can use the bridge, or a port group connected to a bridge.

I have a BRIDGE management, which is my standard bridge that I created in Ubuntu before deploying VME.  it's the bridge that hosts my VME Manager.

I have another BRIDGE compute, which contains mulitiple port groups (= VLANS).
If you use port groups, there is of course no need to set the IP settings on the bridge, but you do that on the port groups (VLANS).

For Windows deploys based on sysprep images, you can try to enable "Force Guest Customization" in the Virtual Image.

For Linux, we use cloudinit.

You can also use "Cloudbase Init" on Windows, but it requires to install Cloudbase before sysprepping.

[dya]

Yes, I know and have configured the settings in port groups, etc.

However, I am writing because there are cases where it still does not work.
I am thinking that perhaps there are cases where the settings are not reflected as configured. (I suspect it is a bug in HVM)

Regarding the deployment of sysprep'd images, I think your answer is different from what is described in the documentation.
https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006560en_us&page=GUID-FBB8F5A7-8358-4CB7-9C31-10D74E2F3AE7.html

Translated with DeepL.com (free version)