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 13.3 is built on CentOS 6, which in turn is a RHEL 6 clone.
This post will be around when SPACE 13.3 is history.
The easiest One way to figure out what version of CentOS it might, somewhat loosely, be based on, is to run uname -a and take a look at the kernel version:
Linux space-0050568776bc 2.6.32-100.24.1.el5 #1 SMP Tue Aug 20 12:17:49 CST 2013 x86_64 x86_64 x86_64 GNU/Linux
Cross-reference to the Wiki entry for CentOS and you can see that 2.6.32-xx is some version of CentOS 6.
Note: Check the comments below, not all versions of SPACE are created equal. Yours might be based on RHEL 5/CentOS 5. There’s a faster way to check for version, suggested by commenter Riley: “rpm -qa | grep el”. 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 6. You’ll want the following (or their current equivalent):
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, 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
You’ll notice some errors about initctl missing, and that means the service didn’t get installed. We’ll fix that next.
4) Copy the vmware-tools-services script over to init.d, and rename it while you’re at it
cp /etc/vmware-tools/init/vmware-tools-services /etc/init.d/vmware-tools
5) Edit /etc/init.d/vmware-tools with vi and add two lines, so chkconfig knows what to do with it:
# chkconfig: 345 20 80
# description: VMWare Tools
6) And add it to startup:
chkconfig --add vmware-tools
If you like, you can use
to make sure that worked.
7) Last, start the tools
service vmware-tools start
And satisfy yourself that this worked, too:
ps -ef | grep vmtoolsd
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.