Nimsoft Monitor vcloud Guide - CAdocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/vclo… · ·...

vcloud Guide v2.0

Nimsoft® Monitor™

Legal Notices

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 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(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 the Nimsoft Monitor solution is documented in Nimsoft Monitor Third-Party Licenses and Terms of Use (http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html).

http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html

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 http://ca.com/support, 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 Nimsoft product documentation to [email protected].

To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://www.ca.com/docs

Contents 5

Contents

Chapter 1: vcloud 2.0 7

vcloud Overview ........................................................................................................................................................... 7

Chapter 2: vCloud Probe Deployment 9

Prerequisites ................................................................................................................................................................ 9

Software Requirements ............................................................................................................................................... 9

Deployment Using Infrastructure Manager ................................................................................................................. 9

Deployment Using Nimsoft Distribution Application ................................................................................................. 10

Probe Configuration Interface Installation ................................................................................................................. 11

Chapter 3: Configuring the vCloud Probe 13

Monitoring Capabilities .............................................................................................................................................. 13

Templates ................................................................................................................................................................... 14

The vCloud Configuration Interface ........................................................................................................................... 14

Configuration Interface Navigation ..................................................................................................................... 14

vcloud Configuration .................................................................................................................................................. 17

General Setup ..................................................................................................................................................... 18

Creating or Editing a Resource ............................................................................................................................ 18

Message Pool Manager ....................................................................................................................................... 19

Create New Template ......................................................................................................................................... 21

Chapter 4: Adding Monitors 23

Manually Selecting Monitors to be Measured ........................................................................................................... 23

Enabling the Monitors for QoS and Alarming ............................................................................................................ 23

Editing Monitor Properties ......................................................................................................................................... 24

Using Templates ......................................................................................................................................................... 25

Creating or Editing a Template ........................................................................................................................... 26

Adding Monitors to a Template .......................................................................................................................... 27

Editing Monitors Within a Template ................................................................................................................... 27

Applying a Template ........................................................................................................................................... 27

Chapter 5: Using Automatic Configurations 29

Adding a Monitor to the Auto Configurations Node ........................................................................................... 29

Adding a Template to the Auto Configurations Node ......................................................................................... 30

Exploring the Contents of the Auto Configuration Node .................................................................................... 30

6 vcloud Guide

Checking the Auto Monitors Node ...................................................................................................................... 30

vcloud Metrics ............................................................................................................................................................ 31

vcloud Alert Threshold Metrics ........................................................................................................................... 33

Chapter 6: Troubleshooting 35

Chapter 1: vcloud 2.0 7

Chapter 1: vcloud 2.0

This document describes how to configure the CA Nimsoft vcloud probe version 2.0.

This section contains the following topics:

vcloud Overview (see page 7) Documentation Changes (see page 8)

vcloud Overview

Business based on Virtualization Technology depends on a high degree of quality and availability.

The Nimsoft vcloud monitoring probe automates all common monitoring and data collection tasks, and lets you focus on problems as they arise.

The vcloud probe collects and stores data on an organization, its components such as vApps, and the resources it relies upon such as provider vDCs. Within a vCloud environment you can monitor multiple tenants for which you have access permissions.

You can define alarms to be raised and propagated to the Alarm Console when specified thresholds are breached.

vcloud Overview

8 vcloud Guide

Documentation Changes

This table describes the version history for the vcloud document.

Version Date What's New?

2.0 March 2014 Updated to support vCloud v5.5.

2.0 March 2013 Updated to support vCenter 5.1 with continued support for vCenter 1.5. Support for vCenter 1.0 has been discontinued.

1.1 May 2012 Added default templates, ability to update log level and ability to create alarm messages.

1.0 December 2011 Initial Release

Note: Serial releases within a version do not affect the documentation for the series. For example, v1.0 documentation would apply to release 1.01.

Related Documentation

Documentation for other versions of the vcloud probe

The Release Notes for the vcloud probe

Monitor Metrics Reference Information for CA Nimsoft Probes (http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm)

http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/vcloud/ReleaseNotes/index.htm

http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm


Chapter 2: vCloud Probe Deployment

Successful distribution of the vcloud probe package relies on the Java package installed with the Nimsoft Management Server.

The vcloud probe is supported on Nimsoft robots v5.32 and above.

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 Nimsoft Distribution application.


Prerequisites (see page 9) Software Requirements (see page 9) Deployment Using Infrastructure Manager (see page 9) Deployment Using Nimsoft Distribution Application (see page 10) Probe Configuration Interface Installation (see page 11)

Prerequisites

The vcloud probe requires account access to the following applications:

■ Administrator access to the vCloud environment.

Software Requirements

The vcloud probe requires the following Nimsoft Monitor software environment:

■ VMware vCloud Director 1.5x or 5.5x is supported

■ Nimsoft Monitor Server 5.1.1 or later

■ Nimsoft robot version 5.32 or later

■ Java Virtual Machine version 1.6 or later

■ Infrastructure Manager v4.02 or later

■ .NET v3.5 on the hardware running the Infrastructure Manager application

Deployment Using Infrastructure Manager

There are two methods within Infrastructure Manager to distribute an archive package: drag and drop or right-click on a package name.

Deployment Using Nimsoft Distribution Application

10 vcloud Guide

Note: The package must have a green box icon before you can distribute it to a machine. If the box icon is not green, you must download the package to the archive and have a valid license before distributing to a machine.

Drag and Drop Method:

1. Select a package name in the archive.

2. Drag and drop the package name to the domain/hub/robot.

A View Distribution Progress dialog box appears with detailed information about the distribution.

Note: You can minimize this dialog box and continue working in Infrastructure Manager without interfering with the distribution.

3. Click the Close Dialog button after distribution is finished.

Right-click Method:

1. Select a package name in the archive.

2. Right-click and select Distribute from the menu.

A Distribute dialog box appears.

3. Select the domain/hub/robot where you want to distribute the package, and click the Add button.

The domain/hub/robot name appears in the right column.

4. Click OK.

A View Distribution Progress dialog box appears with detailed information about the distribution.

Note: You can minimize this dialog box and continue working in Infrastructure Manager without interfering with the distribution.

5. Click the Close Dialog button after distribution is finished.

Deployment Using Nimsoft Distribution Application

Packages can be deployed using the standalone Nimsoft Distribution application. This distribution method allows for the ability to create distribution tasks. A task is a profile containing information about what packages to distribute and the set of destination robots. See the Infrastructure Manager documentation for more information.

Probe Configuration Interface Installation


Probe Configuration Interface Installation

The vcloud probe configuration interface is automatically downloaded and locally installed by the Nimsoft Infrastructure Manager as part of launching the interface.


Chapter 3: Configuring the vCloud Probe

With the vcloud probe installed, you must next define what to monitor. At a high level, there are four steps:

1. Connect to the vcloud environment.

2. Enable the appropriate organizations within your vcloud environment.

3. Add monitors (checkpoints). See the description in the section Adding Monitors (Checkpoints).

4. Configure the properties for the checkpoints, in which you define QoS data, and define alarms to be sent if specified thresholds are breached.

Note: You must always click the Apply button to activate any configuration changes.


Monitoring Capabilities (see page 13) Templates (see page 14) The vCloud Configuration Interface (see page 14) vcloud Configuration (see page 17)

Monitoring Capabilities

The following component entities may be monitored:

■ Organizations

■ vApps and VMs within Organizations

■ Provider vDCs (virtual data centers)

Note: Only Provider vDCs associated with an enabled/managed organization can be monitored.

Templates

14 vcloud Guide

Templates

Templates let you define reusable sets of monitors to apply to various Orgs, vApps, VMs and Provider vDCs. After you create a template and define a set of checkpoints belonging to that template, you can either:

■ Drag and drop the template into the vCloud resource hierarchy where you want to monitor the checkpoints defined for the template.

■ Drag and drop the template into the Auto-Configuration to add the template contents to the list of auto-configuration monitors.

See the section Using Templates for details. The vCloud probe contains the following default templates:

■ Provider VDCs

■ vApps

■ Org VDC

■ VMs

The vCloud Configuration Interface

The vcloud probe collects and stores data and information from the monitored components within a vcloud environment.

Double-click the line representing the vcloud probe in the Infrastructure Manager to launch the vcloud probe configuration interface. It initially appears with the Resources hierarchy empty.

Configuration Interface Navigation

The configuration interface 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, date and time when the probe was last started.



The Tool Buttons

The configuration interface contains a row of tool buttons:

The General Setup button allows you to set the log level.

The New Resource button allows you add a new resource.

The Message Pool Manager button allows you to add, edit or remove messages from the message pool.

The Create New Template button allows you to create a new template.

The Navigation (left-side) Pane

The division on the left side of the window is the navigation pane. It displays the monitored Resources.

You can create a new Resource by clicking the New Resource tool button ( ), or by right-clicking Resources and selecting New Resource.

■ Resources

The Resource is configured as a link to the vCloud environment. Note the following icons for the Resource node:

Resource is inactive

Resource is marked for deletion

Resource is unable to connect

New resource (not yet saved)

Resource is connected and inventory is ready to browse

Resource is loading inventory. Not ready to browse

The Resources node contains the following sub-hierarchies:

■ The Auto Configurations node

One or more checkpoints (or templates) can be added to this node, using drag and drop. These checkpoints can to be used for auto configuring unmonitored devices. See the section Using Automatic Configurations for further information.


16 vcloud Guide

■ The Auto Monitors node

This is a list of the monitors that have been created based on the Auto-Configuration entries and the inventory available on the Resource.

See the section Using Automatic Configurations for further information.

■ The All Monitors node

This node contains the complete list of Monitors for the Resource. This includes Auto Monitors and manually configured Monitors. See the section Using Automatic Configurations for further information.

■ The vCloud hierarchy

This is a list of the Organizations and Provider vDCs available in the vCloud environment for monitoring.

■ Templates

Templates let you define reusable sets of monitors for the various Org vDCs, vApps, VMs and Provider vDCs. This node does not contain any templates initially.

■ To add a template, click the Create New Template button ( ).

■ To edit or delete a template, click on the template name to select it, then right-click and select the action you want.

The properties for a template are Name and Description. See the section Using Templates for details.

Navigation Pane Updates

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-side) pane

