In a vSphere environment with DPUs, using a kickstart file with "network –bootproto=dhcp" option results in installation failure
search cancel

In a vSphere environment with DPUs, using a kickstart file with "network –bootproto=dhcp" option results in installation failure

book

Article ID: 313258

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:

When using x86 ESXi installer with a kickstart to automate the install, it hits a failure in fetching network IP Address for 'Management Network' portgroup.

The NIC which is automatically selected for vSwitch0 is the DPU NIC function.


Environment

VMware vSphere ESXi 8.0.1

Cause

DPU pnic is incorrectly chosen for ESXi management network when "network –bootproto=dhcp" option is used.

Resolution

Currently there is no resolution to the issue. This will be fixed in the future release.


Workaround:

To workaround the issue, change the kickstart file without using 'network –bootproto=dhcp' and skip the boot option .