Home > Storage, Virtualization > vSphere 5.5 & the Isilon NAS VAAI Plugin – Part 1

vSphere 5.5 & the Isilon NAS VAAI Plugin – Part 1

September 30th, 2013 Leave a comment Go to comments

Just a quick heads up for anyone running vSphere 5.0/5.1 with the Isilon NAS-VAAI plugin for vSphere/OneFS 7.0.

If you are planning to upgrade to vSphere 5.5, there are a couple things to know. The plugin does not work in 5.5 (new or upgraded) installations.

I built a new vSphere 5.5 installation, and the plugin loaded fine.  But… When attempting to configure the credentials for the OneFS 7.0 cluster you are connecting to, the authorization tool fails to operate properly.

Screen Shot 2013-09-30 at 3.39.46 PM

In a new vSphere 5.1 installation, the error is not present.

Proper Loading

I upgraded a vSphere 5.1 host to 5.5 to determine if I would retain functionality.  Maybe the authorization piece (auth_gen) was the only part affected.  On this host that had successfully used the plugin, it no longer worked after the upgrade to 5.5.

In vSphere 5.5, the libssl.so shared library is libssl.so.1.0.1, while in vSphere 5.1, it is libssl.so.0.9.8.

I reached out to the team responsible for the plugin, and have confirmed they are aware of the issue, and working on a resolution.

Categories: Storage, Virtualization Tags: , , ,
  1. Skippy
    January 22nd, 2014 at 14:51 | #1


    I was able to get auth_gen to run yesterday on 5.5 using the following from a server. I still have no idea if the plug-in is working, but will do some clone testing later today…
    (I installed the standalone bundle using VUM to three 5.5 hosts in a cluster).

    Host 1
    # cd /lib
    # ln -s libssl.so.1.0.1 libssl.so.0.9.8
    # ln -s libcrypto.so.1.0.1 libcrypto.so.0.9.8
    # /usr/lib/vmware/nas_plugins/isi_plugin_credentials/auth_gen
    host: some.isilon.local
    User: root
    Pass: pass
    pass: pass

    THis was an old Linux workaround back in the Openssl upgrade days. IIRC, there weren’t huge FUNCTIONAL changes in Openssl between 0.98 and 1.01 and the import tables for the shared objects were compatible. That said, I still haven’t OBSERVED the plugin working.

    Hope this helps someone…


  2. Skippy
    January 22nd, 2014 at 14:57 | #2

    P.S. The fix should be as simple as EMC support re-compiling the driver and linking against updated Openssl, of course that introduces version dependencies and forces them to maintain a separate plugin chain for 5.5…

  3. Skippy
    January 23rd, 2014 at 07:03 | #3

    I tested it today; the links (obviously) do not persist through reboot, but VM copies before and after recreation of the links is significantly different.

    On an 7 node X200 cluster without SSD, I was seeing ~400M on the “cluster throughput” tab through a 10G link during a clone operation; after recreating the links to libssl and libcrypto, cluster throughput to a clone thick provisioned eager zero’d 60G VM were hitting ~5G.

    Try it, test, see what your results are. If I’m right, a recompile of the VAAI vib by EMC with either a statically linked OpenSSL or dynamically linking against 1.0.1 will solve the issues with 5.5.


    • jase
      January 26th, 2014 at 20:26 | #4


      Great info. I believe they are working on a newer build already.

      I’ll ask, and be sure to report what I find.


  4. Nicolai Imset
    September 19th, 2014 at 04:38 | #5

    Any more info around this?

    • jase
      September 19th, 2014 at 14:26 | #6

      Nope, I pinged them the other day… Haven’t heard back.

  5. Nicolai Imset
    September 22nd, 2014 at 05:33 | #7

    ok, I will stay tuned and open a request to have it fixed internally.

  1. No trackbacks yet.