The content of the right pane depends on the current selection in the navigation pane.

If you select a Resources node in the navigation pane, the content pane lists the vCloud environments.

vcloud Configuration


If you select an organization or provider vDC 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.

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

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.


This section contains specific configuration information for the vcloud probe.


18 vcloud Guide

General Setup

Click the General Setup button to set the level of details written to the log file for the vcloud 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.

Creating or Editing a Resource

There are two ways to create a Resource:

■ Click the toolbar button for New Resource ( ).

■ Right click Resource in the navigation pane, and choose New Resource from the menu.

To edit the properties for an existing Resource, right-click on the resource in the navigation pane, and chose Edit from the context menu.

Either method brings up the Resource dialog, which contains the following fields:

Hostname or IP address

The hostname or IP-address to the vCloud environment to monitor.

Port

This is the https port for the vCloud Director System. The default is 443, which ensures a secure connection (all communication will be encrypted).

Active

Use this option to activate or deactivate the connection to the Resource.

Username

A valid administrator username to be used by the probe to log on the vCloud environment.

Password

A valid password to be used by the probe to log on the vCloud environment.

Alarm Message

Select the alarm to be sent if the Resource does not respond.



Check interval

The check interval defines how often the probe checks the values of the monitors. Intervals of 10 minutes or greater should be used.

