Installing VMWare Tools (Open VM Tools) on JunOS SPACE 16.1 or newer

These instructions are for JunOS SPACE 16.1 or newer. I also have instructions for JunOS SPACE 15.2 or older.

JunOS SPACE, Juniper’s management tool for JunOS devices (switches, routers, firewalls), officially supports Open VM Tools for management from ESXi. Unfortunately, Juniper’s instructions are to build Open VM Tools, and that won’t work without a dev environment, which is not present in JunOS SPACE.

SPACE 16.1 is built on CentOS 6, which in turn is a RHEL 6 clone. Open VM Tools exist in CentOS 6 repositories, so all we need to do is to enable those repositories and we can install binaries.

Install

Navigate to /etc/yum.repos.d and create a new file named centos6.repo, with this content:

[centos6]
name=CentOS 6 Repository
baseurl=http://mirror.centos.org/centos/6/os/$basearch
enabled=1
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/6/os/x86_64/RPM-GPG-KEY-CentOS-6

[extras]
name=CentOS 6 Extras Repository
baseurl=http://mirror.centos.org/centos/6/extras/$basearch
enabled=1
gpgcheck=0

Back on command line, add the EPEL repository:

yum install epel-release

Install Open VM Tools:

yum install open-vm-tools

Start them:

service vmtoolsd start

Cleanup

For good measure, you can now disable the centos 6 and epel repos again, by editing centos6.repo and epel.repo in /etc/yum.repos.d/ and setting this line for centos6, extras, and epel:

enabled=0

Verify those repos are disabled:

yum repolist

 

Advertisements

Installing VMWare Tools on JunOS SPACE 15.2 or older

[Edit 2017-05-04] The below is still valid for JunOS SPACE 15.2 or older. From JunOS SPACE 16.1 on, you can use “Open VM Tools” instead.

JunOS SPACE, Juniper’s management platform for JunOS devices (switches, routers, firewalls) does not come with gcc or kernel-headers. Installing VMWare Tools from a mounted ISO via vmware-install.pl is not all that successful. Happily, VMWare still provides RPM versions of those tools. SPACE 15.2 is built on CentOS 5, which in turn is a RHEL 5 clone.

Be sure to use the VMWare Tools package that matches the version of CentOS your SPACE is running.

1) Start by downloading the RPMs for VMWare Tools on RHEL 5. You’ll want the following (or their current equivalent):

vmware-tools-core-10.0.6-1.el5.x86_64.rpm
vmware-tools-esx-nox-10.0.6-1.el5.x86_64.rpm
vmware-tools-foundation-10.0.6-1.el5.x86_64.rpm
vmware-tools-guestlib-10.0.6-1.el5.x86_64.rpm
vmware-tools-libraries-nox-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-autoUpgrade-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-deployPkg-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-grabbitmqProxy-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-guestInfo-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-hgfsServer-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-powerOps-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-timeSync-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-vix-10.0.6-1.el5.x86_64.rpm
vmware-tools-plugins-vmbackup-10.0.6-1.el5.x86_64.rpm
vmware-tools-services-10.0.6-1.el5.x86_64.rpm
vmware-tools-vgauth-10.0.6-1.el5.x86_64.rpm

That list might change with newer versions of the tools and of RHEL, of course. When in doubt, grab just the vmware-tools-esx-nox package, try to install it, and take a note of all the dependent packages it wants, then download those too.

2) scp the lot to SPACE, say to /var/tmp. While WinSCP is unhappy with the shell the admin user runs on, command-line scp does not care and will work. Choose any version you like: The one that comes with Putty, the one that comes with Cygwin, an Ubuntu one on Windows 10, or any other. And if you’re running OSX or Linux, you can feel extra-smug because you have scp as part of your base OS.

3) Install those RPMs. Now, you could install the GPG key they are signed with, but if you trust that you got them from VMWare, in an unaltered form, then just:

yum install --nogpgcheck vmware-tools*rpm

If there are dependency errors, download the missing packages as well and try again.

5) Satisfy yourself that vmtoolsd is running:

service vmware-tools-services status

 

vSphere should now be reporting that SPACE is running “VMtools 3rd party/independent”. And that’s all there is to it.

The kmod portion of the tools won’t install, by the way – but then it’s not needed.