Deploying a Junos Space Virtual Appliance on a KVM Server
The Junos Space Virtual Appliance Release 16.1R1 and later can be deployed on qemu-kvm (KVM) Release 1.5.3 or later.
Juniper Networks does not provide any support for installing and configuring the KVM server. You must install the virtual appliance image and configure it as per the recommended specifications for the virtual appliance. Juniper Networks will provide support only after the Junos Space Virtual Appliance has booted successfully.
The prerequisites to deploy a Junos Space Virtual Appliance on a KVM server are as follows:
Knowledge about configuring and installing a KVM server.
KVM server and supported packages must be installed on your Linux-based system. Contact your Linux vendor or documentation for information about installing KVM.
An application or method to view the remote system virtual monitor, such as Virtual Machine Manager (VMM), Virtual Network Computing (VNC) Viewer, or any other application.
Bridge Interface configured according to your environment and at least two free static IP addresses.
For information about the minimum hardware requirements for deploying a Junos Space Virtual Appliance, see Junos Space Virtual Appliance Deployment Overview.
The deployment of a Junos Space Virtual Appliance on a KVM server by using VMM includes the following tasks:
Though deploying the Junos Space Virtual Appliance on the KVM server by using virtual machine clients other than VMM is possible, Juniper Networks does not provide support for installing the Junos Space Virtual Appliance using clients other than VMM.
Installing a Junos Space Virtual Appliance on the KVM Server by Using VMM
Use the VMM virtual machine client to install the Junos Space Virtual Appliance on a KVM server.
To install the Junos Space Virtual Appliance on a KVM server by using VMM:
Modifying the Type of Virtual Disk Interface
After the Junos Space Virtual Appliance is created, you must change the hard disk interface type to Integrated Drive Electronics (IDE) to avoid any issues with the booting up of the Junos Space Virtual Appliance due to kernel panic.
If you are using CLI of VMM to set up KVM, you set the type of virtual disk interface to IDE at the start of the set up. You do not have to reset the type of interface again.
To change the hard disk interface type to IDE:
Modifying RAM for a Junos Space Virtual Appliance
The Junos Space Virtual Appliance file is distributed with 8 GB of RAM and four virtual CPUs. You need 32-GB RAM to configure the Junos Space Virtual Appliance as a Junos Space node or as an FMPM node.
To modify RAM for the Junos Space Virtual Appliance:
Adding Disk Resources for a Junos Space Virtual Appliance
For information about adding disk resources for Junos Space Virtual Appliance, see Adding Disk Resources for a Junos Space Virtual Appliance.
Enabling Multicast on Bridged Interfaces of a KVM-Host Machine
For creating Junos Space clusters, multicast must be enabled on the bridged interface of a KVM-host machine on which Junos Space node is deployed to allow multicast traffic to flow between the nodes of the cluster.. If Junos Space nodes in a cluster are deployed on different host machines, multicast must be enabled on the bridged interface of each host machine.
To configure multicast on a bridged interface of a KVM-host
machine, log in to the KVM-host machine after the UI of the Junos
Space node is up and execute the ifconfig InterfaceName allmulti
command, where InterfaceName is the name of the interface.
Example:
-bash-4.1$ ifconfig macvtap0 allmulti
Configure multicast on all the KVM-host machines before adding a Junos Space node to a cluster.