Note: A collection cycle scans the entire vCloud environment. This check interval should be set long enough to not overload the server. An alarm is sent if the polling interval is too short.

Organizations

Select the organizations within this resource you would like to monitor.

Test button

Click the Test button to verify the connection to the host. This test populates or updates the Org list for the vCloud environment.

Note: When you click the Test button you should receive a dialog box stating one of the following:

■ <hostname> is responding.

■ An unexpected exception occurred when testing the resource. Please retry your test.

Message Pool Manager

You can add, remove, or modify alarm messages. These are the messages sent when a QoS threshold has been breached.

Add a New Alarm Message

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

The name of the message.

Token

The type of alarm, either "monitor_error" or "resource_error".


20 vcloud Guide

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 RHEV Manager system.

4. Click OK to save the new message.

Delete an Alarm Message

To delete 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.

Edit an Alarm Message

To edit an alarm message:



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.


Chapter 4: Adding Monitors

There are different ways to add monitors to a vCloud environment:

■ Manually select the monitors

■ Use Templates

■ Use Auto Configurations

Example:

The Auto Configuration feature, when configured, creates Auto Monitor(s) for the vCloud environment and automatically starts monitoring the environment.


Manually Selecting Monitors to be Measured (see page 23) Enabling the Monitors for QoS and Alarming (see page 23) Editing Monitor Properties (see page 24) Using Templates (see page 25) Using Automatic Configurations (see page 29) vcloud Metrics (see page 31)

