[IDPA] ESXi Host shows disconnected on the vCenter WebClient causing all IDPA components to appear with red exclamation in the ACM UI


   Article Number:     536576                                   Article Version: 2     Article Type:    Break Fix 




Integrated Data Protection Appliance Family,Integrated Data Protection Appliance Hardware,Integrated Data Protection Appliance Software,DP4400 Appliance,Integrated Data Protection Appliance,Integrated Data Protection Appliance 2.4





Login to the vCenter WebClient and verify the ESX Host showing disconnected :       
        User-added image       
        Right Click on the ESX Host --> Connection --> Connect.       
        If the ESX Host does not automatically reconnect, a wizard appears.       
        Follow the wizard and provide ESXI host root username and password in the authentication tab and click on Connect.       
        If there are any issues, the connect operation might fail.        
        Note: Make sure the root user password is correct. Remove the ESXI host from vcenter inventory and try readding/registering the same again.        
        If the following error message is seen, review the vcenter vpxd log:
      Unable to add the ESXi Host << Error message: There was an error communicating with the remote host     
      SSH to the vcenter and traverse to /var/log/vmware/vmware-vpxd/vpxd.log and review the vpxd.log.       
        The following error message can be seen :
      2019-08-13T10:08:41.753-06:00 info vpxd[7F1D96978700] [Originator@6876 sub=Default opID=AddHostWizard-add-45159-ngc:70005260-7a] [VpxLRO] -- ERROR task-2395 -- group-h4       
         -- vim.Folder.addStandaloneHost: vmodl.fault.HostCommunication:       
        --> Result:       
        --> (vmodl.fault.HostCommunication) {       
        -->   faultCause = (vmodl.MethodFault) null,       
        -->   faultMessage = <unset>       
        -->   msg = ""       
        --> }       
        --> Args:       
        --> Arg spec:       
        --> (vim.host.ConnectSpec) {       
        -->   hostName = "x.x.x.x",       
        -->   port = <unset>,       
        -->   sslThumbprint = <unset>,       
        -->   userName = "root",       
        -->   password = (not shown),       
        -->   vmFolder = 'vim.Folder:78a59c25-81c3-4169-85a6-61914d3e00c8:group-v3',       
        -->   force = true,       
        -->   vimAccountName = "vpxuser",       
        -->   vimAccountPassword = (not shown),       
        -->   managementIp = <unset>,       
        -->   lockdownMode = "lockdownDisabled",       
        -->   hostGateway = (vim.host.GatewaySpec) null       
        --> }       
        --> Arg compResSpec:       
        --> Arg addConnected:       
        --> true       
        --> Arg license:       
        2019-08-13T10:08:41.753-06:00 error vpxd[7F1D95FE5700] [Originator@6876 sub=licenseClient opID=AddHostWizard-add-45159-ngc:70005260-7a-LicenseClientUnregisterHostAsync-       
        60e04d00] Swallowing exception 'vim.fault.LicenseEntityNotFound' thrown when unregister entity 'host-106'
      This error could be caused if the vpxa password is already available in vCenter cache. 






The ESX Host vpxa password is already available in vCenter cache or the vCenter database which caused the ESX Connect operation to fail with error message: "Error message: There was an error communicating with the remote host"                                                           






1: SSH to ESX Host as root user and stop the vpxa service :       
        /etc/init.d/vpxa stop       
        2: On the vCenter WebClient UI, try readding the ESX Host.       
        Right click on the datacenter 'DPappliance- and select 'Add Host'       
        Walk through the wizard and provide ESXI host 'root' user credentials to connect.       
        3: ESXI integration/connect should work fine without issues.       
        4: On the ESX Host CLI session, verify the vpxa service came up after the integration automatically.       
        /etc/init.d/vpxa status       
        The service status should show as running.       
        5: At this point, the ESX Host should start showing as connected again in the vCenter WebClient.