Space, the final frontier!Junos Space is largely the replacement for Juniper's previous management platform (NSM). In this post, I'll run through configuring a small lab environment and give an overview of the features built in to Space.
Part of the reason that I've been investigating Space is that I've been engaged to recommend a solution for a network that requires remote management of 30 or so Juniper SRX devices. As such, I'll also touch on the Security Director side of Space.
Space is fairly easy to obtain assuming you already have an account on Juniper's website. For those of you who don't, I'm assuming that a free account will also give you access to the image but if not, please don't ask me!
At the time of writing, Release 13.1 only contains the image for Security Director. We'll come back to this in a future post so for now change Release to 12.3 and grab the virtual appliance image.
The virtual appliance is designed to run in ESX but as I don't have that available to me at the moment I'll use VMWare Player instead.
You will likely be notified that the ova does not comply with the OVF specification and/or virtual hardware compliance checks. I suspect this is due to the use of Player over full ESX. Select Retry.
I'm also doing this on a laptop with less RAM than Space expects at first import so I'll also reduce the amount of RAM allocated to the virtual machine. Space will complain about this initially but besides reduced performance everything appears to operate correctly.
|Select Retry if you get this error.|
Adding an Additional Disk
The next step is one that is widely missed. By default, the VM only has an 8GB disk. Unfortunately, installing some applications (such as Security Director) requires that 10 times the application be available for installation. Security Director weighs in at ~500mb so we'll need to add an additional disk.
I would recommend adding at least 40GB if you can based on Juniper Support documents.
|Select Hard Disk|
|Create a new virtual disk|
|SCSI is preferred|
|Enter 40GB. As this is a lab machine, don't worry about allocating all of the space now.|
|Choose a filename for your new disk image|
Logging in for the first time
Great, now you've got a virtual machine running Space.
Login using the default credentials and let's take it for a spin.
I've made a deliberate decision to reduce the RAM and accept the risks so let's charge on!
The next bit covers configuring IP addresses for the primary interface, nameservers and the like.
An important thing to note is that you will need at least two IP addresses. One is used for communication with devices, etc. and the second is used exclusively for the web GUI. Both IP addresses must be in the same subnet but can not be the same.
You will also be prompted to enter a maintenance password. This is used when Space has entered maintenance mode. This can occur after an unexpected reboot, during software upgrades or other unexpected conditions. It's important to keep this handy.
|All configured and ready to go|
About that disk drive..
Finally, we've got to expand the volume group.
We've already added the virtual disk so go ahead and choose option 5.
And we're done!
In part two I'll cover logging in to Space and importing a device. Finally, we'll also take a look at Security Director and see how it compares to NSM.