Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

System Requirements

Before installing kLWC in a KVM environment, ensure that your system meets the following requirements.

KVM Environment Requirements

kLWC is currently supported on KVM running on Ubuntu 22.04 LTS or later. The kLWC virtual machine is delivered as a compressed tar gzipped (.tgz) package.

To run kLWC, the KVM host must meet the following minimum requirements:

  • Install the following Ubuntu packages

    • qemu-kvm

    • libvirt-daemon-system
    • libvirt-clients
    • virtinst
    • ipcalc-ng
    • jq
  • Required OS—Ubuntu 22.04 LTS or later
  • Networking Requirements—Three Linux bridge networks for internal, external, and management interfaces.

    Connectivity from the internal bridge network to Junos devices being monitored by JSI.

    Connectivity from the external bridge network to the Internet or an active proxy server.

  • User and Permission Requirements—If the kLWC Manager script is not executed as the root user or with sudo, the following requirements must be met:

    • A Linux user with a UID of 4000 and a Primary GID of 4000 is required.
    • The user must belong to either the libvirt or kvm group
    • The user must have sudo access to the following commands:
      • chown
      • dd
      • mkfs.ext4
      • mount
      • umount
      • find
      • tail
      • cat
Note:

The kLWC Manager attempts to automatically install required packages and configure the user (UID/GID 4000) during setup. However, this is performed on a best-effort basis, and manual configuration may be required if any step fails.

Hardware Requirements

This section lists the minimum hardware resources required for kLWC to run properly.

Table 1: Hardware Requirements
Configuration Type Minimum vCPUs Minimum Memory Minimum Storage
Small 6 16 GB 400 GB
Large 12 32 GB 400 GB
Warning:

If the system does not meet the minimum requirements, kLWC may experience data collection issues.

Insufficient CPU or memory resources can cause the kLWC to enter a holding state. In this state, the collector may stop collecting data until adequate resources are available.