AutoDeploy does not set correct ESXi boot order
Article ID: 441578
Updated On:
Products
Issue/Introduction
AutoDeploy completes but boot order is incorrect.
Autodeploy does correctly install the ESXi image but the boot order is set incorrectly.
Example
Expected / Correct UEFI Boot Sequence
BOSS in SL XX
PXE Device #: NIC in Slot X Port Y Partition Z
Unavailable: NOSBOOT
Actual / Incorrect UEFI Boot Sequence
PXE Device #: NIC in Slot X Port Y Partition Z
Unavailable: NOSBOOT
BOSS in SL XX
Cause
The following options were set on the vCenter for AutoDeploy. These were set for earlier ESXi versions but are no longer required.
'extra-boot-args' = 'norts=1'
'extra-kernel-args' ='-U'
- Connect to vCenter Server using VMware PowerCLI. For more information , see vSphere PowerCLI Administration Guide.
# Connect-VIServer -Server vCenter_IP -Protocol https -User [email protected] -Password <password>
Example:
# Connect-VIServer -Server vcsa.example.com -Protocol https -User [email protected] -Password ******2. Confirm the values are set
# Get-DeployOption -Key "extra-kernel-args"
Key Value
--- -----
extra-kernel-args -U
# Get-DeployOption -Key "extra-boot-args"
Key Value
--- -----
extra-boot-args norts=1
Reference:
https://knowledge.broadcom.com/external/article/326289/
https://knowledge.broadcom.com/external/article/314045/
Resolution
Unset these options on the vCenter using powerCLI
- Connect to vCenter Server using VMware PowerCLI. For more information , see vSphere PowerCLI Administration Guide.
# Connect-VIServer -Server vCenter_IP -Protocol https -User [email protected] -Password <password>
Example:
# Connect-VIServer -Server vcsa.example.com -Protocol https -User [email protected] -Password ******
Output should look similar to the following:
- Run the following PowerCLI Commands:
# Set-DeployOption "extra-boot-args" " "
# Set-DeployOption "extra-kernel-args" " "
Additional Information
https://knowledge.broadcom.com/external/article/326289/ VMware ESXi 7.0/8.0 with Auto Deploy fails to boot with error "Shutting down firmware services... Using 'simple offset' UEFI RTS mapping policy"
https://knowledge.broadcom.com/external/article/314045/ Booting an ESXi host over UEFI PXE hangs with the message "Using 'simple offset' UEFI RTS mapping policy"
Feedback
