4 Replies Latest reply on Apr 1, 2020 4:06 AM by Sreec

    VSphere 6.5 U3b + NSX 6.4.6 - EAM Failure

    ChrisD1884 Lurker

      Morning / Afternoon All,

       

      Sorry for the scatter gun approach to this question and I may be barking up the wrong tree, I am attempting to build-out a temporary testing environment with a 4 node Dell XS23

       

      I have managed to install the following

       

      ESX Hyper Visor

      VMware-VMvisor-Installer-6.5.0.update03-13932383.x86_64 - 2 nodes

      VMware-VMvisor-Installer-201908001-14320405.x86_64 - 2 nodes

       

      Vcenter Appliance - 6.5 u3b

      VMware-VCSA-all-6.5.0-15259038

       

      NSX 6.4.6

      VMware-NSX-Manager-6.4.6-14819921

       

      But I have a issue with the deployment of NSX, it seem the EAM process/database are either corrupt or something is not correct, as the NSX snap-in continually says that EAM is starting, at the EAM service on the VCenter via UI and Shell say's the process is started, but I am not able to view the via http://(VCenter Address)/eam/mob - I noticed this address on another forum post.

       

      I am running the environment on evaluation licenses of Vsphere and a temporary 50 node licence for NSX.

       

      If anyone could point me in the right direction, or errors on my ways.

       

      Kind Regards

       

      This could also be a duplicate post but I could not find the original post.

        • 1. Re: VSphere 6.5 U3b + NSX 6.4.6 - EAM Failure
          scott28tt Champion
          VMware EmployeesUser ModeratorsCommunity Warriors

          Moderator: Moved to NSX

          • 2. Re: VSphere 6.5 U3b + NSX 6.4.6 - EAM Failure
            Sreec Master
            Community WarriorsvExpertVMware Employees

            1.Can you share the logs of EAM -> var/log/vmware/vpx/eam/log and logs from one of the ESXI host were you tried to prepare the cluster  -> var/log/esxupdate.log

            2.Events related to EAM -> Administration->vcenter extensions->manage->monitor -> Monitor events

            3. Any firewall between NSX and VC&ESXI ?

            4. Did you reboot ESXI/VCSA/NSX ?

            5. Ensure DNS is working correctly in this setup.

            • 3. Re: VSphere 6.5 U3b + NSX 6.4.6 - EAM Failure
              ChrisD1884 Lurker

              Hi Sreec,

               

              In response to your questions please see below.

               

              1.Can you share the logs of EAM -> var/log/vmware/vpx/eam/log and logs from one of the ESXI host were you tried to prepare the cluster  -> var/log/esxupdate.log

                        See Attached Files

              2.Events related to EAM -> Administration->vcenter extensions->manage->monitor -> Monitor events

                        They does not seem to be any events related to EAM

              3. Any firewall between NSX and VC&ESXI ?

                        No Firewall between VCSA, NSX, ESXi - Flat Network

              4. Did you reboot ESXI/VCSA/NSX ?

                        All have been reboot various times

              5. Ensure DNS is working correctly in this setup.

                        Could well have been DNS / NTP, I have gone an reconfigured some of the NTP setting but it is still not resolving the issue.

               

              Kind Regards

              • 4. Re: VSphere 6.5 U3b + NSX 6.4.6 - EAM Failure
                Sreec Master
                Community WarriorsVMware EmployeesvExpert

                EAM logs are reporting lot of logging failures -

                 

                2020-03-31T08:15:21.153Z | ERROR | vim-monitor | VcConnection.java | 210 | Failed to login to vCenter as extension. vCenter has probably not loaded the EAM extension.xml yet.: Cannot complete login due to an incorrect user name or password.

                2020-03-31T08:15:21.153Z |  WARN | vim-monitor | VcListener.java | 110 | Trying to recover from error

                (vim.fault.InvalidLogin) {

                   faultCause = null,

                 

                Do check  wrapper.logs as well -> VMware Knowledge Base to confirm if you are hitting with same issue ( I understand that you are already at 6.5 U3b)