Manually Selecting Monitors to be Measured

To manually select monitors, select a Resource node in the navigation pane. This lists the monitors available for that node in the right pane. Use the check-boxes to enable the monitors.

Note: Using the check-boxes to enable a monitor only enables the QoS metrics. You must edit the monitor to enable alarming and set thresholds. See Enabling the Monitors for QoS and Alarming.

Select the All Monitors node to see a list of all monitors currently being measured. You can select or deselect monitors here as well.

Enabling the Monitors for QoS and Alarming

To enable the probe to send QoS data and/or send alarms on threshold breaches, modify the properties for each of the monitors. Double-click a monitor (or right-click and select Edit) to launch the monitor’s properties dialog. See the Editing Monitor Properties section for further information about editing a monitor.

Editing Monitor Properties

24 vcloud Guide

For a list of the QoS metrics, see the QoS Metrics section.

Editing Monitor Properties

To edit the properties for a monitor, double-click the monitor in the list in the window (or right-click and select the Edit menu-item).When activating a monitor for the first time using the checkbox, a static monitor is created with QoS enabled. You must edit the monitor to enable alarms.

Note: Monitor names are pre-assigned and cannot be renamed.

The properties for monitors are as follows:

Name

This is a read-only field containing the name of the monitor. The name is inserted into this field when the monitor is retrieved from the vCloud environment.

Key

This is a read-only field, describing the monitor key.

Description

This is a read-only field, describing the monitor. This description is inserted into this field when the monitor is fetched from the vCloud environment.

Value Definition

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, meaning that the most current value measured will be used.

■ The delta value (current –previous). This means that the delta value calculated from the current and the previous measured sample will be used.

■ Delta per second. This means that 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 ... This is the average value of the number of samples designated. When you select this value option the number of samples box becomes active and editable.

Active

This activates the monitoring of the resource.

Using Templates


Enable Alarming

Selecting this option activates the alarming. You can define both a high and a low threshold.

Initially the high threshold is set to a default value, or 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.

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 greater than or equal to 90.

= 90 means the monitor is in alarm condition if the measured value is exactly 90.

Threshold

The alarm threshold value. An alarm message is sent when this threshold is exceeded.

Unit

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.

Publish Quality of Service

Select this option if you want QoS messages to be issued on the monitor.

QoS Name

This field is read-only and contains the name of the QoS metric.

Using Templates

Templates let you define reusable sets of monitors to be measured on vCloud environments. They provide an easy way to accomplish consistent monitoring of your vCloud environment.

Using Templates

26 vcloud Guide

The Templates node in the navigation pane contains the following templates:

■ Provider VDCs

■ vApps

■ Org VDC

■ VMs

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, the monitors are applied to all Orgs, vApps, VMs and Provider vDCs 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. Note that 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 section for details on Auto Configuration.

Creating or Editing a 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.

To edit an existing template, select one of the templates defined under the Templates node in the navigation pane, right-click the template name, and select Edit from the menu.

Using Templates


Adding Monitors to a Template

To add a monitor (checkpoint) to a template, you can either:

■ Drag it from the content pane and drop it on the template in the navigation pane

■ Right-click and select Add to Template.

You can edit the properties for monitors in the template as described in the section Creating or Editing a Template.

Editing Monitors Within a Template

To edit monitors within a template:

1. Select the template in the navigation pane, then double-click on the monitor name.

The Edit Monitor Properties screen appears.

2. Change the options as needed, then click OK.

Applying a Template

Drag the template to the Auto Configuration node or the Resource (Orgs, vApps, VMs or Provider vDCs) 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 object and all its subordinate objects where the monitor exists. A message will report how many monitors were applied.


