Skip to main content

Having an issue for getting vxlan vmk installed on ESXi host?

Hi There,

I was working on a host expansion and unfortunately after following the standard procedure, NSX manager was not able to install the vxlan vmkernels.

The first thing I had to do is to put the host into cluster in maintenance mode and immediately had to follow the log file esxupdate.log file under the folder /var/log/ and then found the below error for three vibs.

ESXi : 6.7 build # 13981272

NSX: 6.4.4

-----------------------------------------------------------------------------------------------------------------------------

esxupdate: 2106395: esxupdate: ERROR: vmware.esximage.Errors.DependencyError: VIB QLC_bootbank_qedi_2.10.15.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.11.6.0, but the requirement cannot be satisfied within the ImageProfile.

 esxupdate: 2106395: esxupdate: ERROR: VIB QLC_bootbank_qedf_1.3.35.0-1OEM.600.0.0.2768847 requires qedentv_ver = X.11.6.0, but the requirement cannot be satisfied within the ImageProfile.

 esxupdate: 2106395: esxupdate: ERROR: VIB QLC_bootbank_qedrntv_3.11.7.0-1OEM.670.0.0.8169922 requires qedentv_ver = X.11.6.0, but the requirement cannot be satisfied within the ImageProfile.

-------------------------------------------------------------------------------------------------------------------------

With the help of KB article[https://kb.vmware.com/s/article/78389], I had to remove three vibs which were blocking the installation for ESXi host, below are the commands which I have used to first validate the vibs then had to remove them.

Validation:

[root@esx11.syed.in:~]esxcli software vib list | grep qedi

[root@esx11.syed.in:~]esxcli software vib list | grep qedf

[root@esx11.syed.in:~]esxcli software vib list | grep qedrntv

 Deletion:

 [root@esx11.syed.in:~]esxcli software vib remove -n qedi -f

[root@esx11.syed.in:~]esxcli software vib remove -n qedf -f

[root@esx11.syed.in:~]esxcli software vib remove -n qedrntv -f

 

Once the deletion of vibs was successful, I tried to add the host to the cluster and it worked fine.

Comments

Popular posts from this blog

System Recovery Partition Disk Blocks The Extension of Windows Disk - Sysprep Issues

Requirement : Windows Activated Template on vCenter  Issue : After the windows is installed, system recovery partition end up created next to windows disk.  Resolution Credit : Mohammed Junaid Ahmed                           Resolution :  1) Create a VM using standard procedure on vCenter  2) Power ON the VM and follow below screen instructions  Click Next   Click on ' Repair your computer '  Click on Troubleshoot       Click on Command Prompt     You should see the command prompt Begin with Diskpart   Click Turn off your PC Restart your computer and continue windows installation, and you will see the disk partitions as below

Renew SSL Certificate for vCloud Director 10.4

Hello There, I would like to give credit for this article to my colleague Muhannad S. Aljaghthami who worked on this task and gave us full insight on how to do. Now lets talk about replacing an expired/ about to expire SSL certificate for the vCloud Director application which is hosted on internet. Prerequisites: Digicert Certificate utility for windows.  Putty/Mobaxterm application for SSH to vCD cells. Winscp to transfer the files to vCD cells. SSH access should be validated on vCD Cells Backup tool to take a backup of vCD cells. Versions & products used while writing this article: vCloud Director 10.4 NSX AVI 22.1.1 Step by step procedure: Initiated a CSR request using Digicert utility for windows and shared the CSR with the team who manages the SSL certificates.  Post submission of CSR,we received the root & SSL certificate for our vCloud Director URL. Using the Digicert utility, we have extracted the pfx file and key file, sample screenshot below.     No...

Create a vCenter role using vCenter MOB

 Requirement: Finding a way to automate the creation of Role for any services with its permissions. Example: Citrix service account to be integrated with vCenter. Steps: 1) Login to vCenter : https://192.168.1.68/mob  2) Click on 'Content'                3) Click on Authorization Manager                                     4) Click on  'AddAuthorizationRole'                             5) Provide name in name field & privId in xml format & Click Invoke Method                        This should give you a return value and then the Role will be reflected on vCenter.