5 Replies Latest reply on Jun 1, 2011 9:47 AM by Garrett Gross

    Profiler can't connect to VMware clusters

    LeeG

      Hello, I've had an issue with Profiler for a while now where it's unable to connect at the VMware cluster level. Profiler happily connects to VirtualCenter and each ESX host but is unable to login to gather cluster information. We have a Profiler domain user account which has read-only access in VC, does this need elevated privileges?

      Cheers, Lee.

        • Re: Profiler can't connect to VMware clusters
          animelov

          Technically yes, in general you need to have the read-only account + datastore.browse permissions.  But this doesn't solve your issue, you'll just have different issues later on.  Anyway, did you assign the ESX hosts by Cluster or by individual ESX host?  If you do it by individual, then you may not see cluster information.

          • Re: Profiler can't connect to VMware clusters
            Garrett Gross

            We have also seen issues recently where incomplete (possibly corrupted) information gets passed to the xml and results in an error like "device123 does not define a class or type mapping".

            In that case, the workaround that has proven to be successful in most cases is a "rediscovery" of the VMware devices.  To do this, follow the instructions below:

            #Unassign Clusters and ESX Hosts

            Settings->Virtualization (Assign ESX Hosts)

            Put a check mark in the box at the left side of the cluster

             

            Click 'Assign to Poller'

            #A window called 'Assign to Poller' will popup.

            Select Poller: Unassign

            Click Save

             

            Click the 'ESX' tab

            select the 'ESX Host' box (all ESX hosts should automatically be selected)

            Click 'Assign to Poller'

            #A window called 'Assign to Poller' will popup.

            Select Poller: Unassign

            Click Save

             

            #Unassign the Virtual Center

            Settings->All Resources

            #Find the Virtual Center

            Filter: VMware VC   Click 'Go'

            Click 'Edit' (pad and pencil)

            #In the 'Edit Virtual Center' screen

            Poller: 'select a poller for this device'

            Click 'Save'

             

            #Go to poller agent(s) and verify all VMware devices are removed from xml

             

             - To check this edit the xml file in \systemic\mod.sys.virtual.Virtual_1.0\mod.sys.virtual.Virtual.XML

             

             - Make sure everything within the Devices tags is gone.

            ex: <Devices>

                   </Devices>

             

            Stop poller agent service (ProfilerAgent)

             

            Delete the "data" directory for each poller agent

            \Program Files\SolarWinds\Profiler Agent\systemic\mos.sys.virtual.Virtual_1.0\data

            Note: Only the 'data' directory, nothing else.

             

            Start poller agent service (ProfilerAgent)

             

            #Reassign Virtual Center(s) and verify discovery completes. 

            Settings->All Resources

            #Find the Virtual Center

            Filter: VMware VC   Click 'Go'

            Click 'Edit' (pad and pencil)

            #In the 'Edit Virtual Center' screen

            Poller: 'select the Poller server'

            Click 'Save'

             

            #Check the VC resource and ensure it is online and collecting before assigning ESX and Clusters.

             

            Virtualization->Virtual Center

             

            #Once discovery completes reassign ESX / Clusters appropriately

            Note: You can monitor the Virtualization log file for Discovery status

             

            Settings->Virtualization (Assign ESX Hosts)

            Put a check mark in the box at the left side of the cluster

             

            Click 'Assign to Poller'

            A window called 'Assign to Poller' will popup.

            Select Poller: Poller name

            Click Save

             

            Click the 'ESX' tab

            select the 'ESX Host' box (all ESX hosts should automatically be selected)

            Click 'Assign to Poller'

            A window called 'Assign to Poller' will popup.

            Select Poller: Poller name

            Click Save

             

            **If the above process does not work, feel free to submit a support ticket at solarwinds.com/support/ticket and one of our support reps will look into it.**