Virtual Logmanager Deployment Guide

Introduction

Logmanager is available both as a hardware appliance and as a virtual machine. The currently supported virtual platforms are VMware ESXi, Microsoft Hyper-V, and Proxmox VE. Virtual Logmanager is designed to run on-premises in your datacenter.

Overview

Two different virtual images are available:

• OVA — can be imported directly into VMware ESXi / vSphere and used on other KVM-based platforms such as Proxmox VE. Most configuration options such as memory and vCPUs are pre-set.
• VHDX — a virtual hard disk for Microsoft Hyper-V. When working with the VHDX file, you must configure virtual hardware (RAM, vCPUs) on the Hyper-V side.

Requirements

OS Requirements

• VMware: ESXi 7.0 or higher
• Microsoft Hyper-V: Windows Server 2012 R2 or higher
• Proxmox VE: Proxmox VE 8.3 or higher with KVM virtualization enabled

Hardware Requirements

Additional disks

It is necessary to add an extra disk both for Virtual Logmanager and for Virtual Logmanager Forwarder. The additional disk is used for data storage / cache.

Additional disks can be added later to increase storage or cache size. Removing or shrinking an already initialized drive is not supported, so do not start with an unnecessarily large disk.

Deploy the Virtual Appliance

Choose your virtualization platform below. For detailed video walkthroughs, see: VMware deployment video and Hyper-V deployment video.

VMware ESXi / vSphere Microsoft Hyper-V Proxmox VE

Step-by-step wizard

Click a step to see details and screenshots.

1. Use Deploy OVF Template 2. Select the downloaded OVA file 3. Name the VM and choose a folder 4. Select a compute resource 5. Review template details 6. Accept the license agreement 7. Select storage 8. Select the target network 9. Review and finish the deployment 10. Adjust vCPU and RAM 11. Add an extra data disk 12. Power on the virtual machine

1. Use Deploy OVF Template

In the vSphere / ESXi client, right-click your cluster, host, or datastore and select Deploy OVF Template.

2. Select the downloaded OVA file

Browse to the Virtual Logmanager .ova file you downloaded and click Next.

3. Name the VM and choose a folder

Enter a meaningful virtual machine name and choose the target folder or inventory location. Click Next.

4. Select a compute resource

Choose the host or cluster that will run the Virtual Logmanager VM and click Next.

5. Review template details

Review the OVF template details and confirm that the configuration matches your expectations. Then click Next.

6. Accept the license agreement

Read and accept the license agreement, then click Next.

7. Select storage

Choose the datastore where the virtual machine files will be stored and click Next.

8. Select the target network

Select the virtual network / port group that the VM will use and click Next.

9. Review and finish the deployment

Review the final summary and click Finish to deploy the VM.

10. Adjust vCPU and RAM

After the VM is created, open its hardware settings and adjust vCPUs and RAM according to your desired EPS and the Hardware Requirements table.

11. Add an extra data disk

Add an additional virtual hard disk for data storage/cache. Choose the disk size according to your license and your expected log volume.

12. Power on the virtual machine

Power on the Virtual Logmanager VM. When it boots, proceed with CLI networking configuration and the web UI login.

Step-by-step wizard

Click a step to follow the setup.

1. Copy the VHDX file 2. Open Hyper-V Manager 3. Create a new virtual machine 4. Choose storage location 5. Select Generation 2 6. Assign memory 7. Configure networking 8. Attach the existing VHDX disk 9. Confirm the summary 10. Add a new data disk 11. Choose the path for the secondary disk 12. Set disk size according to your license 13. Disable Secure Boot 14. Start the virtual machine

1. Copy the VHDX file

Copy the Logmanager.vhdx file to the desired storage location on your Hyper-V server.

2. Open Hyper-V Manager

Connect to the Hyper-V server and open the Hyper-V Manager console.

3. Create a new virtual machine

In the left pane, right-click the server name and choose New > Virtual Machine.

4. Choose storage location

Name your server, then optionally select Store the virtual machine in a different location and specify where the VM configuration will be stored. By default it is saved under C:\ProgramData\Microsoft\Windows\Hyper-V\.

5. Select Generation 2

On the Specify Generation screen, choose Generation 2 and continue.

6. Assign memory

In Assign Memory, configure the VM memory. Follow the Hardware Requirements and allocate at least 16 GB RAM.

7. Configure networking

On Configure Networking, select the virtual switch through which the VM will communicate.

8. Attach the existing VHDX disk

In Connect Virtual Hard Disk, select Use an existing virtual hard disk and specify the path to the Logmanager .vhdx file. Click Next.

9. Confirm the summary

Check the summary of VM parameters and confirm with Finish.

10. Add a new data disk

In Hyper-V Manager, right-click the newly created VM and select Settings. Select IDE Controller 0 and click Add to add a new hard drive. For best performance, choose Fixed size for the new data disk and continue.

11. Choose the path for the secondary disk

Specify the path for the secondary virtual disk file and click Next.

