vmware MCS Profile Type Configuration

This article describes how a monitoring administrator uses Monitoring Configuration Service (MCS) to create configuration profiles for groups of devices that are monitored by the vmware probe.
uimpga-ga
vmware_mcs
This article describes how a monitoring administrator uses Monitoring Configuration Service (MCS) to create configuration profiles for groups of devices that are monitored by the vmware probe.
 
Warning! 
You cannot configure a probe through the probe configuration GUI after you apply the MCS profile type to an instance of the probe. We recommend that you test your configuration before applying the configuration to many systems. To delete the configuration that is applied by MCS, you must delete the profile in MCS and then manually delete the probe. When you delete a profile, a lock icon might appear during the deletion process. Do not delete the probe until the profile is completely removed. Once the MCS configuration is deleted, you can manually redeploy the probe and configure monitoring through the probe configuration GUI.
 
Contents
 
 
 
Prerequisites
 
Verify the following information before you create a monitoring configuration profile:
  • Verify that your CA UIM version is at least version 8.5.1 - required by the MCS profile types.
  • Verify that your archive contains an vmware probe that is at least version 7.11 or later.
  • Verify that you meet the minimum hardware and software requirements before you deploy a monitoring configuration profile.
  • Verify that you have a valid license for the probe.
For more information, see vmware (VMware Monitoring) Release Notes.
Upgrade Old MCS Profiles to Enhanced Profiles
To use the enhanced profiles, use the following software environment:
  • CA Unified Infrastructure Management version 9.0.2
  • Monitoring Configuration Service (MCS) version 9.0.2 - HF5 (or later): mon_config_service-9.0.2-HF5
  • Metrics plug-in version 7.96 (or later)
  • Robot version 7.96 (or later)
  • Ensure that VMware probe (version 7.11 or later) is present in your Archive. Deploy the probe using UMP.
    • install vmware_mcs_templates-7.1.1 to the primary hub
    • (optional) Verify the current template version in the UIM database by executing the following query: select probe_template_pkg_version from SSRV2ProbeTemplatesPackage where probe_name = 'vmware'
    • Activate the packages: Navigate to Administration Console, mon_config_service, View Probe Utility in New Window, activate_probe_templates_package and define the following values:
      • template_package_version = 7.11.1808140506 
      • probe_name = vmware
    • select the green arrow to implement the settings
    • Verify that in USM the profile is listing the template version 7.1.1
    • Select the option Enhance this profile to use centralized alarm configuration (any changes will be lost) and then click Save.
      The enhanced profile appears in the list and the legacy profile is disabled.
Enhanced Profiles in MCS
This release of CA UIM includes a new type of Monitoring Configuration Service (MCS) profile, called an enhanced profile. Enhanced profiles enable you to configure metrics, baselines, alarm thresholds, alarms - including Time Over Threshold alarms - and custom alarm and close alarm messages, all within a single MCS profile.
You can convert your existing MCS profiles to enhanced profiles. We recommend that you first migrate existing profiles to the latest available version and then convert them to enhanced profiles.
(CA UIM 9.0.2) Create vmware Group Configuration Profiles
 
Follow these steps:
 
  1. In Unified Service Manager, expand a USM group and select a device OR click a USM group.
    The USM group can be one of the predefined USM groups, for example, the Unix and Windows groups, or a group that you created with at least one device.
  2. Select the 
    Monitoring
     tab.
    The templates that apply to the selected USM group appear in the middle column.
    Example
    : The following figure shows an example of the available monitoring options when you select a group.
      Group_profile.jpg  
  3. Scroll down the list to view all the available templates.
  4. Select any template that you want to apply to your USM group.
    Create and save group profile using the selected template as needed. For more information about the profiles, see VMware Profile Types and Default Settings. For more information about how to configure the enhanced alarm thresholds for vmware 7.x, see Configuring Alarm Thresholds in MCS.
  5. (Optional) Return to any of the template to modify the profile and configure any additional metrics and alarms that you want to apply to the group.
  6. Save any profile changes.
  7. View the 
    Profile Status
     information to verify that the configuration profile was successfully deployed to the target group. Profile status information appears at the bottom of the profile configuration page.
