Archive for the ‘Troubleshooting’ Category

while deploying VCSA from Linux environment to ESXi host check below condition are correct on your system.

  • DNS server should be needed in Linux machine
  • /etct/hosts entry should have esxi and vcsa DNS name entry in Linux machine
  • in the esxi side means where you are deploying esxi from there nslookup sholud work in ESXi
  • in /etct/resolv.conf entry should have only one DNS server. esxi should not have multiple entry like below.

in the above screen shot /etc/resolv.conf have both Ipv4 and IPv6. Actually in this case automatically ipv6 added by some other dhcp in the same network. is actual dns entry rest added by DNS name server because same network multiple dhcp server is running . remove that entry if saw in /etc/resolv.conf.

Solution :

TFTP open time out because server not able to reach tftp server.  If you added iptables rule for tftp dhcpd and http server. Add the rules for this server also and re-trigger the same




while doing pxe boot of any VM or server we will give mac address under this path /tftpboot/linux-install/pxelinux.cfg that time if u gave Upper mac address as below  it will fail

lrwxrwxrwx 1 root root  10 Feb 20 07:32 01-00-50-A6-9C-CE-E7 -> vm68
lrwxrwxrwx 1 root root  10 Feb 20 07:32 01-00-50-A6-9C-C1-C7 -> vm19

change as below it work 🙂 🙂 🙂

lrwxrwxrwx 1 root root  10 Feb 20 07:32 01-00-50-a6-9c-ce-e7 -> vm68
lrwxrwxrwx 1 root root  10 Feb 20 07:32 01-00-50-a6-9c-c1-c7 -> vm19

[root@nagios ~]# pvcreate /dev/sdb3
Device /dev/sdb3 not found (or ignored by filtering).

Fix : kernel partition table  not  synced /dev/sdb3 partition so you got a above error

#init 6 (not recommended)

#partx -av /dev/sdb

[root@localhost ~]# vim /etc/fstab
[root@localhost ~]# mount -a
mount: mount point /data does not exist
mount: mount point /data2 does not exist

Fix : fstab newly added partition information /data /data2 directory is not yet created

#mkdir /data /data2

#mount -a


For the Above issue ESXi  keep on booting PXE only means it is not booting from local Disk.After long time analysis concluded as

In my lab,LUN id is mismatch happen between Storage host LUN id and Blade Server host LUN id.


Storage Boot LUN Host LUN id = ESXi Host blade SAN Boot LUN id

For many users this has worked, for me, it did not. As you can see in the image below, vCenter does not have the vSphere Data Protection.


In order to resolve this problem I accessed https://<vCenterIPAddress>/mob. From there log in with your Administrator account, whatever that might be. From there you will need to select “content”.


After selecting that, you will be presented with a bunch of properties. Scroll down and select “ExtensionManager”


From there you will be presented with another screen that will show you all of your extensions and provide some methods at the bottom. Verify that extensionList[“com.vmware.vdp”] is listed.  You will need to select “UnregisterExtension”.


After selecting “UnregisterExtension” a popup willbe presented. Enter “com.vmware.vdp” without the quotes and select “InvokeMethod”.


Once this has completed, you will notice that extensionList[“com.vmware.vdp”] is no longer listed.

After all the steps above have been completed, reboot your vDP VM by right clicking on the virtual machine and selecting “Restart Guest OS”. Once it reboots, log out of the vCenter Web Client and log back in using your credentials. This should present vSphere Data Protection extension in your vCenter.



If not working above steps reboot vcenter definitely it will work.

Hopefully this will help someone because it ate up a good portion of my time.