U R @ vSphere Admin's Space

Scenario We had a vCenter with External PSC. We converged them and converge job was successful execpt a cert warning. After a week we tried to decommission the old PSC appliance and found that the status is shown in WebClient as "Unknown" Up on checking we found  applmgmt in stopped state. Tried to start it but it failed with below error [ ~ ]# service-control --status Running:  lwsmd pschealth vmafdd vmcad vmdird vmdnsd vmonapi vmware-analytics vmware-certificatemanagement vmware-cis-license vmware-cm vmware-rhttpproxy vmware-sca vmware-sts-idmd vmware-stsd vmware-vapi-endpoint vmware-vmon Stopped:  applmgmt vmware-statsmonitor [ ~ ]# service-control --start applmgmt Operation not cancellable. Please wait for it to finish... Performing start operation on service applmgmt... Error executing start on service applmgmt. Details {     "detail": [         {             "tra...

vMotion Failing at 21% with error ""The vMotion failed because the destination host did not receive data from the source host on the vMotion network. Please check your vMotion network settings and physical network configuration and ensure they are correct." Scenario We built a new ESXi 6.7 Cluster and we couldn't make vMotions work there Troubleshooting steps 1) Make sure there is no IP address conflict. 2) SSH to ESXi and do a VMK Ping check For Default TCP/IP Stack vmkping 10.11.7.188 Or If you are using Multi NIC vMotion, you might want to specify which VMK interface to use vmkping -I vmk<vmkinterfacenumber> <Destination VMK IP to Ping> Eg -:  vmkping -I vmk3 192.168.1.1 For vMotion Stack I f you try above vmkping command on a ESXi host with VMK interfaces on VMK stack, they will fail with an error  Unknown interface 'vmk': Invalid argument Because the command is looking for TCP/IP stack by default and this VMK wont be listed there. So you need...

"Create a vSphere Distributed Switch"   "Status: The operation is not supported on the object" We were using CISCO ACI + vSphere for a while. We now have a new datacentre coming up and there were conversations on ACI vs NSX. But finally decided to give ACI a second chance :( Current datacenters are on vSphere 6.0 and were linked to ACI with no issues. We decided to go with latest 6.7 vSphere and Built them. ESXi hosts were added on to vCenter and a management DVS was created manually (we always had management DVS out side ACI!) and ESXi VMK0 was moved there, basically all went as per plan and well. Then came the ACI integration part... We had 3 vCenters and they were all under same VMM domain. So we decided to add the new VC also there. ACI Role was created in vCenter for permissions, service account is configured there mapping it to the new role. Time came for the integration and it wasn't happy about something.. After adding the new VC, ACI could see ESXi inve...

Today I was trying to install PowerCli on my Windows 10 machine using below command Install-Module -Name VMware.PowerCLI -RequiredVersion 11.1.0.11289667 Ended up with an error "PackageManagement\Install-Package : The following commands are already available on this system:'Get-Cluster,New-Cluster,Remove-Cluster'. This module 'VMware.VimAutomation.Core' may override the existing commands. If you still want to install this module" Looked like some of the modules are conflicting. As per MS document here " If the module being installed has the same name or version, or contains commands in an existing module, warning messages are displayed. After you confirm that you want to install the module and override the warnings, use the -Force and -AllowClobber"  So decided to use  -AllowClobber and it worked! 

vCenter Appliance - WebClient down with "Error: Service name is invalid" Last week I had to shutdown my lab vCenter 6.7. As it's just a lab I just powered it off instead of shutting down. After a few days I powered it back on when I wanted it back, and it booted without issues. But then WebClient wouldn't come up. Just says page cannot be displayed. I logged in to the appliance via SSH and tried to list service status root@vcenter [ ~ ]#  service-control --status --all 2019-04-04T10:43:41.796Z  Error: Service name "applmgmt" is invalid. 2019-04-04T10:43:41.816Z  Error: Service name "content-library" is invalid. 2019-04-04T10:43:41.837Z  Error: Service name "vcha" is invalid. 2019-04-04T10:43:41.857Z  Error: Service name "pschealth" is invalid. 2019-04-04T10:43:41.878Z  Error: Service name "sps" is invalid. 2019-04-04T10:43:41.898Z  Error: Service name "sca" is invalid. 2019-04-04T10:43:41.936Z  Error: Servic...

It's a shame but I recently had to P2V a Windows 2000 server, part of our legacy services, in order to free up and decomm an old physical server. It was not a pleasure at all :( Planning 1) Download and keep VMware Converter 4.0.1 (VMware-converter-4.0.1-161434.exe) – To P2V Windows 2000 P2V Converter 4.0.1 doesn’t support any vCenter/ ESXi later than 4.x. So I ended up in installing ESXi 4.0 on a VM running on top of my vSphere 6.5 infra! So 2) ESXi 4.0 ISO I read articles of people using VMware WorkStation for this, but in my case I didn’t want the export job to run outside datacentre, due to security reasons. My Windows 2000 Server that I need to virtualize is 200 Gig. So if you look at the disk size of ESXi VM, I made sure that It’s bigger than that.      3) Check Patch Level of Windows 2000 server and make sure > It’s updated to SP4 Rollup 1 ( KB891861 ) If not, install from here and reboot the server before running P2V job 4) Download and keep VMware Converter 6...