CA Unified Infrastructure Management

Transcription

1 CA Unified Infrastructure Management vmware Guide v6.2 series

2 Copyright Notice This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time. This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the CA Software ). Such agreement is not modified in any way by the terms of this notice. Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy. The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The manufacturer of this System is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Legal information on third-party and public domain software used in this product is documented in the Third-Party Licenses and Terms of Use (

3 Contact CA Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback about Product Documentation Send comments or questions about CA Technologies product documentation to To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the support website at

4

5 Contents Chapter 1: vmware vmware Overview... 7 Chapter 2: vmware Probe Deployment 11 Requirements Chapter 3: Requirements for vmware 13 Hardware Requirements Software Requirements Supported Platforms Probe Deployment Chapter 4: vmware Probe Configuration v Probe Configuration Interface Installation for vmware Monitoring Capabilities vmware Templates v Probe Configuration General Setup Create a New Resource Message Pool Manager Create New Template Advanced Configuration Chapter 5: Adding vmware Monitors 21 Manually Selecting Monitors to be Measured Enabling the Monitors for QoS and Alarming To Edit Monitor Properties Using Templates To Create a New Template To Add Monitors to a Template To Apply a Template Using Automatic Configurations Adding a Template to the Auto Configurations Node Adding a Monitor to the Auto Configurations Node Contents 5

6 Exploring the Contents of the Auto Configurations Node Checking the Auto Monitors Node Chapter 6: vmware Probe Configuration Interface v Configuration Interface Navigation The Toolbar Buttons The Navigation (Left) Pane Resources Node Templates Node Navigation Pane Updates for vmware The Content (Right) Pane Content Pane Updates for vmware Chapter 7: Best Practices for vmware 35 Support for Instance UUIDs Prepending Origin to the QoS Source Field Chapter 8: Metrics for vmware v6.2 for Infrastructure Manager 37 Chapter 9: vmware Known Issues and Workarounds v No Value is Listed for a vmware Monitor vmware Out of Memory Errors Error When Closing the vmware Configuration GUI vmware UI Fails to Load Auto/All Monitors Nodes vmware UI Slowly Loads Nodes Within the Inventory Tree Chapter 10: vmware v6.2 Error Messages 61 vmware Error Message Examples for v vmware Guide

7 Chapter 1: vmware 6.2 This description applies to the vmware probe version 6.2. This section contains the following topics: vmware Overview (see page 7) Documentation Changes (see page 8) vmware Overview Business based on Virtualization Technology depends on a high degree of quality and availability. In such situations, the availability and performance of the VMware hosts and virtual machines must be as high as possible. Monitoring and managing the components and services can help you ensure optimal performance. The CA Unified Infrastructure Management vmware probe automates all common monitoring and data collection tasks, and lets you focus on problems as they arise. The vmware probe collects and stores data and information from the monitored components through VMware Virtual Center, or by connecting to ESX servers directly, at customizable intervals. You can define alarms to be raised and propagated to the Alarm Console when the specified thresholds are breached. Chapter 1: vmware 6.2 7

8 vmware Overview Documentation Changes This table describes the version history for this document. Version Date What's New? 6.2 September 2014 Updated the vmware Metrics table. 6.1 July 2014 Updated the vmware Metrics table. 6.1 Mar 2014 Added requirements for VMware VirtualCenter 5.5, VMware ESX/ESXi 5.5, and.net. Updated QoS metrics. 6.0 Dec 2013 Updated document for 6.0 release. New features include support for VMware 5.5 and performance enhancements. 5.0 Nov 2013 Updated document for 5.06 service release. 5.0 Mar 2013 Updated to use common components. 4.2 Jun 2012 Added support for multi-tenant tracing and copying a template. 4.1 Mar 2012 Polling interval alarms are now cleared with the collection cycle take less time than the configured interval. Target string corrected for DS, Cluster, and Network auto-monitors created from static monitors. Target string corrected to contain topology path for Resource Pools and Networks. Corrected the robot dependencies setting in the VMware probe package; restored missing VM Memory usage metric in the inventory tree. Corrected reported VM Snapshot size. Added support for tracking VMs by instanceuuids for env. with duplicate UUIDs (e.g., Lab Manager & vcloud) 4.0 Oct 2011 Added support for SOC management of hosts; VMCount and VMCountActive monitors now report zero for vsphere targets with zero VMs. 8 vmware Guide

9 vmware Overview Related Documentation Documentation for other versions of the vmware probe The Release Notes for the vmware probe Monitor Metrics Reference Information for CA Unified Infrastructure Management Probes ( Documentation Changes 9

10

11 Chapter 2: vmware Probe Deployment Successful distribution of the vmware probe package relies on the Java package installed with the CA Unified Infrastructure Management Server. The vmware probe requires a VMware VC/ESX Server environment. This section contains the following topics: Requirements (see page 11) Probe Deployment (see page 14) Requirements This section contains the prerequisites and system requirements for the vmware probe. Chapter 2: vmware Probe Deployment 11

12

13 Chapter 3: Requirements for vmware This section describes the requirements for the VMware Monitoring probe. The vmware probe requires user account access to the following applications: User access to the VMware vcenter or ESX server. Successful distribution of the VMware Monitoring probe package relies on the Java package installed with the CA Unified Infrastructure Management server. The VMware Monitoring probe supports monitoring for the following vsphere environments: v6.1 and later: VMware VirtualCenter 5.1 update 2 or newer, and 5.5 VMware ESX/ESXi 5.1 update 2 or newer, and 5.5 v6.0 and earlier: VMware VirtualCenter 4.1 update 1 or newer, 5.0, 5.1, and 5.5 VMware ESX/ESXi 4.1 update 1 or newer, 5.0, 5.1, and 5.5 Important! The probe requires targeted vsphere environments to use unique UUIDs. This means that when cloning virtual machines (VMs), each clone must have a distinct UUID in order for proper monitoring to occur. If each VM does not have a unique UUID, incorrect data will be reported for the VMs. For more information see Handling Cloned VM Environments. Hardware Requirements The vmware probe should be installed on systems with the following minimum resources: Memory: 2-4 GB of RAM. The probe as shipped requires 512 MB of RAM. CPU: 3GHz dual-core processor, 32-bit or 64-bit. Chapter 3: Requirements for vmware 13

14 Probe Deployment Software Requirements The vmware probe requires the following software environment: CA Unified Infrastructure Management server 7.1 or later. Note: It is recommended that the CA Unified Infrastructure Management server and CA Unified Management Portal (UMP) are the same version. Robot version 5.23 or later. Java Virtual Machine version 1.6 package or later (deployed as part of the probe package). Note: CA Unified Infrastructure Management Server 7.0 or later version is required to use the Unified Service Management (USM) portlet, which most customers use. If you do not want to use USM, data collection and dashboards function with CA Unified Infrastructure Management or later. For Infrastructure Manager users: Infrastructure Manager 4.08 or later. Microsoft.NET framework 3.5 on the system running the Infrastructure Manager and VMware Monitoring probe GUI. Supported Platforms Refer to the Compatibility Support Matrix for the latest information about supported platforms. See also the Support Matrix for Probes for more specific information about the probe. Probe Deployment There are three ways to distribute archive packages. You can distribute the package within the web-based Admin Console (for supported probes), from within Infrastructure Manager, or use the standalone Distribution application. 14 vmware Guide

15 Chapter 4: vmware Probe Configuration v6.2 Important! Service-oriented configuration of the vmware probe through UMP is not compatible with the standard configuration through the probe's configuration interface described here. Do not mix or interchange configuration methods! If you do, the result will be unpredictable monitoring of your VMware hosts and/or VMs. See the VMware section of the Monitor Configuration Reference in UMP help for details on service-oriented configuration. With the vmware probe installed, you must next define what to monitor. At a high level, there are three steps: 1. Connect to the VMware vcenter or ESX server. 2. Add monitors (checkpoints). See the description in the section Adding and Configuring Monitors (Checkpoints). 3. Configure the properties for the checkpoints, in which you define QoS data, set thresholds, and define alarms to be sent if thresholds are breached. Note: Click the Apply button to activate any configuration changes. This section contains the following topics: Probe Configuration Interface Installation for vmware (see page 15) Monitoring Capabilities (see page 15) vmware Templates v6.2 (see page 16) Probe Configuration (see page 16) Probe Configuration Interface Installation for vmware The probe configuration interface is automatically downloaded and installed by the Infrastructure Manager when the probe is deployed on a robot. Monitoring Capabilities The following entities may be monitored on hosts and virtual machines: CPU Memory Disk I/O Chapter 4: vmware Probe Configuration v6.2 15

16 vmware Templates v6.2 Network I/O Events Alarms Datastores Datastore Free Space vmware Templates v6.2 Templates allow you to define reusable sets of monitors to apply to various hosts, VMs, ESX servers, or datastores. After you create a template and define a set of checkpoints for that template, you can either: Drag-and-drop the template into the VMware probe hierarchy where you want to monitor the checkpoints defined for the template. This creates a static monitor for that resource component and its children (recursively) based on the template contents at the time the static monitor is created. Drag-and-drop the template onto the Auto Configuration node to add the template contents to the list of auto configuration monitors. See the section Using Templates for details. Probe Configuration This section contains specific configuration information for the vmware probe. General Setup Click the General Setup button to set the level of details written to the log file for the vmware probe. Log as little as possible during normal operation to minimize disk consumption. This is a sliding scale with the range of information logged being fatal errors all the way to extremely detailed information used for debugging purposes. Click the Apply button to implement the new log level immediately. Note: The probe allows you to change the log level without restarting the probe. 16 vmware Guide

17 Probe Configuration Create a New Resource There are two ways to create a Resource: Click the New Resource button on the toolbar. Right click Resources in the navigation pane and select New Resource. The Resource (New) dialog box appears. Enter the appropriate field information: Hostname or IP Address Port Active The hostname or IP address of the vcenter or ESX server system to monitor. The port number for the vcenter or ESX server REST API environment. Default is 443. Select this checkbox to activate or deactivate monitoring of the Resource. Username A valid username and domain name to be used by the probe to log on to the vcenter or ESX server environment. Example: admin Password A valid password to be used by the probe to log on to the vcenter or ESX server environment. Alarm Message Select the alarm message to be sent if the Resource does not respond. Note: You can edit the message or define a new message using the Message Pool Manager. Check Interval The check interval defines how often the probe checks the values of the monitors. This can be set in seconds, minutes or hours. vcenter or ESX server system data is updated once per minute. We recommend polling once every 10 minutes. The polling interval should not be smaller than the time required to collect the data. Test button Click the Test button to verify the connection to the Resource. After completing the fields and testing that the connection works, click OK to add the Resource. The initial data collection/polling cycle starts. The resource hierarchy will populate once the polling cycle has completed. Chapter 4: vmware Probe Configuration v6.2 17

18 Probe Configuration Message Pool Manager Add a New Alarm Message You can add, remove, or modify alarm messages.these are the messages sent when a QoS threshold has been breached. To add a new alarm message: 1. Click the Message Pool Manager button on the toolbar. The Message Pool dialog appears. 2. Click the Add button. The Message Properties dialog appears. 3. Complete the field information: Identification Name Token Delete an Alarm Message The name of the message. The type of alarm, either "monitor_error" or "resource_error". Error Alarm Text The alarm text sent when a violation occurs. Variables can be used in this field. Example: $monitor This variable will put the actual monitor name in the alarm text. There are several available variables: $resource, $host, $port, $descr, $key, $unit, $value, $oper, and $thr. Clear Alarm Text (OK) The text sent when an alarm is cleared. Error Severity Severity of the alarm. Subsystem string/id The NAS subsystem ID for the vcenter or ESX server system. 4. Click OK to save the new message. To delete an alarm message: 1. Click the Message Pool Manager button on the toolbar. The Message Pool dialog appears. 18 vmware Guide

19 Probe Configuration Edit an Alarm Message 2. Select the message to remove. 3. Click the Remove button. The alarm message is removed. 4. Close the Message Pool Manager window and click Apply to implement the changes. To edit an alarm message: 1. Click the Message Pool Manager button on the toolbar. The Message Pool dialog appears. 2. Select a message id in the list. 3. Click the Edit button. The Message Properties dialog appears. 4. Update the message properties as needed. 5. Click OK. 6. Close the Message Pool Manager window and click Apply to implement the changes. Create New Template There are two ways to create a new template: Click the New Template button on the toolbar. Right click the Templates node in the navigation pane and select New Template. See the section Using Templates for more information. Advanced Configuration Multi-tenant Tracing This section describes advanced configuration options for the vmware probe. This feature assumes that a tenant would be isolated under a Cluster or Template and everything under it belongs to the tenant. By including this path in the QoS details, reporting can filter on the path to display these based on tenants. Chapter 4: vmware Probe Configuration v6.2 19

20 Probe Configuration Multi-tenant tracing can be configured using the Raw Configure option for the probe. 1. Hold the shift key, and right click on the probe in Infrastructure Manager. 2. Select Raw Configure from the menu. The Raw Configure screen appears. 3. Select setup in the left pane and click the New Key button. 4. Enter multi_tenant_path in the Enter key name: field. 5. Enter one of the following values in the Enter value: field: target For VMs and their children a QoS target component is augmented to list the full path from the containing Data Center down to the VM. If this component resides within a template and pool those will be included in the path. source For VMs and their children a QoS source component is augmented to list the full path from the containing Data Center down to the VM. If this component resides within a template and pool those will be included in the path. both This option enables both the target and source settings listed above. The following examples illustrate the path that would display in your reports: Target Example: If you enabled the Memory metric on a VM: Without this setting the target would simply be Memory. With this setting the target would be of the form <DataCenter Name>/<Cluster Name[/<Optional Template Name>[/<Optional pool name>]]::<vm Name>::Memory DataCenter-1/Cluster-1/desktopTemplate/desktops::VM-1::Memory Source Example: If you enabled the Memory metric on a VM: Without this setting the source would simply be the VMs name. With this setting the source would be of the form <DataCenter Name>/<Cluster Name[/<Optional Template Name>[/<Optional pool name>]]::<vm Name> DataCenter-1/Cluster-1/desktopTemplate/desktops::VM-1 20 vmware Guide

21 Chapter 5: Adding vmware Monitors There are three different ways to add monitors to vmware entities: Manually select the monitors To manually select and enable monitors, navigate to the target entity within the Resource. This lists its monitors in the right pane. Use the available check-boxes to enable QoS monitoring for the selected metrics. To enable Alarm thresholding, you will need to launch the Edit Monitor dialog. See the section Manually Selecting Monitors to be Measured. Use Templates Templates let you define reusable sets of monitors to apply to various vmware monitored entities. See the section Using Templates for further information. Use Auto Configurations Auto Configuration is a powerful way to automatically add monitors to be measured. Monitors are created for new devices (that is, ones not currently monitored) that would otherwise need manual configuration to be monitored. Example: Auto Configuration contains an auto-monitor for VM 'Memory Used'. When a new VM is created the Auto Configuration feature creates a monitor automatically for monitoring the VM. See the section Using Automatic Configurations for further information. This section contains the following topics: Manually Selecting Monitors to be Measured (see page 22) Using Templates (see page 25) Using Automatic Configurations (see page 27) Chapter 5: Adding vmware Monitors 21

22 Manually Selecting Monitors to be Measured Manually Selecting Monitors to be Measured To select a monitor you want to be measured for a Resource, click the Resource node in the navigation pane, and navigate through the Resources hierarchy. Select a folder in the hierarchy to see the monitors for it, listed in the right pane. Click the check box beside the Monitors you want to be active. Typically when you select a Resource component in the navigation pane, you see the current value for its monitors in the Value column of the content pane. However, some monitors for the vmware probe take a while to collect. For these monitors, the current value is not displayed unless the monitor is activated (the check box is selected). Once you select the check box, the value is collected during the next polling cycle, even if QoS and alarming are not enabled. Note: You can also add monitors to be measured using templates (see the section Using Templates). Select the All Monitors node to list all monitors currently being measured in the right pane. You can select or deselect monitors here as well. Green icon - the monitor is configured and active Gray icon - the monitor is configured but not active Black icon - the monitor is not configured Note: If a monitor name is in italics you have changed the configuration however have not applied the changes. Enabling the Monitors for QoS and Alarming Selecting the checkbox next to a monitor name only enables the monitor. To configure the probe to send QoS data and/or send alarms you must modify the properties for each monitor. Double-click a monitor (or right-click and select Edit) to launch the monitor s properties dialog. See To Edit Monitor Properties for further information. To Edit Monitor Properties Double-click a monitor (or right-click and select Edit) to launch the monitor s properties dialog. Note the Type column when monitors are listed in the right pane. Monitors of type value and type event have different properties. 22 vmware Guide

23 Manually Selecting Monitors to be Measured Monitors of Type Value The properties for monitors of type value are as follows: Name Key This is the name of the monitor. The name will be inserted into this field when the monitor is retrieved from the vcenter or ESX server environment. This is a read-only field, describing the monitor key. Description This is a description of the monitor. This description will be inserted into this field when the monitor is retrieved from the vcenter or ESX server environment. Value Definition Active This drop-down list lets you select which value to be used, both for alarming and QoS: You have the following options: The current value. The most current value measured will be used. The delta value (current previous). The delta value calculated from the current and the previous measured sample will be used. Delta per second. The delta value calculated from the samples measured within a second will be used. The average value of the last and current sample: (current + previous) / 2. The average value last... The user specifies a count. The value is then averaged based on the last "count" items. This activates the monitoring of the probe. Enable Alarming Selecting this option activates the alarming. Note that the monitor will also be selected in the list of monitors in the right window pane when this option is selected, and that you can enable or disable monitoring of the checkpoint from that list. This section describes the alarm properties for the monitor. You can define both a high and a low threshold. Initially the high threshold is set to the current value. Set this value to match your needs. The low threshold is initially disabled. If you want to use it, you must select another operator than "disabled" from the list and configure it to match your needs. Chapter 5: Adding vmware Monitors 23

24 Manually Selecting Monitors to be Measured Operator Select from the drop-down list the operator to be used when setting the alarm threshold for the measured value. Example: >= 90 means the monitor is in alarm condition if the measured value is equal to or above 90. = 90 means the monitor is in alarm condition if the measured value is exactly 90. Threshold Unit The alarm threshold value. An alarm message is sent when this threshold is violated. This field specifies the unit of the monitored value (for example %, Mbytes etc.). The field is read-only. Message ID Select the alarm message to be issued if the specified threshold value is breached. These messages reside in the message pool. You can modify the messages in the Message Pool Manager. Publish Quality of Service Select this option if you want QoS messages to be issued on the monitor. QoS Name The unique QoS metric. This is a read-only field. 24 vmware Guide

25 Using Templates Monitors of Type Event and Alarm You can monitor vcenter or ESX server events and alarms on entities, such as clusters, hosts, templates, and VMs. The event is forwarded as an alarm message and the suppression key is based on the entity. The properties for monitors of type event are: Name Key This is the name of the monitor. The name will be inserted into this field when the monitor is retrieved from the vcenter or ESX server, and you are allowed to modify the name. This is a read-only field, describing the monitor key. Description This is a description of the monitor. This description will be inserted into this field when the monitor is retrieved from the vcenter or ESX server. This is a read-only field. Subscribe Selecting this option, an alarm will be sent when this event has been triggered. Operator Select the operator to be used when setting the alarm threshold for the event. This threshold refers to the event s severity level in vcenter or ESX server. Example: >= 1 means alarm condition if the event is triggered, and the severity level in vcenter or ESX server is equal to or higher than 1 (Warning). Severity The threshold severity level for the event in vcenter or ESX server. Message Token Select the alarm message to be issued if the specified threshold value is breached. These messages are kept in the message pool. The messages can be modified in the Message Pool Manager. Important! Monitoring events may cause a larger than expected increase in alarm messages and possibly decrease in system performance. Using Templates Templates let you define reusable sets of monitors to be measured on multiple VMs. They provide an easy way to accomplish consistent monitoring of your vcenter or ESX server environment. Chapter 5: Adding vmware Monitors 25

26 Using Templates You can create your own templates and define a set of monitors belonging to each. You can then apply these templates to anything in the Resources or Auto Configurations hierarchies in the navigation pane by dragging the template and dropping it on the appropriate item. This assigns the template monitors to the drop point and everything below it. If you apply a template to the Auto Configuration, its monitors are applied to all vcenter or ESX server monitored entities as they appear in the system. If you need a finer level of control, you can apply a template to anything in the Resources hierarchy; in this case the monitors are applied to the drop-point and everything subordinate to it. Any templates applied within the Resources hierarchy are static monitors. The static monitors override any auto monitors for that specific resource entity. Note: You can do both, placing general-purpose templates in Auto Configuration, and applying special-purpose templates that override the Auto Configuration templates on specific nodes, for specific purposes. See the Using Automatic Configurations (see page 27) section for details on Auto Configuration. To Create a New Template There are two ways to create a template: Click the toolbar button for New Template ( ). Right click the Templates node in the navigation pane, and choose New Template from the menu. In the resulting Template Properties dialog, specify a Name and a Description for the new template. Note that you can also edit an existing template: Select one of the templates defined under the Templates node in the navigation pane, right-click it, and select Edit from the menu. To Add Monitors to a Template There are two ways to add a monitor to a template: Drag it from the content pane and drop it on the template in the navigation pane. Right-click on a monitor in the content pane and select Add to Template. You can edit the properties for monitors in the template as described in the section To Edit Monitor Properties (see page 22). 26 vmware Guide

27 Using Automatic Configurations To Apply a Template Drag the template to the Auto Configuration node or the Resource (VMs, template, pool, or Datastore) where you want it applied, and drop it there. Note: You can drop the template on an object containing multiple subordinate objects. This applies the template to the entity and all its subordinate entities. A static monitor is created for this entity. Using Automatic Configurations Automatic configuration is an optional but powerful way to automatically add monitors to be measured. This is the preferred method for configuring your resources. When new vcenter or ESX server monitored entities are detected, "Auto Monitors" are created for devices that are not currently monitored using a static monitor. In the case of VMs, only VMs in the power on state are monitored using auto-monitors. If the VM is in another state it is ignored. The Auto Configuration feature consists of two sub-nodes located under the Resource node in the navigation pane: Auto Configurations node You can add contents from one or more templates or individual checkpoints to this node, using drag-and-drop. Click the Apply button and restart the probe to activate the changes. The probe then searches through the vcenter or ESX server environment for applicable entities. Auto Monitors representing the monitor(s) under the Auto Configuration node are created (and listed under the Auto Monitor node, see below) for applicable entities where the metric does not already have a static monitor configured for it. Important! If you are experiencing performance problems, we recommend increasing the polling cycle and/or the memory configuration for the probe. Increase memory when the probe is running out of memory. Increase polling cycle when the collection takes longer than the configured interval. Auto Monitors node This node lists Auto Monitors, created based on the contents added to the Auto Configuration node. Auto Monitors are only created for content without an existing static monitor. Chapter 5: Adding vmware Monitors 27

28 Using Automatic Configurations Adding a Template to the Auto Configurations Node You can add a template's content to the Auto Configurations as follows: 1. Click the Templates node in the navigation pane to list all available templates in the content pane. 2. Add a template to the Auto Configurations node by dragging the template from the list and dropping it on the Auto Configurations node in the navigation pane. 3. Click the Auto Configurations node to verify that the template's content was successfully added. See the Using Templates section to learn more about templates. Note: You must click the Apply button and restart the probe to activate configuration changes. Adding a Monitor to the Auto Configurations Node You can add a single monitor (checkpoint) to the Auto Configurations node. To list available monitors: 1. Select the Resource node in the navigation pane and navigate to the point of interest. 2. Select an object to list its monitors in the right pane. 3. Add the monitor to the Auto Configurations node by dragging the monitor to the Auto Configurations node and dropping it there. 4. Click the Auto Configurations node and verify that the monitor was successfully added. Note: You must click the Apply button and restart the probe to activate configuration changes. 28 vmware Guide

29 Using Automatic Configurations Exploring the Contents of the Auto Configurations Node To verify that the monitors were successfully added, click the Auto Configurations node in the navigation pane. To edit the properties for a monitor, right-click in the list and choose Edit from the menu. See the section To Edit Monitor Properties for detailed information. To delete a monitor from the list, right-click in the list and choose Delete from the menu. Note: You must click the Apply button and restart the probe to activate configuration changes. Checking the Auto Monitors Node Note: When monitors have been added to the Auto Configurations node, you must click the Apply button and restart the probe to activate the Auto Configuration feature. When you restart the probe, it searches through the Resource's entities. For each one that is currently not monitored, an Auto Monitor is created for each of the monitors listed under the Auto Configurations node. All defined Auto Monitors are listed under the Auto Monitors node. Chapter 5: Adding vmware Monitors 29

30

31 Chapter 6: vmware Probe Configuration Interface v6.2 This section contains the basic GUI information for the vmware probe. Double-click the line representing the vmware probe in the Infrastructure Manager to launch the vmware probe configuration interface. It initially appears with the Resources hierarchy empty. This section contains the following topics: Configuration Interface Navigation (see page 31) The Toolbar Buttons (see page 31) The Navigation (Left) Pane (see page 32) The Content (Right) Pane (see page 33) Configuration Interface Navigation The window consists of a row of tool buttons above a window split into two parts: The Navigation pane The Content pane In addition, a status bar at the bottom of the window shows version information, and when the probe was last started. The Toolbar Buttons The configuration interface contains a row of toolbar buttons: The General Setup button allows you to configure the log level for the probe. The New Resource button allows you to add a new resource. The Message Pool Manager button allows you to add, remove or edit alarm messages. The Create New Template button allows you to create a new template. Chapter 6: vmware Probe Configuration Interface v6.2 31

32 The Navigation (Left) Pane The Navigation (Left) Pane The pane on the left is the navigation pane. It displays the monitored Resources and any Templates you have created. Resources Node You can create a new Resource by clicking the New Resource button, or by right-clicking the Resources node and selecting New Resource. The Resource is configured as a link to the vcenter or ESX server environment. The icon for each Resource node indicates the status of the resource: Inactive Marked for deletion Unable to connect New (not yet saved) Connected and inventory is ready to browse Loading inventory and not ready to browse Each Resource node contains the following sub-hierarchies: Auto Configurations The monitors under this node are used to automatically configure newly discovered devices. Drag-and-drop individual monitors or templates (which define a set of monitors) onto this node. Auto Monitors Lists the monitors that were created based on the Auto-Configuration entries and the inventory available on the Resource. All Monitors Lists all monitors for the Resource, including Auto Monitors and manually configured monitors. The vmware hierarchy Lists the VMs, vcenters, ESX servers, and data stores available in the VMware environment for monitoring. 32 vmware Guide

33 The Content (Right) Pane Templates Node Templates allow you to define reusable sets of monitors for the vcenter or ESX server resources. This node contains the following default templates: VM and Host Template UMP Metrics More information: Using Templates (see page 25) Navigation Pane Updates for vmware A right-click with the mouse pointer in the navigation pane over the hostname or IP address node opens a pop-up menu with menu items for managing the selected object or creating new objects of its type. Options typically include: New, Edit, Delete, Deactivate, and Refresh. Note: When available, the Refresh menu item retrieves updated values and refreshes the display. The Content (Right) Pane The content of the right pane depends on the selection in the navigation pane. If you select a Resource node in the navigation pane, the content pane lists the vcenter or ESX server environments. If you select a VM, vcenter, ESX server, or Datastore in the navigation pane, the content pane lists the available monitors. Active Monitors are check-marked. The following icons can appear there: Indicates that the monitor is active but not enabled to send alarms. The Enable Monitoring checkbox was not selected for this monitor. Black: Indicates that the monitor is NOT activated. The Action option is not set in the properties dialog for the monitor. Green: Indicates that the monitor is activated for monitoring and, if an alarm threshold is set, the threshold value defined in the properties dialog for the monitor is not exceeded. Gray: Indicates that the monitor is an inactive static monitor. Chapter 6: vmware Probe Configuration Interface v6.2 33

34 The Content (Right) Pane Other colors: Indicates that the monitor is activated for monitoring and the threshold value defined in the properties dialog for the monitor is exceeded. The color reflects the message token selected in the properties dialog for the monitor. This icon represents a monitor where no value has been measured. Note: Any monitor name in italics indicates that the monitor has been modified and you must apply the changes before the monitor results are updated. Content Pane Updates for vmware A right-click with the mouse pointer on objects in the content pane opens a pop-up menu with menu items for managing the selected object type (Edit, Delete, and Add to Template). Note: When available, the Refresh menu item fetches updated values and refreshes the display. 34 vmware Guide

35 Chapter 7: Best Practices for vmware Note: The best practices in this section apply only to users of the CA Unified Infrastructure Management Infrastructure Manager interface for configuring the vmware probe. The Release Notes for the vmware probe contain additional best practices that apply to users of any configuration interface. This section contains the following topics: Support for Instance UUIDs (see page 35) Prepending Origin to the QoS Source Field (see page 36) Support for Instance UUIDs For vcenter environments where VMs are completely cloned, including the VM's UUID, the probe now supports tracking the VMs via the vcenters instanceuuid. This duplicate UUID behavior typically manifests itself within vcenter setups that are being utilized by Lab Manager or vcloud. As for the VMware probe, you may see one or more of the following: VMs missing from the inventory, and/or Missing/incorrect data reported on VM attributes (e.g., a powered off VM is reported as powered on). An alarm notifying that a duplicate UUID has been detected To configure the probe to use the instanceuuid, do the following: 1. Update the probe to v5.01 or newer 2. Launch the Raw Configure tool for the probe 3. Navigate to the 'setup' section 4. Change the 'use_instance_uuid' setting to 'yes' IMPORTANT: The Raw Configure tool is similar to the Windows registry editor and has no error checking. Take care that any changes you make are valid before you continue. 5. Apply the configuration changes. Note: the instanceuuid setting applies to all resources monitored by a probe. Chapter 7: Best Practices for vmware 35

36 Prepending Origin to the QoS Source Field Prepending Origin to the QoS Source Field For multi-tenant environments where there are overlaps in the Virtual System inventory (both vcenter A & B have VMs details in common), prepend the origin to the QoS Source field. This changes the QoS identifying information from <QOS_ID> <Source> <Message> to: <QOS_ID> <Origin>::<Source> <Message> This way, the QoS data from each VMware monitoring probe running on a tenant-dedicated robot is identified using the source field. To enable this functionality, do the following: 1. Ensure the probe is running on a robot with a dedicated origin setting. 2. Launch the 'Raw Configure...' tool for the VMware probe. 3. Navigate to the 'setup' section 4. Change the 'multi_tenant_source' setting from 'no' to 'yes' IMPORTANT: The Raw Configure tool is similar to the Windows registry editor and has no error checking. Take care that any changes you make are valid before you continue. 5. Apply the changes 36 vmware Guide

37 Chapter 8: Metrics for vmware v6.2 for Infrastructure Manager The following table lists the metrics you can collect with the probe, using Infrastructure Manager. RESOURCE Alarm Integer A reported alarm for the resource (3=red RESOURCE Event Integer A reported event for the resource (3=erro RESOURCE VMwareApiAvailable Boolean Availability of the VMware Web Services RESOURCE VMwareApiResponseTime MilliSeconds Response time of the VMware Web Servi VM Alarm Integer A reported ala VM CpuReservation MHz Amount of CPU Reserved CPU reservation, th VM Event Integer A reported eve VM GuestHostName String Host name of t VM GuestIpAddress String Primary IP add VM GuestMemoryUsage MBytes VM GuestMemoryUsage (in % of Memory) Guest memory be between 0 while the virtu Guest memory memory. The n Machine. Valid VM GuestOperatingSystem String Guest operatin VM GuestState State Operation mod (shuttingdown VM HeartbeatStatus State The guest hear VM HostAsHashValue Integer Unique identif VM HostCPUUsage VM HostMemoryUsage MBytes Basic CPU perf is running. Memory consu while the virtu Chapter 8: Metrics for vmware v6.2 for Infrastructure Manager 37

38 Prepending Origin to the QoS Source Field VM HostMemoryUsage (in % of Memory) Host memory memory. This machine is run VM HostName String The name of th VM Memory MBytes Memory size in VM Memory Limit MBytes VM MemoryReservation MBytes The utilization This generally resources. Amount of me Reserved mem reservation, th VM NumCPU Count Number of virt VM OverallCpuUsage MHz Basic CPU perf VM Physical Cores Used Count Total count of VM PowerState State The current po (poweredon)] VM SnapshotCount Count The number o VM SnapshotSize GB The total size o VM StorageProvisioned GB Provisioned st VM StorageUsage GB Committed sp VM Status State The overall ala VM ToolsRunningStatus State VM ToolsVersionStatus State Current status (guesttoolsno Current versio (guesttoolsun (guesttoolsne VM VMName String The name of th VM limit MHz The utilization This generally resources. VM_CPU CPU Idle (% of available) age of VM_CPU CPU Latency VM_CPU CPU Max Limited (% of available) of tim physical CPU(s of tim setting 38 vmware Guide

39 Prepending Origin to the QoS Source Field VM_CPU CPU Ready (% of available) age of run on the phy VM_CPU CPU Run (% of available) age of VM_CPU CPU Swap Wait (% of available) of CPU VM_CPU CPU System (% of available) of tim VM_CPU CPU Usage (Average/Rate) CPU usage as a VM_CPU CPU Usage in MHz (Average) Megahertz CPU usage in m VM_CPU CPU Used (% of available) Total CPU usag VM_CPU CPU Wait (% of available) age of VM_CPU_AGGREGATE CPU Idle (% of available) age of VM_CPU_AGGREGATE CPU Latency VM_CPU_AGGREGATE CPU Limited by Max (% of available) VM_CPU_AGGREGATE CPU Ready (% of available) of tim physical CPU(s of tim setting. age of run on the phy VM_CPU_AGGREGATE CPU Run (% of available) age of VM_CPU_AGGREGATE CPU Swap Wait (% of available) of CPU VM_CPU_AGGREGATE CPU System (% of available) of tim VM_CPU_AGGREGATE CPU Usage (Average/Rate) CPU usage as a VM_CPU_AGGREGATE CPU Usage in MHz (Average) Megahertz CPU usage in m VM_CPU_AGGREGATE CPU Used (% of available) Total CPU usag VM_CPU_AGGREGATE CPU Wait (% of available) age of VM_RES_CPU CPU active average over 1 min (% of mhz*numcpucores) The average o intervals VM_RES_CPU CPU active average over 15 min (% of mhz*numcpucores) The average o intervals VM_RES_CPU CPU active average over 5 min (% of mhz*numcpucores) The average o intervals VM_RES_CPU CPU active peak over 1 min (% of mhz*numcpucores) The peak of th intervals Chapter 8: Metrics for vmware v6.2 for Infrastructure Manager 39

40 Prepending Origin to the QoS Source Field VM_RES_CPU CPU active peak over 15 min (% of mhz*numcpucores) The peak of th intervals VM_RES_CPU CPU active peak over 5 min (% of mhz*numcpucores) The peak of th intervals VM_RES_CPU CPU refused average over 1 min (% of mhz*numcpucores) Amount of CPU intervals VM_RES_CPU CPU refused average over 15 min (% of mhz*numcpucores) Amount of CPU intervals VM_RES_CPU CPU refused average over 5 min (% of mhz*numcpucores) Amount of CPU intervals VM_RES_CPU CPU running average over 1 min (% of mhz*numcpucores) The average o minute interva VM_RES_CPU CPU running average over 15 min (% of mhz*numcpucores) The average o minute interva VM_RES_CPU VM_RES_CPU VM_RES_CPU VM_RES_CPU CPU running average over 5 min (% of mhz*numcpucores) CPU running peak over 1 min (% of mhz*numcpucores) CPU running peak over 15 min (% of mhz*numcpucores) CPU running peak over 5 min (% of mhz*numcpucores) The average o minute interva The peak of th minute interva The peak of th minute interva The peak of th minute interva VM_RES_CPU CPU sample count Count The number o VM_RES_CPU CPU sample period Milliseconds CPU sample pe VM_MEMORY Memory Active (% of Memory) Amount of me touched memo VM_MEMORY Memory Active Write Kilobytes Amount of me VM_MEMORY VM_MEMORY Memory Balloon (% of Memory) Memory Balloon Target (% of Memory) of me which is install Target value se VM_MEMORY Memory Compressed Kilobytes Amount of me VM_MEMORY Memory Compression Rate KBytes / Second Rate of memo VM_MEMORY Memory Consumed (% of Memory) of me 40 vmware Guide

41 Prepending Origin to the QoS Source Field VM_MEMORY Memory Decompression Rate KBytes / Second Rate of memo VM_MEMORY Memory Entitlement Kilobytes VM_MEMORY VM_MEMORY Memory Granted (% of Memory) Memory Host Cache Used for Swapping Kilobytes Amount of hos scheduler of ma a host Space used for VM_MEMORY Memory Latency age of VM_MEMORY Memory Overhead (% of Memory) of me VM_MEMORY Memory Reserved Overhead Memory (perc VM_MEMORY Memory Shared (% of Memory) of gue virtual machin VM_MEMORY Memory Swap In Kilobytes Amount of me VM_MEMORY Memory Swap In Rate KBytes / Second Rate at which VM_MEMORY Memory Swap In Rate from Host Cache KBytes / Second Rate at which VM_MEMORY Memory Swap Out Kilobytes Amount of me VM_MEMORY Memory Swap Out Rate KBytes / Second VM_MEMORY VM_MEMORY VM_MEMORY Memory Swap Out Rate from Host Cache Memory Swap Target (% of Memory) Memory Swapped (% of Memory) KBytes / Second Rate at which interval Rate at which Target percent Current percen by the VMkern VM_MEMORY Memory Usage Memory usage VM_MEMORY Memory Zero (% of Memory) of me VM_MEMORY Memory Zip Saved Kilobytes Memory (KB) s VM_MEMORY Memory Zipped KBytes / Second Memory (KB) z VM_SYSTEM Heartbeats Count Number of hea VM_SYSTEM OS Uptime Seconds Total time elap VM_SYSTEM Total time Seconds Total time elap Chapter 8: Metrics for vmware v6.2 for Infrastructure Manager 41

42 Prepending Origin to the QoS Source Field VM_NIC VM_NIC Network Broadcast Packets Received Network Broadcast Packets Transmitted Packets Packets Number of bro Number of bro VM_NIC Network Data Receive Rate KBytes / Second Average rate a VM_NIC Network Data Transmit Rate KBytes / Second Average rate a VM_NIC VM_NIC Network Error Packets Received Network Error Packets Transmitted Packets Packets Number of err Number of err VM_NIC Network Packet Receive Rate Packets / Second Number of pac VM_NIC Network Packet Transmit Rate Packets / Second Number of pac VM_NIC Network Packets Received Packets / Second VM_NIC Network Packets Transmitted Packets / Second VM_NIC VM_NIC Network Receive Packets Dropped Network Transmit Packets Dropped Packets Packets (Deprecated) P same time. (Deprecated) P same time. Number of rec Number of tra VM_NIC Network usage KBytes / Second Network utiliza VM_NIC_AGGREGATE VM_NIC_AGGREGATE Network Broadcast Packets Received Network Broadcast Packets Transmitted Packets Packets Number of bro Number of bro VM_NIC_AGGREGATE Network Data Receive Rate KBytes / Second Average rate a VM_NIC_AGGREGATE Network Data Transmit Rate KBytes / Second Average rate a VM_NIC_AGGREGATE VM_NIC_AGGREGATE Network Error Packets Received Network Error Packets Transmitted Packets Packets Number of err Number of err VM_NIC_AGGREGATE Network Packet Receive Rate Packets / Second Number of pac VM_NIC_AGGREGATE Network Packet Transmit Rate Packets / Second Number of pac 42 vmware Guide