Chapter 5: Using Automatic Configurations

Auto Configuration is a powerful way to automatically add monitors to be measured. When new vCloud environments are detected, "Auto Monitors" are created for new devices that are not currently monitored.

Example:

When a new vCloud environment is created, the Auto Configuration feature, if used, creates Auto Monitor(s) for the new vCloud environment and automatically starts monitoring it.

The Auto Configuration feature consists of two sub-nodes located under the Resource node in the navigation pane:

Auto Configurations node

You can add the contents of one or more templates or individual checkpoints to this node, using drag and drop. You must click the Apply button for the changes to take affect. The probe will be restarted and your changes activated. The probe then searches through the vCloud environment. Auto Monitors representing the monitor(s) or template(s) under the Auto Configuration node are created (and listed under the Auto Monitor node, see below) for devices that are not monitored at the time they are discovered.

Auto Monitors node

This node lists Auto Monitors, created for previously unmonitored devices, based on the contents added to the Auto Configuration node. The Auto Monitors are only created for devices that are not monitored at the time the device was discovered.

Adding a Monitor to the Auto Configurations Node

You can add a single monitor (checkpoint) to the Auto Configurations node as follows:

1. To list available monitors, select the Resource node in the navigation pane and navigate to the point of interest.

2. Select an object to list the available 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. The probe will be restarted and your configuration changes will be activated.

Using Templates

30 vcloud Guide

Adding a Template to the Auto Configurations Node

You can add a template 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 was successfully added.

See the Using Templates section to learn more about templates.

Exploring the Contents of the Auto Configuration Node

To verify that the monitors and /or templates were successfully added, click the Auto Configurations node in the navigation pane.

■ To edit the properties for the monitor, right-click in the list and choose Edit from the menu. See the section To Edit Monitor Properties for detailed information.

■ To delete the monitor from the list, right-click in the list and choose Delete from the menu.

Note: You must click the Apply button for the changes to take affect. The probe will be restarted and your configuration changes will be activated.

Checking the Auto Monitors Node

Note: When the template contents and/or individual monitors have been added to the Auto Configurations node, you must click the Apply button. The probe will be restarted and your configuration changes will be activated.

When you restart the probe, it searches through the Resources for vCloud environments. For each one that is currently not monitored, an Auto Monitor is created for each of the templates and/or monitors listed under the Auto Configurations node.

Example:

Suppose you have three monitors under the Auto Configurations node; one Provider vDC related monitor and two VM related monitors. This will result in one Auto Monitor created for each Provider vDC found and two Auto Monitors for each VM found, provided that these devices are currently not monitored.

vcloud Metrics


All defined Auto Monitors are listed under the Auto Monitors node.

vcloud Metrics

This section contains the QoS metrics for the vcloud probe.

Resource Entity Metric Name Unit Description

ADMIN_VDC

Resource Guaranteed CPU Percent The Cpu guaranteed to the vDC

Resource Guaranteed Memory Percent The Memory guaranteed to the vDC

VCpuInMhz MHz Maximum CPU in MHz that a single virtual CPU can consume in the Org vDC

vDC CPU Allocated MHz The CPU allocated for the vDC

vDC CPU Limit MHz The CPU limit for the vDC

vDC CPU Overhead MHz The amount of cpu overhead for the vDC

vDC CPU Overhead/Limit Percent The amount of cpu overhead for the vDC

vDC CPU Used MHz The amount of CPU used by the vDC

vDC CPU Used/Limit Percent The amount of CPU used by the vDC

vDC Is Enabled Boolean Indicates whether the vDC is enabled or not.

vDC Memory Allocated MB The memory allocated for the vDC

vDC Memory Limit MB The memory limit for the vDC

vDC Memory Overhead MB The amount of memory overhead for the vDC

vDC Memory Overhead/Limit Percent The amount of memory overhead for the vDC

vDC Memory Used MB The amount of memory used by the vDC

vDC Memory Used/Limit Percent The amount of memory used by the vDC

vDC NIC Quota Integer NIC Quota for the vDC.

vDC Network Quota Integer Network Quota for the vDC.

vDC Status State The status for the vDC [-1 (CREATION_FAILED), 0 (NOT_READY), 1 (READY)]

