# HPVM HP Virtualization Manager monitoring

# Introduction

This plugin monitors HPVM virtualization systems. It could be launched as agent plugin or server plugin, based on a configuration flag.  
  
A new agent will be generated for each virtualized system running in the monitored system.  
  
To retrieve all information about the environment, the plugin uses:  
  
● hpvmstatus

# Compatibility matrix

**Systems where it has been tested**​: HP-UX B.11.31  
**Systems where it works**​: HP-UX

# Requirements

The plugin requires the following:  
● A Pandora FMS agent in the the system  
● A valid user allowed to execute the plugin  
○ This user must have also rights to execute hpvmstatus with next modifiers:  
■ hpvmstatus  
■ hpvmstatus -X  
■ hpvmstatus -r -X

# Configuration

In the configuration file of the Pandora FMS HPVM plugin you can specify the following parameters:

```
#====================================================
#Pandora HPVM Plugin conf file
#====================================================
# HPVM Agent configuration
# comment to use hostname instead
#agent_name = nombre de agente personalizado
# Agent configuration
agent_interval = 300
agent_group = HPVM
# Module interval
module_interval = 1
#module_tags = Networking
module_group =
# Pandora API configuration
#api_url = http://inna.lab.artica.lan/pandora_console/include/api.php
#api_user = admin
#api_user_pass = pandora
#api_pass = 1234
# Pandora Server configuration
mode = tentacle
tentacle_ip = su instalacion de pandorafms
tentacle_port = 41121
tentacle_opts =
tentacle_client = "tentacle_client"
temp = .
```

agent\_name  
Custom agent name.  
agent\_interval  
Agent’s interval.  
agent\_group  
Agent’s group.  
module\_interval  
Agent’s module interval.  
module\_tags  
Some security tags (comma separated).  
module\_group  
Module group (for all modules).  
mode  
It could be transferred by Tentacle or locally. If we specify local mode, we must set a  
target folder where the .data files will be written.

# Manual execution

The Pandora FMS HPVM plugin could be deployed as described next:  
  
Configure the as\_agent\_plugin ​token to 1 (launched as agent plugin)

```
module_plugin /usr/bin/perl pandora_hpvm.pl pandora_hpvm.conf
```

Configure the as\_agent\_plugin ​token to 0 (launched as server plugin), for example, run by crontab:

```
*/5 * * * * root /usr/bin/perl pandora_hpvm.pl pandora_hpvm.conf
```

# Modules generated by the plugin

Parameters monitored by the plugin (grouped by element type):  
Server agent (which launches the plugin)​:  
Available VMs  
HPVM PluginHPVM Plugin execution status  
HPVM ServicePresence of hpvmctrld (X instances)  
HPVM Service CPU usageCPU usage of hpvmctrld (X instances)  
HPVM Service RAM usageRAM usage of hpvmctrld (X instances)  
hpvmappPresence of hpvmapp (X instances)  
hpvmapp CPU usageCPU usage of hpvmapp (X instances)  
hpvmapp RAM usageRAM usage of hpvmapp (X instances)  
  
**Virtual machines​:**  
  
boot\_type  
console\_type  
CPU usage  
device\_number  
direct\_io\_number  
distributed  
effective\_serverid  
guest\_type  
Host RAM available  
Host RAM free  
local\_id  
memory total  
model\_name  
networks\_number  
run\_pid  
run\_serverid  
serial\_number  
uuid  
vcpu\_number  
vm\_condition  
vm\_config\_label  
vm\_config\_version  
vm\_state  
vm\_version  
vm\_version\_label