12. Set disk size according to your license

Choose the disk size according to your license and expected log volume. Review and click Finish.

13. Disable Secure Boot

In Security settings for the VM, uncheck Enable Secure Boot.

14. Start the virtual machine

Start the virtual machine. When it boots, continue with CLI networking configuration and the web UI login.

Step-by-step wizard

Click a step to see details and screenshots.

1. Add Directory storage (Disk image + Import) 2. Upload OVA into Import storage 3. Select OVA and start Import 4. Set import options (VirtIO, disable efidisk0) 5. Watch import task progress 6. Add EFI disk 7. Add SCSI data disk (cache/storage) 8. Set CPU type to Host 9. Verify VM hardware parameters 10. Enter UEFI boot menu / Boot Maintenance Manager 11. Open Boot Options 12. Choose Add Boot Option 13. Select SCSI disk in File Explorer 14. Browse disk directories 15. Open EFI → GRUB folder 16. Select EFI/GRUB/grub64.efi 17. Name the boot option and commit 18. Open Change Boot Order 19. Move Logmanager to first position 20. Return to UEFI main menu 21. Open Device Manager 22. Disable Secure Boot attempt 23. Reset/Reboot VM 24. Logmanager boots successfully

1. Add Directory storage (Disk image + Import)

Create a new storage (e.g. vm-import) with content types Disk image and Import.

2. Upload OVA into Import storage

Upload the downloaded OVA file into the Import-enabled storage.

3. Select OVA and start Import

Select the uploaded OVA in the storage content list and click Import.

4. Set import options (VirtIO, disable efidisk0)

Before importing: uncheck efidisk0, set SCSI Controller to VirtIO SCSI, and Network interface to VirtIO.

5. Watch import task progress

Wait for the import job to finish in the task viewer.

6. Add EFI disk

After import, open VM → Hardware and add a new EFI Disk.

7. Add SCSI data disk (cache/storage)

Add an extra SCSI disk for Logmanager data/cache (size according to your use case).

8. Set CPU type to Host

Set CPU type to Host in VM CPU settings.

9. Verify VM hardware parameters

Review disks, NIC, CPU and memory to confirm everything matches your sizing.

10. Enter UEFI boot menu / Boot Maintenance Manager

Start the VM, press ESC during boot and open Boot Maintenance Manager.

11. Open Boot Options

In Boot Maintenance Manager, select Boot Options.

12. Choose Add Boot Option

Select Add Boot Option to add a new firmware boot entry.

13. Select SCSI disk in File Explorer

In the File Explorer, choose the SCSI disk that contains the bootloader.

14. Browse disk directories

Browse the disk and locate the EFI directory.

15. Open EFI → GRUB folder

Open EFI and then navigate to the GRUB folder.

16. Select EFI/GRUB/grub64.efi

Select EFI/GRUB/grub64.efi as the bootloader file.

17. Name the boot option and commit

Enter a description (e.g. Logmanager) and confirm with Commit Changes and Exit.

18. Open Change Boot Order

Open Change Boot Order to prioritize the new entry.

19. Move Logmanager to first position

Move Logmanager to the first position and commit changes.

20. Return to UEFI main menu

Return to the main menu after saving the new boot option and order.

21. Open Device Manager

Open Device Manager to access Secure Boot settings.

22. Disable Secure Boot attempt

Open Secure Boot Configuration and uncheck Attempt Secure Boot. Save (usually F10).

23. Reset/Reboot VM

Return to the main menu and select Reset to reboot the VM.

24. Logmanager boots successfully

After reboot, the VM should boot into Logmanager successfully. Continue with CLI networking below.

Configure Virtual Logmanager

Once the VM is running, open the virtual console from your hypervisor and log in to the text console with the default credentials:

• Username: admin
• Password: admin

You will perform initial network configuration from the limited Logmanager CLI. For more commands, see the official CLI documentation.

Configuring an IP address

Virtual Logmanager uses static IP addresses. Before you start, decide on the network information you want to use, for example:

• IP address: 192.168.1.29
• Netmask: 255.255.255.0
• Gateway: 192.168.1.1

Then follow the steps below on the VM text console.

Step 1: Add the new static IP

Command syntax:

set ip ip_address network vlan

Example:

set ip 192.168.1.29 255.255.255.0 default_vlan

Step 2: Delete the default route

Command syntax:

delete route target netmask gw

Example:

delete route 0.0.0.0 0.0.0.0 192.168.0.1

Step 3: Add the new route

Command syntax:

set route target netmask gw

Example:

set route 0.0.0.0 0.0.0.0 192.168.1.1

Step 4: Delete the default IP

Command syntax:

delete ip ip_address network vlan

Example (removing the old default address):

delete ip 192.168.0.20 255.255.255.0 default_vlan

Login to the Web UI

After you configure the static IP address and default route, you can access the Logmanager web interface from your browser:

https://YOUR-IP-ADDRESS/

Log in with your administrative credentials and continue with the standard product configuration.