Checking the last two entries in the vpxd.log, there seems to be a gap in the logging before the service actually stops. Are you sure there is nothing there? Maybe, enabling verbose for vpxd migh...
See more...
Checking the last two entries in the vpxd.log, there seems to be a gap in the logging before the service actually stops. Are you sure there is nothing there? Maybe, enabling verbose for vpxd might help for additional logging. **2018-10-10T09:46:52.667+02:00 info vpxd[7FA183A597A0] [Originator@6876 sub=HostGateway] CmConnectionFSM::RunFSM(ST_INIT) 2018-10-10T09:46:52.671+02:00 info vpxd[7FA183A597A0] [Originator@6876 sub=[SSO][SsoCertificateManagerImpl]] [CreateServiceContent] Try to connect to SSO VMOMI endpoint. | 2018-10-10T09:56:59.157+02:00 info vpxd[7FA172B5E700] [Originator@6876 sub=vpxdvpxdSignal] Signal 15 received, exiting 2018-10-10T09:56:59.157+02:00 info vpxd[7FA172B5E700] [Originator@6876 sub=Default] Initiating VMware VirtualCenter shutdown** Cheers, Supreet
Now that you had considerable progress with ESXi 5.5, check the link ESXI 6.0 INSTALLER DOES NOT DETECT NETWORK ADAPTER – The HomeWork and see if you can inject the network driver. Cheers, Su...
See more...
Now that you had considerable progress with ESXi 5.5, check the link ESXI 6.0 INSTALLER DOES NOT DETECT NETWORK ADAPTER – The HomeWork and see if you can inject the network driver. Cheers, Supreet
Nope, auto-unmap is available only with VMFS-6. And only if, the storage array supports auto reclaim. Please close the thread if your queries have been answered. Cheers, Supreet
Since Windows 2003 is no more supported by Microsoft, it is currently in legacy support phase. My strong recommendation would be to go with at least W2k8 and above. Cheers, Supreet
1) Are you referring to automatic unmap with VMFS-6 or are you running manual unmap command? 2) Does your array even support unmap? https://cormachogan.com/2016/12/05/determining-array-supports-...
See more...
1) Are you referring to automatic unmap with VMFS-6 or are you running manual unmap command? 2) Does your array even support unmap? https://cormachogan.com/2016/12/05/determining-array-supports-automated-unmap-vsphere-6-5/ / Storage reclamation – part 1 – VMware vSphere | Kalle's playground 3) During the unmap, are you seeing an increment in the Delete Stats under VAAIStats in esxtop? VAAI Thin Provisioning Block Reclaim/UNMAP In Action - VMware vSphere Blog Cheers, Supreet
From within the VM folder, does the disk report 'Device or Resource Busy' if the command <touch *> is run? If yes, run the command <vmkfstools -D "Server02.MSMETZCO.LOCAL-flat.vmdk"> and identify...
See more...
From within the VM folder, does the disk report 'Device or Resource Busy' if the command <touch *> is run? If yes, run the command <vmkfstools -D "Server02.MSMETZCO.LOCAL-flat.vmdk"> and identify the MAC address of the host that is holding a read-only lock on the disk. Is it a VMFS-6 datastore? Cheers, Supreet
Going by the current information, it might be supported only from ESXi 6.5 onward (Cannot be sure till it comes out of Tech Preview phase) - Cheers, Supreet
Most likely, the vendor images are released only with every major update. For intermediate patches (Patch or Emergency Patch), you will need to download them from VMware Patch Repo or use Update ...
See more...
Most likely, the vendor images are released only with every major update. For intermediate patches (Patch or Emergency Patch), you will need to download them from VMware Patch Repo or use Update Manager. Cheers, Supreet
Do you see any files under /var/core dir? Can you share the vmkernel and hostd log files recorded before the recent reboot of the host? Cheers, Supreet
For the above PSOD, let us uninstall the qfle3 related drivers so that the card is forced to use the bnx2x driver. Run the below commands and reboot the host. Once host is rebooted, check if the ...
See more...
For the above PSOD, let us uninstall the qfle3 related drivers so that the card is forced to use the bnx2x driver. Run the below commands and reboot the host. Once host is rebooted, check if the qfle3 drivers are uninstalled. Post validation, insert the card and see if you still hit the same PSOD. esxcli software vib remove --vibname=qfle3 esxcli software vib remove --vibname=qfle3f esxcli software vib remove --vibname=qfle3i Cheers, Supreet
Check if the KB VMware Knowledge Base helps. If not, start of with checking two things - 1) In the lookupserver.log, check if there are any complaints about the SQL password being expired. 2...
See more...
Check if the KB VMware Knowledge Base helps. If not, start of with checking two things - 1) In the lookupserver.log, check if there are any complaints about the SQL password being expired. 2) If the SSO is external, check if the SSO services are running or not. Cheers, Supreet
This PSOD looks like an issue with the qfle3 driver. Can you run the below commands and share the output? esxcfg-nics -l esxcli software vib list | egrep -i 'qfle|bnx2' Cheers, Supreet
Reboot the host once. If the bootbank still points to /tmp, we might be looking at a bad boot disk. Involve the hardware vendor then. Before rebooting the host, ensure to backup the configuration...
See more...
Reboot the host once. If the bootbank still points to /tmp, we might be looking at a bad boot disk. Involve the hardware vendor then. Before rebooting the host, ensure to backup the configuration - VMware Knowledge Base Cheers, Supreet
