5 Replies Latest reply on Jun 29, 2018 9:57 AM by daphnissov

    vCenter 6.7 fresh install not working

    lecfl Lurker

      Hi guys,

      I have 3 ESXi hosts 5.5 and vCenter 5.5

      I'm trying to move to 6.7,

      So I installed it on 1 of my hosts to test it

      I created the networks, all is good with the host, the problem is with the vCenter:

      If I deploy it on the VManage network (that has no internet), the deployment gets stuck at 80% (something with the RPM (I can't remember the error message))

      If I deploy it on the VM network (that has internet), and configure it as DHCP with FQDN, the deployment finishes stage 1, but gets stuck at stage 2

      If I deploy it on the VM network (that has internet), and configure it as DHCP without FQDN, the deployment finishes successfully,

      (that is what I did last), then move it to the VManage network, here comes all the problems:

      Changing the IP settings from DHCP to static at the vCenter Console gives me an error "management network configuration not allowed vcenter"

      So I followed this  Changing default gateway on vCenter Appliance version 6  guide (post #12)  and I got a ping, but...

      When I go to the vCenter IP address (192.168.202.24), I get this error: "503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http20NamedPipeServiceSpecE:0x00005630563529e0] _serverNamespace = / action = Allow _pipeName =/var/run/vmware/vpxd-webserver-pipe)" non of the google search results helped me

      When I go to https://192.168.202.24/vsphere-client/  I get this error:

      [500] SSO error: Failed to connect to VMware Lookup Service - https://192.168.2.49/lookupservice/sdk

      Check the vSphere Web Client server logs for details.

      And https://192.168.202.24/lookupservice/sdk  gives me a blank page.

       

      Searching the 500 error got me to this thread: 503 error on vCSA 6.5.0a running on ESXi 6.5.0a  but I don't have a duplicate key (or at least I don't think so)

      So far i have:

      Command> service-control --status --all

      Running:

      applmgmt lwsmd vmafdd vmcad vmdird vmdnsd vmware-analytics vmware-cis-license vmware-eam vmware-pod vmware-postgres-archiver vmware-rhttpproxy vmware-statsmonitor vmware-sts-idmd vmware-vmon vmware-vpostgres vsphere-client vsphere-ui

      Stopped:

      pschealth vmcam vmonapi vmware-cm vmware-content-library vmware-imagebuilder vmware-mbcs vmware-netdumper vmware-perfcharts vmware-rbd-watchdog vmware-sca vmware-sps vmware-stsd vmware-updatemgr vmware-vapi-endpoint vmware-vcha vmware-vpxd vmware-vpxd-svcs vmware-vsan-health vmware-vsm vsan-dps

       

      "service-control --start --all" hangs a long time on "Performing start operation on profile: ALL..."

      Command> service-control --start --all

      Operation not cancellable. Please wait for it to finish...

      Performing start operation on service lwsmd...

      Successfully started service lwsmd

      Performing start operation on service vmafdd...

      Successfully started service vmafdd

      Performing start operation on service vmdird...

      Successfully started service vmdird

      Performing start operation on service vmcad...

      Successfully started service vmcad

      Performing start operation on service vmware-sts-idmd...

      Successfully started service vmware-sts-idmd

      Performing start operation on service vmware-stsd...

      Successfully started service vmware-stsd

      Performing start operation on service vmdnsd...

      Successfully started service vmdnsd

      Performing start operation on profile: ALL...

      Service-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start sca, vmonapi, cm, vapi-endpoint services. Error: Operation timed out

       

      Following this post: [500] SSO error: Cannot connect to the VMware Component Manager

      root@vCenter [ ~ ]# cat /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log | grep java.net.NoRouteToHostException

       

      [2018-06-28T19:51:06.008Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:51:29.023Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:51:52.028Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:52:15.037Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:52:38.031Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:53:01.039Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:53:24.036Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:53:47.039Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:54:10.095Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:54:33.097Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:54:56.096Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:55:19.135Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:55:42.133Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T19:56:04.252Z] [ERROR] cm-catalog-manager-pool-3 com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

      [2018-06-28T20:25:15.945Z] [ERROR] http-nio-9090-exec-9     70000003 ###### ###### com.vmware.vise.vim.lookup.impl.LookupServiceImpl             Error when creating lookup service com.vmware.vim.vmomi.client.exception.ConnectionException: java.net.NoRouteToHostException: No route to host (Host unreachable)

      Caused by: java.net.NoRouteToHostException: No route to host (Host unreachable)

       

      (copy pasted from ssh in putty)

       

      I know this is long, but I'm about to give up on VMWare 6.7, and go back to 5.5

      So, if you can help me...

       

      Thanks

        • 1. Re: vCenter 6.7 fresh install not working
          daphnissov Guru
          Community WarriorsvExpert

          To start, redeploy again and take screenshots of the values you're providing in the installer wizard. Let's see what you're providing it.

          • 2. Re: vCenter 6.7 fresh install not working
            lecfl Lurker

            Thanks for the reply,

            I deleted the vCenter and re-deployed it (on the VManage network)

            This time it went good, it past stage1 with no error, but not I have a new error in stage2 (that I have never saw...), I'm adding a zip file with 12 screen shots

            On the Host side, the vCenter is on, so I shut it off and started it up again, then tried to click on the Retry button, but I get the same error...

            • 3. Re: vCenter 6.7 fresh install not working
              daphnissov Guru
              Community WarriorsvExpert

              Ok, a few things from your screenshots:

               

              1. You have not used a FQDN hostname when deploying the appliance. I don't know why the wizard says "optional" but it's not. You must use a fully-qualified hostname, which means you need forward and reverse DNS records for this vCenter.
              2. You've chosen to sync time with your ESXi host. In general, this isn't recommended. If you don't have internal (not external) NTP, then double check that all your ESXi hosts have their time set correctly, are consistent, and are in sync with the workstation *from which you're running this deployment wizard*. Time must be in sync and accurate all the way around.
              3. You have misspelled "vsphere.local" when creating your default SSO domain. You put "vspere.local" which is going to create problems for you very likely down the road.

               

              Fix these three things, redeploy, again taking screenshots as you go.

              • 4. Re: vCenter 6.7 fresh install not working
                lecfl Lurker

                Will do...

                You have not used a FQDN hostname when deploying the appliance. I don't know why the wizard says "optional" but it's not. You must use a fully-qualified hostname, which means you need forward and reverse DNS records for this vCenter.

                Do I need a FQDN even if there is no DNS server on that network (don't forget there is no internet on the VManage network) ?

                • 5. Re: vCenter 6.7 fresh install not working
                  daphnissov Guru
                  Community WarriorsvExpert

                  It doesn't matter that the Internet is not accessible from that segment, but you *must* have a DNS server that is reachable and you *must* have static (forward and reverse) records in place or else the vCSA will not work properly.