SiteScope can't connect to VmWare

Hi, guys.

I'm trying to connect SiteScope's 11.30 monitor to the VmWare vSphere host.

The host URL is kind of like this: https://vmware-host-name/sdk

Unfortunately, just when I click "get counters", Sitescope results in an error:

Error 31008
Error getting counters : com.vmware.vim.ArrayOfPerfCounterInfo cannot be cast to [Lcom.vmware.vim.PerfCounterInfo;

 

thus making impossible to add any counters to the monitor list. I've tried 2 SiteScope hosts, the second one with SiteScope 11.20, but to no avail.

 

Is anybody having any luck with monitoring VmWare with the SiteScope?

Parents
  • Seems like the Perf API from VMWare is not giving expected values, can you confirm your ESX version is supported? Also share error.log to check the complete stack trace of the error,

  • We have VmWare vCenter Server version 6.0.0 build 2559267. Is it supported?

    I have tried to connect a bare ESXi 5.5 machine, but got the same error.

    Log attached.

  • Hi,

     

    have a look at the 11.30 SiteScope manual "Monitor Reference":

     

    VMWare Datastore Monitor:
    This monitor supports monitoring remote servers running on VMware vSphere 4.0, 4.1, 5.0, 5.1, 5.5.

     

    VMWare Host Monitor
     VMware VirtualCenter 2.x
     VMware ESX 3.x, 4.0, 4.1
     VMware ESXi 3.5, 4.0, 4.1, 5.0, 5.1
     VMware ESX 2.5 via VirtualCenter 2.x
     VMware ESX 3.x via VirtualCenter 3.x
     VMware vSphere 4.0, 4.1, 5.0, 5.1 (also supported with SSO login), 5.5

     

    VMWare Performance Monitor
     VMware VirtualCenter 2.x
     VMware ESX 3.x, 4.0, 4.1
     VMware ESXi 3.5, 4.0, 4.1, 5.0, 5.1
     VMware ESX 2.5 via VirtualCenter 2.x
     VMware ESX 3.x via VirtualCenter 3.x
     VMware vSphere 4.0, 4.1, 5.0, 5.1 (also supported with SSO login), 5.5

     

    No ESX 5.5 nor ESX 6 support.

    Mhm, partly wrong, as per CR

     QCCR1I106882 VMware ESXi 5.5 support is not documented in the VMware Datastore/Host/Performance monitors

    ESXi 5.5 already was verified and certified in SiS 11.24.

     

    So check what the exact error is with ESX 5.5. If it is the same as then one in the logfile you provided, then:

     

    it seems that we fail because nothing is coming back from the URL you specified to access VMWare:

     

    2015-05-27 10:18:49,349 [http-bio-18080-exec-2] (VimConnection.java:138) ERROR - Failed to initialize connection to http://10.161.100.100/sdk(301)Moved Permanently Url : http://10.161.100.100/sdk User : monitor@vsphere.local
    ..
    2015-05-27 10:18:49,350 [http-bio-18080-exec-2] (VimConnectionPool.java:64) ERROR - Unable to get connection to URL http://10.161.100.100/sdk with username monitor@vsphere.local waited: 134 milliseconds.(301)Moved Permanently
    ..
    2015-05-27 10:18:49,351 [http-bio-18080-exec-2] (APIMonitor.java:1319) ERROR - Failed to get class property details for property: availableCountersHierarchical in monitor type: VMWarePerformanceMonitorCOM.freshtech.SiteScopeException.SiteScopeOperationalException: Error Code: 31008.  Error Description: Error getting counters : Unable to get connection to URL http://10.161.100.100/sdk with username monitor@vsphere.local waited: 134 milliseconds.(301)Moved Permanently

    The issue seems to be that the URL is not correct?
     (301)Moved Permanently

    Can you access the following URLs via a browser running on the SiteScope server:

     http://10.161.100.100

     http://10.161.100.100/sdk
     http://10.161.100.100/sdk/vimservice.wsdl

     http://10.161.100.100/mob

     

    Greetings

    Siggi

  • Siggi, the "moved permanently" error was due to a wrong address (mostly, without https prefix), so it's not an url issue, I guess.

     

     https://10.161.100.100 - works (welcome page)
     https://10.161.100.100/sdk - blank page 
     https://10.161.100.100/sdk/vimservice.wsdl - blank page
     https://10.161.100.100/mob - works (authorization works fine as well)

     

    The vCenter is currently of version 6.0, but it's a recent update, a week ago we had 5.5, therefore, I presume, it's not a version issue.

     

  • Siggi, the "moved permanently" error was due to a wrong address (mostly, without https prefix), so it's not an url issue, I guess.

     

     https://10.161.100.100 - works (welcome page)
     https://10.161.100.100/sdk - blank page 
     https://10.161.100.100/sdk/vimservice.wsdl - blank page
     https://10.161.100.100/mob - works (authorization works fine as well)

     

    The vCenter is currently of version 6.0, but it's a recent update, a week ago we had 5.5, therefore, I presume, it's not a version issue.

     

  • Siggi, the "moved permanently" error was due to a wrong address (mostly, without https prefix), so it's not an url issue, I guess.

     

     https://10.161.100.100 - works (welcome page)
     https://10.161.100.100/sdk - blank page 
     https://10.161.100.100/sdk/vimservice.wsdl - blank page
     https://10.161.100.100/mob - works (authorization works fine as well)

     

    The vCenter is currently of version 6.0, but it's a recent update, a week ago we had 5.5, therefore, I presume, it's not a version issue.

     

  • there might be any issue.

     

    1. Install the certificate of vcenter in sitecope.

    2. verify the login credentials by login vsphere (vcenter) and check whether that host is available or not. From sitescope server only

    3. if all are part of same domain. Then nslookup must work fine for vcenter, VM host by IP and hostname.

     

    connection URL -https://IPaddress/sdk

     

    Try now. contact me for further help at "rahul4985@gmail.com"

     

    Regards,

    Rahul

     

     

  • Rahul, of course I've tried using an IP address instead of an URL, but to no avail.

    The certifcate is imported as well. The SiteScope is not a part of the domain, but does it really matter as long as credentials are fine? And yes, they are fine, I can successfully login with them to the vCenter Web GUI and vSphere app.

    If the credentials are wrong, SiteScope outputs a different error.

  • Hi,

     

    after this works fine

     

     https://10.161.100.100 - works (welcome page)
     https://10.161.100.100/sdk - blank page 
     https://10.161.100.100/sdk/vimservice.wsdl - blank page
     https://10.161.100.100/mob - works (authorization works fine as well)

     

    there is no real reason for the monitor to fail, however version 6.0 is simply not supported, and it's tricky to troubleshoot something which hasn't been tested (or even worse, it has been tested but found that it doesn't work).

     

    If you do have an ESX 5.5 environment for further tests, it would be helpful. Then simply try to setup the monitor once again and post the error.log file.

     

    Greetings

    Siggi

  • Attaching the same error while connecting to ESXi 5.5.

    Maybe it has something to do with vim.jar & vim25.jar? I have them installed, but maybe there's a specific version required? I tried some of them I found on the internets with no luck.

  • Attaching the same error while connecting to ESXi 5.5.

    Maybe it has something to do with vim.jar & vim25.jar? I have them installed, but maybe there's a specific version required? I tried some of them I found on the internets with no luck.

  • Attaching the same error while connecting to ESXi 5.5.

    Maybe it has something to do with vim.jar & vim25.jar? I have them installed, but maybe there's a specific version required? I tried some of them I found on the internets with no luck.

Reply Children