Syed's Notes

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: esxupdat...

Hi There, This article will help you to validate the vxlan vmkernel network validation which can be performed on the host before its released into a production cluster. [root@esx11.syed.in:~] vmkping ++netstack=vxlan -s 1570 -d -I vmk3 172.18.6.85 [root@esx11.syed.in:~] vmkping ++netstack=vxlan -s 1570 -d -I vmk4 172.18.6.37 Note: vmk3 & vmk4 are the vmkernel created by NSX.

Hi There, This article will help you in validating the vmotion network connectivity between the hosts. I came across this validation while working on host expansion.  Below is the command can be used by just replacing the IP address and vmkernel of vmotion . [root@esx01.syed.in:~] esxcli network diag ping -I vmk1 --netstack=vmotion -H 172.18.2.102 Note: vmk1 was used for vmotion in my case. vmk1 of host01 : 172.18.2.101 vmk1 of host 02 : 172.18.2.102

Hi There, This article will help you to check network connectivity of vSAN vmkernel as I came across the situation where I was having issues with cluster partition and had to validate the vSAN network connectivity between the hosts. 1) Ping using vSAN vmkernel of host esx01 to esx02 vSAN vmkernel. [root@esx01.syed.in:~] vmkping -I vmk2 172.8.3.102 -d -s 7472  -I <interface> -d <set DF bit (do not fragment) in IPv4 or Disable Fragmentation (IPv6)> -s <size> Note: In my case vmk2 was assigned to vSAN vmkernel. vmk2 for host01 - 172.18.3.101 vmk2 for host02 - 172.18.3.102

 This article will help you to get the details of the physical switch port details of  ESXi uplinks. Step 1: Login to the ESXi host using root user/ SSO User. Step 2: Enter the below command into the terminal.   vim-cmd hostsvc/net/query_networkhint | grep 'portId\|devId\|vmnic' Output will show the details of the associated physical switch. Note: CDP, LLDP has to be enabled on physical switch. This information is needed when you end up in a troubleshooting session with network team for physical uplinks down/inconsistency of traffic.