Delete Profiles
Delete the enhanced profiles first to unlock the legacy profiles for deletion.
(CA UIM 8.5.1) Prerequisites
Verify the following information before you create a monitoring configuration profile:
  1. Verify that your CA UIM version is at least version 8.5.1 - required by the MCS profile types.
  2. Verify that your archive contains an vmware probe that is at least version 6.81.
  3. Complete any probe-specific prerequisites.
  4. Verify that you meet the minimum hardware and software requirements before you deploy a monitoring configuration profile.
  5. Verify that you have a valid license for the probe.
     Do not install the template vmware_mcs_templates-7.1.1 or higher version on an 8.51 installation. The template vmware_mcs_templates-7.1.1 is the only version of the vmware templates packages that allows for migration of legacy templates to enhanced templates.
For more information, see vmware (VMware Monitoring) Release Notes.
(CA UIM 8.5.1) Create vmware Configuration Profiles
 
Use the vmware profile types to create configuration profiles. You can configure all instances of the vmware probe with configuration profiles. The quality of service metrics (QoS) that the probe can publish appear in each profile.
 We recommend that you do not activate any profiles until you complete your monitoring configuration. The probe restarts every time you activate a profile.
 
Follow these steps:
 
  1. In Unified Service Manager, expand a USM group and select a device OR click a USM group.
    The USM group can be one of the predefined USM groups (for example, the Unix and Windows groups) in a test environment or a test group you created that has one device.
  2. Select the Monitoring tab.
    The profile types that apply to the selected device or USM group appear in the middle column. If you select a device and profile types do not appear in the middle column of the Monitoring tab, deploy a robot to the device.
    The following figure shows an example of the available monitoring options when you select a device.
    Example Setup VMware profile type for a device
    The following figure shows an example of the available monitoring options when you select a USM group.
    Example Setup VMware profile type for a group  
  3. Hover over the 
    Setup VMware
     profile type name, and then click '
    +
    ' to create a profile.
     If you see a dialog with a prompt to install the probe, verify that the probe is in the archive and select 
    Yes
    .
  4. Complete and save the required settings. The resource profile type node is added under the Setup VMware profile. Expand the list to view the node.
  5. Hover over the 
    VMware Resource node
    , and then click '
    +
    ' to create a resource profile.
  6. Complete the profile setup information so that the probe can access the resources in a VMware environment.
    Additional profile type nodes are added under the profile.  
  7. Expand the list to view the available profile type nodes.
  8. Create and save profiles for any of the profile types as needed. For more information about the profiles, see VMware Profile Types and Default Settings.
  9. (Optional) Return to any of the profiles and configure any additional metrics and alarms. Select the desired QoS metrics and alarms in the Monitor column. The available options are:
    None: 
    Choose this option if you do not want to publish data or alarms for the monitor.
    Alarm:
     Choose this option if you only want to publish alarms for the monitor.
    Alarm and QoS: 
    Choose this option if you want to publish both alarms and QoS data for the monitor.
    QoS: 
    Choose this option if you only want to publish QoS data for the monitor.
  10. Save any profile changes.
  11. View the 
    Profile Status
     information to verify that the configuration profile was successfully deployed to the target device (or devices in a group if you created a group configuration profile). Profile status information appears at the bottom of the profile configuration page.  
VMware Profile Types and Default Settings
Use the VMware profile types to create configuration profiles for a VMware environment. Some of the profile types contain default monitor and alarm settings. These default settings are provided so you can configure your probes to collect data for the predefined probe dashboards in UMP. The predefined dashboards display the data that we recommend for monitoring various devices and services in your environment. Deploy all the monitoring profiles with default settings to automatically enable the metrics required by the predefined probe dashboards.
 If you deactivate any of the default metric settings, your predefined probe dashboards might not populate correctly. The default metrics required by a dashboard are included in the article for the specific dashboard.
