AppNeta V25
search cancel

AppNeta V25

book

Article ID: 263674

calendar_today

Updated On:

Products

AppNeta

Issue/Introduction

I've deployed my AppNeta V35 for VMWare or KVM, but the appliance is appearing as a Custom Appliance -  V25 or vk25:

Cause

This is usually caused by the monitoring point having resource restraints.  Please check the available memory and cpu resoruces. 

Any virtual machine that comes up without the following minimum requirements will show up in AppNeta as a v25, which is an unsupported Monitoring Point type that cannot be licensed.

KVM Requirements:

 

Guest requirements

v35 KVM

CPU

2 cores

RAM

4 GB

Storage

16 GB

File system

ext4

Network interfaces

1 virtio_net interface

kernel drivers

virtio_net virtio scsi virtio balloon kvm-clock

VMware Requirements:
 
Guest requirements
v35 VMware
CPU
2 cores
RAM
4 GB
Storage
16 GB
Network interfaces
1 vmxnet3 interface
Host kernel drivers
vmxnet3

 

Resolution

If the appliance is detected as a V25, please attempt to redeploy the monitoring point again, and ensure you have provided sufficient resources.
If the issue continues, please open a support ticket.

Additional Information

A common reason for a v35 to be demoted with KVM is due to mrg_rxbuf=off as it is necessary for this setting to be set off.

As an example, the message would be: model vk35 expects mrg_rxbuf=off - demoting to vk25