LiDAR-LOC on Virtual Machines: Installation and Licensing

LiDAR-LOC (LLS) can be installed on both Linux and Windows operating systems, including virtual environments running these systems. However, deploying LiDAR-LOC on a virtual machine (VM) requires consideration of certain factors. This article outlines best practices to help you successfully deploy LLS in Virtual Machines.

For further details about options to run LLS on Docker, please contact SICK Support.

There are two possible ways to license LLS in VMs:

1. Recommended: CmDongle with USB dongle
   • Hardware-based, portable, and resistant for VM cloning
2. Alternative: CmAct license 
   • This process requires downloading the license from the SICK license server using a unique ticket ID, which is then stored in a license container on your system. You can choose to store the license either on the host machine or locally within the virtual machine

To store the license locally in the VM, please consider that Wibu uses a propietary mechanism to detect hardware changes, and even minor system modifications can cause it to believe the software is no longer running on the originally licensed hardware, thus it may result in locked license containers:

• Avoid frequent hardware changes (e.g., CPU, MAC address, disk UUID)
• Disable features like dynamic MAC addresses or auto-scaling hardware
• Use fixed virtual hardware identifiers where possible
• Do not activate licenses before taking snapshots
• Avoid restoring snapshots after license activation
• Keep logs of VM changes and license status

To check for locked license containers, use the command cmu --list in Linux Terminal or cmu32 --list in Windows (via CodeMeter Command Prompt).

1. Once the Virtual Machine is rolled out, choose the corresponding LLS installer to download from here depending on the VM OS (Linux, Windows) and the local host's system architecture (ARM, x86/64...) and place the installer files in the VM
   
   
2. Follow the steps in our Operating Instructions to install LLS in your VM. The process should be identical as if you were installing LLS on a local machine
   
   
3. After installation of LLS and CodeMeter services, the LLS webUI is accessible on VM's localhost IP and port 80. It is possible to set up port forwarding rules in the VM. As such LLS webUI can also be accessed from the VM's host IP.

To generate an OS image out of the VM's configuration in order to distribute it to other VMs, proceed with step 2 depending on license type.

Prerequisite

• For hardware-based licensing option CmDongle, make sure the VM has access to the physical USB port.
• Base installation reference system fully installed and configured

Approach

1. Clone VM without special procedure.
2. License fleet by plugin in the USB dongle.

Prerequisite

• Base installation reference system fully installed and configured

Approach

Before doing a snapshot or clonning your VM, make sure no license is active and follow these steps:

1. Delete any existing CmContainer (again, make sure no license is stored in any of the existing containers before proceeding). You can list the existing CmContainers using the command cmu --list in Linux or cmu32 --list in Windows (via CodeMeter Command Prompt)
   
   The command to delete the CmContainer is 
   • cmu --delete-cmact-license --serial <Serial Number of the CmContainer> in Linux systems and 
   • cmu32 --delete-cmact-license --serial <Serial Number of the CmContainer> for Windows (via CodeMeter Command Prompt)
     
     
2. Generate the snapshot or the clone of the VM
   
   
3. Deploy the clone image in another VM or restore your current VM with the snapshot
   
   
4. Generate a CmContainer in the newly generated VM using the following command:
   • cmu --import --file /opt/sick/SICKAppEngine/SICK_CmActLicense_6001264.WibuCmLif in Linux sytems
   • cmu32 --import --file C:\Program Files\SICK\SICK AppEngine\SICK_CmActLicense_6001264.WibuCmLif in Windows (via CodeMeter Command Prompt)
     
     
5. Activate the CmAct license in each VM