vCLI for Linux is not compatible with vSphere 5.1?

I installed vSphere CLI 5.1 64-bit on CentOS 64-bit 6.3.  The problem I have is that if I try to run resxtop on a 5.1 ESXi host, I get the error:

Connection failed, reason: HTTPS_CA_FILE or HTTPS_CA_DIR not set.

So I export the following environment variables:

export PERL_LWP_SSL_CA_FILE="/etc/pki/tls/certs/ca-bundle.crt".

export HTTPS_CA_FILE="/etc/pki/tls/certs/ca-bundle.crt".

However, I still get the same error when I try to run resxtop.  I even tried to modify the module for SSLeay perl directly, but it does not help with vCLI.

Connection failed, reason: HTTPS_CA_FILE or HTTPS_CA_DIR not set.

Here's the thing.  If I do my own perl script to test the connection to the host via SSL, it works and hope the certificate.  Also if I don't have openssl s_client-connect it returns 0 so that the certificate works.  That is the question in vCLI 5.1 release notes seem to suggest that resxtop is not compatible with the 5.1 ESXi hosts.  Is it possible?  It seems that it would be a big gap. Here's the exact quote:

  • resxtop fails to run against targets of vSphere
    When you run resxtop against a target of vSphere 5.1, an error occurs.

    • If the SSL certificate is defined in the client vCLI, results in the following error:
      SSL Exception: Verification parameters
    • If the SSL certificate is not set, the error message following the result:
      Login failed, reason: HTTPS_CA_FILE or HTTPS_CA_DIR not set

    Solution: If your environment supports it, run esxtop in the Shell of ESXi. Otherwise, no work around.

    https://www.VMware.com/support/developer/VCLI/vcli51/vsp5_51_vcli_relnotes.html

    Is - this average resxtop is not all compatible with ESXi 5.1?

    • Hi djsupreme,.

    The last 5.1 vCLI which includes resxtop is compatible with ESXi 5.1, but unfortunately there was a bug introduced that now requires the validation of SSL certificates (it was supposed to be an indicator not required & optional) when executing against an ESXi host. As Matt mentioned, it is a known problem that we are currently working.

    To successfully connect to a 5.1 ESXi host using the last resxtop, you will need to actually set two environmental variables:

    HTTPS_CA_FILE and HTTPS_CA_DIR, this is not a statement 'or' as shown in the error message but was originally intended to direct the user to check that these variables ENV could be configured by Miss. It is necessary that you define two variables.

    Here is an example in my lab environment after establishing a properl SSL certificate, to say that your CA file is located in /home/vi-admin/cacaert.pem

    Then you run the following command:

    export HTTPS_CA_FILE = cacert.pem

    Export HTTPS_CA_DIR = / home/vi-admin

    Then, you will be able to use the resxtop command to connect remotely to your 5.1 ESXi host:

    resxtop - vesxi51-4 - username root server

    A solution alternative, but is not ideal, it is you can always use the local esxtop if you need to collect statistics immediately or you can even use a resxtop 5.0, which is part of vCLI 5.0 (has no bug check SSL, but you won't see any 5.1 News stats).

    We apologize for any inconvience this has cuased and rest assured, it is being developed and we hope to get a fix for this soon.

    Tags: VMware

    Similar Questions

    Maybe you are looking for