|
Date
|
Description
|
State
|
Version
|
|
|
|
|
|
06.03.2017
|
What's new:
- capman_da now supports the ibmvm_rest 1.03 probe. However, to make it compatible with the existing DM and ensure successful integration, you must apply a patch following the steps described here.
- For the ibmvm_rest probe, the following metrics have been added:
- host_cpu_global_shared_processor_pool_utilization
- host_global_shared_processor_pool_size
- vm_memory_used
- vm_memory_assigned
Fixed Defect:
- IBMVM configuration files not getting generated (DE254675)
- In the updated version of the IBMVM 2.52 probe, an issue with the encoding of the server names caused capman_da to receive a null value for any server name. As a result, the capman_da probe was not able to process the data further, or to generate the configuration files. The capman_da probe has been updated to fix this issue.
- In the IBMVM 2.52 probe, some of the monitor names were updated in a way that was not compatible with the existing capman_da probe. We have made some changes in the capman_da probe to include the updated monitor names.
- VMware configuration files incomplete (DE254675)
- There was an issue with the VMware probe due to which monitor values were missing after the configuration was saved using the Infrastructure Manager (IM). As a result, some of the values were missing in the generated configuration file. A VMWare team provided a hotfix of VMWare probe v6.75, which is now compatible with the capman_da probe.
md5: be3adb91ae7cf43fc3f8b47c3bc7ccd0
sha1: e33e8d7a5e4e6f7ce6a8c3e28cf260d4773c2453
|
GA
|
2.95
|
|
|
|
|
|
03.11.2016
|
The following capman_da issues were resolved in this release:
1. capman_da creates an invalid 'C:\Program' file (DE244022)
The capman_da probe creates an invalid file named 'Program' under 'C:\' whenever the probe is deployed. The post-install.bat file has been updated in this release to fix this issue.
2. capman_da probe unable to read messages from VMware 6.72 probe (DE237626)
The capman_da probe returned an error when trying to read messages from the VMware 6.72 probe. This was being caused by the VMware probe encoding the 'name' value in the get_node_values callback, which capman_da was unable to read. The issue has been fixed in this release by enabling the capman_da probe to read the encoded value.
For Detailed Release Notes-Please refer
https://docops.ca.com/ca-capacity-management/2-9-4/en/release-notes/resolved-issues/resolved-issues-capman_da-probe
|
|
2.94
|
|
|
|
|
|
08.04.2016
|
Issue:
Incorrect parsing of QoS data
Description:
A comma in QoS data prevented proper building and parsing of the .csv file. The comma has been replaced with an underscore.
For Detailed Release Notes-Please refer
https://docops.ca.com/ca-capacity-management/2-9-3/en/release-notes/new-features-and-enhancements#NewFeaturesandEnhancements-Updatestothecapman_daProbe
|
|
2.93
|
|
|
|
|
|
21.12.2015
|
Fixed Issue:
1. Linux Systems marked z/OS: For Linux physical systems that are monitored via CDM probe, DM was not able to perform correct Operating system grouping in CCC.
2. capman_da probe fails to get configuration data from vmware and ibmvm probes: The capman_da probe is not fetching Cluster and Data Center information for the VM’s and Hosts.
3. capman_da data upload failure: When the capman_da probe is required to upload data on two DM instances, the capman_da probe fails to upload data to the second DM instance.
For Detailed Release Notes-Please refer
https://docops.ca.com/display/CCM292/New+Features+and+Enhancements
|
|
2.92
|
|
|
|
|
|
12.06.2015
|
Fixed an issue where the probe used to fail to start when the Restart option is selected in UIM Admin Console.
New features added, for that please refer following link
For Detailed Release Notes-Please refer
https://wiki.ca.com/display/CCM29/Release+Notes
|
|
2.90
|
|
|
|
|
|
24.03.2015
|
New version of 2.80 provides
Support for Storage probes
The CA UIMData Adapter (formerly Nimsoft Data Adapter) adds data collection from the following CA UIM EMC storage probes, version 1.30.
CLARiiON
VMAX, version 1.30
CLARiiON
The CLARiiON (clariion) monitoring probe collects and stores data and information from the monitored EMC CLARiiON systems.
Important: The CLARiiON probe is not supported in production environments. To use this probe, contact your CA support team for information about participating in the Beta program.
VMAX
The VMAX (vmax) monitoring probe handles all common monitoring and data collection tasks for vmax users, providing Quality of Service (QoS) data and alarms whenever it detects sub- optimal performance in the EMC VMAX system.
For more information about CA UIM probes reference
https://wiki.ca.com/display/UIMPGA/Getting+Started.
Version Support
Your system must be running CA UIM r8.0 or later to collect data using the CA UIM capman_da probe.
capman_da Probe Configuration
A new configuration key—collection_enabled—is added for the VMAX probe, metric family and metrics. This key allows you to specify whether or not to collect metrics for a probe. By default, this key is set to true, to collect metrics.
For more information about this key, reference "Setting-up the capman_da probe" in the CA Capacity Command Center Administration Guide 2.8.
|
|
2.80
|
|
|
|
|
|
11.12.2014
|
fixed a problem where the CA Nimsoft capman_da and cdm probe directories were not accessible through the CA Data Manager.
|
|
2.70
|
|
|
|
|
|
29.09.2014
|
Initial Release
|
|
2.60
|
|
|
|
|