Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Install Security Director Insights

We support two deployment options on KVM, that is, virt-manager runs on Ubuntu Linux as a host and Proxmox. In this topic you'll learn how to install Security Director Insights with virt-manager and Proxmox. The minimum requirements on KVM are 32GB RAM and 8 vCPU.

Before You Begin

  • Ensure that there are no snapshots. You must delete the snapshot before expanding the disk size.

  • We recommend to create a backup by cloning the VM before expanding the disk size.

  • You have already installed KVM, qemu, virt-manager, Proxmox, and libvirt on your host OS.

  • You have created a bridge network to access KVM through SSH.

    In this document, a bridge network br0 is created with Netplan. Here is a sample from the /etc/netplan/00-installer-config.yaml file.

    Figure 1: Example Configuration of br0 YAML snippet of network bridge setup with br0: interfaces eno2, STP disabled, 0s forward delay, DHCP4 yes, DHCP6 no.

KVM virt-manager

You can install and launch Security Director Insights with KVM virt-manager GUI package.

  1. Download the Security Director Insights KVM image from the Juniper software download site.

  2. On your host OS, type virt-manager

    The Virtual Machine Manager page appears.

    Note:

    You must have admin rights on the host OS to use virt-manager.

  3. Click the Create a new virtual machine icon.

    The Create a new virtual machine page appears.

    Figure 2: Create a New Virtual Machine Virtual Machine Manager interface with ak-qspace running and sdi-231 shut off. Toolbar options available. CPU usage graph on the right.

  4. Select Import existing disk image, and click Forward.

    Figure 3: Import Disk Image Create a new virtual machine dialog in virt-manager. Step 1 of 4. Import existing disk image option selected. Navigation buttons: Cancel, Back, Forward.

  5. Browse to the location of the downloaded Security Director Insights image and select the image.

    Select Ubuntu 22.04 as the OS

    Figure 4: Select Storage Path And Operating System Step 2 of 4 in virtual machine creation; set storage path to /root/juniper-security-director-insights-24.1.R2.s64c2.qcow2; OS is Ubuntu 22.04 LTS; buttons: Cancel, Back, Forward.

  6. Click Forward.

  7. Set the Memory and CPU value.

    Figure 5: Configure Memory And CPUs Step 3 configuration: Allocate 32768 MiB memory and 8 CPUs for the new virtual machine. Options to cancel, go back, or proceed.

    Click Forward.

  8. Select the Customize configuration before install option.
    Figure 6: Network Selection Page Virtual machine setup final step; name: juniper-insights-qcow, OS: Ubuntu 22.04 LTS, import OS image method, 32 GB memory, 8 CPUs, QCOW2 disk storage, customize before install, NAT network.

  9. In the Network selection field, select the network from the list.

  10. Click Finish.

  11. Click Add Hardware.

    The Add New Virtual Hardware page appears.

  12. Select Network from the left side menu and click Finish

    Figure 7: Network Details Page Virtual machine network configuration interface with Network tab open, showing Virtual network default: NAT, MAC address, and virtio device model.

  13. Click Begin Installation.

    Figure 8: Begin Installation Virtual machine console on QEMU/KVM shows systemd boot logs with OK status for tasks like mounting file systems and starting services.

    The VM manager creates the virtual machine and launches the Security Director Insights console.

KVM Proxmox

To install Security Director Insights with KVM Proxmox:

  1. Download the Security Director Insights KVM image from the Juniper software download site.

  2. Create a VM on Proxmox.

  3. Enter the details on the General page.

    User interface for creating a virtual machine on General tab with fields for Node, VM ID, Name, and Resource Pool. Navigation buttons include Help, Advanced, Back, and Next.

  4. Enter the details on the OS page.

    Select Do not use any media.

    Configuration screen for virtual machine setup, showing OS tab. Media option: Do not use any media, Guest OS: Linux 6.x - 2.6 Kernel. Back and Next buttons visible.

  5. Enter the details on the System page.

    Virtual machine creation interface System tab showing settings for graphics card default machine i440fx BIOS SeaBIOS and SCSI Controller VirtIO SCSI single.

  6. Enter the details on the Disks page.

    Configuration screen for VM creation showing Disk settings: Bus set to SCSI, SCSI Controller to VirtIO SCSI single, Storage selected as vm, Disk size 32 GiB, Format QEMU image format, Cache Default No cache, Discard unchecked, IO thread checked. Navigation buttons Back and Next, Add button, Advanced checkbox visible.

  7. Enter the details on the CPU page.

    CPU settings tab for virtual machine configuration; Sockets: 2, Cores: 4, Total cores: 8, Type: x86-64-v2-AES. Navigation buttons: Back and Next are visible.

  8. Enter the details on the Memory page.

    Memory configuration screen for virtual machine with 16384 MiB set. Navigation buttons: Back, Next, Advanced checkbox, Help button. Tabs for General, OS, System, Disks, CPU, Network, Confirm.

  9. Enter the details on the network page.

    Network settings tab for virtual machine creation: select network bridge vmbr2, VirtIO adapter, no VLAN, auto MAC, firewall enabled.

  10. On the Confirm page, verify all the details and click Finish.

    Configuration summary for creating a VM in Proxmox VE: 4 CPU cores, x86-64-v2-AES CPU, 16 GB RAM, juniper-insights-qcow name, VirtIO network on bridge vmbr2 with firewall, hosted on chicagopve01 node, Linux 2.6+, QCOW2 SCSI disk with I/O threading, 2 CPU sockets, VM ID 205. "Start after created" is unchecked.

  11. In the Hardware section, note down the disk name of the VM.

    Virtual machine juniper-insights-qcow on node chicagopve01 with 16 GiB RAM, 8 vCPUs, SeaBIOS, i440fx machine type, VirtIO SCSI controller, 32 GB disk, VirtIO network device bridged to vmbr2.

  12. SCP the qcow file to Proxmox. The directory to use is the image id.

    For example, /mount/vm-storage/images/200/

  13. Untar the file, change the disk name to disk-name.old and change the untarred filename to the disk name and power on the VM.

    Terminal window showing a user on system chicagopve01 listing files in directory /mnt/pve/vm-nfs/images/201. Files: juniper-security-director-insights-24.1.s320c12.qcow2.tgz, space-24.1R3.399219.ova, vm-201-disk-0.qcow2, vm-201-disk-0.qcow2.old.

Expand the VM Disk Size

To expand the disk to the maximum available size:

  1. Log in to the host of the KVM and power down the VM.

    Figure 9: Power Down the VM Virtual Machine Manager showing two VMs: jsa running and sdiq-disk shut off, with CPU usage graphs and a tooltip to shut down a VM.

  2. From the host, increase the disk size using the qemu-img resize vmdisk.img +XG command, where vmdisk.img is the name of the image and XG is the size in GB you want to expand the disk to.Terminal window showing command to resize disk image using qemu-img tool, adding 200GB to juniper-security-director-insights-22.2.s20c3.qcow2 file.

    The size denotes how much you want to expand the disk. It is not the maximum size of the disk.

  3. Power on KVM and log in to the Admin CLI. Switch to the server mode and run set disk-partition-to-full command. Terminal screen showing Linux disk partitioning and filesystem management commands, including sgdisk resizing warning, lsblk disk layout, resize2fs on ext4 filesystem, and df -h mounted filesystems.

    The new disk size is the size of /dev/vda2.