The following table lists the VMware profile types.
Profile Type
Notes
CA UIM version
Setup VMware (Enhanced)
9.00 and later
VMware Resource (Enhanced)
9.00 and later
VMware Cluster (Enhanced)
9.00 and later
VMware Cluster Services (Enhanced)
9.00 and later
VMware Datastore (Enhanced)
9.00 and later
VMware Datastore Cluster Storage Pod (Enhanced)
9.00 and later
VMware Datastore Disk (Enhanced)
9.00 and later
VMware Distributed Port Group (Enhanced)
9.00 and later
VMware Host (Enhanced)
9.00 and later
VMware Host CPU (Enhanced)
9.00 and later
VMware Host CPU Aggregation (Enhanced)
9.00 and later
VMware Host CPU Time Aggregation (Enhanced)
9.00 and later
VMware Host Datastore (Enhanced)
9.00 and later
VMware Host Disk (Enhanced)
9.00 and later
VMware Host Disk Aggregation (Enhanced)
9.00 and later
VMware Host Memory (Enhanced)
9.00 and later
VMware Host Network Interface (Enhanced)
9.00 and later
VMware Host Network Interface Aggregation (Enhanced)
9.00 and later
VMware Host Power (Enhanced)
9.00 and later
VMware Host System (Enhanced)
9.00 and later
VMware Host Virtual Switch (Enhanced)
9.00 and later
VMware Network (Enhanced)
9.00 and later
VMware Resource Pool (Enhanced)
9.00 and later
VMware System (Enhanced)
9.00 and later
VMware Virtual Application (Enhanced)
9.00 and later
VMware Virtual Disk (Enhanced)
9.00 and later
VMware VM (Enhanced)
9.00 and later
VMware VM CPU (Enhanced)
9.00 and later
VMware VM CPU Aggregation (Enhanced)
9.00 and later
VMware VM CPU Time Aggregation (Enhanced)
9.00 and later
VMware VM Datastore (Enhanced)
9.00 and later
VMware VM Disk (Enhanced)
9.00 and later
VMware VM Disk Aggregation (Enhanced)
9.00 and later
VMware VM Guest Disk (Enhanced)
9.00 and later
VMware VM Memory (Enhanced)
9.00 and later
VMware VM Network Interface (Enhanced)
9.00 and later
VMware VM Network Interface Aggregation (Enhanced)
9.00 and later
VMware VM Power (Enhanced)
9.00 and later
VMware VM System (Enhanced)
9.00 and later
VMware VM Template (Enhanced)
9.00 and later
Setup VMware
This profile is required to configure general settings for the probe.
8.5.1 and later
VMware Resource
This profile is required to connect to a VMware environment.
8.5.1 and later
VMware Cluster
-
8.5.1 and later
VMware Cluster Services
-
8.5.1 and later
VMware Datacenter
-
8.5.1 and later
VMware Datastore
This profile contains default metric and alarm settings.
8.5.1 and later
VMware Datastore Cluster Storage Pod
-
8.5.1 and later
VMware Datastore Disk
-
8.5.1 and later
VMware Distributed Port Group
-
8.5.1 and later
VMware Host
This profile contains default metric and alarm settings.
8.5.1 and later
VMware Host CPU
-
8.5.1 and later
VMware Host CPU Aggregation
This profile contains default metric and alarm settings.
8.5.1 and later
VMware Host CPU Time Aggregation
-
8.5.1 and later
VMware Host Datastore
-
8.5.1 and later
VMware Host Disk
This profile contains default metric and alarm settings.
8.5.1 and later
VMware Host Disk Aggregation
This profile contains default metric and alarm settings.
8.5.1 and later
VMware Host Memory
This profile contains default metric and alarm settings.
8.5.1 and later
VMware Host Network Interface
-
8.5.1 and later
VMware Host Network Interface Aggregation
This profile contains default metric and alarm settings.
8.5.1 and later
VMware Host Power
-
8.5.1 and later
VMware Host System
-
8.5.1 and later
VMware Host Virtual Switch
-
8.5.1 and later
VMware Network
-
8.5.1 and later
VMware Resource Pool
This profile contains default metric and alarm settings.
8.5.1 and later
VMware System
-
8.5.1 and later
VMware Virtual Application
-
8.5.1 and later
VMware Virtual Disk
-
8.5.1 and later
VMware Virtual Disk Aggregation
-
8.5.1 and later
VMware VM
This profile contains default metric and alarm settings.
8.5.1 and later
VMware VM CPU
-
8.5.1 and later
VMware VM CPU Aggregation
This profile contains default metric and alarm settings.
8.5.1 and later
VMware VM CPU Time Aggregation
-
8.5.1 and later
VMware VM Datastore
-
8.5.1 and later
VMware VM Disk
-
8.5.1 and later
VMware VM Disk Aggregation
This profile contains default metric and alarm settings.
8.5.1 and later
VMware VM Guest Disk
This profile contains default metric and alarm settings.
8.5.1 and later
VMware VM Memory
This profile contains default metric and alarm settings.
8.5.1 and later
VMware VM Network Interface
-
8.5.1 and later
VMware VM Network Interface Aggregation
-
8.5.1 and later
VMware VM Power
-
8.5.1 and later
VMware VM System
-
8.5.1 and later
VMware VM Template
-
8.5.1 and later
 
For more information: