Introduction

The purpose of thisThis document isaims to describe the monitoring of XenServer servers with Pandora FMS. Based on our experience in system monitoring, we have chosen a series of parameters have been chosen to monitorbe monitored by default,default; later modifications can be made according to the needs of each client.

To broadly describe the XenServer architecture we can talk about three elements:

● The XenServers or hosthosts (Citrix calls the XenServers "hosts"“hosts”, do not confuse VMs with hosts).
● The virtual machines or VMs that will be installed on a given host.
● The Storage Repositories or SRs that will also be associated with a givenspecific host.

The information of these elements will be extracted through queries to the XenAPI queries and RRD queries. More information is available at (http:https://docs.vmd.citrix.com/XenServer/6.0.0/1.0/en_gb/api/pypi.org/project/XenAPI/.

and

 http://xenserver.org/partners/developing-products-forxenserver/18-sdk-development/96-xs-dev-rrds.html). The way in which this extracted data arrives to the Pandora server will be
the following:

In a machine with connection to the XenServer we will install a Pandora SF agent, in this machine theThe plugin will be executed, it will make the queries to extract the information, select the required information and generate an XML document for each VM, for each host and for each SR. Each XML will contain the data of the parameters that we have decided to monitor offor each element. These xml will be sent by Tentacle to the Pandora server. Once these xml arrive toat the server, in the web console we will see how a new agent is generated for each xml, and how in these agents a module is generated for each parameter that we are monitoring.

For the execution of the plugin in the SF agent we will need:

● The software already installed in the system (Powershell).
● Python libraries so that .py scripts can be executed (usually already installed in the system).
installed on the system)
● The XenAPI.py and xmltodict.py libraries.

On the XenServer, port 443/TCP has tomust be enabled so that API queries can be performed.made. In addition, port 80/TCP (or the port wherethrough thewhich http connections occur) has tomust be enabled, inso order to be able to makethat the
RRDDRR queries.consultations.