vDC Storage Allocated MB The storage allocated for the vDC

vDC Storage Limit MB The storage limit for the vDC

vcloud Metrics

32 vcloud Guide


vDC Storage Overhead MB The amount of storage overhead for the vDC

vDC Storage Overhead/Limit Percent The amount of storage overhead for the vDC

vDC Storage Used MB The amount of storage used by the vDC

vDC Storage Used/Limit Percent The amount of storage used by the vDC

vDC VM Quota Integer VM Quota for the vDC.

VM

VM CPU Count Integer The VM's virtual CPU count

VM Disk Count Integer The VM's virtual Disk count

VM Disks size MB The VM's total virtual Disk size

VM Memory Size MB The VM's Virtual Memory size

VM Status State VM Status [-1 (CREATION_FAILED), 0 (UNRESOLVED), 1 (RESOLVED), 2 (DEPLOYED), 3 (SUSPENDED), 4 (POWERED_ON), 5 (WAITING_FOR_USER_INPUT), 6 (UNKNOWN), 7 (UNRECOGNIZED_STATE), 8 (POWERED_OFF), 9 (INCONSISTENT_STATE)]

VM is Deployed Boolean Indicates if the VM is deployed

VAPP

vApp Deployment Lease Expiration Days Indicates vApp's remaining deployment lease in days

vApp Status State vApp Status [-1 (CREATION_FAILED), 0 (UNRESOLVED), 1 (RESOLVED), 2 (DEPLOYED), 3 (SUSPENDED), 4 (POWERED_ON), 5 (WAITING_FOR_USER_INPUT), 6 (UNKNOWN), 7 (UNRECOGNIZED_STATE), 8 (POWERED_OFF), 9 (INCONSISTENT_STATE), 10 (ALL_CHILD_STATUSES_ARE_NOT_THE_SAME)]

vApp Storage Lease Expiration Days Indicates the vApp's remaining storage lease in days

vApp is Deployed Boolean Indicates if the vApp is deployed

PROV_VDC

vDC CPU Allocated MHz The amount of CPU allocated to the vDC

vDC CPU Allocated/Capacity Percent The amount of CPU allocated to the vDC

vcloud Metrics



vDC CPU Capacity MHz The CPU capacity of the vDC

vDC CPU Overhead MHz The amount of CPU overhead for the vDC

vDC CPU Overhead/Capacity Percent The amount of CPU overhead for the vDC

vDC CPU Used MHz The amount of CPU used by the vDC

vDC CPU Used/Capacity Percent The amount of CPU used by the vDC

vDC Memory Allocated MB The amount of memory allocated to the vDC

vDC Memory Allocated/Capacity Percent The amount of memory allocated to the vDC

vDC Memory Capacity MB The memory capacity of the vDC

vDC Memory Overhead MB The amount of memory overhead for the vDC

vDC Memory Overhead/Capacity Percent The amount of memory overhead for the vDC

vDC Memory Used MB The amount of memory used by the vDC

vDC Memory Used/Capacity Percent The amount of memory used by the vDC

vDC Storage Allocated MB The amount of storage allocated to the vDC

vDC Storage Allocated/Capacity Percent The amount of storage allocated to the vDC

vDC Storage Capacity MB The storage capacity of the vDC

vDC Storage Overhead MB The amount of storage overhead for the vDC

vDC Storage Overhead/Capacity Percent The amount of storage overhead for the vDC

vDC Storage Used MB The amount of storage used by the vDC

vDC Storage Used/Capacity Percent The amount of storage used by the vDC

vcloud Alert Threshold Metrics

The vcloud probe will not have default QoS alert threshold values set. You must set the threshold values when you configure the probe.

Chapter 6: Troubleshooting 35

Chapter 6: Troubleshooting

If the vcloud configuration GUI does not open then .NET v3.5 may not be installed on the machine running Infrastructure Manager. Check the Windows/Microsoft.NET/Framework directory for the .NET versions.

Date post:	26-Apr-2018
Category:	Documents
Upload:	voduong
View:	222 times
Download:	0 times

Nimsoft Monitor vcloud Guide - CAdocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/vclo… · ·...

Documents