SupreetK's Accepted Solutions

AFAIK with vDS, these policies are defined at the portgroup level. Then, they can be overridden at the individual ports level. Also, either all the portgroups can be similarly configured for the policies or they can have their individual configuration. More details in the below links - Manage Policies for Multiple Port Groups on a vSphere Distributed Switch Configure Overriding Networking Policies on Port Level Cheers, Supreet

Looks like you have verbose logging enabled for the vpxa agent. Can you change it to Info level and see if it makes any difference? Verbose and Trivia logging is enabled only in case of troubleshooting and should be changed back to Info or Warning at the earliest - VMware Knowledge Base​ Cheers, Supreet

Based on the event description, it looks like they logged in to the host client of the host in question as a root user. Regarding the host losing connectivity to the boot SD card, what events (except the login ones) do you see in the vCenter or on the host? How often does it occur? Does reboot of the host addresses the issue? Cheers, Supreet

Hope you have already validated the compatibility of your server hardware and its components with ESXi 6.5. Proceed, only if they are compatible. If the ESXi is installed on the same local disk as the local datastore where the VMs reside, you have to use the 'Upgrade ESXi, preserve VMFS datastore' option. Ensure the use the hardware vendor custom image for 6.5 and not the VMware standard image. Other details and step-by-step instructions with screenshots are provided in both the below links - Upgrade ESXi 6 to ESXi 6.5 | Mastering VMware​ How to Upgrade ESXi 6.0 to ESXi 6.5 using ISO image Cheers, Supreet

Create a new alarm definition and add the below VOB entries on the Triggers section - esx.problem.storage.apd.start esx.problem.storage.apd.timeout More details in the below blogs - https://www.virtuallyghetto.com/2014/04/how-to-create-vcenter-alarm-to-alert-on-esxi-5-5u1-nfs-apd-issue.html Elastic Sky Labs: All Paths Down (APD) and Permanent Device Loss (PDL) Cheers, Supreet

Port binding mainly depends on whether both the storage vmkernel ports (and the array targets) are going to be in the same network or in different network. If both the iSCSI vmkernel ports are going to be in the same subnet, create a single vSwitch and two vmkernel ports. Assuming the two uplinks are vmnic2 and vmnic3 - For vmkernel port-1, vmnic-2 should be active and vmnic-3 should be in unused. And vice versa for vmkernel port-2. Only then, you will have a compliant iSCSI port binding configuration. More details in the below links - VMware Knowledge Base iSCSI Port Binding in vSphere 6 – Virtual Reality Cheers, Supreet

For VM processor metrics, look at the 'VM Processor' counter. For the host metrics (core-1 and core-2), check the CPU metrics on the ESXi performance charts, not inside the Windows guest operating system. Cheers, Supreet

I don't think any of the below models are supported beyond ESXi 6.0. At 'Loading /tools.t00' phase, the ESXi kernel will not be loaded yet. So even enabling the serial logging is of no use. My suggestion would be to go with the supported version of ESXi. Cheers, Supreet

1) Upgrade the host client to the latest version - ESXi Embedded Host Client​ 2) Since the ESXi is still on a version below 6.5 U1, you can use the vSphere client to connect to the host - http://vsphereclient.vmware.com/vsphereclient/5/1/1/2/5/0/8/VMware-viclient-all-6.0.0-5112508.exe Cheers, Supreet

I understand that you want the previously run commands to not show up when you use the up arrow mark on the ESXi command line. If yes, follow the below steps in order - 1) Login to ESXi via SSH. 2) Run the command "> /.ash_history" to null the history file. 3) Logout and re-login. Now, it will not show you the previous commands when using up arrow mark. 4) Irrespective of the user, all the commands are stored even in shell.log (under /var/run/log). You can clear that as well using the command "> /var/run/log/shell.log". Cheers, Supreet

Seeing the below errors in vpxd.log --> 2018-09-14T17:32:22.276+03:00 error vpxd[7F73A580C700] [Originator@6876 sub=vpxUtil opID=FlowBasedWizard-apply-911-ngc-80] /usr/bin/python failed with error [1] and output [2018-09-14T14:32:22.095Z   Failed to start statsmonitor services. Error: Operation timed out 2018-09-14T17:32:22.276+03:00 info vpxd[7F73A580C700] [Originator@6876 sub=Default opID=FlowBasedWizard-apply-911-ngc-80] [VpxLRO] -- ERROR task-65223 -- FailoverClusterConfigurator -- vim.vcha.FailoverClusterConfigurator.deploy: vmodl.fault.SystemError: --> Result: --> (vmodl.fault.SystemError) { -->    faultCause = (vmodl.MethodFault) null, -->    faultMessage = <unset>, -->    reason = "Failed to start HACore profile on node 192.168.18.22" -->    msg = "" --> } Before initiating vCHA, perform the below steps on the vCSA active node - Take a snapshot of the vCSA VM. Login to vCSA with root credentials via SSH. Modify statsmonitor service config for vMon                sed -i '/StartTimeout/d' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json                sed -i '/ApiHealthFile/a "StartTimeout": 600,' /etc/vmware/vmware-vmon/svcCfgfiles/statsmonitor.json Reload vMon service config through SIGHUP                kill -HUP $(cat /var/run/vmon.pid) Stop and start statsmonitor service.                /usr/lib/vmware-vmon/vmon-cli -k statsmonitor                /usr/lib/vmware-vmon/vmon-cli -i statsmonitor Enable vCHA. Cheers, Supreet

Two things to start of with - 1) For the VMs to move automatically when the host is placed in maintenance mode, the DRS should be set to Fully Automated mode. 2) With just two hosts in the cluster, do not use vSphere Admission Control feature. Maybe that is why it is complaining about 'Insufficient vSphere HA failover resources' once one of the host is put into maintenance mode. Cheers, Supreet

This is a known issue with the iLO firmware version 1.30. Downgrade to version 1.20. VMware Knowledge Base​ https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00053955en_us Cheers, Supreet