xenserver
Citrix XenServer Probe

The Nimsoft xenserver monitoring probe has the capability of handling all common monitoring and data collection tasks for Citrix XenServer systems.
The probe collects and stores data and information from the monitored system at customizable intervals.
You can easily define alarms to be raised and propagated to the Nimsoft Enterprise Console when specified thresholds are breached.


Prerequisites


The xenserver probe requires the following:
  • An account with access to the XenServer pool master (if monitoring a pool) or host.

  • Collection of metrics enabled on each XenServer host. Typically this is enabled by default, but may not be for some versions of XenServer. See the Citrix XenServer documentation for information about your version. Most metrics are obtained using the Citrix XenServer RRD, and the rest are obtained using the xenapi.

  • Some versions of XenServer do not collect CPU utilization metrics by default. If this data is not being collected, run the following command on the XenServer system or a remote xe client to enable the collection of CPU utilization metrics (and the related probe checkpoints), and then restart the system:
    xe host-param-set uuid= other-config:rrd_update_interval=1
    Substitute your host's uuid for . The xe host-list command can be used to find the uuid of the host.

  • Installation of XenServer tools on each VM. We recommend creating XenCenter templates that have the XenServer tools installed. You may see some metrics returned without having the XenServer tools installed on each VM, but some metrics, such as guest memory usage, cannot be obtained unless the XenServer tools are present

    Installation Steps

    1. Install the package into your local archive
    2. Drop the package from your local archive onto the targeted robot. As part of the distribution to the target robot, the Nimsoft JRE package is included for the vcloud probe to use.
    3. The first time a configuration is applied with a new Virtual Center, the startup of the probe may take several minutes (depending on number of VMs in the Virtual Center).

      4. Guest Disk Usage Metrics Are Static

      VM Guest disk usage metrics coming from XenServer represent initial static guest usage only. XenServer does not provide real-time updated VM guest disk usage via xenapi or RRD.
    • Revision history
    Date Description State Version
    21.02.2018

    What's New:

    Added support for the following versions of XEN Server: 7.0, 7.1, 7.2, 7.3

     Fixed Defects:

    Fixed an issue in which the probe did not detect xen-tools. Support case 00755583

    For Detailed Release Notes-Please refer

    https://docops.ca.com/rest/ca/product/latest/topic?format=rendered&language=&space=UIMPGA&hid=xenserver_RN

    Note: Support case(s) may not be viewable to all

    SHA-1:07ab614efa6cee32f689c23fe83adf8320e4ab80
    MD5:e7f2fd4ab536286a4738cf0c31d8f22e
     
    		 GA 2.35
    11.04.2017 What's New:
    • Added support for Admin Console.
    • Added support for multiple resources to the same host
    • Enhanced metric processing performance
    • Added a metric for the HOST_CPU_GROUP: Host CPU Average Utilization. Salesforce case 00037522
    • Added the ability to send QoS values for the Virtual Machine State. Salesforce case 00071197
    Fixed Defects:
    • Fixed a defect in which the probe puts a host prefix on the source field for hypervisors. Salesforce case 00071197
    • Fixed a defect in which the probe created monitors for devices that were not configured to have them. Salesforce case 70003268
    • Fixed a defect in which session connections were not closed at the end of a session. Salesforce case 0000131675
    • Fixed a defect in which the Unified Dashboards for the probe were not correctly populating with data.
      Note: After you upgrade to v2.30, reapply the UMP templates for the Unified Dashboards to populate correctly.
    • Fixed a defect in which the Virtual Machine State metric for the VM and Host Template had a QOS value of "Default." The correct possible values are: -1 (Unknown), 0 (Unrecognized), 1 (Halted), 2 (Paused), 3 (Running), 4 (Suspended).
    md5sum: 8a9588a9d6e83c63cac58481ab567d22
    sha1sum: 3627fda70c0afa30d11f9ac51300a2a92f895c9d
    		 2.32
    03.11.2015 Fixes defects discovered since last release

    md5sum: b5bdf942899570cb7df2d6b655b4bd9e
    sha1sum: e907eb94db017371c66a16a514cf7141bdf81dab
    		 2.30
    21.12.2013 Added ability to configure the probe using the Admin Console or Snap UI. 2.03
    02.09.2013 Fixed the master failover issue. Improved CPU metric collection. Improved performance. Additional metrics. 2.01
    12.08.2013 Fixed the master failover issue. Improved CPU metric collection. Improved performance. Additional metrics. 2.00
    01.05.2013 Fixes for Pool behavior 1.22
    12.09.2012 Fixed robot config locking behavior 1.21
    30.09.2009 Commercial Release 1.10
    Requirements
    Platform: Please refer to the Platform Support Matrix located in the Download section of http://support.nimsoft.com
    Software: Java 1.6.0 , XenServer 4.1,5.0&6.0,Nimsoft Monitor Server 5.1.1 or later,NET Framework 3.5.x ,Nimsoft Robot 5.23 or later
    Hardware: None